jaraco / jaraco/jaraco.develop

Fully type module then mark as `py.typed`

Open
#22 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
7
Forks
5
Avg merge
20m
Merged PRs (30d)
1

Description

This is an issue to track `jaraco.develop` 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

No files, tests, or entry points are identified in the issue. Begin by inventorying jaraco.develop's public members and determining the current annotation coverage; completion means the public API is fully or best-effort typed and the package can be marked py.typed without misrepresenting its typed state.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.