Python usage numbers
jmfauth
wxjmfauth at gmail.com
Tue Feb 14 03:00:01 EST 2012
More information about the Python-list mailing list
Tue Feb 14 03:00:01 EST 2012
- Previous message (by thread): Python usage numbers
- Next message (by thread): Python usage numbers
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 13 fév, 04:09, Terry Reedy <tjre... at udel.edu> wrote: > > > * The new internal unicode scheme for 3.3 is pretty much a mixture of > the 3 storage formats (I am of course, skipping some details) by using > the widest one needed for each string. The advantage is avoiding > problems with each of the three. The disadvantage is greater internal > complexity, but that should be hidden from users. They will not need to > care about the internals. They will be able to forget about 'narrow' > versus 'wide' builds and the possible requirement to code differently > for each. There will only be one scheme that works the same on all > platforms. Most apps should require less space and about the same time. > > -- Python 2 was built for ascii users. Now, Python 3(.3) is *optimized* for the ascii users. And the rest of the crowd? Not so sure, French users (among others) who can not write their texts will iso-8859-1/latin1 will be very happy. No doubts, it will work. Is this however the correct approach? jmf
- Previous message (by thread): Python usage numbers
- Next message (by thread): Python usage numbers
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list