Timezone.now() vs datetime.datetime.now()

python django datetime django-timezone
David542 picture David542 · Nov 15, 2014 · Viewed 10.5k times · Source

When should I be using django's timezone.now() and when should I be using python's datetime.datetime.now().

For example, in the following INSERT which would make more sense?

- Product.objects.create(title='Soap', date_added=datetime.datetime.now())
- Product.objects.create(title='Soap', date_added=timezone.now())

Is there a rule of thumb on when to use each?

Answer

dgel picture dgel · Nov 15, 2014

Just always use timezone.now(). Django now has timezone support which requires timezone 'aware' datetime objects. datetime.now() will return a timezone naive object, whereas timezone.now() will return a timezone aware object.

Read more about Django timezones

Related questions

DateTimeField received a naive datetime

I have model with DateTimeField column. I'm try to insert row with database current_time value directly into table by sql query. My sql query for MySQL database like: INSERT INTO MyTable (..., my_datetime, ...) VALUES (..., current_time, ...) And get: RuntimeWarning: …

Read More
Django auto_now and auto_now_add

For Django 1.1. I have this in my models.py: class User(models.Model): created = models.DateTimeField(auto_now_add=True) modified = models.DateTimeField(auto_now=True) When updating a row I get: [Sun Nov 15 02:18:12 2009] [error] /home/ptarjan/projects/twitter-meme/django/…

Read More
How can I filter a date of a DateTimeField in Django?

I am trying to filter a DateTimeField comparing with a date. I mean: MyObject.objects.filter(datetime_attr=datetime.date(2009,8,22)) I get an empty queryset list as an answer because (I think) I am not considering time, but I want "…

Read More