You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've encountered a few cases where users were baffled when they found out that a certain error (to them obvious) was not reported, and the reason was that some essential file was excluded due to use of the --silent-imports (-s) flag.
It seems to be particularly baffling when there's a base class that comes from a silenced import. See e.g. #1363 -- once we fix that, there remains the problem that Base has type Any and so in Derived, self has effectively type Any (as do all other instances of Derived).
One possibility would be to have an option that's just like --silent-imports but which reports an error at every suppressed import (possibly displaying a different message depending on whether the module was found or not). This option might also add an additional message when a base class is undefined due to a missing import.
Another approach might be to treat this as a new reporting option.
The text was updated successfully, but these errors were encountered:
We've encountered a few cases where users were baffled when they found out that a certain error (to them obvious) was not reported, and the reason was that some essential file was excluded due to use of the --silent-imports (-s) flag.
It seems to be particularly baffling when there's a base class that comes from a silenced import. See e.g. #1363 -- once we fix that, there remains the problem that Base has type Any and so in Derived, self has effectively type Any (as do all other instances of Derived).
One possibility would be to have an option that's just like --silent-imports but which reports an error at every suppressed import (possibly displaying a different message depending on whether the module was found or not). This option might also add an additional message when a base class is undefined due to a missing import.
Another approach might be to treat this as a new reporting option.
The text was updated successfully, but these errors were encountered: