Author ncoghlan
Recipients dstufft, ncoghlan, tim.peters, yselivanov
Date 2014-03-05.23:24:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1394061891.73.0.846311880063.issue20855@psf.upfronthosting.co.za>
In-reply-to
Content
Alexander, my goal is to flip the default assumption in the time discussion. It is clear from the documentation that the current behaviour is intentional, but there is no concrete *use case* given for it. This is in stark contrast to the other types where treating zero or an empty container differently is quite common, and hence generally unsurprising.

This has resulted in a problem, since the default for most types is that all instances are true, and users mistakenly assume that assumption will hold for datetime.time objects. This is particularly likely for newer users that don't have experience with lower level models of time of day as "seconds since midnight" (which is the mental model where the current behaviour makes sense, and the most plausible rationale for its origins).
History
Date User Action Args
2014-03-05 23:24:51ncoghlansetrecipients: + ncoghlan, tim.peters, yselivanov, dstufft
2014-03-05 23:24:51ncoghlansetmessageid: <1394061891.73.0.846311880063.issue20855@psf.upfronthosting.co.za>
2014-03-05 23:24:51ncoghlanlinkissue20855 messages
2014-03-05 23:24:50ncoghlancreate