10 ms·

I was wondering that, too. Seems like he'd be better served contributing to mod_wsgi if he's got the itch to play again. It's going to be a whole lot of work to

• saurik 13y ago
  I use mod_python, and the only reason I see to switch to mod_wsgi is "mod_wsgi is maintained": it has nowhere near the functionality that mod_python did, and as far as I can tell runs the Python code in separate processes (which will result in even more context switches and data marshaling). I currently am using Apache with mpm_event and mod_python using Apache's SSI to do sub-request compositing between different systems all within the same embedded Python VMs. Honestly, I've always been under the impression that mod_wagi is the project that needed to catch up... WSGI as an API mostly seems to be about attempting to rebuild some of the stuff Apache has had in place, in an implementation-agnostic fashion, for well over a decade (like the middleware stuff, which they are still having troubles integrating with "write callables", something that seems to be a non-issue with Apache filters).