{{ message }}
bpo-32582: chr() doesn't raise OverflowError anymore#5218
Closed
vstinner wants to merge 3 commits into
Closed
Conversation
chr() now catchs OverflowError and raises a ValueError exception instead.
zhangyangyu
reviewed
Jan 18, 2018
zhangyangyu
approved these changes
Jan 18, 2018
Member
Author
|
Hum, this PR changes the exception type for large float. Patched: Python 3.6: |
Sorry, something went wrong.
Member
|
Ahh, yes. And now it could accept small float while not the case before. So still need to call "PyArg_Parse" and catch OverflowError then. |
Sorry, something went wrong.
serhiy-storchaka
left a comment
Member
There was a problem hiding this comment.
Needed updating the chr() documentation an an entry in the What's New document, in the section "Porting to 3.7".
Sorry, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.
chr() now catchs OverflowError and raises a ValueError exception
instead.
https://bugs.python.org/issue32582