Ben Bangert wrote:

It'd be hot if you could load up Pylons and then fork for each app, sharing a bunch of the libraries.

You can't. But such a thing is not impossible. Mmm... a whole entry point:

[app:otherprocapp] use = egg:DeploySubprocess app = config:%(here)s/myapp.ini # maybe also: add_libraries = /path/to/some/virtualenv-or-workingenv/

It'd fork, use that add_libraries to do a site.addsitedir(), and maybe start up with flup's scgi or fcgi server, with s/fcgi_app on the unforked site, forwarding any requests over, and doing a little process management (just passing over signals, so that you can kill both as a unit by killing the parent).

I'm guessing 200 lines of code. Who wants to write it?

Note you won't notice the memory savings unless you look closely; it's hard to see shared memory. Surprisingly hard. But much of the memory will be shared between the master process and the forked subprocess.