WebOb going to Python 3 was held up by waiting for WSGI 2.
I certainly hope not. Now that PEP 3333 has been ratified, there can
be no more waiting. (3333 = WSGI 1.0.1, fully compliant with Python 3.)
meanwhile WSGI 2 itself had lost momentum in the course of disagreement
over goals/scope/etc.
Also, not entirely true. Have a gander at the Web-Sig mailing list
traffic for the last few months:
http://mail.python.org/pipermail/web-sig/2010-November/thread.html
http://mail.python.org/pipermail/web-sig/2010-December/thread.html
http://mail.python.org/pipermail/web-sig/2011-January/thread.html
January was particularly high-traffic.
As the current maintainer of PEP 444 (a Possible WSGI 2 Specification™
— some people really, really hate it when I'm not clear about the
'possible' part) I'm continuing to develop solutions (including WebOb
replacement, stanadardized middleware, etc.) and the 444 specification
itself. I should be able to dedicate signifigantly more time to 444
next month during the ConFoo and PyCon conferences.
Sooner or later (hopefully sooner) the dominoes will fall on this
because it's starting to feel odd when a developer has the freedom to
start a new project from scratch but is unable to choose Pyramid or
Pylons yet also work completely in Python 3. I'll be patient and
optimistic... and if current projects work out all right maybe I'll
actually get some time to help break the impasse.
http://bit.ly/gmT17O -- PEP 444 (Old, python.org copy.)
http://bit.ly/fRyMJ2 -- PEP 444 (My rewritten draft.)
All of my Marrow projects are Python 2 and 3 cross-compatible without
[automated] code modification and have signifigant unit testing and
documentation; most conform to my rewritten draft (e.g. the draft
branch of marrow.server.http) and some (such as marrow.wsgi.objects)
support WSGI 1 and PEP 444's definition of WSGI 2. Other than
marrow.util, no package reaches 1.0 without 100% coverage and full
documentation.
http://bit.ly/ei29t5 -- WIP WebOb replacement (WSGI 1 & 2).
http://bit.ly/etUUDW -- Example compression filter/middleware.
http://bit.ly/fLfamO -- Ultra-high performance HTTP/1.1 server.
http://bit.ly/wsgi-marrow -- GitHub page w/ all Marrow projects.
There is enough there to get started porting and testing to PEP 444.
Also, the differences between 333 and 3333 are small enough that
porting existing WSGI 1 solutions to Python 3 should/can begin
immediately.
— Alice.
--
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.
