GeezerVison

All commit authors signed the Contributor License Agreement.

@ashm-dev, one thing worth a look from you: I changed an assertion in test_reentrant_detach_during_read, which came from #157370. It asserted the ValueError from wrapper.buffer; the test's subject is that the buffer survives the read and the wrapper does not crash, which still passes, so it now asserts wrapper.buffer is None.

Before gh-157364 the attribute was a member descriptor, so a detached wrapper read as None, and _pyio still returns None. If you would rather keep that test untouched, I can restore the old assertion and move the None expectation somewhere else, but the two behaviours cannot both hold.

Need to work out what the right behavior here is before getting to a PR. Ideally get an agreement in the issue first, then once have that can work on a PR. In this case that means propose the change you'd like to make there and wait for a python triager or developer to figure out if that is the right direction.

Fair. I will take the behaviour question to gh-160427 and hold this as a draft until a triager or developer settles it.

Noted on gh-160472 being closed as a duplicate, and the parity point: when the behaviour question on gh-160427 is settled, the _pyio half will go into this same PR so _io and _pyio land together rather than as two changes.

Closing this draft: gh-160427 is still undecided, and cmaloney has raised reverting gh-157364, which would remove the case entirely. The branch stays on my fork and goes into a fresh PR if a fix is still wanted once a triager or developer settles it.