Thanks Jesse. As per comments against the second article, I am contemplating changes to mod_wsgi to trigger garbage collection before destroying sub interpreters as it seems to be that it is a mistake that Python internals do not itself do this. The issue I have created so I don't forget is:
https://github.com/GrahamDumpleton/mod_wsgi/issues/43 On a slight backlog due to recently holidays and exploding discussion about WSGI on the WEB-SIG which am far from catching up on, so not sure when I will get to it. Graham On 14/10/2014, at 5:43 AM, A. Jesse Jiryu Davis <[email protected]> wrote: > Friends, I've written two in-depth articles related to mod_wsgi that you > might like. One is from last year, it's about writing C extensions that are > compatible with mod_wsgi: > > http://emptysqua.re/blog/python-c-extensions-and-mod-wsgi/ > > The other I wrote this weekend, it's just a funny story about an exception > raised from a __del__ method in a mod_wsgi application: > > http://emptysqua.re/blog/a-normal-accident-in-python-and-mod-wsgi/ > > Enjoy! > Jesse > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/modwsgi. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
