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

Might be some things to learn from paulross/typin

Open
  • Is something wrong?
#65 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
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Start by comparing pyannotate's current goals with the linked paulross/typin project, especially src/typin/types.py around line 537 and its type-aware documentation-string example. Determine whether that behavior fits pyannotate and turn the suggestion into a concrete, testable scope before implementation.

Written by the indexing model from the issue text.

Description

Here is a similar project with some of the same goals as pyannotate: https://github.com/paulross/typin

There might be something useful in there for you. Injecting type aware documentation strings for example: https://github.com/paulross/typin/blob/master/src/typin/types.py#L537

Now that I have discovered pyannotate I doubt I will progress typin as it was just a side project!

Dominant language
Python
Stars
1.4k
Forks
59
No merged PRs in 30d

Getting set up

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 dropbox/pyannotate

All issues in dropbox/pyannotate

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.