Another attempt to fix relative imports…
Still fixing relative imports…
move the sparks fabfile into the module (back as it should have always be since the creation of the correct python module…)
Move the main `fabfile` into the fabric submodule, this will avoid a massive namespace conflict with the external fabric package.
Create fabric.utils to hold, well… utils.
Rewrite to use the new utils.
Finally use the main fabfile to install things.
Relative cross-modules imports.
Again, relative cross-modules imports.
Handle the case where there is no PIP for a given Python version.
Deal with local/remote environments in runable()
Install the django full stack on the system, to allow python packages compilation.
Implement `dev_memcache` and `dev_django_full` fabric tasks.
In hostnames, replace '.' by '_' instead of '-'.
bump version in setup.py
Merge branch 'release/1.11.4'
Merge tag 'sparks-1.11.4' into develop

1.11.4