-
-
Notifications
You must be signed in to change notification settings - Fork 600
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
Check adherence with sp-repo-review
guidelines
#3489
Comments
Output from running sp-repo-review locally
The |
Here's an updated output from Expand to view
@Saransh-cpp, it looks like we have a few MyPy-related issues here, could you ensure that they are fixed (or addressed as best they can based on feasibility) when you return to #3853? P.S. I'll take up the "Have unique names for artifacts" point soon. |
* #3489 Use unique artifact names for all jobs * Limit benchmarks results to PyBaMM repo
* pybamm-team#3489 Use unique artifact names for all jobs * Limit benchmarks results to PyBaMM repo
Hi, I see this is pending from a long time I would like to take upon the mypy part, can this issue be assigned to me? |
We will have a list of things to fix once #4897 is merged - [tool.repo-review]
ignore = [
"MY", # ignore all MyPy setting checks (MY101, MY103, MY104, MY105, MY106)
"PP004", # ignore the check that prevents an upper cap on Python requires
"PP308", # ignore the explicit pytest summary flag (-ra) check
"PC140", # ignore missing type checker in pre-commit
"PC160", # ignore missing spell checker in pre-commit
"PC180", # ignore missing markdown formatter in pre-commit
"RF102", # ignore the missing isort selection in Ruff configuration
] |
There are a lot of interesting things available in the Scientific Python ecosystem, perhaps we should also try using
sp-repo-review
?Originally posted by @agriyakhetarpal in #3390 (comment)
The text was updated successfully, but these errors were encountered: