Message 76345 - 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	vstinner
Recipients	Neil Muller, andersjm, belopolsky, davidfraser, hodgestar, tebeka, vstinner, werneck
Date	2008-11-24.17:34:56
SpamBayes Score	0.0007367736
Marked as misclassified	No
Message-id	<200811241832.56431.victor.stinner@haypocalc.com>
In-reply-to	<d38f5330811240933x49bd9163vaf9b56f7ec4259b9@mail.gmail.com>

Content
> > Hum, it's maybe not possible to choose between integer and float. Why > > not supporting both? Example: > > - totimestamp()->int: truncate microseconds > > - totimestamp(microseconds=True)->float: with microseconds > > I would still prefer totimestamp()->(int, int) returning (sec, usec) > tuple. The important benefit is that such totimestamp() will not > loose information Right, I prefer your solution ;-)

> > Hum, it's maybe not possible to choose between integer and float. Why
> > not supporting both? Example:
> >  - totimestamp()->int: truncate microseconds
> >  - totimestamp(microseconds=True)->float: with microseconds
>
> I would still prefer totimestamp()->(int, int) returning (sec, usec)
> tuple.  The important benefit is that such totimestamp() will not
> loose information

Right, I prefer your solution ;-)

History
Date	User	Action	Args
2008-11-24 17:34:57	vstinner	set	recipients: + vstinner, tebeka, davidfraser, belopolsky, andersjm, werneck, hodgestar, Neil Muller
2008-11-24 17:34:56	vstinner	link	issue2736 messages
2008-11-24 17:34:56	vstinner	create