Tox automates the creation of virtualenvs for each configured interpreter. Generates a package distribution according to setup.py. And finally installs that package in each environment before running the tests.
It is one of tox's features to also test dependencies are in place when running tests.
adds test environment for python 3.5
removes redundant pip command from tox.ini
Coverage increased (+0.08%) to 74.289% when pulling 1134084 on medecau:fix_tests into 7366f96 on paramiko:master.
Thanks for this & the other ticket!
We don't fully support the tox.ini right now; I just haven't really wanted to remove it after somebody added it 🙁 Unsure if I want to keep fielding PRs to it or remove it (or spend the time to figure out if I want to instead embrace tox after all...) - will have to think about it.
Re: PyPy (#837) - I've never explicitly tested Paramiko on PyPy, but now that we are using cryptography.io on the backend, I wonder how well it would work. (One of the crypto principals is also a PyPy developer.)
If you want to update travis.yml so it adds PyPy cells, then at least we can see how Travis+PyPy runs the PR's branch and get a sense :) if it's happy I may then just merge the whole PR.
Changelog closes #866, closes #838
Cherry-picked the superceding #866 back to 1.17. Still includes Python 3.5 testing on Travis; changelog credit included. thanks!