CACHE and SWAP documentation is vague with the meaning of the oparg

[MatthieuDartiailh]

Documentation

The current documentation says that CACHE and SWAP acts on the ith element of the stack but it is nowhere mentioned if the stack is indexed from 0 or 1. Looking at the actual implementation in ceval.c makes the answer obvious but it is tedious and the documentation could be improved I believe.

• PR: gh-96461: clarify the meaning of the oparg for CACHE and COPY opcode  #96462

[hauntsaninja]

Should this PR have been backported to 3.11?

[MatthieuDartiailh]

It could be but 3.12 already changed quite a bit the bytecode and the back port would not be straightforward.

[hauntsaninja]

Okay, thanks, I'll close this then :-)