-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi.

As I wrote in a previous message, in an effort to improve the WSGI
module, I have moved Python support to a separate module:
http://hg.mperillo.ath.cx/nginx/ngx_python_module

When the module is included in Nginx, the Python interpreter will be
initialized unconditionally.

The new `ngx_http_wsgi module` now use the "module init" callback
function, to do its own Python specific initialization (in old version
this was done in the HTTP post configuration callback), since this is
the only place where we know the `ngx_python_module` has been fully
initialized.


A different solution is to define a custom "python" directive in the
`ngx_python_module`, and initialize the Python interpreter here only if
directive is specified in configuration file.

The disadvantage is that:

* I can no more use multiple directives for Python configuration
(not a big deal)
* The `ngx_http_wsgi_module must` can no more assume the Python
interpreter is initialized (again, not a big deal)


What is the best solution?


Thanks Manlio
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkutIfoACgkQscQJ24LbaUQCoACeOFTPzpKSRQFZG+gwLyhXCWus
It8AoJdZeYEY2s89FWvhKt8gl2+lbCo1
=PYew
-----END PGP SIGNATURE-----

_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://nginx.org/mailman/listinfo/nginx-devel