On Sat, Aug 15, 2009 at 4:48 PM, Graham
Dumpleton wrote:
> On Aug 15, 6:42 pm, Yuri Baburov wrote:
>> On Sat, Aug 15, 2009 at 12:24 PM, Graham
>> Dumpleton wrote:
>> > On Aug 15, 1:15 pm, Yuri Baburov wrote:
>> >> Hi all,
>>
>> >> I'm trying to figure out correct overall and settings path usage
On Aug 15, 6:42 pm, Yuri Baburov wrote:
> On Sat, Aug 15, 2009 at 12:24 PM, Graham
>
>
>
>
>
> Dumpleton wrote:
> > On Aug 15, 1:15 pm, Yuri Baburov wrote:
> >> Hi all,
>
> >> I'm trying to figure out correct overall and settings path usage
> >> strategy for my Django applications.
> >> What I
On Sat, Aug 15, 2009 at 12:24 PM, Graham
Dumpleton wrote:
> On Aug 15, 1:15 pm, Yuri Baburov wrote:
>> Hi all,
>>
>> I'm trying to figure out correct overall and settings path usage
>> strategy for my Django applications.
>> What I am experiencing now is that settings.py is imported 4 times on
>>
On Aug 15, 1:15 pm, Yuri Baburov wrote:
> Hi all,
>
> I'm trying to figure out correct overall and settings path usage
> strategy for my Django applications.
> What I am experiencing now is that settings.py is imported 4 times on
> "python manage.py runserver" command,
> twice as "settings", an
Hi all,
I'm trying to figure out correct overall and settings path usage
strategy for my Django applications.
What I am experiencing now is that settings.py is imported 4 times on
"python manage.py runserver" command,
twice as "settings", and twice as "myapp.settings", given that my
project is na
