[issue29921] datetime validation is stricter in 3.6.1 than previous versions

New submission from m-parry: The change in issue #29100 - intended AFAICS simply to fix a regression in 3.6 - seems to have made datetime validation via certain code paths stricter than it was in 2.7 or 3.5. I think it's the case that some routes via the C API now reject out of range v

[issue29921] datetime validation is stricter in 3.6.1 than previous versions

m-parry added the comment: >From my opening comment (with new emphasis): "I think it's the case that **some routes via the C API** now reject out of range values that were previously permitted." The pywin32 repro I gave above eventually calls PyDateTimeAPI->DateTime_Fro

[issue29921] datetime validation is stricter in 3.6.1 than previous versions

m-parry added the comment: That's just a Python C API call. It looks like it eventually resolves to new_datetime_ex(30828, 9, 13, 3, 48, 5, 48, Py_None, PyDateTime_DateTimeType). We also have some internal code that sees a similar problem from calling PyTime_FromTime(), tha

[issue29921] datetime validation is stricter in 3.6.1 than previous versions

m-parry added the comment: pywin32 is not my code. It is a ubiquitous Python library on Windows that cannot be used under Python 3.6.1. -- ___ Python tracker <http://bugs.python.org/issue29