Simon Willison wrote:
On 8 Nov 2005, at 08:47, Ian Bicking wrote:
However, I don't think you'd lose anything by routing everything through
WSGI.
IIRC, the reason Django doesn't use WSGI in the first place is that
when we first created it two years ago WSGI was still bei
t, and only
usable in threaded or single-process/non-concurrent environments.
However, I don't think you'd lose anything by routing everything through
WSGI.
--
Ian Bicking | [EMAIL PROTECTED] | http://blog.ianbicking.org
eadlocal objects to
achieve this -- for instance, SQLObject uses a threadlocal connection
descriptor, to override a class variable globally based on
configuration, but without being particularly attached to any
configuration mechanism.
--
Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org
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
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 describe what I think it might m
