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 pje
Recipients pje, snprbob86
Date 2009-11-03.19:05:17
SpamBayes Score 2.3463594e-05
Marked as misclassified No
Message-id <1257275120.05.0.460450812771.issue7250@psf.upfronthosting.co.za>
In-reply-to
Content
This is not an issue with CGI, but an issue with using an inappropriate
WSGI handler for a long-running process environment that only emulates CGI.

That is, in a true CGI environment, there can't be *multiple* requests
made to CGIHandler, and so it can't leak.  In "normal" (i.e. pre-GAE)
long-running web environments, os.environ would not contain any request
information, only the process startup environment.

This limitation of CGIHandler should be better documented, but it's a
natural consequence of its design.  The os_environ and base_environ
variables are provided so that subclasses with specialized needs can
handle them differently, and GAE is definitely a specialized need.

If someone wants to provide a GAEHandler class, great; otherwise, the
documented way to run a WSGI app under GAE is the
google.appengine.ext.webapp.util.run_wsgi_app function.
History
Date User Action Args
2009-11-03 19:05:20pjesetrecipients: + pje, snprbob86
2009-11-03 19:05:20pjesetmessageid: <1257275120.05.0.460450812771.issue7250@psf.upfronthosting.co.za>
2009-11-03 19:05:17pjelinkissue7250 messages
2009-11-03 19:05:17pjecreate