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

[v2] Update ruff rules #2416

Open
21 tasks
Tracked by #1791
Samoed opened this issue Mar 23, 2025 · 1 comment
Open
21 tasks
Tracked by #1791

[v2] Update ruff rules #2416

Samoed opened this issue Mar 23, 2025 · 1 comment
Labels
v2 Issues and PRs related to `v2` branch

Comments

@Samoed
Copy link
Collaborator

Samoed commented Mar 23, 2025

I think we can enable:

  • T20 - flake8-print print found
  • ERA - Found commented-out code
  • B - flake8-bugbear.
  • A - flake8-builtins. To see if shadow builtins functions
  • LOG - flake8-logging. Simple logging checkers
  • ICS - flake8-implicit-str-concat
  • ICN - flake8-import-conventions
  • PT - flake8-pytest-style
  • RET - flake8-return
  • SIM - flake8-simplify
  • PTH - flake8-use-pathlib
  • NPY - NumPy-specific rules
  • PD - pandas-vet
  • N - pep8-naming
  • W - pycodestyle warnings (now only errors are enabled)
  • DOC - pydoclint
  • RUF - Ruff-specific rules

Possible:

  • ANN - flake8-annotations. if we want better type annotations
  • TID - flake8-tidy-imports. Will use absolute imports instead of relative
  • TC - flake8-type-checking
  • ARG - flake8-unused-arguments
@Samoed Samoed added the v2 Issues and PRs related to `v2` branch label Mar 23, 2025
@KennethEnevoldsen
Copy link
Contributor

I would take one or a couple of these at a time. Then it is also possible to review what influence they have.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v2 Issues and PRs related to `v2` branch
Projects
None yet
Development

No branches or pull requests

2 participants