Formatters and static code analysis roadmap
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 30
- Forks
- 13
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 8
Description
Formatters
- black
- isort
Flake8
- flake8
- flake8-sfs
- flake8-bugbear
- flake8-docstrings, needs more discussion, because we are not even consistent in other projects of ours
- flake8-simplify
- flake8-no-u-prefixed-strings, this PR
- flake8-future-import, this PR
- flake8-tidy-imports, this PR
Mypy
- mypy, includes searching all
# type:comments and converting them to Python 3 syntax
After all of those are done we can look into using LintLizard
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the unchecked flake8-docstrings discussion in PR 256 and the mypy item, including its request to search and convert # type: comments; done means the relevant roadmap items are resolved and reflected in this checklist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100