On Wed, Jun 16, 2010 at 1:04 AM, Giuseppe Ciotta wrote:
> On Wed, Jun 16, 2010 at 12:46 AM, Jeremy Dunck wrote:
>> On Sun, Jun 13, 2010 at 7:18 AM, lenz wrote:
>>> Could you share your code with us?
>>> Thanks you!
>>
>> This might help:
>> http://g
On Wed, Jun 16, 2010 at 12:46 AM, Jeremy Dunck wrote:
> On Sun, Jun 13, 2010 at 7:18 AM, lenz wrote:
>> Could you share your code with us?
>> Thanks you!
>
> This might help:
> http://gist.github.com/425403
I have some similar code here: http://gist.github.com/439868
It might be better because
On Tue, Apr 20, 2010 at 4:39 PM, Jacob Kaplan-Moss wrote:
> On Mon, Apr 19, 2010 at 2:32 PM, Giuseppe Ciotta wrote:
>> Having an additional field{s} in the ticket, only accessible to core
>> developers, where they would put the "official" (as in: approved by a
>> c
On Mon, Apr 19, 2010 at 4:19 PM, Jacob Kaplan-Moss wrote:
> So: here's your chance. You have suggestions about Django's
> development process? Make them. I'm listening.
My understanding is that write access to triage stage and tickets
details is granted to everybody (even to anonymous users), an
On Wed, Mar 17, 2010 at 8:54 AM, Russell Keith-Magee
wrote:
>
> In the interim, there are two other ways you could limit your exposure
> to this problem (other than the obvious "write your own
> login_required" check):
>
> * Use a permissions check in addition to the login_required check --
> as
On Wed, Jan 27, 2010 at 1:19 AM, Russell Keith-Magee
wrote:
> On Wed, Jan 27, 2010 at 12:30 AM, Giuseppe Ciotta wrote:
>> http://code.djangoproject.com/ticket/12399
>>
>> It's a nasty bug which leads to a 100% cache misses situation on
>> memcached when using
http://code.djangoproject.com/ticket/12399
It's a nasty bug which leads to a 100% cache misses situation on
memcached when using long keys timeouts.
Do you think we can have this included in 1.2? Should i mark it with
Version:1.2 or something? The patch itself is trivial.
--
You received this m
