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 | jribbens |
|---|---|
| Recipients | guettli, jribbens, skip.montanaro, tim.peters |
| Date | 2007年09月02日.14:03:09 |
| SpamBayes Score | 0.17250983 |
| Marked as misclassified | No |
| Message-id | <1188741790.25.0.67967017151.issue1673409@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Almost everything you just said about time_t is wrong. time_t is signed, and always has been (otherwise the 'end of time' for 32-bit time_t would be 2106, not 2038). Also, time_t does not end at 2038 because nothing says it must be 32 bits. Also, Python has 'long integers' which do not overflow. Also, I don't understand what you mean about use cases. The "use case" is "dealing with anything which expects standard Unix time_t, for example the Python standard library". The use case I have personally is the program I was working on when I encountered the problem described in this bug report. Also I think symmetry is a darn good argument. Why does fromtimestamp exist if, as you claim, nobody uses time_t? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2007年09月02日 14:03:10 | jribbens | set | spambayes_score: 0.17251 -> 0.17250983 recipients: + jribbens, tim.peters, skip.montanaro, guettli |
| 2007年09月02日 14:03:10 | jribbens | set | spambayes_score: 0.17251 -> 0.17251 messageid: <1188741790.25.0.67967017151.issue1673409@psf.upfronthosting.co.za> |
| 2007年09月02日 14:03:10 | jribbens | link | issue1673409 messages |
| 2007年09月02日 14:03:09 | jribbens | create | |