➜

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 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:14p-gansslesetrecipients: + p-ganssle, atuining, belopolsky, dlenski
2018-07-05 15:54:14p-gansslesetmessageid: <1530806054.59.0.56676864532.issue30155@psf.upfronthosting.co.za>
2018-07-05 15:54:14p-gansslelinkissue30155 messages
2018-07-05 15:54:14p-gansslecreate