-
Notifications
You must be signed in to change notification settings - Fork 326
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 import error #6425
Comments
Moreover, if I run this in
(where
|
Pavel Marek reports a new STANDUP for today (2023-05-22): Progress: - Looking into where the error message stems from
|
Pavel Marek reports a new STANDUP for yesterday (2023-05-23): Progress: - More improvements It should be finished by 2023-05-25. |
Run:
It will print:
I don't understand what Imports must have a valid module path. means in this context. The path is valid.
The real issue is that I think renaming imports are not supported this way.
Instead to make this work I'd have to write:
OK, but the error telling me that the first syntax I tried is not supported should ideally be a bit clearer - there is no module path issue.
I think this boils down to the issue that we have:
so this seems to be a constant message for
InvalidImport
, but apparently there is more than this one way for an import to be invalid - I think we may need more granular error reporting here.The text was updated successfully, but these errors were encountered: