[C API] Make _PyTuple_FromArray() function public

[vstinner]

I dislike PyList_New() + PyList_SET_ITEM() API since the list is immediately tracked by the GC and so calling gc.get_objects() can expose an invalid list object (ex: calling repr(list) can crash). See:

• Disallow creation of incomplete/inconsistent objects capi-workgroup/problems#56
• gh-107137: Add _PyTupleBuilder API to the internal C API #107139
• Avoid creating incomplete/invalid objects capi-workgroup/api-evolution#36

The internal PyObject * _PyTuple_FromArray(PyObject *const *src, Py_ssize_t n) function should be made public.

cc @erlend-aasland

UPDATE: I updated the issue to request promoting _PyTuple_FromArray() instead of _PyList_FromArraySteal().

Linked PRs

• gh-111489: Add PyList_FromArrayMoveRef() function #112975
• gh-111489: Add PyTuple_FromArray() function #139691
• gh-111489: Remove _PyTuple_FromArray() alias #139973

[vstinner]

We should also make PyObject* _PyTuple_FromArraySteal(PyObject *const *src, Py_ssize_t n) public.

[encukou]

Can you wait until the new guidelines are approved? Not everyone is happy with the term steal.

[vstinner]

Can you wait until the new guidelines are approved?

The name is discussed at capi-workgroup/problems#11 (comment)

[vstinner]

Naming is discussed at capi-workgroup/api-evolution#25

[vstinner]

@encukou:

Can you wait until the new guidelines are approved?

Ok, I close the issue.