Add py.typed marker to google-iam-v1 for PEP 561 compliance

Open Beginner friendly
#16,200 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
python
Domain
build-system

Research direction

Start by inspecting the google/iam package and the distribution's MANIFEST.in or package_data configuration. Add the empty py.typed marker at the package root and verify that the built distribution includes it so mypy can resolve google.iam.v1 types without ignore_missing_imports.

Written by the indexing model from the issue text.

Description

priority: p2 type: bug

The google-iam-v1 package currently lacks a py.typed marker file. Even though the library contains type hints, static analysis tools like mypy fail to recognize them, resulting in the following error for downstream consumers:

error: Skipping analyzing "google.iam.v1": module is installed, but missing library stubs or py.typed marker

Include an empty py.typed file in the root of the google/iam package and ensure it is included in the MANIFEST.in or package_data of the distribution. This will allow mypy to resolve types without requiring ignore_missing_imports = True.

Dominant language
Python
Stars
5.4k
Forks
1.8k
Avg merge
1d 17h
Merged PRs (30d)
93

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.

More from googleapis/google-cloud-python

All issues in googleapis/google-cloud-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.