CODEWITHSUNDEEP
pythondjangodatetimedjango-timezone
David542
David542

Reputation: 110257

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

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?

Upvotes: 33

Views: 20138

Answers (3)

dgel
dgel

Reputation: 16806

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

Upvotes: 51

culix
culix

Reputation: 10616

If you want to use UTC, and you're using Python 3.2 or higher, this answer says you can do:

import datetime
datetime.datetime.now(datetime.timezone.utc)

This will give you a timezone-aware UTC datetime.

Upvotes: 2

eEmanuel Oviedo
eEmanuel Oviedo

Reputation: 69

You can write in shell, for example:

timezone.datetime.now() < timezone.now()

And the error message is:

TypeError: can't compare offset-naive and offset-aware datetimes

They are different objects, only timezone.now() have UTC support

Upvotes: 4

Related Questions