add more explanatory comments in test_proxy.use,
and prepare for rename of proxy2.py to proxy_server.py in next
commit (separate so that the rename can be seen as such).
Signed-off-by: Sebastien Awwad <sebastien.awwad@gmail.com>
- adds inaz2/proxy2.py, copied code.
- adds dev dependency on twisted for a simple proxy test
- adds a new test module, test_proxy_use, and runs those tests only in
Python2.7 (as proxy2 only supports Python2.7) using new logic in
aggregate_tests.py.
Signed-off-by: Sebastien Awwad <sebastien.awwad@gmail.com>
See comments on PR 778:
https://github.com/theupdateframework/tuf/pull/778
In short, pyup is trying to update dependencies that are active
only when Python2 is being used to versions that no longer
support Python2.
Signed-off-by: Sebastien Awwad <sebastien.awwad@gmail.com>
by specifying the appropriate versions of pylint and astroid
for Python2. pylint and astroid dropped Python2 compatibility
for their latest major revisions, so dev-requirements now pins
the latest compatible revision for Python2 if installing in a
Python2 environment.
Signed-off-by: Sebastien Awwad <sebastien.awwad@gmail.com>
Update astroid from 1.6.5 to 2.0.4
Update cryptography from 2.2.2 to 2.3
Update cryptography from 2.2.2 to 2.3
Update gitdb2 from 2.0.3 to 2.0.4
Update gitpython from 2.1.10 to 2.1.11
Update pbr from 4.0.4 to 4.2.0
Update pluggy from 0.6.0 to 0.7.1
Update py from 1.5.3 to 1.5.4
Update pylint from 1.9.2 to 2.1.1
Update pyyaml from 3.12 to 3.13
Update smmap2 from 2.0.3 to 2.0.4
Update stevedore from 1.28.0 to 1.29.0
Update tox from 3.0.0 to 3.2.1
Signed-off-by: Sebastien Awwad <sebastien.awwad@gmail.com>
pip install -r dev-requirements.txt using Python3 currently
breaks due to futures 3.2.0 not being available for Python3.
dev-requirements.txt was recently flattened (using pip-compile).
This flattening was performed in a Python2 environment.
Dependencies will vary in different environments.
Currently, futures 3.2.0 appears in the dev-requirements file
that pip-compile generated while running in Python2. If you try
installing futures 3.2.0 in a Python3 environment (if you try
`pip install -r dev-requirements.txt` running Python3, in other
words), you will encounter an error. Removing futures from
flattened dev-requirements fixes this.
There are several larger issues here that are not addressed and
must have issues created for them:
- pip-compile on existing dev-requirements.txt to generate new
dev-requirements.txt will retain orphaned dependencies,
accumulating cruft; you need a one-layer (non-flattened)
dev-dependencies file to use as a source file for pip-compile,
I think
- Python2 and Python3 dependencies will frequently vary, so
it MAY be worth having dev-requirements-python2.txt and
dev-requirements-python3.txt
- Perhaps as a result of all this, we should reconsider pinning?
Signed-off-by: Sebastien Awwad <sebastien.awwad@gmail.com>
