Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Fully type module then mark as `py.typed`

Open
#22 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

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.

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:

Dominant language
Python
Stars
7
Forks
5
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jaraco/jaraco.develop

All issues in jaraco/jaraco.develop

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.