STINNER Victor <[EMAIL PROTECTED]> added the comment: > > 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 ;-) _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2736> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
