-
Notifications
You must be signed in to change notification settings - Fork 9
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
Improve "code quality" #60
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One of the more innocuous PRs we've had, seems like it is a positive thing. Didn't want to merge this in case you had a preference for it going after #59.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine to me. Thanks for fixing the iter
issue.
iter = 0 | ||
_iter = 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh yeah. This definitely needed to be changed, since iter
is actually a reserved word right?
Improve "code quality"
Improve "code quality" baseline.
This PR just makes a bunch of fixes to the doctrings to bring the code quality up to a baseline that looks good enough to actually look over. Initially, there were a slew of failing marks because of the docstrings and imports, and these were so distracting that you couldn't barely even see the real issues in the code.
The code quality check I turned on should help us identify bad code practices in the code, and avoid code problems in the future. I'll open an issue to address the remaining issues identified by the code quality assessment.