DateField with auto_now=True is not coming in as Python's datetime.date object in Python 2.4 / 2.5

[mischko]

Oracle backend with cx_Oracle 5.0.4
Python 2.4.3
Oracle 11

class scott_test1(models.Model):
    graphic_id = models.IntegerField()
    graphic_desc = models.CharField(max_length=30)
    curves = models.TextField()
    graphic_type = models.CharField(max_length=4)
    df = models.DateField(null=True, auto_now = True) # datetime.date
    dtf = models.DateTimeField(null=True, auto_now = True) # datetime.datetime
    tf = models.TimeField(null=True, auto_now =True) # datetime.time

foo=scott_test1(graphic_id=2,graphic_desc="here is some text", curves= ", ".join([str(x * 3.1514) for x in xrange(1000)]), graphic_type="none")

foo.save()

According to the docs at ​http://docs.djangoproject.com/en/dev/ref/models/fields/#datefield, foo.df should be a datetime.date object, not datetime.datetime:

In [7]: foo.df
Out[7]: datetime.datetime(2010, 11, 5, 10, 13, 3, 744903)

In [8]: foo.dtf
Out[8]: datetime.datetime(2010, 11, 5, 10, 13, 3, 745076)

In [9]: foo.tf
Out[9]: datetime.time(10, 13, 3, 745130)

[mischko]

Tested on 1.1.0 and 1.2.3.

[Alex Gaynor]

Added formatting.

[Erin Kelly]

I think this may actually be an auto_now bug. The test_datefield_auto_now_add test in the datatypes suite of the 1.2.X branch is failing for both oracle and sqlite3 backends when running Python 2.5, but not with Python 2.7. The test_date_type test in the same suite that tests for this bug in the more general case is not failing at all.

[Erin Kelly]

Dup of #10970