On Sun, Oct 30, 2011 at 4:19 PM, Jeremy Dunck wrote:
> On Sun, Oct 30, 2011 at 8:48 AM, Jim Dalton wrote:
> ...
>> Anyhow, I honestly agree with you and Aymeric that a simple cache.clear() is
>> fine, but I thought the CLEAR_BETWEEN_TESTS flag was a good
On Sun, Oct 30, 2011 at 8:48 AM, Jim Dalton wrote:
...
> Anyhow, I honestly agree with you and Aymeric that a simple cache.clear() is
> fine, but I thought the CLEAR_BETWEEN_TESTS flag was a good way to answer any
> objections that we should be cautious about clearing the
Hello guys,
in the past few months I have been developing a simple web site using
Django. I found Django amazing and mature framework for my needs. I am
now about to publish it in public hosting.
To my dismay the erro info I have included in Http404 calls is wasted
by Django and cannot make it's
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
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
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
> If I personally were given the choice between cache.clear() and nothing at
> all, i'd take cache.clear() and be careful with it. But I'm not sure if the
> rest of the community is willing to accept such a solution. Hence the
> CLEAR_BETWEEN_TESTS flag as a compromise.
But the flag doesn't