Age | Commit message (Collapse) | Author |
|
Updated all dependencies to the latest version. This brings us to back
to 2016 :-)
The only dependency not getting an update is 'sh' because the 0.12.x
release series seems to be very buggy (performance issues, regressions, etc).
This commit does contain a guard for checking '_ok_code' during sh
invocation as that was an issue with 1.12.x (submitted
https://github.com/amoffat/sh/issues/343). Might as well patch it
already if we ever do go to sh==1.12.x.
|
|
Gitlint now passes pylint validation. Currently only supported for
python 2.7.
We've added a .pylintrc to customize pylint's behavior for gitlint.
|
|
We now fully support python 2.6. We had to include the unittest2
dependency, update pytest to 2.9.2 and update a bunch of format strings,
but this was relatively straightforward :)
Also enabled python 2.6 unit tests in TravisCI.
|
|
gitlint-ignore: B5,B6
|
|
Py.test is a more powerful test and test runner library than the default
unittest. In particular, it allows us to use the same library to invoke
our tests in python 2.6, 2.7 and 3.x.
|
|
Added some install commands to the Vagrantfile so we can more easily
work on python 3 and python 2.6 support. However, both are currently blocked.
- Python 3 support: currently blocked on Click not supporting python 3
without significant workarounds:
http://click.pocoo.org/5/python3/
- Python 2.6 support: Too many errors around unittest2 incompatibility
|
|
|
|
In a fresh vagrant (vagrant destroy -f ; vagrant up) you would see the
following messages. Though the pip packages install, pip actually ends
up downgraded.
==> dev: % (cmd_desc, proc.returncode))
==> dev: OSError
==> dev: :
==> dev: Command /vagrant/.venv/bin/python -c "import sys, pip;
sys...d\"] + sys.argv[1:]))" setuptools pip failed with error
code 1
pip downgrades itself after installing the sh module:
==> dev: Installing collected packages: pip
==> dev: Found existing installation: pip 7.1.2
==> dev: Uninstalling pip-7.1.2:
==> dev: Successfully uninstalled pip-7.1.2
==> dev: Successfully installed pip-1.5.4
==> dev: You are using pip version 1.5.4, however version 7.1.2 is
available.
==> dev: You should consider upgrading via the 'pip install
--upgrade pip' command.
==> dev: You are using pip version 7.1.0, however version 7.1.2 is
available.
==> dev: You should consider upgrading via the 'pip install
--upgrade pip' command.
This seems to be caused by pip being upgraded via requirements.txt. So
this change upgrades pip outside of pip via easy_install.
The pip version we get via easy_install at time of writing is 7.1.2. It
runs fine and does not show the above messages.
Also removed python-pip from being installed via apt-get as
python-virtualenv comes with its own (albiet broken) and the version in
python-pip is quite old (1.5.x).
|
|
There are now also unit tests for the Display utility class, that make
use of the mock testing library.
|
|
- setup.py
- travis integration
- README
- Vagrantfile
- run_tests.sh
- gitignore
- requirements.txt
|