-
Notifications
You must be signed in to change notification settings - Fork 45
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
Use pylint to ensure code quality - 5 errors were detected #82
Comments
|
could you push a PR with pylint formatted files? Also a good idea would be to add a pre-commit config to run linters and formatters each time someone is doing a commit |
I added |
I'll take a look later today |
Looks better now but @mkalioby please remove all unused files and imports |
I think what matters is to establish and enforce some "quality control" rules...
I wanted to mention that earlier in the "adding pytest" pull request but I was waiting for the dev to be merged with main. Once there is a way to run tests, you could automate running tests with actions and establish some rules regarding pull requests. Eventually you will see there is little need for the "dev" branch, and you will be using feature branches, tags, and releases. Patching bugs will be faster and publishing new versions will also be faster. The miracles that DevOps concepts brings from manufacturing sector to the IT world. |
Pylint is a linter for python, there are several plugins for different frameworks and use cases such as the pylint-django plugin.
Using pylint with pylint-django plugin I got the following result:
install it with:
And the full output...
The text was updated successfully, but these errors were encountered: