fix(travis): review build step requirements and docs

Author: KaiSchwarz-cnic

.travis.yml

@@ -19,10 +19,14 @@ before_install:
 - npm prune
 install:
 - npm i
+- pip install -r requirements.txt
 before_script:
 - npm run lint
 script:
 - npm run test
+- "./scripts/pep8check.sh"
 after_success:
 - if [[ "$TRAVIS_BRANCH" == "master" && "$TRAVIS_PULL_REQUEST" == "false" ]]; then
-    npx travis-deploy-once "npx semantic-release" ; fi
+    git config --replace-all remote.origin.fetch +refs/heads/*:refs/remotes/origin/*
+    && git fetch --tags
+    && npx travis-deploy-once "npx semantic-release" ; fi

AUTHORS.md

@@ -0,0 +1,4 @@
+> ⚠ This document _only_ reflects the responsible developers at HEXONET GmbH. For a list of MUCH-APPRECIATED CONTRIBUTORS -- people who helped developing and extending this library, applying patches, adding helpful comments
+and thus generally made it that much better, see [GitHub's list of contributors](https://github.com/hexonet/python-sdk/contributors).
+
+* [Kai Schwarz](//github.com/papakai) - Full Review

CONTRIBUTING.md

@@ -0,0 +1,85 @@
+# Contributing
+
+When contributing to this repository, please first discuss the change you wish to make via issue,
+email, or any other method with the owners of this repository before making a change.
+
+Please note we have a code of conduct, please follow it in all your interactions with the project.
+
+## Pull Request Process
+
+Read [here](https://github.com/hexonet/idna-uts46/wiki/Development-Guide#pull-request-pr-procedure).
+
+## Code of Conduct
+
+### Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+### Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+### Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+### Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+### Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team. All complaints will be reviewed and
+investigated and will result in a response that is deemed necessary and appropriate
+to the circumstances. The project team is obligated to maintain confidentiality
+with regard to the reporter of an incident. Further details of specific enforcement
+policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+### Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

LICENSE.txt LICENSE

@@ -43,7 +43,7 @@
     "test-MOCHA": "./node_modules/.bin/_mocha $(find ./test -type f -name '*.spec.js')",
     "test-COVERAGE": "cross-env NODE_ENV=development nyc npm run test-MOCHA --silent",
     "lint": "eslint --fix --config=./.eslintrc.js uts46.js README.md *.json test/*.spec.js && npm run lint-python",
-    "lint-python": "autopep8 -i -a -a *.py",
+    "lint-python": "./scripts/pep8fix.sh",
     "semantic-release": "semantic-release"
   },
   "dependencies": {
@@ -103,4 +103,4 @@
       "@semantic-release/github"
     ]
   }
-}
+}

package.json

@@ -0,0 +1,4 @@
+autopep8==1.4.4
+pep8==1.7.1
+pip==19.0.3
+pycodestyle==2.5.0

requirements.txt

@@ -0,0 +1,2 @@
+#!/bin/bash
+pycodestyle --first --show-source --show-pep8 setup.py hexonet/apiconnector/*.py tests/*.py

scripts/pep8check.sh

@@ -0,0 +1,2 @@
+#!/bin/bash
+autopep8 -i -a -a ./*.py