Massimo - thanks for the reply. Looks like 2.6 is the way to go until the developers catch-up with Python3 (that is if they think if it's worth doing in the first place).
Regards, Alan On 26 Oct, 02:36, mdipierro <[email protected]> wrote: > This issues comes up once every week. > > Web2py promises backward compatibility. We never broke and it we never > will. Python 3.x is not compatible with 2.4 and 2.5 because of > differences in the syntax. This means web2py will not move. This does > not exclude (and it actually is likely) that a web2py successor (with > a different name to avoid confusion) will be based on 3.x > > Right now very few third party libraries work well with 3.x compared > to 2.x, so I would not use for any production quality job. In > particular the database drivers we need do not work. > > Massimo > > On Oct 25, 6:40 pm, aharrisreid <[email protected]> wrote: > > > I am very much new to Python, and one of my first projects is a simple > > data-based website. However, looking to the future, I am > > starting with Python 3.1 (I can hear many of you shouting "don't - > > start with 2.6"), so I need to know - is web2py compatible with 3.1 > > yet. If not, are plans in the pipeline? > > > Many thanks, > > Alan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
