Author vstinner
Recipients Neil Muller, andersjm, belopolsky, davidfraser, hodgestar, tebeka, vstinner, werneck
Date 2008-11-24.17:34:56
SpamBayes Score 0.000736774
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 ;-)
History
Date User Action Args
2008-11-24 17:34:57vstinnersetrecipients: + vstinner, tebeka, davidfraser, belopolsky, andersjm, werneck, hodgestar, Neil Muller
2008-11-24 17:34:56vstinnerlinkissue2736 messages
2008-11-24 17:34:56vstinnercreate