DateField uses date() which might not be correct in timezone aware situations

[Mitar]

DateField uses date() to convert to date, which might not be correct in timezone aware situations. At least ​according to documentation, a more precise handling should be made.

[Aymeric Augustin]

This is probably on purpose and not changeable in a backwards compatible way. See ​http://groups.google.com/group/django-developers/browse_thread/thread/cf0423bbb85b1bbf

If you tell me which function you're referring to, I'll take a look.

[Mitar]

I think about this lines:

• ​timezone information is lost

Otherwise, such ​function used everywhere instead of .date() call would not really break backwards compatibility, I believe.

[Aymeric Augustin]

My personal opinion is that DateField shouldn't accept datetime objects. However it did long before I started using Django :)

My advice is ​not to mix dates and datetimes.

Could you clarify why you need to feed a datetime into a DateField?

[Mitar]

I think you get this when you specify default value with timezone.now() call?