[Python-Dev] PEP 575: Unifying function/method classes
Nick Coghlan
ncoghlan at gmail.com
Mon Apr 30 09:49:43 EDT 2018
More information about the Python-Dev mailing list
Mon Apr 30 09:49:43 EDT 2018
- Previous message (by thread): [Python-Dev] PEP 575: Unifying function/method classes
- Next message (by thread): [Python-Dev] PEP 575: Unifying function/method classes
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 30 April 2018 at 23:38, Mark Shannon <mark at hotpy.org> wrote: > > On 12/04/18 17:12, Jeroen Demeyer wrote: > >> Dear Python developers, >> >> I would like to request a review of PEP 575, which is about changing the >> classes used for built-in functions and Python functions and methods. The >> text of the PEP can be found at >> > > > The motivation of PEP 575 is to allow introspection of built-in functions > and to allow functions implemented in Python to be re-implemented in C. > > These are excellent goals. > That summary misses the 3rd goal, which is the one that answers your other questions: to allow 3rd party extension modules access to the hot paths in CPython that are currently restricted to true built-in and Python native functions (without making those hot paths measurably slower). Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20180430/e96fdcab/attachment.html>
- Previous message (by thread): [Python-Dev] PEP 575: Unifying function/method classes
- Next message (by thread): [Python-Dev] PEP 575: Unifying function/method classes
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list