On Apr 21, 12:40 am, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> -1 here too, for exactly the same reason. Add to that the inevitable
> Murphyism that the one time you specify N=10 will be the time that the
> 11th oldest query will be the one causing the problem.
I agree, though my suggest
On Mon, 2008-04-21 at 01:50 -0700, ludvig.ericson wrote:
> On Apr 21, 12:40 am, "Russell Keith-Magee" <[EMAIL PROTECTED]>
> wrote:
> > -1 here too, for exactly the same reason. Add to that the inevitable
> > Murphyism that the one time you specify N=10 will be the time that the
> > 11th oldest qu
On Apr 20, 11:23 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> -1 for the reasons that James Bennett stated above. That it crashes
> and burns in production is actually a feature in this case.
If we want to crash and burn if you use DEBUG=True in production we
should do that explicitly, n
> If we want to crash and burn if you use DEBUG=True in
> production we should do that explicitly, not as a side effect
> of another feature. I think there is enough real-world
> evidence that people are being tripped up by this for
> legitimate reasons (running import scripts in development
> mod
On Mon, 2008-04-21 at 03:46 -0700, Simon Willison wrote:
> On Apr 20, 11:23 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> > -1 for the reasons that James Bennett stated above. That it crashes
> > and burns in production is actually a feature in this case.
>
> If we want to crash and burn
Simon Willison wrote:
> Of course, this behaviour is documented... but I think it's reasonable
> to expect that many people will miss that part of the docs.
Where? I didn't know about this and feel like I've read most of the
Django documentation and the Django book. I'm purposefully looking
for
On Mon, Apr 21, 2008 at 1:26 PM, Rob Hudson <[EMAIL PROTECTED]> wrote:
>
> Simon Willison wrote:
> > Of course, this behaviour is documented... but I think it's reasonable
> > to expect that many people will miss that part of the docs.
>
> Where? I didn't know about this and feel like I've read m
or more specifically:
http://www.djangoproject.com/documentation/faq/#why-is-django-leaking-memory
On Apr 21, 7:14 pm, "John-Scott Atlakson"
<[EMAIL PROTECTED]> wrote:
> On Mon, Apr 21, 2008 at 1:26 PM, Rob Hudson <[EMAIL PROTECTED]> wrote:
>
> > Simon Willison wrote:
> > > Of course, this beha
+1 because this is annoying behavior.
I ALWAYS run scripts with DEBUG on, that doesn't mean they're on a
production server, because these things are cronned. And I'm always
doing stuff that involves the shell, etc, (imports) where debug is on.
The first thing I've had to do in any shell session,
I'm -1 against any change to this. In most use cases, it's not as
simple as resorting your python results, or refiltering them, as you
have sliced the queryset and the query needs to be executed again to
retrieve proper results.
On Apr 17, 11:18 am, Travis Parker <[EMAIL PROTECTED]> wrote:
> > I'
On Tue, Apr 22, 2008 at 1:26 AM, Rob Hudson <[EMAIL PROTECTED]> wrote:
>
> Simon Willison wrote:
> > Of course, this behaviour is documented... but I think it's reasonable
> > to expect that many people will miss that part of the docs.
>
> Where? I didn't know about this and feel like I've re
Hello Django Developers,
Just checked my mail and saw that I have been selected for Google
Summer of Code, 2008. This is the second time I am participating in
the contest and for the second time I have got a chance to contribute
to the Djangoproject :) My mentor for this project is Jannis Leidel.
12 matches
Mail list logo
