➜

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 belopolsky
Recipients Arfrever, Niklas.Claesson, Ramchandra Apte, andrewclegg, belopolsky, goshawk, holdenweb, lemburg, mdcb808@gmail.com, pitrou, pythonhacker, r.david.murray, scoobydoo, serhiy.storchaka, tim.peters, tomikyos, vstinner
Date 2016-07-16.02:34:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1468636446.29.0.565481495644.issue15443@psf.upfronthosting.co.za>
In-reply-to
Content 
Note that the patches attached so far to this issue are nowhere close to a complete implementation.  I don't think a python-only prototype (a patch to datetime.py) would be hard to implement, but implementation would be easier if nanoseconds replaced microseconds in datetime and timedelta objects with new microsecond(s) becoming a computed property.
History
Date User Action Args
2016-07-16 02:34:06belopolskysetrecipients: + belopolsky, lemburg, tim.peters, holdenweb, pitrou, vstinner, pythonhacker, Arfrever, r.david.murray, andrewclegg, Ramchandra Apte, serhiy.storchaka, goshawk, Niklas.Claesson, mdcb808@gmail.com, scoobydoo, tomikyos
2016-07-16 02:34:06belopolskysetmessageid: <1468636446.29.0.565481495644.issue15443@psf.upfronthosting.co.za>
2016-07-16 02:34:06belopolskylinkissue15443 messages
2016-07-16 02:34:05belopolskycreate