ambitioninc/django-db-mutex

DateTimeField received a naive datetime

Closed this issue · 0 comments

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.```