Message290708
| Author |
vstinner |
| Recipients |
Eli Collins, Jordon Phillips, belopolsky, dstufft, lemburg, python-dev, vstinner |
| Date |
2017年03月28日.13:11:33 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1490706693.58.0.115402095967.issue29100@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
m-parry reported the issue #29921 "datetime validation is stricter in 3.6.1 than previous versions". He is right, the C API of Python 3.6.1 is now stricter than Python 2.7 and 3.5. The C API doesn't allow anymore to create datetime objects outside the [datetime.datetime.min; datetime.datetime.max] range (what I would call "invalid" datetime objects). I closed the bug as NOT A BUG since I consider that it's a deliberate design choice and not a regression. |
|