Changes by Éric Araujo mer...@netwok.org:
--
nosy: +eric.araujo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14654
___
___
Python-bugs-list
Serhiy Storchaka storch...@gmail.com added the comment:
See issue14738 for advanced optimization.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14654
___
Jesús Cea Avión j...@jcea.es added the comment:
I understand Martin point, but I think 95% of issues in the bugtracker are
work in progress, mine included.
Maybe the issue is that Serhiy hasn't made a concrete proposal to be tested
integrated. It seems to be more an exploratory work.
I am
Serhiy Storchaka storch...@gmail.com added the comment:
Martin, sorry to have wasted your time. I understand that you are busy,
so I'm not too worried not receiving a feedback for ten days.
At this point, it appears that you don't intend to submit any of these
patches for inclusion into
Serhiy Storchaka storch...@gmail.com added the comment:
Well, it seems, 64-bit processors are smart enough to not feel the need
for this optimization. On 32-bit platforms I see a noticeable increase
in speed.
I am now working on a more advanced optimization, which now shows a gain
of +20-60%
Martin v. Löwis mar...@v.loewis.de added the comment:
I'll be closing this issue at this point. Serhiy: I don't think the bug tracker
should be used to evolve work in progress (except when responding to reviews
received). Use a Mercurial clone for that instead. By posting a patch here, you
Antoine Pitrou pit...@free.fr added the comment:
I'll be closing this issue at this point. Serhiy: I don't think the
bug tracker should be used to evolve work in progress (except when
responding to reviews received). Use a Mercurial clone for that
instead. By posting a patch here, you are
Martin v. Löwis mar...@v.loewis.de added the comment:
That's not very nice. If Serhiy wants feedback on his work, he
definitely has to post *somewhere*. The bug tracker sounds like a
reasonable place (certainly more reasonable than python-dev).
I completely disagree (and I really tried to be
Serhiy Storchaka storch...@gmail.com added the comment:
title: More fast utf-8 decoding - Faster utf-8 decoding
Éric, there is already an issue (#4868) with this title.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14654
Martin v. Löwis mar...@v.loewis.de added the comment:
There is nothing wrong with two issues having the same title. Of course, it
would be best if the title reflected the *actual* defect or change, such as
specialize UTF-8 decoding by character width, or some such.
In any case, the title
Serhiy Storchaka storch...@gmail.com added the comment:
Thank you, Martin, this is what I had in mind. Lost in translation. ;)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14654
___
Antoine Pitrou pit...@free.fr added the comment:
64-bit Linux, Intel Core i5-2500K CPU @ 3.30GHz:
vanilla 3.3 patch 2 patch 3
utf-8 'A'*1 6931 (+3%)7115 (+0%) 7117
utf-8 'A'*+'\x80'
Changes by Éric Araujo mer...@netwok.org:
--
title: More fast utf-8 decoding - Faster utf-8 decoding
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14654
___
13 matches
Mail list logo