| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Co-authored-by: Sam Gross <colesbury@gmail.com>
Co-authored-by: Sam Gross <colesbury@gmail.com>
| Py_VISIT(mc->args); | ||
| Py_VISIT(mc->kwds); | ||
| Py_VISIT(mc->vectorcall_args); | ||
| Py_VISIT(mc->vectorcall_kwnames); |
There was a problem hiding this comment.
Note mc->vectorcall_kwnames is a tuple of strings, but the strings can be subclasses of str, so we need to visit this.
Sorry, something went wrong.
There was a problem hiding this comment.
Looks good. A few small comments below
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM. Thanks for fixing this!
Sorry, something went wrong.
…GH-127746) The function `operator.methodcaller` was not thread-safe since the additional of the vectorcall method in pythongh-89013. In the free threading build the issue is easy to trigger, for the normal build harder. This makes the `methodcaller` safe by: * Replacing the lazy initialization with initialization in the constructor. * Using a stack allocated space for the vectorcall arguments and falling back to `tp_call` for calls with more than 8 arguments.
| Back | FazBrowse Home | New Git URL |
See #127245 for details.