We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
__init__.py
__init__.py shouldn't be considered code, or at least it should be considered differently.
It doesn't make sense to enforce print_function, division on a file that only contains imports, a docstring, and perhaps __all__.
print_function
division
__all__
Perhaps a better option would be, don't enforce for an __init__.py file only having some subset of {imports, docstrings, comments, all = ...}?
Another option would be to have a separate --select or --ignore for __init__.py files.
--select
--ignore
The text was updated successfully, but these errors were encountered:
require-code=True solves this for empty __init__ files
require-code=True
__init__
Sorry, something went wrong.
If you don't want a specific error on non-empty __init__.py just add it to your per-file-ignores.
per-file-ignores
Should the require-code option also ignore imports?
require-code
No branches or pull requests
__init__.py
shouldn't be considered code, or at least it should be considered differently.It doesn't make sense to enforce
print_function
,division
on a file that only contains imports, a docstring, and perhaps__all__
.Perhaps a better option would be, don't enforce for an
__init__.py
file only having some subset of {imports, docstrings, comments, all = ...}?Another option would be to have a separate
--select
or--ignore
for__init__.py
files.The text was updated successfully, but these errors were encountered: