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 Denny Weinberg, FrankBlabu, Jim.Jewett, Roman.Evstifeev, ammar2, belopolsky, christian.heimes, cschramm, josh.r, ncoghlan, ndjensen, p-ganssle, palm.kevin, steve.dower, yan12125
Date 2018-07-05.15:53:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1530805994.19.0.56676864532.issue27400@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 17:14:18pablogsalunlinkissue27400 messages
2018-07-05 15:53:14p-gansslesetrecipients: + p-ganssle, ncoghlan, belopolsky, christian.heimes, palm.kevin, Roman.Evstifeev, Jim.Jewett, steve.dower, josh.r, ndjensen, yan12125, Denny Weinberg, ammar2, cschramm, FrankBlabu
2018-07-05 15:53:14p-gansslesetmessageid: <1530805994.19.0.56676864532.issue27400@psf.upfronthosting.co.za>
2018-07-05 15:53:14p-gansslelinkissue27400 messages
2018-07-05 15:53:14p-gansslecreate