Message76345
| 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 ;-) |
|