Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
black, isort, and doc8 - should we use them in our CI?
See original GitHub issueblack is an extremely popular tool for automatically formatting Python code to match the very opinionated black coding standard.
isort is a tool for automatically sorting Python imports to match a given style.
doc8 is a Sphinx style checker.
mypy is an optional static type checker
Should we incorporate one or more of these tools into our CI process similar to how we have incorporated flake8? Of course, we can tweak the default configuration for each of these tools to make them match our stylistic preferences if we desire.
Issue Analytics
- State:
- Created 3 years ago
- Comments:13 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@xNinjaKittyx Since we went ahead and made the various CI improvements using GitHub actions, albeit not use pre-commit hooks, I"m thinking of deleting your
ci_improvementsbranch as part of some cleanup. But I’ll wait a week or so in case you plan on doing anything more with that branch.I don’t have much knowledge into github actions, maybe i’ll check it out sometime in the future. Feel free to delete the branch, thanks for letting me know!