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 | werneck |
|---|---|
| Recipients | tebeka, werneck |
| Date | 2008年05月03日.02:18:59 |
| SpamBayes Score | 0.16495965 |
| Marked as misclassified | No |
| Message-id | <1209781140.38.0.013960645482.issue2736@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
That's expected as mktime is just a thin wrapper over libc mktime() and it does not expect microseconds. Changing time.mktime doesn't seems an option, so the best alternative is to implement a method in datetime type. Is there a real demand for C code implementing this to justify it? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年05月03日 02:19:00 | werneck | set | spambayes_score: 0.16496 -> 0.16495965 recipients: + werneck, tebeka |
| 2008年05月03日 02:19:00 | werneck | set | spambayes_score: 0.16496 -> 0.16496 messageid: <1209781140.38.0.013960645482.issue2736@psf.upfronthosting.co.za> |
| 2008年05月03日 02:18:59 | werneck | link | issue2736 messages |
| 2008年05月03日 02:18:59 | werneck | create | |