Use mypy and ruff from pixi environment - #3124
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3124 +/- ##
==========================================
- Coverage 96.40% 96.40% -0.01%
==========================================
Files 280 280
Lines 16248 16250 +2
==========================================
+ Hits 15664 15665 +1
- Misses 584 585 +1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
valeriupredoi
left a comment
There was a problem hiding this comment.
thanks bud - a very welcome approach indeed! Approving preemptively (don't pull a Klaus on me since I approve drafts 😆 ) since I'll be away most next week
9dd9763 to
639434b
Compare
|
gotta be a solution to have pre-commit.ci work - let me dig around for a bit tomorrow |
|
hey @bouweandela we has pixi in the pre-commit CI environment! Unfortunately that pixi is newer than the pixi we have in the box, so it says we should |
Description
Use mypy and ruff from the pixi environment instead of installing them with pre-commit.
Pros
mypyandruffcan be used without pre-commit. Useful if you want to run these tools with additional options, e.g.ruff check --fix --unsafe-fixesCons
We could decide to move away from pre-commit.ci and instead just run the pre-commit hooks on CircleCI as part of the test suite. That would also have the advantage that it has one less CI service, so easier to understand for new contributors.
Link to documentation: https://esmvaltool--3124.org.readthedocs.build/projects/ESMValCore/en/3124/contributing.html#code-quality
Before you get started
Checklist
It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.
To help with the number pull requests: