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 belopolsky, ncoghlan, p-ganssle, tim.peters
Date 2017-12-30.15:34:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>

I'm certainly fine with re-configuring my PR to center around a new capsule module with deprecation of the old C API (though if you have any examples of what you have in mind that would be helpful to me). Certainly the "C global needs to be initiated" problem has bitten me in the past and I'm certain will continue to bite people in the future.

That said, I think it would be really good if we could get a fast path for timezone creation and access to the UTC singleton into the Python 3.7 release. I think it's kind of a big disparity between the Python and C APIs that's existed for too long already.
Date User Action Args
2017-12-30 15:34:04p-gansslesetrecipients: + p-ganssle, tim.peters, ncoghlan, belopolsky
2017-12-30 15:34:04p-gansslesetmessageid: <>
2017-12-30 15:34:04p-gansslelinkissue10381 messages
2017-12-30 15:34:04p-gansslecreate