On 21/04/2013 10:02, Terry Jan Reedy wrote:
On 4/20/2013 9:37 PM, rusi wrote:
I believe that the recent correction in unicode performance followed
jmf's grumbles
No, the correction followed upon his accurate report of a regression,
last August, which was unfortunately mixed in with grumbles a
On 4/20/2013 9:37 PM, rusi wrote:
I believe that the recent correction in unicode performance followed
jmf's grumbles
No, the correction followed upon his accurate report of a regression,
last August, which was unfortunately mixed in with grumbles and
inaccurate claims. Others separated out
jmfauth於 2013年4月21日星期日UTC+8上午1時12分43秒寫道：
> In a previous post,
>
>
>
> http://groups.google.com/group/comp.lang.python/browse_thread/thread/6aec70817705c226#
>
> ,
>
>
>
> Chris “Kwpolska” Warrick wrote:
>
>
>
> “Is Unicode su
On Sun, Apr 21, 2013 at 1:36 PM, Steven D'Aprano
wrote:
> On Sat, 20 Apr 2013 18:37:00 -0700, rusi wrote:
>
>> According to jmf python sucks up to ASCII (those big bad Americans… of
>> whom Steven is the first…)
>
> Watch who you're calling an American, mate.
I think he knows, and that's why he s
On Sat, 20 Apr 2013 18:37:00 -0700, rusi wrote:
> According to jmf python sucks up to ASCII (those big bad Americans… of
> whom Steven is the first…)
Watch who you're calling an American, mate.
--
Steven
--
http://mail.python.org/mailman/listinfo/python-list
On Apr 21, 4:03 am, Neil Hodgson wrote:
> Hi jmf,
>
> > This gives me plenty of ideas to test the "flexible string
> > representation" (FSR). I should recognize this FSR is failing
> > particulary very well...
>
> This is too vague for me.
>
> Which string representation should Python
On 04/20/2013 11:14 AM, Chris Angelico wrote:
Flash forward to current date, and jmf has hijacked so many threads to
moan about PEP 393 that I'm actually happy about this one, simply
because he gave it a new subject line and one appropriate to a
discussion about Unicode.
+1000
--
http://mail.py
Hi jmf,
This gives me plenty of ideas to test the "flexible string
representation" (FSR). I should recognize this FSR is failing
particulary very well...
This is too vague for me.
Which string representation should Python use?
1) UTF-32
2) UTF-8
3) Python 3.3 -- 1, 2, or 4 bytes per
Unicode support so hard, especially in the 21st century?”
--
Unicode is not really complicate and it works very well (more
than two decades of development if you take into account
iso-14).
But, - I can say, "as usual" - people prefer to spend their
time to make a "better Unicode th
up/comp.lang.python/browse_thread/thread/6aec70817705c226#
>>> ,
>>>
>>> Chris “Kwpolska” Warrick wrote:
>>>
>>> “Is Unicode support so hard, especially in the 21st century?”
>>>
>>> --
>>>
>>> Unicode is not really complicate and
On Sun, Apr 21, 2013 at 3:22 AM, Ned Batchelder wrote:
> I'm totally confused about what you are saying. What does "make a better
> Unicode than Unicode" mean? Are you saying that Python is guilty of this?
> In what way? Can you provide specifics? Or are you saying that you like
> how Python h
On Sat, Apr 20, 2013 at 10:22 AM, Ned Batchelder wrote:
> On 4/20/2013 1:12 PM, jmfauth wrote:
>>
>> In a previous post,
>>
>>
>> http://groups.google.com/group/comp.lang.python/browse_thread/thread/6aec70817705c226#
>> ,
>>
>> Chris “Kwpolsk
On 4/20/2013 1:12 PM, jmfauth wrote:
In a previous post,
http://groups.google.com/group/comp.lang.python/browse_thread/thread/6aec70817705c226#
,
Chris “Kwpolska” Warrick wrote:
“Is Unicode support so hard, especially in the 21st century?”
--
Unicode is not really complicate and it works
In a previous post,
http://groups.google.com/group/comp.lang.python/browse_thread/thread/6aec70817705c226#
,
Chris “Kwpolska” Warrick wrote:
“Is Unicode support so hard, especially in the 21st century?”
--
Unicode is not really complicate and it works very well (more
than two decades of
14 matches
Mail list logo
