On May 4, 4:55 pm, Anand Chitipothu <[email protected]> wrote:
> 2009/4/30 Sherwin Soltani <[email protected]>:
>
>
>
> > 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.
>
> Did you manage to run web.py on python3.0 with your patch?
> I couldn't run the hello world example using either wsgiserver or
> fastcgi as both are not python3.0 compatible.
Please be aware that if you are relying on WSGI, that there is no WSGI
specification which covers Python 3.0. There is still discussion going
on as to how it should look and chances are that anything you produce
now may not work when details are nailed down. So, although Apache/
mod_wsgi 3.0, for which there is a release candidate, supports Python
3.0, it is quite liberal in what it allows. Chances are though that
various things it currently allows it will not allow when WSGI
specification for Python 3.0 is settled on. It may thus be premature
to be looking at Python 3.0 support.
Graham
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
