[Python-Dev] PEP 590: vectorcall without tp_call (original) (raw)
Brett Cannon brett at python.org
Wed May 29 12:49:00 EDT 2019
- Previous message (by thread): [Python-Dev] PEP 590: vectorcall without tp_call
- Next message (by thread): [Python-Dev] Per opcode cache for LOAD_GLOBAL
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, May 29, 2019 at 7:55 AM Jeroen Demeyer <J.Demeyer at ugent.be> wrote:
On 2019-05-29 16:00, Christian Heimes wrote: > You could add a check to PyTypeReady() and have it either return an > error or fix tpcall.
Yes, but the question is: which of these two alternatives? I would vote for fixing tpcall but Petr voted for an error.
I also vote for the error so that people are sure they get the semantics they want/expect. If not defining tp_call is a reasonable thing then I would expect it to never have to be set to begin with and that doesn't sound like what anyone wants if we're talking about automatically filling it. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20190529/0715e993/attachment.html>
- Previous message (by thread): [Python-Dev] PEP 590: vectorcall without tp_call
- Next message (by thread): [Python-Dev] Per opcode cache for LOAD_GLOBAL
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]