Future of mod_wsgi

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

Hi all.

I’m finally allocating some time to update mod_wsgi to recent Nginx
versions. The target is the development branch.

While doing so I plan to remove some features that I’m not currently
using, or that have problems.

  1. First of all, I plan to remove support for Python sub-interpreters.
    CPython support for multiple sub-interpreters has some problems, and the
    current code in mod_wsgi has problems, too.

Is there here someone that is using subinterpreters?
The simple fix is to use separate Nginx instances.

  1. I plan to remove the experimental extension for asynchronous
    applications.
    The current code has some problems, and, above all, the API is not very
    convenient to use.

I know of at least one software that is using this extension: eventlet
by Donovan Preston, but I don’t know if he is still using it.

My plan is to use greenlet in mod_wsgi, but this requires better
planning.

That’s all.
I have some other fixes to the code to apply, and some new features.

Thanks to the people who sent me patches to support recent Nginx
versions.

The current version available at
http://hg.mperillo.ath.cx/nginx/mod_wsgi
will be frozen.
New work will happen in a separate branch, probably
http://hg.mperillo.ath.cx/nginx/mod_wsgi-dev

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

iEYEARECAAYFAktYgI8ACgkQscQJ24LbaUQwOwCeJPpb2fJZp+ybbQobQKyd+9eb
G94AnikPPE4UZEKTB4+3APRmKGA74JVR
=6dv3
-----END PGP SIGNATURE-----

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs