INADA Naoki songofacandy at gmail.com
Fri Jul 6 20:20:40 EDT 2018

• Previous message (by thread): [Python-Dev] On the METH_FASTCALL calling convention
• Next message (by thread): [Python-Dev] On the METH_FASTCALL calling convention
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Sat, Jul 7, 2018 at 7:29 AM Victor Stinner <vstinner at redhat.com> wrote:
>
> Hi,
>
> I designed FASTCALL with the help of Serhiy for keywords. I prepared a long email reply, but I found an opportunity for optimisation on **kwargs and I need time to see how to optimize it.
>
> Maybe there is a need for passing **kwargs as a dict at C level, but use FASTCALL for positional arguments? I only know dict.update() which would benefit of that. All other functions are fine with FASTCALL for keywords.
>
> Victor
>

I agree with Jeroen.  If only few methods can be improved, it's not
necessary.  METH_VARARGS | METH_KEYWORDS is fine.

-- 
INADA Naoki  <songofacandy at gmail.com>

---

• Previous message (by thread): [Python-Dev] On the METH_FASTCALL calling convention
• Next message (by thread): [Python-Dev] On the METH_FASTCALL calling convention
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list