This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients grahamd, ncoghlan, pitrou
Date 2012-08-21.14:47:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1345560247.3383.9.camel@localhost.localdomain>
In-reply-to <1345559624.38.0.254577276692.issue15751@psf.upfronthosting.co.za>
Content
> My understanding of the mod_wsgi architecture is that it uses
> subinterpreters to maintain a persistent process, while still
> providing a relatively pristine interpreter state to handle each new
> request.

I don't think that's true. On hg.python.org, the hglookup application
keeps a cached mapping of changeset ids to repo URLs, which wouldn't be
possible if its interpreter was re-bootstrapped for each new request.
History
Date User Action Args
2012-08-21 14:47:26pitrousetrecipients: + pitrou, ncoghlan, grahamd
2012-08-21 14:47:26pitroulinkissue15751 messages
2012-08-21 14:47:26pitroucreate