Re: "More About Unicode in Python 2 and 3"

From	Ned Batchelder <ned@nedbatchelder.com>
Subject	Re: "More About Unicode in Python 2 and 3"
Date	2014-01-06 17:22 -0500
References	(2 earlier) <laf2qm$4ep$1@ger.gmane.org> <201401061617.06746.gheskett@wdtv.com> <laf7fu$se5$1@ger.gmane.org> <laf7ut$1be$2@ger.gmane.org> <laf9gn$le8$1@ger.gmane.org>
Newsgroups	comp.lang.python
Message-ID	<mailman.5075.1389046967.18130.python-list@python.org> (permalink)

Show all headers | View raw

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

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: "More About Unicode in Python 2 and 3" Ned Batchelder <ned@nedbatchelder.com> - 2014-01-06 17:22 -0500

csiph-web