Bug report

Bug description:

The comment here

deffunc(a,b,c=0):returna-b-cp2=partial(func,1,c=1)In [13]:print(p2(2))# -1vectorcallcall-2In [14]:In [14]:print(p2(2))# -1call-2In [15]:delp2.keywords['c']In [16]:print(p2(2))# -1call-1

I see 3 possibilities:

1. Set additional flag inpartial_setvectorcall(pto->hasvcall) storing state whethervectorcall is supported. Then implement fallback inpartial_call in the same manner as it looks now inpartial_vectorcall
2. Re-setting vectorcall after_PyObject_MakeTpCall inpartial_vectorcall_fallback. So thatpartial_vectorcall will stay as a primary entry in all cases. This adds 4ns overhead compared to 1.
3. Leave it as it is, but remove confusion that this needs to be checked more than 1 time.

CPython versions tested on:

3.11

Operating systems tested on:

macOS

Linked PRs

• gh-119109: functools.partial.fallforward fix #119125
• gh-119109: functool.partial vectorcall supports pto->kw & fallback to tp_call removed #120783
• gh-119109: improvefunctools.partial vectorcall with keywords #124584