Closed derpadoo closed 7 years ago
Thanks for this! I need to setup travis-ci to run tests and a linter as well at some point.
By the way your git config seems to have an issue based on the user associated to your commits. I'll wait for you to decide if you want to fix that or not before merging. Fixing it might involve re-playing the commits to a new branch and opening a new pull request.
Are you referring to the "invalid-email-address"? I'll probably create a new branch.
Created a new PR: https://github.com/rapid7/nexpose-client-python/pull/16
This one can be closed.
Description
Really excited for this project! After reviewing the code using a Atom's linter-pycodestyle 2.0.2 linter, I noticed there were quite a few PEP8 violations (https://www.python.org/dev/peps/pep-0008/). There is a mix of tabs/spaces for indentations, 1-2 new lines after classes/functions, testing conditional to None using "=" instead of none, and one-line if statements.
Motivation and Context
Standardizes files and makes them easier to read and debug. This is OCD, but it's better to address this early on in the project than later. In my linter config, I ignore error codes: E265, E266, E501 (http://pep8.readthedocs.io/en/release-1.7.x/intro.html). I addressed the cosmetic ones and didn't touch functional ones that I am not sure what they do, like line 1380 in nexpose.py
requestor = lambda: self.RequestSiteScanHistory(site_or_id)
I also didn't touch imports that were not at the top of the file.
How Has This Been Tested?
Ran pytest
Types of changes
Replaced tabs with 4 spaces, added new lines after functions/classes, removed one-line if statements, added/removed spaces around variables, and added two spaces after end of lines that contained comments.
Checklist: