Message232684
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. |
|
Date |
User |
Action |
Args |
2014-12-15 21:35:36 | vstinner | set | recipients:
+ vstinner, lemburg, loewis, ishimoto, r.david.murray, methane, serhiy.storchaka, t2y |
2014-12-15 21:35:36 | vstinner | link | issue23050 messages |
2014-12-15 21:35:36 | vstinner | create | |
|