Message226410
> If there are no objections I'll commit the patch soon.
Replacing TypeError with ValueError is fine. TypeError was a bad choice. If an application relies on TypeError to check for null character, it's easy to replace "except TypeError:" with "except (TypeError, ValueError):" to stay compatible with Python < 3.5.
Instead of "NUL character" (and "NUL byte), I had prefer "null character" (and "null byte"):
http://en.wikipedia.org/wiki/Null_character
I talking about the error message because you changed it in a few places. |
|
Date |
User |
Action |
Args |
2014-09-05 08:56:51 | vstinner | set | recipients:
+ vstinner, python-dev, serhiy.storchaka |
2014-09-05 08:56:51 | vstinner | set | messageid: <1409907411.08.0.35468479469.issue22215@psf.upfronthosting.co.za> |
2014-09-05 08:56:51 | vstinner | link | issue22215 messages |
2014-09-05 08:56:50 | vstinner | create | |
|