On Fri, 2007-06-15 at 03:17 -0700, Tipan wrote:
>
> On Jun 14, 10:50 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
> wrote:
> > See django/db/models/loading.py, in the register_models() function.
> >
> > I'm not 100% certain that will be the right fix, but from reading the
> > ticket and the model d
On Jun 14, 10:50 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> See django/db/models/loading.py, in the register_models() function.
>
> I'm not 100% certain that will be the right fix, but from reading the
> ticket and the model dispatching code, it looked like the right idea.
> Not a change
On Thu, 2007-06-14 at 08:51 -0700, Tipan wrote:
>
> > It's ticket #3951, most likely. As you'll see in the comments there,
> > there is an approach for fixing it. However, it's likely to wait until
> > after some serious surgery is done on the signals module and that is
> > ongoing work at the mo
> It's ticket #3951, most likely. As you'll see in the comments there,
> there is an approach for fixing it. However, it's likely to wait until
> after some serious surgery is done on the signals module and that is
> ongoing work at the moment. So for now, you'll just have to work around
> it a b
On Thu, 2007-06-14 at 06:33 -0700, Tipan wrote:
> I've recently made some modifications to my views/urls and settings
> files to improve portability of the application. This took out some
> explicit references to the application files.
>
> For example, the line:
>
> from test.promotions.models i
I've recently made some modifications to my views/urls and settings
files to improve portability of the application. This took out some
explicit references to the application files.
For example, the line:
from test.promotions.models import * was reduced to:
from promotions.models import *
Now w
6 matches
Mail list logo
