inconsistency in 3.13 LOAD_GLOBAL docs
Open
Nobody has claimed this yet.
docs
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
LOAD_GLOBAL was changed in 3.11 to push NULL before callable if low bit of argument (namei) is set. But since CALL instruction now expects NULL|self after callable, shouldnt it now push NULL after callable?
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 with the Python 3.13 documentation for the LOAD_GLOBAL and CALL instructions, comparing the described NULL and callable ordering. Confirm whether the wording is inconsistent, then update the relevant documentation so the relationship between both instructions is accurate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100