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 <[email protected]> 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 <[email protected]> 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 [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 -~----------~----~----~----~------~----~------~--~---
