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-30.03:44:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1514605498.17.0.213398074469.issue10381@psf.upfronthosting.co.za>
In-reply-to
Content
Would it be possible to deprecate (or at least stop enhancing) the current datetime C API and add a new capsule based one instead?

We're trying to get extension module authors to *stop* relying on C level globals, since it causes problems with:

- memory usage analysis
- interpreter reinitialisation
- module reloading
- subinterpreters

Unfortunately, the current design of the datetime C API *requires* the use of C level global state.
History
Date User Action Args
2017-12-30 03:44:58ncoghlansetrecipients: + ncoghlan, tim.peters, belopolsky, p-ganssle
2017-12-30 03:44:58ncoghlansetmessageid: <1514605498.17.0.213398074469.issue10381@psf.upfronthosting.co.za>
2017-12-30 03:44:58ncoghlanlinkissue10381 messages
2017-12-30 03:44:57ncoghlancreate