Message 369999 - 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	petr.viktorin, shihai1991, vstinner
Date	2020-05-26.15:15:54
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1590506154.62.0.848716127159.issue40601@roundup.psfhosted.org>
In-reply-to

Content
> Technically, it is not, see https://www.python.org/dev/peps/pep-0384/#structures > Structures like PyLong_Type are not part of the limited API. The symbol is exported by libpython: $ objdump -T /lib64/libpython3.8.so.1.0\|grep PyLong_Type 000000000030de00 g DO .data 00000000000001a0 Base PyLong_Type A C extension can use a reference to PyLong_Type. > I don't think it's necessary here. Did you read my rationale (first message)? Do you mean that per-interpreter GIL is not worth it? -- A first step would be to expose "CheckExact" macros as function calls in the limited C API.

> Technically, it is not, see https://www.python.org/dev/peps/pep-0384/#structures
> Structures like PyLong_Type are *not* part of the limited API.

The symbol is exported by libpython:

$ objdump -T /lib64/libpython3.8.so.1.0|grep PyLong_Type
000000000030de00 g    DO .data	00000000000001a0  Base        PyLong_Type

A C extension can use a reference to PyLong_Type.

> I don't think it's necessary here.

Did you read my rationale (first message)? Do you mean that per-interpreter GIL is not worth it?

--

A first step would be to expose "CheckExact" macros as function calls in the limited C API.

History
Date	User	Action	Args
2020-05-26 15:15:54	vstinner	set	recipients: + vstinner, petr.viktorin, shihai1991
2020-05-26 15:15:54	vstinner	set	messageid: <1590506154.62.0.848716127159.issue40601@roundup.psfhosted.org>
2020-05-26 15:15:54	vstinner	link	issue40601 messages
2020-05-26 15:15:54	vstinner	create