| Age | Commit message (Collapse) | Author |
|---|
|
Gitlint is now linted for all supported python versions.
Additionally, did some refactoring to run_tests.sh so that we can more
easily install and uninstall specific python environments (vs. all at
once).
|
|
- importlib is now only used for python 2.6 and not included for all
builds. This fixes issues with python3.
- run_tests.sh: --clean option: clean up the working directory (delete
cache, dist, build, etc)
- run_tests.sh: --install-virtualenvs and --remove-virtualenvs options
to install/remove virtualenvs for other python versions. This code
used to live in the Vagrantfile but has been moved to run_tests.sh so
that it can be used more easily during development.
|
|
./run_test.sh --all: run all tests (unit, integration, pep8, git)
./run_test.sh --all-env: run all tests against all python environments
defined in Vagrantfile
|
|
This allows users to lint repos other than the current directory.
Also added silver-searcher to the Vagrantfile for developer convenience.
|
|
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
|
|
To reduce the time to re-download packages during the 'apt-get update'
in Vagrantfile, cache downloaded packages if the vagrant-cachier plugin
is available.
|
|
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).
|
|
* Correct path to activate
* More robust .bashrc editing
* Git ignore .vagrant directory
|
|
- setup.py
- travis integration
- README
- Vagrantfile
- run_tests.sh
- gitignore
- requirements.txt
|
