[MAINTENANCE] only provide py.typed
files for fully typed sub-packages
#7438
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.
Changes proposed in this pull request:
py.typed
from the top-levelgreat_expectations
packagepy.typed
file markers for sub-packages that are fully typeddatasource/fluent
-datasource/
has one untyped module that prevents us from putting it at the top-levelexecution_engine
https://peps.python.org/pep-0561/#packaging-type-information
See below for the modules we currently don't type-check.
Note: This doesn't mean that anything not in this list is "typed" it just means we run the type-checker against it. So any types we do declare should be correct. See
mypy
section on "dynamically typed code"great_expectations/pyproject.toml
Lines 50 to 202 in 95f1c37