On Tue, Jul 12, 2016 at 3:25 AM Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> def _populate(self):
> with self._lock:
> if self._populated:
> return
> # … populate …
> self._populated = True
>
Depending on how frequently the code is called
On Mon, 2015-03-23 at 19:16 -0600, Carl Meyer wrote:
> And it still seems to me that it's bad for Django's default config to
> set `level: ERROR` and `propagate: False` on the django.request and
> django.security loggers, as that prevents those logs from propagating to
> higher-level handlers someo
nstalled that
> it'll be used. Testing's another story: this is likely to be something
> that's really tricky to test. If you come to the conclusion that this
> simply can't be tested than that might be OK, but you should
> explicitly explain your reasoning behind test
I've noticed that the auto-reload support isn't kind to my laptop battery,
so I was happy to find that somebody's already done the work to get inotify
support into the autoreloader. The patches are in
https://code.djangoproject.com/ticket/9722
This ticket seems to have been around for a while wit
On Fri, Feb 24, 2012 at 9:45 AM, Tom Evans wrote:
> In your folder are:
> {^ for item in folder ^}
> {{ item }},
> {^ endfor ^}
>
> This would render as "In your folder are: item1,item2,item3,"
>
> Changing some of the carets:
>
> In your folder are:
> {% for item in folder ^}
> {{ item }},
> {^ e
On Thursday, April 14, 2011 12:30:56 PM UTC-4, Jannis Leidel wrote:
>
> On 14.04.2011, at 17:27, Jacob Kaplan-Moss wrote:
>
> > I think I agree with Ned here: I can't see the downside to fixing it
> > on the release branch. "It violates our policy" doesn't count IMO:
> > it's *our* policy, and we g
