Skip to content

DateTimeField received a naive datetime #22

@jwkvam

Description

@jwkvam

Is there a more universal solution that uses timezone.now instead of datetime.utcnow? Right now I'm getting a bunch of runtimewarnings because the datetime isn't timezone aware, but I realize that timezone.now isn't necessarily UTC. If someone has USE_TZ = False, I'm sure there would be problems during savings time changes.

RuntimeWarning: DateTimeField DBMutex.creation_time received a naive datetime (2015-03-24 15:50:28.141220) while time zone support is active.```

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions