This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients Arfrever, jcea, loewis, pitrou, serhiy.storchaka, vstinner
Date 2012-05-05.22:06:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20120506000608.Horde.zfgkf8L8999PpaRQSquHWOA@webmail.df.eu>
In-reply-to
Content
> 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 nice).

It is my utmost belief that the tracker must not be used for
work-in-progress. For any open issue, numerous people review the
issue, and even if they spend only a few minutes, this easily adds
up to a lot of wasted time if there isn't anything to be done about
an issue.

OTOH, discussing it on python-dev indeed seems more appropriate:
even though the readership is larger, people know that they can safely
skip over messages that clearly don't need their attention. So if
Serhiy posts a message titled "UTF-8 performance", people will hit
the delete button very quickly if they are not interested.

However, it would really be best in this case if Serhiy takes a step
back, and analyzes the performance of the current decoder carefully,
then proposes a patch which undoubtedly improves the performance and
is meanwhile also maintainable.

He may come to the conclusion that further improvement isn't really
possible or reasonable, in which case it would be good if he posted
his findings to python-dev.
History
Date User Action Args
2012-05-05 22:06:18loewissetrecipients: + loewis, jcea, pitrou, vstinner, Arfrever, serhiy.storchaka
2012-05-05 22:06:18loewislinkissue14654 messages
2012-05-05 22:06:17loewiscreate