➜

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 ncoghlan
Recipients belopolsky, ncoghlan, p-ganssle, tim.peters
Date 2017-12-31.04:30:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7dXANi=16-6BdDp2fHfJLj6PPan7STa=Bt6JZ=QZphKww@mail.gmail.com>
In-reply-to <1514648044.84.0.213398074469.issue10381@psf.upfronthosting.co.za>
Content 
On 31 December 2017 at 01:34, Paul Ganssle <report@bugs.python.org> wrote:
> 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.

It turns out the API already *is* exported as a capsule:
https://github.com/python/cpython/blob/master/Include/datetime.h#L149

Our general guidance for capsule usage is just outdated, and the
datetime API follows that dated advice:
https://docs.python.org/3/extending/extending.html#providing-a-c-api-for-an-extension-module

I'll file a separate issue for that docs problem later (the tracker is
reporting 502 Proxy Error for me right now)
History
Date User Action Args
2017-12-31 04:30:13ncoghlansetrecipients: + ncoghlan, tim.peters, belopolsky, p-ganssle
2017-12-31 04:30:11ncoghlanlinkissue10381 messages
2017-12-31 04:30:02ncoghlancreate