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.env` 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 inventorying the public members of jaraco.env and reading the linked skeleton issue and pull-request discussion for the project's typing expectations. Done means the public members are fully annotated, or covered to the stated best-effort standard, before the package is marked as py.typed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- developer-experience
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100