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

Burst down the lint package into 5 files #3516

Conversation

Pierre-Sassoulas
Copy link
Member

Description

This permits to have smaller files and easier reading of them in the lint packages. The Pylinter class is still huge but this would require too much work to refactor.

Type of Changes

Type
🔨 Refactoring

@coveralls
Copy link

Coverage Status

Coverage increased (+0.007%) to 90.449% when pulling e06535d on Pierre-Sassoulas:one-class-per-file-in-lint-package into 0f88ff2 on PyCQA:master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage increased (+0.007%) to 90.449% when pulling e06535d on Pierre-Sassoulas:one-class-per-file-in-lint-package into 0f88ff2 on PyCQA:master.

@Pierre-Sassoulas Pierre-Sassoulas merged commit be5a61b into pylint-dev:master Apr 26, 2020
@Pierre-Sassoulas Pierre-Sassoulas deleted the one-class-per-file-in-lint-package branch April 26, 2020 14:14
@doublethefish
Copy link
Contributor

Given you touched check_parallel it might have been a nice idea to take #3474 first, which puts it under test.

Having fixed the import issues, the tests in PR #3474 no longer pass. Can you have a look at fixing them, please.

@@ -43,8 +43,6 @@
# Licensed under the GPL: https://www.gnu.org/licenses/old-licenses/gpl-2.0.html
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Pierre-Sassoulas We should keep these two lines in each file since they are not added by https://github.com/PCManticore/copyrite (which is the tool I was using for adding the copyright notices).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, I'm going to fix this, sorry.

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

Successfully merging this pull request may close these issues.

4 participants