fix(packaging): publish py.typed marker for mypy consumers#10
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary:\n- add setuptools package-data config so pipeworks_ipc includes a py.typed marker in distributions\n- add pipeworks_ipc/py.typed to advertise inline typing support to type checkers\n- add a packaging regression test that asserts the marker is present at runtime\n\nValidation:\n- pyenv exec pytest -q\n- RUFF_CACHE_DIR=/tmp/ruff-cache-pipeworks-ipc pyenv exec ruff check pipeworks_ipc tests\n- pyenv exec black --check pipeworks_ipc tests\n- pyenv exec mypy pipeworks_ipc\n\nContext:\nThis fixes downstream mypy import-untyped failures in consumer repos that import pipeworks_ipc.