bpo-15988: make various overflow messages more consistent and helpful#668
bpo-15988: make various overflow messages more consistent and helpful#668orenmn wants to merge 21 commits into
Conversation
…i added to csv, as the inconsistent message in csv was already fixed, and so my patch isn't related to it anymore
…oryio, and optimized an if in seterror
…fix my socket tests
…Arg_* funcs in mmapmodule.c
… remove redundant code in _PyLong_AsInt
serhiy-storchaka
left a comment
There was a problem hiding this comment.
This is a great patch! Thanks Oren.
I made the first turn of reviewing. In general LGTM, but I left a number of comments. I think some changes could be extracted to separate issues. Some OverflowErrors could be avoided at all. I didn't tested all changes. I am not sure that reraising OverflowError with new error messages is appropriate in all cases. In some cases current error message looks not obviously worse.
Sorry, something went wrong.
|
@orenmn, could you please merge with master and resolve conflicts? This will help further reviewing this giant PR. Some issues may be already solved, perhaps in slightly different way. |
Sorry, something went wrong.
|
I still have some small issues that i wish to take care of before diving into this one, but i hope to get to it sometime soon. |
Sorry, something went wrong.
|
This PR is currently irrelevant, as explained in https://bugs.python.org/issue15988#msg303192 |
Sorry, something went wrong.
|
To try and help move older pull requests forward, we are going through and backfilling 'awaiting' labels on pull requests that are lacking the label. Based on the current reviews, the best we can tell in an automated fashion is that a core developer requested changes to be made to this pull request. If/when the requested changes have been made, please leave a comment that says, |
Sorry, something went wrong.
|
Based on @orenmn's last message and the merge conflicts, I'm going to close this pull request. I believe @serhiy-storchaka was suggesting for this to be split into smaller pull requests that would be easier to review. If that's not the case, feel free to re-open this PR. |
Sorry, something went wrong.
according to http://bugs.python.org/issue15988:
(I ran the test module, and on my Windows 10, the same tests failed with
and without my patches. However, on my Ubuntu 16.04 VM, none of the tests
failed.)