Howdy!
> I've written up a semi-radical proposal to replace Pylons' WSGI stack with a
> WebOb-based stack, so this will also be among the discussions. With the
> impasse on getting WSGI to Python 3, some of us are impatient to just go our
> own direction, and we may want to jump to a higher-level protocol while we're
> at it.
While I’m currently thoroughly enjoying WebOb, some of the design ideas and
compatibility cruft go against my coding aesthetic. It’s functional, but it
could be cleaner/better.
A short while ago I started up a repository called Pulp[1] (Paste → Pulp,
right? ;) with the idea to bring the best ideas from Paste*, WebOb, WebHelpers,
WebError, Flup, and other common elements, etc. together under one roof in such
a way as to be source compatible with both Python 2.5+ and Py3K. (Namespace
packages, FTW, though waiting on full venv and distribute support in Py3K.)
The Response object is already compatible with the draft WSGI 2.0 spec while
continuing to work as a WSGI 1, too.
Just an idea that we can take what has been learned thus far, and create
something new and wonderful with our knowledge.
— Alice.
[1] http://github.com/GothAlice/Pulp/
Soon to be http://www.wsgi-pulp.org/
--
You received this message because you are subscribed to the Google Groups
"TurboGears" 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/turbogears?hl=en.
