On Aug 2, 2012 1:21 PM, "Anand Chitipothu" <[email protected]> wrote: > > On Thu, Aug 2, 2012 at 10:42 PM, Michael Diamond <[email protected]> wrote: > > Any thoughts on this from the developers? Haven't heard anything about this > > Sorry for the delay Michael. Thanks for the fix. I've pushed it now.
No worries, glad it's helpful. > > > or my email about making web.py Python 3 compatible. > > > > I'm interested in contributing in these and other areas, but I want to > > confirm my efforts are desired. > > They are very much desired. Please share your ideas about python3 compatibility. 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. Michael --- Michael Diamond Sent from my phone - please excuse the brevity. -- 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.
