Message 325991 - Python tracker

➜

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	vstinner
Recipients	gvanrossum, ned.deily, vstinner, yselivanov
Date	2018-09-21.15:28:42
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1537543722.87.0.956365154283.issue34762@psf.upfronthosting.co.za>
In-reply-to

Content
IMHO it's not too late to change the public C API in Python 3.7.1, since it's a very new API, I don't expect many users, and I only expect compiler warnings nor hard error if existing code pass PyContextVar* instead of PyObject. I agree that it's way better to use PyObject rather than specific PyContextVar*. The C API should not leak implementation details ;-)

IMHO it's not too late to change the public C API in Python 3.7.1, since it's a very new API, I don't expect many users, and I only expect compiler warnings nor hard error if existing code pass PyContextVar* instead of PyObject*.

I agree that it's way better to use PyObject* rather than specific PyContextVar*. The C API should not leak implementation details ;-)

History
Date	User	Action	Args
2018-09-21 15:28:42	vstinner	set	recipients: + vstinner, gvanrossum, ned.deily, yselivanov
2018-09-21 15:28:42	vstinner	set	messageid: <1537543722.87.0.956365154283.issue34762@psf.upfronthosting.co.za>
2018-09-21 15:28:42	vstinner	link	issue34762 messages
2018-09-21 15:28:42	vstinner	create