Change by David Hewitt :
--
keywords: +patch
pull_requests: +28438
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/30217
___
Python tracker
<https://bugs.python.org/issu
New submission from David Hewitt :
The limited api methods `PyBuffer_GetPointer`, `PyBuffer_FromContiguous`,
`PyBuffer_ToContiguous` and `PyMemoryView_FromBuffer` take buffer arguments as
`Py_buffer *`.
They do not mutate the buffer info, so could simply take `const Py_buffer
New submission from David Hewitt :
I'm unsure if this is a packaging error or a misunderstanding by me.
I'm trying to link a binary on windows with Py_LIMITED_API set. According to
https://www.python.org/dev/peps/pep-0384/#linkage I _think_ I'm supposed to be
linking against python3.lib
David Hewitt added the comment:
I had suspected that might be the case. We already use PyObject_Call but had
been hoping to experiment with the Vectorcall optimizations.
Without the symbols I might resort to reproducing the implementation of these
functions on the Rust side. Shouldn't
New submission from David Hewitt :
I have been looking into using vectorcall in
[pyo3](https://github.com/PyO3/pyo3) (Rust bindings to Python) against
python3.8.
It looks like the _PyObject_Vectorcall symbols are not included in the shared
library. I've checked both Windows and Linux.
I
