Add PyTuple_FromArray

[bschoenmaeckers]

Avoids creating tuples using mutation api's.

This will add a additional Py_INCREF + Py_DECREF on the tuple items, so this may be slower.

[codspeed-hq]

Merging this PR will not alter performance

✅ 105 untouched benchmarks
⏩ 1 skipped benchmark¹

---

_{Comparing bschoenmaeckers:tuple_from_array (970d57d) with main (c24a951)}

Footnotes

1. 1 benchmark was skipped, so the baseline result was used instead. If it was deleted from the codebase, click here and archive it to remove it from the performance reports. ↩

[davidhewitt]

It might be possible to reclaim some peformance loss here by making an array of borrowed rather than owned values at the callsites of array_into_tuple, so only owned references actually get the incref/decref cycle.

Alternatively, if this is for RustPython, could gate this path on #[cfg(RustPython)]?

[bschoenmaeckers]

It might be possible to reclaim some peformance loss here by making an array of borrowed rather than owned values at the callsites of array_into_tuple, so only owned references actually get the incref/decref cycle.

Thanks! Using Borrowed gives some performance back indeed. But it still has some small performance hit (for owned IntoPyObject results).

Alternatively, if this is for RustPython, could gate this path on #[cfg(RustPython)]?

If the performance hit is too large, I will consider adding support for RustPython cfg.

[davidhewitt]

I asked about the question of switching entirely for 3.15 at python/cpython#127058 (comment)

[bschoenmaeckers]

I've removed the compat function and made it only available on python 3.15 & RustPython. Because of the slowdown I only actually use it for RustPython.

[bschoenmaeckers]

Thanks!