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 vstinner
Recipients ishimoto, lemburg, loewis, methane, r.david.murray, serhiy.storchaka, t2y, vstinner
Date 2014-12-15.21:35:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwY_hHyo085GWjeJJ0__XiW1H9fWVJNVARf05s7UGGj2nw@mail.gmail.com>
In-reply-to <CAGBzy2rpf4ZD=v5O7jwDc+0sRdZ+drHpfP0a_Bnoy=-hanFUuw@mail.gmail.com>
Content
I refactored some parts of CJK codecs for performances, after the PEP 393
was implemented. A blocker point was that these codecs have very few tests.
Not for valid data but for invalid data. It may be a little bit better. I
tried to write a test for each path in if/else, to test all cases, in the
codecs that I modified.

By error prone, it mean that it's easy to introduce a bug or a regressio,
since the code is complex and almost nobody maintains it.

I'm not stongly opposed to any change. I'm just trying to understand the
context.
History
Date User Action Args
2014-12-15 21:35:36vstinnersetrecipients: + vstinner, lemburg, loewis, ishimoto, r.david.murray, methane, serhiy.storchaka, t2y
2014-12-15 21:35:36vstinnerlinkissue23050 messages
2014-12-15 21:35:36vstinnercreate