Message212772
The rationale for making this change is that the current behaviour converts a stylistic problem in checking values against a sentinel via "bool(value)" instead of "value is not None" into a subtle data driven behavioural bug that only occurs exactly at 0x0.0p+0.
If someone wants to write the patch to deprecate this behaviour in Python 3.5 (reporting a deprecation warning whenever midnight is interpreted as False, perhaps suggesting the use of "is" or "is not" instead), and then actually change the behaviour in 3.6, I don't believe we should actively oppose them from doing so.
See also issue #13936. |
|
Date |
User |
Action |
Args |
2014-03-05 22:50:10 | belopolsky | set | recipients:
+ belopolsky, ncoghlan |
2014-03-05 22:50:10 | belopolsky | set | messageid: <1394059810.09.0.454278014303.issue20855@psf.upfronthosting.co.za> |
2014-03-05 22:50:09 | belopolsky | link | issue20855 messages |
2014-03-05 22:50:09 | belopolsky | create | |
|