On Wed, Nov 25, 2009 at 12:10 AM, jedie <google.gro...@jensdiemer.de> wrote: > DateTimeField "auto_now" and "auto_now_add" used datetime.now(). But > why this? IMHO it's better to use datetime.utcnow(), isn't it?
Why would it be? A datetime field isn't necessarily stored in UTC. It uses datetime.now() because that will return the same time as settings.TIME_ZONE. On top of that, making this change would be a *huge* backwards incompatibility, as any existing uses of auto_now etc would break. Time zone handling is definitely something that Django could handle better, but simply switching to UTC for certain functions isn't the solution. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
