﻿id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
35771	Bugs: models.DateField value has not been assigned correct date value when auto_now_add  is set	Racing Car		"class Vote(models.Model):
    class Points(models.IntegerChoices):
        Top = 3
        Second = 2
        Third = 1

    points: models.IntegerField = models.IntegerField(choices=Points.choices, default=Points.Top)
    date: models.DateField = models.DateField(auto_now_add=True)


from django.utils import timezone

timezone.now() # datetime.datetime(2024, 9, 18, 3, 7, 3, 608467, tzinfo=datetime.timezone.utc)
timezone.now().date()# datetime.date(2024, 9, 18)

import datetime
datetime.datetime.now() #datetime.datetime(2024, 9, 17, 23, 7, 14, 337114) My local pc timezone is UTC-4
datetime.date.today() #datetime.date(2024, 9, 17)

v = Vote(points=Vote.Points.Top)

v.save()
v.date # Expected value is datetime.date(2024, 9, 18) since I enabled USE_TZ=True in settings.py
       # current value is  datetime.date(2024, 9, 17)


""""""
I figured it out myself and in `pre_save` function of models.DateField class, we should use timezone.now().date() instead of datetime.date.today()
"""""""	Bug	new	Database layer (models, ORM)	5.0	Normal		auto_now		Unreviewed	1	0	0	0	0	0
