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 larry
Recipients Arfrever, gvanrossum, larry, loewis, pitrou, r.david.murray, rosslagerwall, vstinner
Date 2012-03-04.00:24:23
SpamBayes Score 0.0019494052
Marked as misclassified No
Message-id <1330820664.37.0.722687223014.issue14127@psf.upfronthosting.co.za>
In-reply-to
Content
Actually, I'm hoping that by the time we get better than nanosecond resolution, we can also switch to 128-bit floats, and then the existing st_[acm]time field will become the preferred representation once more.  What goes around comes around!
History
Date User Action Args
2012-03-04 00:24:24larrysetrecipients: + larry, gvanrossum, loewis, pitrou, vstinner, Arfrever, r.david.murray, rosslagerwall
2012-03-04 00:24:24larrysetmessageid: <1330820664.37.0.722687223014.issue14127@psf.upfronthosting.co.za>
2012-03-04 00:24:23larrylinkissue14127 messages
2012-03-04 00:24:23larrycreate