[Web-SIG] Pre-PEP: Python Web Container Interface v1.0

[A.M. Kuchling]

On Wed, Dec 10, 2003 at 02:15:10PM -0500, Michael C. Neel wrote:
> Which leads to my other concern; should this even be a concern?  The
> goal here is to update/add to the stdlib.  Since the odds of mod_python
> becoming part of the stdlib are nil, should we even worry about a spec
> for things like mod_python and Zope?

No, adding to the stdlib is not necessarily the goal.  The DB-API isn't
represented in the stdlib either, yet it's still useful for ensuring a
certain amount of consistency between database modules.  Authors of modules
can follow the API or not, and they're only responsible to their users  
about whether they do.

Similarly, this PEP is an informational document describing a certain
convention that web frameworks can follow or not, as they see fit.  And it
helps alleviate the O(n**2) problem of connecting various publishing schemes
together.  Want to run Quixote under Twisted?  Go write an adapter.  Want to
run Webware under SCGI.  Go write an adapter.  If each piece supported this
interface, at least it would be fairly easy to combine tools without having
to write a different chunk of adapter code for each possible pair.

--amk