pyro-ppl / pyro-ppl/numpyro

Use type hints whenever possible

Open
#299 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

low priority refactor
Dominant language
Python
Stars
2.8k
Forks
315
Avg merge
3d 9h
Merged PRs (30d)
27

Description

Since we are using python 3, we can start taking advantage of type hints wherever possible.

Contributor guide

Open the contributing guide

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.

Research direction

No files, tests, or entry points are named. Start by surveying the Python source tree for existing type hints and decide which modules can be annotated consistently; done would require a defined scope and verification that the annotations do not disrupt the project.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.