RetroSearch Browse

Sat Feb 16 05:15:44 EST 2019 · https://mail.python.org/pipermail/python-dev/2019-February/156345.html

On 2019-02-16 00:37, Eric Snow wrote:
> One thing that would help simplify changes
> in this area is if PyInterpreterState were defined in
> Include/internal.

How would that help anything? I don't like the idea (in general, I'm not 
talking about PyInterpreterState specifically) that external modules 
should be second-class citizens compared to modules inside CPython.

If you want to break the undocumented API, just break it. I don't mind. 
But I don't see why it's required to move the include to 
Include/internal for that.

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2019-February/156345.html below:

[Python-Dev] Making PyInterpreterState an opaque type