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

Add pylint to CI #290

Merged
merged 1 commit into from
Jan 11, 2023
Merged

Add pylint to CI #290

merged 1 commit into from
Jan 11, 2023

Conversation

berland
Copy link
Contributor

@berland berland commented Jan 6, 2023

Currently every current pylint issue is exempted.

Excemptions (disables) in .pylintrc are to be removed one-by-one in upcoming PRs.

@berland
Copy link
Contributor Author

berland commented Jan 6, 2023

See #289

@berland berland changed the title Add pylint to ci Add pylint to CI Jan 6, 2023
@@ -39,3 +40,7 @@ jobs:
- name: Lint with flake8
Copy link
Member

Choose a reason for hiding this comment

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

Just a question: is the idea that pylint will replace flake8, maybe when its errors have been dealt with? Or do we normally have both on a project?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We will run both.

.pylintrc Outdated
@@ -0,0 +1,63 @@
[MESSAGES CONTROL]
Copy link
Member

Choose a reason for hiding this comment

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

Instead of having a dot file to control pylint, it might be preferable to put its options in setup.cfg (and, eventually, pyproject.toml if/when we move to PEP621-style packaging).

The disable list would go into a [pylint.messages control] section of setup.cfg.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks, that made it prettier. Used setup.cfg.

@berland berland self-assigned this Jan 9, 2023
@berland berland mentioned this pull request Jan 9, 2023
@berland berland force-pushed the pylint_in_ci branch 2 times, most recently from 4de83b7 to d4715c0 Compare January 9, 2023 13:35
@berland berland requested a review from kwinkunks January 10, 2023 08:46
@@ -27,6 +27,7 @@ jobs:

- name: Install dependencies
run: |
pip install .
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@xjules , it seems your comment here has been lost. This line is added in order to let pylint check that everything is importable, so this is used only to get the dependencies in, not to get komodo itself in.

Copy link
Contributor

@xjules xjules left a comment

Choose a reason for hiding this comment

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

🚀 🍴

Currently every current pylint issue is exempted.

Excemptions (disables) in .pylintrc are to be removed one-by-one in
upcoming PRs.
@berland berland merged commit d1beced into equinor:main Jan 11, 2023
@berland berland deleted the pylint_in_ci branch September 27, 2023 19:56
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.

3 participants