Steve Yeung added the comment:
I'm not sure what format I'm supposed to provide the test in. I attached a file
that has the diff of the changes I made, and how the error message is changed
(and improved!) in both datetime and time.
--
Added file: http://bugs.python.org/file
New submission from Steve Yeung:
Currently, the regex in TimeRE enforces the numeric ranges. For example:
'm': r"(?P1[0-2]|0[1-9]|[1-9])",
As a result, an invalid month will cause an generic regex error:
ValueError: time data '2015/16/5' does not match for
