auto_now_add for DateField evaluetes to datetime.datetime instance

[Ivan Gromov]

I've set auto_now_add to DateField, but it evaluates to datetime.datetime instance rather than datetime.date.
Here some example:

code in models.py

class Order(models.Model):
    created = models.DateField(auto_now_add=True)

and manage.py shell output:

In [1]: from app.models import Order
In [3]: o = Order()
In [4]: o.save()
In [5]: o.created
Out[5]: datetime.datetime(2009, 5, 1, 2, 53, 32, 280919)

I'm using django-1.0.2-final

[Ivan Gromov]

Checked out to revision #10650, bug still there

[Alex Gaynor]

This patch doesn't work as DateTimeField relies on inhering this method.

[Tyson Clugg]

Surely datetime.date.today() is more concise than datetime.datetime.now().date() - is there a good reason why the latter was selected?

[Ivan Gromov]

Nope, there wasn't reason to use datetime.now().date() instead datetime.date.today(). I've updated patch, thank you.

[Cyberj]

Patch for rev 12847

[Cyberj]

This bug remains an issue for applications like ​http://code.google.com/p/django-reversion/ because it takes a serialized datetime object for datefield with auto_now_add.

I've updated patch for r12846 and tests are OK

[Ramiro Morales]

See #14037 for a manifestation of this bug when using Django's own serialization machinery)

[Ramiro Morales]

Patch updated to r14002 (test fixed to actually fail before the fix and updated to unittest)

[Jannis Leidel]

(In [14029]) Fixed #10970 -- Initialize DateFields with datetime.date objects, not datetime.datetime. Thanks, summerisgone, Cyberj and Ramiro Morales.

[Jacob]

Milestone 1.3 deleted