Fully type module then mark as `py.typed`
- Dominant language
- Python
- Stars
- 2
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
This is an issue to track `jaraco.path` 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/pypa/setuptools/issues/2345
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no source files, tests, or entry points. Start by inventorying jaraco.path's public members and reviewing the linked typing discussions; done means the public API is annotated to a best-effort standard and the package can be marked py.typed without overstating its typed coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100