-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Confusing "Could not resolve module" errors when verifying types of a sub-package. #9529
Comments
The I tried installing prefect using I'm going to close the issue because I think that pyright is working correctly. If I misunderstood the issue or missed something, let me know. |
That's not the right reproducer. I didn't run the command in the repository, I used From my report:
Perhaps that's not supposed to work either but let's make that explicit if so. |
…fytypes` while targeting a submodule within a package and that submodule is a single-file module. This addresses #9529.
This is addressed in pyright 1.1.391. |
I tried to use the
--verifytypes
option on a submodule of a Python project. This works, except that the Public modules section contains a series of errors that indicates that pyright tried to resolve other submodules of the same project against the selected submodule.Concretely, the project in question is
prefect
, where I wanted to validate their public SDK packageprefect.main
; the command line used ispyright --verifytypes prefect.main
, and the resulting public modules section output is:The rest of the report is still extremely useful and as far as I am aware, correct.
Reproduce with:
Context
The text was updated successfully, but these errors were encountered: