➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lemburg
Recipients Amber.Yust, Andreas.Pelme, Lakin.Wecker, belopolsky, cvrebert, dstufft, eric.araujo, georg.brandl, gwrtheyrn, lemburg, ncoghlan, pitrou, r.david.murray, shai, tim.peters, yselivanov
Date 2014-03-06.09:37:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <531841CD.6000403@egenix.com>
In-reply-to <1394098246.86.0.961300209536.issue13936@psf.upfronthosting.co.za>
Content 
On 06.03.2014 10:30, Antoine Pitrou wrote:
> 
> Antoine Pitrou added the comment:
> 
> I agree that having midnight evaluate to false is completely unexpected and unintuitive. I can imagine situations where it bites people in production use in the uncommon case that a time is exactly equal to midnight.

datetime values with the time set to midnight are *very* common in practice.
You run into them whenever you convert dates into datetime values.
History
Date User Action Args
2014-03-06 09:37:24lemburgsetrecipients: + lemburg, tim.peters, georg.brandl, ncoghlan, belopolsky, pitrou, eric.araujo, r.david.murray, cvrebert, gwrtheyrn, Lakin.Wecker, yselivanov, shai, dstufft, Andreas.Pelme, Amber.Yust
2014-03-06 09:37:24lemburglinkissue13936 messages
2014-03-06 09:37:24lemburgcreate