Skip to content
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

disable for too-many-lines must go on first line of module #321

Closed
pylint-bot opened this issue Aug 24, 2014 · 2 comments
Closed

disable for too-many-lines must go on first line of module #321

pylint-bot opened this issue Aug 24, 2014 · 2 comments
Labels

Comments

@pylint-bot
Copy link

Originally reported by: Radek Holý (BitBucket: PyDeq, GitHub: @PyDeQ?)


Quoting https://mail.python.org/pipermail/code-quality/2013-December/000191.html:

"[...] it seems that the disable comment for C0302 HAS to go on the first line. This gets awkward because one has to mix it with the shebang line [...]"


@pylint-bot
Copy link
Author

Original comment by Claudiu Popa (BitBucket: PCManticore, GitHub: @PCManticore):


Issue #340 was marked as a duplicate of this issue.

@pylint-bot
Copy link
Author

Original comment by Claudiu Popa (BitBucket: PCManticore, GitHub: @PCManticore):


'too-many-lines' disable pragma can be located on any line, not only the first.

Closes issue #321.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant