On Nov 7, 2010, at 2:55 PM, Mike Orr wrote: > On Sun, Nov 7, 2010 at 2:43 PM, Graham Dumpleton > <[email protected]> wrote: >> He would have meant 3333. See: >> >> http://www.python.org/dev/peps/pep-3333/
Yup, doh. > Well, Pyramid is moving away from middleware anyway, and providing > other ways to extend applications (e.g., the event hooks), so maybe > this will be less significant. But I still think WSGI needs to get rid > of 'start_response' and 'close', they make WSGI-compliant interfaces > unnecessarily hard to write and read, and more error prone. Right, well at least, middleware is fine, but we're trying to keep it now for things that aren't actually necessary for a Pyramid app to run. Like how a PylonsApp actually required a specific middlware stack to run. Weak that PEP-3333 still uses the start_response stuff, sigh. At this point, I honestly don't care as long as its "good enough" for us to write WSGI webapps with it under Py3. Cheers, Ben -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
