This project uses git & python.


In order to contribute, please start by making your own fork of this repository, and proceed to clone your own nifty fork to your local machine.

Isolating the Python environment with virtualenv is recommended. Use the following commands to set up a development environment within the Git workspace:

$ virtualenv .
$ . bin/activate
(transip-api) $ pip install -r dev_requirements.txt

Or by using virtualenvwrapper:

$ mkvirtualenv transip-api
$ cd /path/to/clone
$ setvirtualenvproject

Proceed to using pip to install all the dependencies

$ pip install -r dev_requirements.txt


Please make sure that you make a separate branch for the changes you propose. Subsequent commits to the same branch as the Pull-Request originated from will be picked up by GitHub and added to the Pull-Request.

This is quite handy to change things when there are comments about the changeset, but can be annoying if not taken into account. If you make a Pull- Request from your develop branch and you continue developing, all new commits get added to the Pull-Request, which is clearly not wanted.

Testing & Code-quality

This project uses unittest to automatically test the software. Every Pull Request should contain tests, unless it is clear why they are not needed. (e.g. document change only, changes that don’t change behaviour.)

To ensure consistent code, pylint has been enabled for this project. Included is a .pylintrc file, with configuration for this project.

To run tests & pylint you can run these two commands

$ nosetests --rednose --with-coverage --cover-package=transip
$ pylint --rcfile=.pylintrc transip


pylint configuration is not set in stone. Change the configuration if you feel the need to do so. Please do explain the reason for changing the configuration in the Pull-Request.


Bugfixes should add a test that fails with the bug unfixed, but passes with the bux fixed.


When a Pull-Request is made, TravisCI will automatically pick it up and test it using the settings from .travis.yml. The results will be made available both on GitHub with the Pull-Request, as on the specific page for this repository at TravisCI: If anything fails, you can see the specifics about the failure there.

Obviously, Pull-Request that fail the test will not be merged.