Author eric.snow
Recipients eric.snow, gvanrossum, ned.deily, rhettinger, vstinner, yselivanov
Date 2018-09-21.16:32:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1537547544.45.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]  As well, cross-interpreter data must not be PyObject, though that isn't much of an issue (yet). :)  At some point it may make sense to make _PyCrossInterpreterData [2] part of the public C-API.  However, we can cross *that* bridge later. :)

Using PyObject for contextvars makes sense (for the reasons you described) as long as they won't be shared between interpreters.  I'm not super familiar with the contextvars C-API, but it looks like cross-interpreter issues are *not* a factor.  If that's the case then there's nothing further to discuss. :)

[1] https://docs.python.org/3/c-api/buffer.html#buffer-structure
[2] https://github.com/python/cpython/blob/master/Include/internal/pystate.h#L137
History
Date User Action Args
2018-09-21 16:32:24eric.snowsetrecipients: + eric.snow, gvanrossum, rhettinger, vstinner, ned.deily, yselivanov
2018-09-21 16:32:24eric.snowsetmessageid: <1537547544.45.0.956365154283.issue34762@psf.upfronthosting.co.za>
2018-09-21 16:32:24eric.snowlinkissue34762 messages
2018-09-21 16:32:24eric.snowcreate