python / python/typing-council
Review Request: PEP 835 – Shorthand syntax for Annotated type metadata
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 57
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Please provide a recommendation for PEP 835.
The current draft addresses the core technical feedback from the community thread, specifically regarding annotationlib safety, migration impact, and establishing strict metaclass boundaries to protect runtime matrix multiplication. Prototype implementations for CPython, Mypy, Pyright, and Ruff are complete and linked in the PEP.
- PEP: https://peps.python.org/pep-0835/
- Discourse: https://discuss.python.org/t/pep-835-shorthand-syntax-for-annotated-type-metadata/107814
- Sponsor: @ilevkivskyi
TC Sign-off
- Carl
- Dave
- Jelle
- Joren
- Rebecca
Contributor guide
No contributing guide indexed for this repository
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 PEP 835 and the linked Discourse thread, then review its discussion of annotationlib safety, migration impact, and metaclass boundaries. Check the linked CPython, Mypy, Pyright, and Ruff prototypes for context. Done means forming a recommendation and updating the TC sign-off checklist as the council reaches decisions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100