Message212879
| Author | ncoghlan |
|---|
| Recipients | Amber.Yust, Andreas.Pelme, Hanxue.Lee, Lakin.Wecker, alex, belopolsky, cvrebert, dstufft, eric.araujo, ethan.furman, georg.brandl, gwrtheyrn, lemburg, ncoghlan, pitrou, r.david.murray, shai, skip.montanaro, tim.peters, yselivanov |
|---|
| Date | 2014-03-07.14:22:46 |
|---|
| SpamBayes Score | -1.0 |
|---|
| Marked as misclassified | Yes |
|---|
| Message-id | <CADiSq7c=Uom3iNe1weAZJa+0FS6RQ+DQMV=j-H9pA3c7bWy+Lg@mail.gmail.com> |
|---|
| In-reply-to | <1394198362.0.0.893392430588.issue13936@psf.upfronthosting.co.za> |
|---|
| Content |
|---|
Structured data is just a shorthand way of referring to any Python objectwhich is neither a number or a container and exhibits the default booleanbehaviour where all instances are true.The problem datetime.time is both that its current behaviour is internallyincoherent (whether or not an aware time is false depends on the currenttimezone in unpredictable ways) and *also* inconsistent with its otherbehaviours that indicate it should be handled as a non-numeric value. Sinceit isn't a container either, standard conventions suggest that it shouldalways be true. No *compelling* justifications for its atypical behaviourhave been presented, just a case of Tim wanting to leave the door open toadding modular arithmetic directly on time instances.I suggest it makes far more sense to instead eliminate the quirky behaviourentirely and instead provide an easy way to convert a time to a timedeltarelative to midnight. |
| History |
|---|
| Date | User | Action | Args |
|---|
| 2014-03-07 14:22:46 | ncoghlan | set | recipients: +ncoghlan,lemburg,tim.peters,skip.montanaro,georg.brandl,belopolsky,pitrou,eric.araujo,alex,r.david.murray,cvrebert,ethan.furman,gwrtheyrn,Lakin.Wecker,yselivanov,shai,dstufft,Andreas.Pelme,Amber.Yust,Hanxue.Lee | | 2014-03-07 14:22:46 | ncoghlan | link | issue13936 messages | | 2014-03-07 14:22:46 | ncoghlan | create | |
|