gh-70647: Add detail to error message when parsing a bad day of month. #116184
+3 −2
Conversation
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
… month. The presence of the values in the error message gives a stronger hint as to what went wrong. ``` >>> datetime.strptime("2.29", "%m.%d") Traceback (most recent call last): File "<stdin>", line 1, in <module> datetime.strptime("2.29", "%m.%d") ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^ File ".../Lib/_strptime.py", line 565, in _strptime_datetime return cls(*args) ~~~^^^^^^^ ValueError: day 29 is out of range for month 2 in year 1900 ``` 
Member
| +1 on the principle, but ideally there would be a test for this. |
Member Author
| closing in favor of #131335 |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit. 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. Add this suggestion to a batch that can be applied as a single commit. 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. Suggestion cannot be applied right now. Please check back later.
The presence of the values in the error message gives a stronger hint as to what went wrong.