[Python-Dev] Can we use "designated initializer" widely in core modules?
Antoine Pitrou
solipsis at pitrou.net
Wed Jan 18 06:33:52 EST 2017
More information about the Python-Dev mailing list
Wed Jan 18 06:33:52 EST 2017
- Previous message (by thread): [Python-Dev] Can we use "designated initializer" widely in core modules?
- Next message (by thread): [Python-Dev] Can we use "designated initializer" widely in core modules?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, 18 Jan 2017 08:44:29 +0100 Victor Stinner <victor.stinner at gmail.com> wrote: > > My patch adds Py_TPFLAGS_HAVE_FINALIZE and Py_TPFLAGS_HAVE_FASTCALL to > Py_TPFLAGS_DEFAULT. So all modules compiled with Python 3.7 will > announce that they have tp_finalize and tp_fastcall fields, even if > they are NULL. I don't know why this change wasn't done before for > tp_finalize. I don't think I thought about that idea at the time. tp_finalize doesn't benefit many extension types, so it's not a huge burden to add a FLAGS value for the few cases where you want to use it. Regards Antoine.
- Previous message (by thread): [Python-Dev] Can we use "designated initializer" widely in core modules?
- Next message (by thread): [Python-Dev] Can we use "designated initializer" widely in core modules?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list