Fully type module then mark as `py.typed`
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
This is an issue to track `jaraco.input` being marked as `py.typed`.
I'd rather not lie about the typed state of a library and wait until all its public members are fully annotated (or at least to a "best effort") before being marked as `py.typed`.
Refs:
- https://github.com/jaraco/skeleton/issues/98
- https://github.com/jaraco/skeleton/pull/136#discussion_r1714057809
- https://github.com/jaraco/skeleton/issues/143
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by inspecting the public members of jaraco.input and the typing guidance in the linked skeleton issues and pull request discussion. Identify the remaining annotations needed, then verify the package can truthfully be marked py.typed; done means its public API is fully annotated or meets the stated best-effort standard.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100