Message321112
| Author | p-ganssle |
|---|---|
| Recipients | atuining, belopolsky, dlenski, p-ganssle |
| Date | 2018-07-05.15:54:14 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1530806054.59.0.56676864532.issue30155@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Hmm. I never noticed this. In the past I have used the (undocumented) PyDateTimeAPI struct, which the official macros wrap. I'm not sure how official that struct is considering it doesn't show up in the documentation. I agree that it should be possible to construct TZ-aware datetimes using the official C API, so I guess the question is whether to add a bunch more macros or document the existing struct. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-07-05 15:54:14 | p-ganssle | set | recipients: + p-ganssle, atuining, belopolsky, dlenski |
| 2018-07-05 15:54:14 | p-ganssle | set | messageid: <1530806054.59.0.56676864532.issue30155@psf.upfronthosting.co.za> |
| 2018-07-05 15:54:14 | p-ganssle | link | issue30155 messages |
| 2018-07-05 15:54:14 | p-ganssle | create | |