DateField uses unlocalized function when auto_now is True

[M1ha Shvn]

Hi.

django.db.models.fields.DateField(auto_now=True) sets date as datetime.date.today() (see ​here). This date is not localized with django and can be different from django.utils.timezone.now() used in DateTimeField, if django and local timzeones differ.

Suggestion:
Change datetime.date.today() to django.utils.timezone.now().date()

[Mariusz Felisiak]

This is a ​documented behavior:

"The auto_now and auto_now_add options will always use the date in the default timezone at the moment of creation or update. If you need something different, you may want to consider using your own callable default or overriding save() instead of using auto_now or auto_now_add; or using a DateTimeField instead of a DateField and deciding how to handle the conversion from datetime to date at display time."

[Mariusz Felisiak]

Also, unlike DateTimeField, DateField isn't timezone-aware. See a ​pull request thread where the change you suggested was proposed.