I second the statement about multi-threading headaches if you use
globals in this way.
In Aquarium, since I have to support different threading API's (no
threads, Python threads, coroutines), I put everything in a Context
object, and then pass that Context object to everything's constructor.
- I second the statement about multi-threading headaches if you use
- globals in this way.
-
- In Aquarium, since I have to support different threading API's (no
- threads, Python threads, coroutines), I put everything in a Context
- object, and then pass that Context object to everything's
Hi,
Sorry if this is a trivial question, but does it sounds reasonable to
use WSGI for pluggable standard applications, instead of usual
Python imports? For example, standard news module, like:
app = NewsApp(path='/site/news/')
The content of news app would be inserted into site template,
Ksenia Marasanova wrote:
Sorry if this is a trivial question, but does it sounds reasonable to
use WSGI for pluggable standard applications, instead of usual
Python imports? For example, standard news module, like:
app = NewsApp(path='/site/news/')
The content of news app would be
Ksenia Marasanova wrote:
2005/9/10, Ian Bicking [EMAIL PROTECTED]:
Ksenia Marasanova wrote:
Sorry if this is a trivial question, but does it sounds reasonable to
use WSGI for pluggable standard applications, instead of usual
Python imports? For example, standard news module, like:
app =
