Hi Aymeric, First, thanks for all your triage work on track, it's very much appreciated. This is a large proposal, but I think it covers the issue pretty completely.
I agree with your approach of using UTC internally and converting on output. My main concern with your proposal is that it may require two different code paths for a lot of code. I have no objection to the dependency on pytz, but I don't want this to result in pytz-aware code that diverges significantly from the non-pytz default path. I would like this new code to eventually become the default setting, but acknowledge that there doesn't seem to be a good way to do that and maintain our current backwards compatibility (and external dependency) policy. This isn't my area of expertise, so I'm not a good mentor candidate, but I'd be excited to help you with this project where I can. I'm wholeheartedly +1 on this. Best, -Paul -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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.
