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 | erik.stephens |
|---|---|
| Recipients | brett.cannon, catlee, erik.stephens, guettli, jribbens, skip.montanaro, tim.peters, tomster |
| Date | 2008年07月10日.18:35:42 |
| SpamBayes Score | 0.0007599511 |
| Marked as misclassified | No |
| Message-id | <1215714943.97.0.797750636261.issue1673409@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I'm not sure this is still being considered, so I just wanted to add my opinion. This seems like such a simple request being made overly complicated. We just want seconds since epoch since that is used in many other functions and libraries (i.e. the time module, os.stat().st_mtime). Why is there toordinal()?!? If there is going to be any toxxx() methods, there should definitely be a tosecs()/totimestamp() method or an 'epoch/timestamp' attribute. For boundary cases, I would look to the std time module for guidance. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年07月10日 18:35:44 | erik.stephens | set | spambayes_score: 0.000759951 -> 0.0007599511 recipients: + erik.stephens, tim.peters, skip.montanaro, brett.cannon, jribbens, guettli, catlee, tomster |
| 2008年07月10日 18:35:44 | erik.stephens | set | spambayes_score: 0.000759951 -> 0.000759951 messageid: <1215714943.97.0.797750636261.issue1673409@psf.upfronthosting.co.za> |
| 2008年07月10日 18:35:42 | erik.stephens | link | issue1673409 messages |
| 2008年07月10日 18:35:42 | erik.stephens | create | |