"More About Unicode in Python 2 and 3"
Ned Batchelder
ned at nedbatchelder.com
Mon Jan 6 17:22:34 EST 2014
More information about the Python-list mailing list
Mon Jan 6 17:22:34 EST 2014
- Previous message (by thread): "More About Unicode in Python 2 and 3"
- Next message (by thread): "More About Unicode in Python 2 and 3"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 1/6/14 5:08 PM, Mark Lawrence wrote: > On 06/01/2014 21:42, Ned Batchelder wrote: >> On 1/6/14 4:33 PM, Mark Lawrence wrote: >>> On 06/01/2014 21:17, Gene Heskett wrote: >>>> On Monday 06 January 2014 16:16:13 Terry Reedy did opine: >>>> >>>>> On 1/6/2014 9:32 AM, Gene Heskett wrote: >>>>>> And from my lurking here, its quite plain to me that 3.x python has a >>>>>> problem with everyday dealing with strings. >>>>> >>>>> Strings of what? And what specific 'everyday' problem are you >>>>> referring >>>>> to? >>>> >>>> Strings start a new thread here at nominally weekly intervals. Seems >>>> to me >>>> that might be usable info. >>>> >>>> Cheers, Gene >>>> >>> >>> That strikes me as being as useful as "The PEP 393 FSR is completely >>> wrong but I'm not going to tell you why" approach. >>> >> >> Please stop baiting people. >> > > What are you on about? The comment has been made that "its quite plain > to me that 3.x python has a problem with everyday dealing with strings". > Myself, Terry Reedy and Steven D'Aprano have all commented on this, > asking for more data. We've been given nothing, which is precisely what > our resident unicode expert has given us. > I'm on about your comment being a gratuitous jab at someone who isn't even participating in the thread. Stop it. -- Ned Batchelder, http://nedbatchelder.com
- Previous message (by thread): "More About Unicode in Python 2 and 3"
- Next message (by thread): "More About Unicode in Python 2 and 3"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list