python / python/docs-community
How to communicate the philosophy of type annotations in Python?
Open
Nobody has claimed this yet.
discussion
- Dominant language
- Makefile
- Stars
- 55
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
A question from the Typing summit:
How to communicate the philosophy of type annotations in Python?
- Beginners don't need annotations
- "Catching bugs" is how to sell it to your engineering director :-)
- Adding improvements like new Union to simplify the syntax
There's a nice community around typing that is responsive to ideas and thoughts.
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 the question and the referenced Typing summit context; no documentation file, test, or entry point is identified. Clarify the intended audience and desired documentation outcome with the typing community, then record an agreed explanation of the philosophy of Python type annotations.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100