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 brett.cannon, eric.snow, ncoghlan
Date 2017-12-31.05:26:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1514698021.73.0.467229070634.issue32459@psf.upfronthosting.co.za>
In-reply-to
Content
After commenting [1] on the fact that the current datetime module C API [2] is problematic due to its reliance on C level global variables, I discovered that this is actually the outcome of our recommended approach to using capsules to export a C API as function pointers: https://docs.python.org/3/extending/extending.html#providing-a-c-api-for-an-extension-module

So we first need to fix the documentation to propose a reloading friendly way of using capsules in other extension modules, and then we can then propose updating the public datetime C API accordingly (probably by defining new macros that accept the capsule reference as their first argument).

[1] https://bugs.python.org/issue10381#msg309214
[2] https://docs.python.org/3/c-api/datetime.html
[3] https://docs.python.org/3/extending/extending.html#providing-a-c-api-for-an-extension-module
History
Date User Action Args
2017-12-31 05:27:01ncoghlansetrecipients: + ncoghlan, brett.cannon, eric.snow
2017-12-31 05:27:01ncoghlansetmessageid: <1514698021.73.0.467229070634.issue32459@psf.upfronthosting.co.za>
2017-12-31 05:27:01ncoghlanlinkissue32459 messages
2017-12-31 05:26:59ncoghlancreate