Is using version 2 of the pickle protocol in {DB,FileBased}Cache

Hello there, I was experiencing some problems with Django's caching system on 1.2.X (1.2.5, to be more specific) when using either the database or the file-based backends. Both use pickle and call pickle.dumps(..., pickle.HIGHEST_PROTOCOL) when serializing the data after being called by

Re: Tying log messages from a single request together?

Thanks for the answers. I ended up writing a simple middleware that sticks a request id in thread local (so not acceptable to django). And then there's a logging.Filter that attaches the request_id to log records. This works nicely with the settings.LOGGING configuration option. Russell, I

Re: Fixing makemessages for Javascript

On Fri, Apr 15, 2011 at 9:25 PM, Ned Batchelder wrote: > On 4/14/2011 11:40 PM, Russell Keith-Magee wrote: >> >> No offense intended to Ned, but I simply don't see sufficient evidence >> to be confident that this is the case. 216 lines of tests doesn't >> strike me as

Re: Accidental logging disabling

On 04/15/2011 04:20 AM, akaariai wrote: > I have been using setup_environ in my projects, and the lazy > initialization in can cause some weird problems, for example if you do > manual timing using: > start = datetime.now() > access settings > print 'Used %s' % (datetime.now() - start) > > You

Re: Filter via related_name in inherited model not working .. Bug?

Hi Alex, On 04/15/2011 07:51 AM, robim42 wrote: > --- models.py code --- snip --- > from django.db import models > > class Base(models.Model): > name = models.CharField(max_length=20) > > def __unicode__(self): > return self.name > > class Seller(Base): > childa =

Re: Fixing makemessages for Javascript

On 4/14/2011 11:40 PM, Russell Keith-Magee wrote: On Fri, Apr 15, 2011 at 12:30 AM, 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"

Filter via related_name in inherited model not working .. Bug?

Hi guys, I used model inheritance quite a while and came across a problem which I can not resolve and actually think is might be a bug in django itself. Because of the size of the project I'm working on it would be a waste of space using the original models here ... so I simplified the classes to

Re: A few questions regarding writing a new localflavor

On Fri, Apr 15, 2011 at 6:51 PM, Vasil Vangelovski wrote: > Hi > > I decided to collect some validation rules and regional data we've been > using for various projects under a localflavor for Macedonian. I hope > someone can help me with some dilemmas I currently have: > >

Re: RFC #2705 (Support for SELECT FOR UPDATE)

Thanks for following up on those. I reviewed the Oracle tests shortly before the 1.3 release and fixed all the real failures in the backend. The remaining failures as of then were due to the backend not interacting well with the test suite as documented in ticket #15573, plus a DB cache issue

A few questions regarding writing a new localflavor

Hi I decided to collect some validation rules and regional data we've been using for various projects under a localflavor for Macedonian. I hope someone can help me with some dilemmas I currently have: 1. All localflavors except for the US localflavor include only form fields and widgets (not

Re: Accidental logging disabling

On Apr 15, 7:34 am, Ivan Sagalaev wrote: >      import logging > >      import settings >      from django.core.management import setup_environ >      setup_environ(settings) > >      from django.test.client import RequestFactory > >      factory = RequestFactory() >