Just so you guys know, I'm watching Python 3.x very closely and in some places helping it along. Here are the things that need to happen before Python 3.x becomes a viable web-platform (for a new project):
- The email module need to be fixed (it hasn't been rebuilt to handle the unicode conversion) - The cgi module depends on the email module - Flup works but it's only experimental and not currently part of the main trunk. Allan Saddi just ported it as a curiosity. - "Fast" Database drivers Currently there is support for SQLite, Postgres and MySQL, but the latter two are Python-only drivers which means they run 10x slower than their 2.x equivalent drivers. Here's some milestones you can expect: The email team has a goal of having email fixed by Python 3.2. Once that happens, fixing the cgi module will be a cakewalk (I might even do it). So look for that in 3.2.1. I don't know Allan Saddi's plans for flup, but after looking at the code, the prefork fcgi adapter is very Unix-specific. (Uses os.fork() and socketpair()) The multi-threaded one should still work just fine if you don't mind the GIL. Stay tuned. -tim On Oct 26, 8:48 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > I am wrong. I remember trying this and having problems but I tried > again with 3.1.1 and worked fine. I must have done something wrong > before. > > Massimo > > On Oct 26, 8:30 pm, Alan Harris-Reid <aharrisr...@googlemail.com> > wrote: > > > Hi Massimo, thanks for the insight. > > > If you think moving over to unicode is such a bad thing, why do you > > think the Python developers have decided to go down this route? > > Surely there must be advantages in the long-term? > > > Alan > > > On Oct 26, 11:57 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > > In Python 2.x you can do s.find(..), s.replace(..), etc. where s is a > > > byte string. This API does not exist anymore in in Python 3.x and you > > > can only do string manipulation if s a unicode string. This is very > > > bad because all network protocols use bytes not unicode. The solution > > > bytes>unicode>manipulate>unicode>bytes does not work because not all > > > ascii data can be represented in unicode (and at least not without a > > > major performance penalty). > > > > Python 3.x is making more difficult to program low level network > > > protocols and it moves the developer away from the OS representation > > > of data. > > > > Massimo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
