Sune Kirkeby wrote:
On 10/11/05, hugo <[EMAIL PROTECTED]> wrote:
Actually I think a better way might just be to change django so that it
doesn't pull the DJANGO_SETTINGS_MODULE from the environment, but use a
django.settings_module from the WSGI environment - that can be handled
distinctly for
On 10/11/05, hugo <[EMAIL PROTECTED]> wrote:
> Actually I think a better way might just be to change django so that it
> doesn't pull the DJANGO_SETTINGS_MODULE from the environment, but use a
> django.settings_module from the WSGI environment - that can be handled
> distinctly for every applicati
>> Because of the magic Django does with settings, there can only ever
>> be one instance per Python process... Unless I'm missing something.
>That would be somewhat of a problem, because you couldn't install two
>Django apps in the same process without them being aware of each other,
>so in effe
Sune Kirkeby wrote:
On 10/11/05, Ian Bicking <[EMAIL PROTECTED]> wrote:
* easily installable. easy_install being a good way to do that. This
means each app goes in its own package with a setup.py file. This isn't
absolutely necessary, but packaging each app is generally good for
deployment.
On 10/11/05, Ian Bicking <[EMAIL PROTECTED]> wrote:
> * easily installable. easy_install being a good way to do that. This
> means each app goes in its own package with a setup.py file. This isn't
> absolutely necessary, but packaging each app is generally good for
> deployment.
Definetly. And
Hello Djangoists.
Ben Bangert mentioned that he was having some conversations with Adrian
about Paste and "Paste Enabling" Django. I haven't written up my Paste
Enabling Propoganda yet, but I'll just say that I *will* write up
propoganda ;)
Anyway, I thought I'd descr
