New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace TypeError with ValueError in doc regarding "embedded NUL character" #71668
Comments
Errors regarding "embedded NUL character" were changed from TypeError to ValueError, in r92365, bpo-22215, but the doc doesn't get updated. Add a patch to apply the change in doc. |
Just for a note, there has already been an bpo-26401 fixing the function.rst. Upload a new patch adding versionchanged tag. |
LGTM. But while we are here, it would be worth to change "NUL character" and "NUL byte" to "null character" or "null byte" as most used in the documentation and the code. |
Yes. I noticed the change but didn't change it. Now add it. |
Python strings contain characters, not bytes. |
Sorry, I didn't notice the difference. |
LGTM. Thanks Xiang. |
New changeset 420030a5e854 by Serhiy Storchaka in branch '3.5': New changeset 00b9c734af87 by Serhiy Storchaka in branch 'default': |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: