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 | skip.montanaro |
|---|---|
| Recipients | guettli, jribbens, skip.montanaro, tim.peters |
| Date | 2007年09月02日.03:22:52 |
| SpamBayes Score | 0.3647863 |
| Marked as misclassified | No |
| Message-id | <1188703372.8.0.174601033133.issue1673409@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
There is no datetime.totimestamp because the range of time represented by a datetime object far exceeds the range of a normal int-based Unix timestamp (roughly 1970-2038). Datetime objects before the start of the Unix epoch would be represented by negative numbers. As far as I know, the common Unix library functions which accept epoch times wouldn't know what to do with a negative number. That said, you stated these missing methods were important. Can you offer some use cases which would support that contention? I personally don't think a argument for symmetry would be a convincing use case and that's the only one I can think of. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2007年09月02日 03:22:53 | skip.montanaro | set | spambayes_score: 0.364786 -> 0.3647863 recipients: + skip.montanaro, tim.peters, jribbens, guettli |
| 2007年09月02日 03:22:52 | skip.montanaro | set | spambayes_score: 0.364786 -> 0.364786 messageid: <1188703372.8.0.174601033133.issue1673409@psf.upfronthosting.co.za> |
| 2007年09月02日 03:22:52 | skip.montanaro | link | issue1673409 messages |
| 2007年09月02日 03:22:52 | skip.montanaro | create | |