Don't all cheer at once, but I think I've gotten compatibility. It's a little ugly, and its definitely not backwards-compatible. I'm going to email the maintainer to see if we can put in a python3 branch, and commit to that one. I would guess that from then on, further development in web.py can continue in the main branch, with someone (me, I guess?) converting the changes over to 3.0.
On Apr 30, 3:02 am, Sherwin Soltani <[email protected]> wrote: > I think I read that web.py is python3 compatible. Cloning the latest > git and then trying to run out-of-box doesn't seem to work. I patched > the entire tree with 2to3, then tried again; some imports here and > there are still triggering errors. I hunted a few of them down, but > one in particular in http.py has me stumped. > > Please tell me I'm doing this wrong, and there is another way you're > supposed to get this module to work with python3. > > Otherwise I'd be happy to branch my work so far, and collaborate so > that we can make it 3.0 compatible. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
