On Oct 29, 4:50 pm, Russell Keith-Magee
wrote:
> Django's dependence on DJANGO_SETTINGS_MODULE is an oft-lamented
> problem. Suggestions on how to address this constraint are most
> welcome.
With an explicit main (i.e. a single explicit entry point to code).
Would also
Thanks. This link is exactly what i need.
On Oct 29, 5:07 pm, Waylan Limberg wrote:
> On Thu, Oct 29, 2009 at 10:37 AM, Johan wrote:
>
> > I am
> > wanting to use the template engine outside the context of a django
> > project so I would not have a
Thanks for the quick reply. I discovered exactly what you said about 2
seconds after pressing the submit on my query.
On Oct 29, 4:50 pm, Russell Keith-Magee
wrote:
> On Thu, Oct 29, 2009 at 10:37 PM, Johan wrote:
>
> > Hi. In
On Thu, Oct 29, 2009 at 11:07 AM, Waylan Limberg wrote:
> On Thu, Oct 29, 2009 at 10:37 AM, Johan wrote:
>>
>> I am
>> wanting to use the template engine outside the context of a django
>> project so I would not have a settings file anywhere on my path.
>
On Thu, Oct 29, 2009 at 10:37 AM, Johan wrote:
>
> I am
> wanting to use the template engine outside the context of a django
> project so I would not have a settings file anywhere on my path.
This is documented here:
On Thu, Oct 29, 2009 at 10:37 PM, Johan wrote:
>
> Hi. In django\template\__init__.py on line 54 there is a line of
> code : from django.conf import settings. Firstly there is no
> settings.py file in django\conf, ther is however a file called
> global_settings.py. In my
Hi. In django\template\__init__.py on line 54 there is a line of
code : from django.conf import settings. Firstly there is no
settings.py file in django\conf, ther is however a file called
global_settings.py. In my context the is issue is fxed by changing the
line to from django.conf import