➜
See More

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 gvanrossum
Recipients gvanrossum, ned.deily, vstinner, yselivanov
Date 2018-09-21.15:32:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJLig4ejH577f3V+kqjrqWBxHu3w__h2vmUFz-i-hVe5=A@mail.gmail.com>
In-reply-to <[email protected]>
Content 
Let’s change it ASAP. It’s still up to Ned whether to hold up 3.7.1, if he
won’t it should go into 3.7.2.

On Fri, Sep 21, 2018 at 8:28 AM STINNER Victor <[email protected]>
wrote:

>
> STINNER Victor <[email protected]> added the comment:
>
> 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 ;-)
>
> ----------
> nosy: +vstinner
>
> _______________________________________
> Python tracker <[email protected]>
> <https://bugs.python.org/issue34762>
> _______________________________________
>
-- 
--Guido (mobile)
History
Date User Action Args
2018-09-21 15:32:12gvanrossumsetrecipients: + gvanrossum, vstinner, ned.deily, yselivanov
2018-09-21 15:32:12gvanrossumlinkissue34762 messages
2018-09-21 15:32:12gvanrossumcreate