Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
ENH: Bring over Microsoft typing stubs as starting point for typing public API
See original GitHub issueFrom discussion on pandas typing meeting on January 7, 2022 (notes at https://docs.google.com/document/d/1tGbTiYORHiSPgVMXawiweGJlBw5dOkVJLY-licoBmBU/)
Follow up to discussion here: #28142 (comment)
Goal is to copy over the pandas stubs created by Microsoft that are shipped with Visual Studio Code: https://github.com/microsoft/python-type-stubs/tree/main/pandas
Unclear whether this should be done a file at a time, or all at once. Need to resolve conflicts between the pandas source and those stubs. Possible to publish partial stubs by indicating they are partial within a py.typed file.
@gramster (main author of the Microsoft stubs)may be willing to help (nudge, nudge)
Ideally, the testing framework for the stubs should be created first. See #45252
Issue Analytics
- State:
- Created 2 years ago
- Comments:12 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Have created the https://github.com/pandas-dev/pandas-stubs project from MS stubs.
It looks like I should just be able to open these tests in VS Code with Pylance and see any issues. I am doing that and I don’t see the very first issue, but I’m also using latest stubs from the repo and it looks like you have made some changes, Irv. So I will look at the things that are still being squiggled.
Of course, that means I am assuming that these test snippets should be clean and free of warnings; is that a correct assumption?