END_ASYNC_FOR expects an undocumented argument in 3.14
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
Documentation
The dis documentation does not mention that END_ASYNC_FOR takes an argument under Python 3.14.
Also this opcode is now a backward jump which contrary to other backward jump opcode is not obvious from the name. Having new sets in opcode describing forward jumping and backward jumping opcode (rather than just jumping opcode) would be useful to third party libraries interacting with the bytecode (such as the bytecode lib).
Linked PRs
- gh-142281
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the dis documentation and the linked PR gh-142281, then inspect the opcode definitions involved in END_ASYNC_FOR and the existing jump-opcode sets. Done means documenting the argument and backward-jump behavior and adding clear forward/backward opcode sets if the linked work still requires it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100