Hi Preston,
On 30 oct. 2011, at 17:07, ptone wrote:
> I do think a better label than "value" could be used for the
> thread.local for the current timezone, as this is really a thread
> global - something less ambiguous and conflict prone would be better
> IMO.
I used this name for consistency wit
I just did an initial scan through:
https://bitbucket.org/aaugustin/django/compare/..django/django
and this looks like a great piece of work.
I do think a better label than "value" could be used for the
thread.local for the current timezone, as this is really a thread
global - something less amb
Hello,
This check-in is highly topical, as clocks rolled back one hour in most parts
of Europe this morning :)
I've implemented conversions in forms and widgets, and in the admin too. I've
made template filters convert their input to the current time zone when
appropriate. I've added a context