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 yselivanov
Recipients eric.snow, gvanrossum, ned.deily, rhettinger, vstinner, yselivanov
Date 2018-09-21.16:37:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1537547841.3.0.956365154283.issue34762@psf.upfronthosting.co.za>
In-reply-to
Content
> > one of the things we want to fix is to eliminate non-PyObject
> pointer types from public APIs entirely.

> A notable exception is Py_buffer. [1]

Right, because Py_buffer isn't a PyObject at all :)

> Using PyObject for contextvars makes sense (for the reasons you described) as long as they won't be shared between interpreters.

Yeah, PyContext, PyContextVar, and PyContextToken aren't supposed to be shared between sub-interpreters directly.  Context is essentially a mapping of Context Variables to arbitrary Python Objects, so sharing it transparently isn't possible.
History
Date User Action Args
2018-09-21 16:37:21yselivanovsetrecipients: + yselivanov, gvanrossum, rhettinger, vstinner, ned.deily, eric.snow
2018-09-21 16:37:21yselivanovsetmessageid: <1537547841.3.0.956365154283.issue34762@psf.upfronthosting.co.za>
2018-09-21 16:37:21yselivanovlinkissue34762 messages
2018-09-21 16:37:21yselivanovcreate