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

Full type checking pyright coverage

Open
#169 2 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
tooling

Research direction

Start by reviewing how migrated OpenInference libraries are currently opted out of pyright and where the agent skill applies. Define the instrumentation coverage and enforcement boundary, then verify that existing code and new changes pass pyright.

Written by the indexing model from the issue text.

Description

Adding type annotations and getting pyright passing is not in scope for migrated OpenInference libs. The skill we use tells the agent to opt the package out of pyright checking.

This is good for the initial pass, but it would be much better to have static coverage for instrumentations, and required any new code to pass type checking.

Originally posted by @lmolkova in https://github.com/open-telemetry/opentelemetry-python-genai/pull/143#discussion_r3463754653

Dominant language
Python
Stars
47
Forks
102
Avg merge
2d 13h
Merged PRs (30d)
111

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 open-telemetry/opentelemetry-python-genai

All issues in open-telemetry/opentelemetry-python-genai

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.