>> I posted some details of my initial thoughts on the 22nd, but two immediate >> action items were to update the wsgiserver code from CherryPy as that is now >> Python 2/3 compatible, and to identify how to best upgrade to Python 3's >> unicode handling (moving encoding/decoding to a python 2 only module, >> perhaps) since that was the biggest issue I ran into with my first attempt. > > I think we should start depending on cherrypy-wsgiserver instead of > shipping a copy with web.py. When we started using it, it was not > available on pypi. > > cherrypy-wsgiserver is not available for Python3, at least on pypi. We > should provide alternate implementation of dev server using wsgiref.
One of the burdens web.py carries is python2.3 compatibility. When I last heard, Python 2.3 was still supported on Redhat servers. It might have changed now. Anybody knows what is the status now? Anand -- You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en.
