feat: add py.typed marker for PEP 561 compliance#2267
Open
kalichiruvelli-art wants to merge 1 commit into
Open
feat: add py.typed marker for PEP 561 compliance#2267kalichiruvelli-art wants to merge 1 commit into
kalichiruvelli-art wants to merge 1 commit into
Conversation
kalichiruvelli-art
requested review from
PranavBhatP,
benHeid,
fkiraly,
fnhirwa,
jdb78,
phoeenniixx and
yarnabrina
as code owners
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
Adds an empty
py.typedmarker file to thepytorch_forecasting/package directory as specified by PEP 561.Problem
Type checkers (Pyright, Pylance, mypy) treat
pytorch-forecastingas untyped because there is nopy.typedmarker, causing warnings like:Stub file not found for "pytorch_forecasting"(reportMissingTypeStubs)Fix
pytorch_forecasting/py.typedmarker file (zero bytes, no logic changes)[tool.setuptools.package-data]entry inpyproject.tomlso the file is included in the built distributionNo logic changes, no new dependencies.