-
Notifications
You must be signed in to change notification settings - Fork 3
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
Check fails for submodules #1
Comments
No, it actually wants you to type I see where you're coming from, and it makes sense. Maybe it should be an option at least. The convention that birthed this module was basically to never use However, the error message is definitely wrong. It should say |
Ability to configure the project and relax some constraints would be super useful! |
Since relative imports don't work with the `import <>` syntax, suggest importing the names directly. In this cases, the `i.module` is `None` and the `i.level` has the number of levels down in the relative import, e.g. `1` means the current directory. If there's only one name, suggest: use 'import module.name' instead of 'from module import name' This implements the enhancement proposed in sfstpala#1.
Since relative imports don't work with the `import <>` syntax, suggest importing the names directly. In these cases, the `i.module` is `None` and the `i.level` has the number of levels down in the relative import, e.g. `1` means the current directory. If there's only one name, suggest: use 'import module.name' instead of 'from module import name' This implements the enhancement proposed in sfstpala#1.
Current behaviour:
Checks should pass for second file, shouldn't they?
The text was updated successfully, but these errors were encountered: