-
-
Notifications
You must be signed in to change notification settings - Fork 143
GH1222 Candidate for ty on pandas-stubs #1240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could start including this as part of the regular CI - and we'd want to test it locally and with the stubs installed as well. If we start seeing a lot of failures, we could then move it to only run on doing a merge.
Co-authored-by: Irv Lustig <[email protected]>
Agreed with adding it to the CI, for how it would only be for pandas-stubs and not the tests as the project is still experimental there is a lot to do and understand on the tests side. Worst case if we see it as a blocker on velocity we can bring it to merge only. Let me do the changes |
Right now this would run with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @loicdiridollou you'll have to keep an eye on version improvements on ty
so that pyproject.toml
gets properly updated.
assert_type()
to assert the type of any return valueProposal to have ty on pandas-stubs, on tests there are still a lot of errors that come back as TODO from ty and the inference is a bit unclear for many tests (or it comes back as Unknown so would need more investigation and learning on my end).