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 snprbob86
Recipients pje, snprbob86
Date 2009-11-03.20:58:13
SpamBayes Score 1.5835047e-05
Marked as misclassified No
Message-id <b2126670911031257g21ef5d68ke34568356e87bdc4@mail.gmail.com>
In-reply-to <1257275120.05.0.460450812771.issue7250@psf.upfronthosting.co.za>
Content
> 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.

That's fair. In this case the CGIHandler should raise an exception on
subsequent requests to prevent this programming error.

> 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.

I'm not sure if run_wsgi_app was available right from the start, as
some early tutorials and samples show using CGIHandler. That's how we
ran into this issue.
History
Date User Action Args
2009-11-03 20:58:15snprbob86setrecipients: + snprbob86, pje
2009-11-03 20:58:14snprbob86linkissue7250 messages
2009-11-03 20:58:13snprbob86create