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 pitrou
Recipients Arfrever, gvanrossum, larry, loewis, pitrou, r.david.murray, rosslagerwall, vstinner
Date 2012-03-04.00:37:58
SpamBayes Score 0.00171522
Marked as misclassified No
Message-id <1330821242.3362.4.camel@localhost.localdomain>
In-reply-to <>
> 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 if your hope isn't fulfilled? That doesn't sound like a reasonable
decision-making strategy.
Date User Action Args
2012-03-04 00:37:59pitrousetrecipients: + pitrou, gvanrossum, loewis, vstinner, larry, Arfrever, r.david.murray, rosslagerwall
2012-03-04 00:37:58pitroulinkissue14127 messages
2012-03-04 00:37:58pitroucreate