Message 249282 - Python tracker

➜

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	aconrad, belopolsky, larry, mark.dickinson, r.david.murray, tbarbugli, tim.peters, trcarden, vivanov, vstinner
Date	2015-08-28.17:17:30
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1440782250.49.0.0257936395098.issue23517@psf.upfronthosting.co.za>
In-reply-to

Content
I wish we could use the same algorithm in datetime.utcfromtimestamp as we use in float to string conversion. This may allow the following chain of conversions to round trip in most cases: float literal -> float -> datetime -> seconds.microseconds string

I wish we could use the same algorithm in datetime.utcfromtimestamp as we use in float to string conversion.  This may allow the following chain of conversions to round trip in most cases:

float literal -> float -> datetime -> seconds.microseconds string

History
Date	User	Action	Args
2015-08-28 17:17:30	belopolsky	set	recipients: + belopolsky, tim.peters, mark.dickinson, vstinner, larry, r.david.murray, aconrad, vivanov, tbarbugli, trcarden
2015-08-28 17:17:30	belopolsky	set	messageid: <1440782250.49.0.0257936395098.issue23517@psf.upfronthosting.co.za>
2015-08-28 17:17:30	belopolsky	link	issue23517 messages
2015-08-28 17:17:30	belopolsky	create