On Wed, 2014-03-19 at 14:25 +0100, victor stinner wrote: > Hi, > > According to the following table, paste is blocking many OpenStack servers to > be ported to Python 3: > > https://wiki.openstack.org/wiki/Python3#Core_OpenStack_projects > > The author of paste, Ian Bicking, gave me the commit permission to paste. I > integrated patches from Debian and my colleague Cyril Roelandt, and I added > even more patches. All these changes are just for the Python 3 syntax > (import, except as, print, etc.). It looks like paste doesn't know anything > about Python 3 and WSGI 1.0.1 (PEP 3333): > > http://legacy.python.org/dev/peps/pep-3333/ > > A function handling a web page must return bytes (b'data' in Python 3), > whereas nativate string can be used in Python 2. It looks like paste is old > (last release was 4 years ago, version 1.7.5.1 in 2010). Even the author of > paste suggest to use something else like WebOb: > > "Paste has been under development for a while, and has lots of code in it. > Too much code! The code is largely decoupled except for some core functions > shared by many parts of the code. Those core functions are largely replaced > in WebOb, and replaced with better implementations." > > http://pythonpaste.org/future.html#introduction > > What is the plan for OpenStack? Should we use something else?
AFAIK, we only use paste.deploy, and we use WebOb already (even though it has a host of issues itself...) Best, -jay _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
