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 Alexandre.Zani
Recipients Alexander.Belopolsky, Alexandre.Zani, barry, belopolsky, djc, lemburg, r.david.murray
Date 2012-06-04.17:33:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1338831189.04.0.931111112346.issue14908@psf.upfronthosting.co.za>
In-reply-to
Content
I think the easiest and most intuitive approach is to simply define timestamp() as being the reverse of fromtimestamp(). Don't worry about leap seconds and all that stuff.

If non-1970 epochs are a concern, this could be renamed to posix_timestamp or some such with perhaps a generic timestamp function that takes both a time and epoch.

But let's not let such a useful function not happen just because it won't solve everyone's problem.
History
Date User Action Args
2012-06-04 17:33:09Alexandre.Zanisetrecipients: + Alexandre.Zani, lemburg, barry, belopolsky, djc, r.david.murray, Alexander.Belopolsky
2012-06-04 17:33:09Alexandre.Zanisetmessageid: <1338831189.04.0.931111112346.issue14908@psf.upfronthosting.co.za>
2012-06-04 17:33:08Alexandre.Zanilinkissue14908 messages
2012-06-04 17:33:08Alexandre.Zanicreate