add .travis.yml #31
40
.travis.yml
|
|
@ -1,13 +1,35 @@
|
|||
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
sudo: false
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
dist: xenial
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
language: python
|
||||
python:
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
- "3.4"
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
- "3.5"
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
- "3.6"
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
- "pypy3"
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
# command to install dependencies
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
matrix:
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
include:
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
- python: 3.5
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
env: TOXENV=py35
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
- python: 3.6
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
env: TOXENV=py36
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
- python: 3.7
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
env: TOXENV=py37
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
- python: pypy3
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
env: TOXENV=pypy3
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
- python: 3.5
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
env: TOXENV=pep8
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
- python: 3.7
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
env: TOXENV=pep8
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
cache:
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
directories:
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
- $HOME/.cache/pip
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
install:
|
||||
- pip install -r requirements.txt
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
- pip install tox-travis
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
# command to run tests
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
- pip install tox
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
- if [[ $TOXENV == py* ]]; then pip install coveralls; fi
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
script:
|
||||
- tox
|
||||
|
you probably want to add flake8 also you probably want to add flake8 also
oh, unless you run it via tox oh, unless you run it via tox
|
||||
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
notifications:
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
email: false
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
after_success:
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
- if [[ $TOXENV == py* ]]; then coveralls; fi
|
||||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
|
|
|
|||
|
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally
|
||||
50
tox.ini
|
|
@ -9,7 +9,7 @@ envlist =
|
|||
mypy
|
||||
pep8
|
||||
docs
|
||||
skip_missing_interpreters = true
|
||||
skip_missing_interpreters = True
|
||||
|
||||
[flake8]
|
||||
# Use the more relaxed max line length permitted in PEP8.
|
||||
|
|
@ -23,47 +23,17 @@ import-order-style = google
|
|||
application-import-names = netbox_agent
|
||||
|
||||
[testenv]
|
||||
setenv =
|
||||
COVERAGE_FILE = .coverage.{envname}
|
||||
# This is required in order to get UTF-8 output inside of the subprocesses
|
||||
# that our tests use.
|
||||
setenv = LC_CTYPE = en_US.UTF-8
|
||||
# Pass Display down to have it for the tests available
|
||||
passenv = DISPLAY TRAVIS TRAVIS_JOB_ID TRAVIS_BRANCH
|
||||
whitelist_externals=convert
|
||||
deps =
|
||||
-r{toxinidir}/requirements.txt
|
||||
# -r{toxinidir}/dev-requirements.txt
|
||||
# commands =
|
||||
# # Use -bb to enable BytesWarnings as error to catch str/bytes misuse.
|
||||
# # Use -Werror to treat warnings as errors.
|
||||
# # Must ignore a DeprecationWarnings triggered in pytest until the following are fixed:
|
||||
# # https://github.com/pytest-dev/pytest/issues/1403
|
||||
# # https://github.com/pytest-dev/pytest/issues/4507
|
||||
# # Must ignore DeprecationWarnings in virtualenv site.py only if supporting Travis CI
|
||||
# # Python 3.5 environments that bundle an older version of virtualenv.
|
||||
# python -bb \
|
||||
# -Werror -Wignore:::_pytest.assertion.rewrite -Wignore:::_pytest.tmpdir -Wignore:::site \
|
||||
# -m pytest --cov="{envsitepackagesdir}/fact"
|
||||
|
||||
# [testenv:coverage]
|
||||
# skip_install = true
|
||||
# depends = py35,py36,py37
|
||||
# # Set blank setenv to overwrite setenv from [testenv] (inherited).
|
||||
# setenv =
|
||||
# deps =
|
||||
# -r{toxinidir}/dev-requirements.txt
|
||||
# commands =
|
||||
# coverage combine
|
||||
# coverage html
|
||||
|
||||
# [testenv:mypy]
|
||||
# skip_install = true
|
||||
# setenv =
|
||||
# deps =
|
||||
# -r{toxinidir}/requirements.txt
|
||||
# -r{toxinidir}/dev-requirements.txt
|
||||
# commands =
|
||||
# mypy src
|
||||
|
||||
[testenv:pep8]
|
||||
skip_install = true
|
||||
setenv =
|
||||
deps =
|
||||
-r{toxinidir}/dev-requirements.txt
|
||||
commands =
|
||||
flake8 netbox_agent tests
|
||||
flake8
|
||||
pep8-naming
|
||||
commands = flake8 {toxinidir}/netbox_agent {toxinidir}/tests
|
||||
|
|
|
|||
always good to add pypy (and pypy3) to the list as it's a completely different interpreter, it can raise some interesting issues that you wouldn't see normally