Re: Some tickets that need love before 1.3 feature freeze.

2010-12-13 Thread Russell Keith-Magee
On Tue, Dec 14, 2010 at 11:34 AM, Tai Lee wrote: > There are a few tickets that I believe are or should be RFC that I > would like to see committed before the 1.3 feature freeze kicks in, > which I just heard was very soon now. If anyone has time, could they > please review the following and bump

Some tickets that need love before 1.3 feature freeze.

2010-12-13 Thread Tai Lee
There are a few tickets that I believe are or should be RFC that I would like to see committed before the 1.3 feature freeze kicks in, which I just heard was very soon now. If anyone has time, could they please review the following and bump to RFC or provide additional feedback if they're not yet r

Re: Models.py not loaded at server startup ?????

2010-12-13 Thread Pakal
I've never used these handlers yet, but from what I've browsed from django's code, it seems low level handlers have nothing to import models, so I guess the result would be the same. I guess I'll manually import all my INSTALLED_APPS models from within my settings.py or urls.py, for the moment. Bu

Re: Models.py not loaded at server startup ?????

2010-12-13 Thread Harro
Is this mod_python specific or does it also happen with mod_wsgi or gunicorn? On Dec 13, 3:47 pm, Carl Meyer wrote: > Hi, > > On Dec 12, 4:40 pm, Pakal wrote: > > > Why, then, isn't it specified that all models.py files should be > > loaded by each starting worker ? That would solve the whole pr

Re: Models.py not loaded at server startup ?????

2010-12-13 Thread Carl Meyer
Hi, On Dec 12, 4:40 pm, Pakal wrote: > Why, then, isn't it specified that all models.py files should be > loaded by each starting worker ? That would solve the whole problem > and hidden errors around startup code like signals and startup checks. This is a real issue for me as well; not necessar

Re: Need help w/ sql.where.WhereNode tree

2010-12-13 Thread Jonas H.
On 12/03/2010 03:06 PM, Jonas H. wrote: On 12/03/2010 10:04 AM, Waldemar Kornewald wrote: You probably don't want to use those aliases. Instead, you should use a separate alias namespace for embedded object filters. Otherwise you'll have to deal with the complex JOIN code in the backend unnecess

Re: Need some feedback for a fix for #14249

2010-12-13 Thread Harro
Shameless bump to get some attention for 1.3 :) Would be really nice to have this for 1.3 as it puts us one step closer to making the User model replacable ! I think it might be a good idea to move all the checks to the authentication backend so it works consistently for User.has_perm, User.has_p