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

ci: add flake8 tests #3

Merged
merged 1 commit into from
Dec 13, 2023
Merged

Conversation

vicentebolea
Copy link
Collaborator

No description provided.

@vicentebolea vicentebolea enabled auto-merge (squash) December 8, 2023 23:45
@vicentebolea vicentebolea force-pushed the add-flake8-ci branch 3 times, most recently from 96c32dc to 7512341 Compare December 11, 2023 23:33
@vicentebolea
Copy link
Collaborator Author

@alesgenova

@jcfr
Copy link
Member

jcfr commented Dec 12, 2023

I suggest to adopt ruff instead of the obsolete flake8.

You may be interested in https://learn.scientific-python.org/ where we maintain templates:

@alesgenova
Copy link
Member

Looks like ruff is gaining quite some traction, pyvista is also just switching to it: pyvista/pyvista#5304

@vicentebolea
Copy link
Collaborator Author

Thanks for the suggestion. I must ask, how is flake8 obsolete? I can see that they support py 3.12 it is actively maintained, plus it seems to be still the "industry" standard for linting python code.

@jcfr
Copy link
Member

jcfr commented Dec 12, 2023

obsolete

What I meant is that considering that all1 rules have been have been implemented in Ruff, explicitly integrating flake8 tooling should be considered an obsolete practice.

The rules defined/discussed/developed under the flake8 project are still relevant.

Footnotes

  1. https://docs.astral.sh/ruff/rules/

@vicentebolea
Copy link
Collaborator Author

explicitly integrating flake8 tooling should be considered an obsolete practice

I understand that ruff has been chosen as the linting tool for scientific python cookie, this does not make using flake8 as an obsolete practice across python projects.

In any case, the feature is already developed in this PR, I am happy to move to something else if needed but I suggest to bring this to a discussion after merging this so we have linting asap.

@jcfr
Copy link
Member

jcfr commented Dec 12, 2023

I just wanted to point out that some useful resources intended to streamline overall python development, this should not prevent you from moving forward with this PR. When the time comes, consider @ me in the relevant discussion.

@vicentebolea
Copy link
Collaborator Author

@jcfr thanks for bringing ideas to help us with the development of this project. I am sure that ruff is a much better alternative, I was genuinely curious about the rationale of the claim as I could see some other big python project persisting in their use of flake8 and others versus ruff. Lets explore this later!

@vicentebolea vicentebolea merged commit 7dcd11f into Kitware:main Dec 13, 2023
4 checks passed
@vicentebolea vicentebolea deleted the add-flake8-ci branch December 13, 2023 20:09
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