Merge pull request #72 from mgeisler/master

zpm: don't from os import path
tox: break long cmdlines

This will make it easier to add new flags in the future.
tox: genereate XML coverage report

This will be used by the Cobertura Jenkins plugins.
tox: order related py.test cmdline flags together
Merge pull request #73 from mgeisler/tox-xml-coverage

tox: generate XML coverage report
zpm: abstract the swift_url construction logic

This moves the construction of the swift_url (for the .zar, which looks
like "swift://AUTH_abcdef.../test_container/myapp.zar") to a seperate
util function--with doctests, for good measure.
zpm: abstract `_prepare_job` from `deploy_project`

This util function adds runtime information to the job template json
(namely, the swift:// path to the application .zar).
test_zpm: add `test__prepare_job`

This is a test to exercise `zpmlib.zpm._prepare_job`.
doc/api.rst: include private members of zpmlib.zpm
README.md: use GitHub markdown header style
README.md: add installation instruction section

Installation instructions were missing from the README, and this seemed
to be causing confusion for the users (who though they had to package
`zpm` in order to install and use it).
README.md: add a usage note to `Packaging`

Packaging is only interesting to maintainers and packagers, not end
users. So I think it's a good idea to put a small warning/note at the
top of the packaging section to keep users from falling down rabbit
holes.
Merge pull request #76 from larsbutler/clarify-readme-install-instructions

Clarify readme install instructions
Merge pull request #75 from larsbutler/refactor-test-deploy-2

Refactor and test `deploy`, part 2
templates: give arg labels consistent widths
templates/index: add output heading
templates/index: put stdout in a pre element

A pre element resizes itself to fix the text and I think that looks
slightly better.
Merge pull request #79 from mgeisler/styling

Improve styling in generated web UI
new: put name of project into generated zar.json

This way, 'zpm new foo' will create a zar.json with 'foo' in the
zar['meta']['name'] field.
new: strip trailing white space from generated zar.json

The JSON generated by json.dump has lots of trailing white space. We
should not let the user start with such a crufty file.