It isn't possible to temporarily resurrect objects safely in the Py3.15t limited API

Bug report

Bug description:

In Cython we do something like

Py_SET_REFCNT(o, Py_REFCNT(o) + 1);
// Run user implemented deallocation code
Py_SET_REFCNT(o, Py_REFCNT(o) - 1);

The reason for this is that we don't want any refcounting (e.g. of temps) within the user code to accidentally trigger a recursive call to dealloc (the user code really shouldn't resurrect the object and it's their own problem if they do, but it is reasonable for it to generate temporaries, which may well be out of their control anyway).

This turns out not to be thread-safe in the freethreaded build because it makes TryIncRef succeed. Outside the limited API it's possible to fix by manual access to the reference count, but obviously not inside the limited API.

It would be nice to have a way of to avoid this.

• Most convenient would be to properly access _PyObject_ResurrectStart and _PyObject_ResurrectEnd.
• The other thing that could work is some way to defer the deallocation until the next GC cycle (when I think any TryIncRefs would have fall out of scope anyway). I suspect I could manually arrange to do that, although it feels fragile, possibly relies on the GC being single-threaded, and which I haven't tested (so may not work...)

CPython versions tested on:

3.15

Operating systems tested on:

No response

まず、ここで説明されている参照カウントの復活と free-threaded の TryIncRef 動作に関係する limited-API の範囲を確認し、次に _PyObject_ResurrectStart と _PyObject_ResurrectEnd、および Cython issue #7769 と比較してください。ユーザーの解放処理コード中に安全でない一時的な復活を回避する、定義済みでスレッドセーフな limited-API のメカニズムが実現されれば完了です。