enable Travis-CI testing
try to get travis to run
more travis hacking
travis: emit git version during testing
travis: hush the 'install' step
handle refnames made by git-1.8.3 and later

Git-1.8.3 introduced a change to the way "$Format" strings (specifically
the "%d" variable) are expanded in git-archive -generated tarballs. The
list of refs has always included both branch names and tags. But in
older versions, tags were not emitted any differently than branch names:
the list might say:

 (master, HEAD, v1.0)

Starting in 1.8.3, tags are marked with a distinctive "tag: " prefix, so
you get:

 (master, HEAD, tag: v1.0)

The versioneer code that deduces version tags from generated tarballs
was not spotting the newly-marked tags, and falling back to reporting a
full SHA1 hash as the revision, instead of the intended tag name.

This change fixes the parser and restores compatibility with newer
versions of git. Closes: #11.
test_git.py: oops, fix python2-ism
test py2.5 compatibility too
Silence py3 warnings about files left open
update instructions for "update_files" to match reality
test_git: don't hard-code "_test" to run the tests in

This paves the way to run tests in other directories, e.g. under /tmp/ .
run tests in a /tmp/ directory

These test directories do not live inside a git checkout (the versioneer
source tree itself), so they can exercise different codepaths. Namely,
what happens when 'git describe' or 'git rev-parse' cannot find a .git
directory.
Use 'git rev-parse --show-toplevel' to find the repo's root-dir

Signed-off-by: Giel van Schijndel <me@mortis.eu>
Try installing __file__ first, only using `versioneer.py` as a fallback

Signed-off-by: Giel van Schijndel <me@mortis.eu>
do_vcs_install(): add versioneer.py, not .pyc
hide the scary git message when running in a non-git tree

To do this, we hide stderr while running the 'git rev-parse
--show-toplevel' command that is used to find out where the root of the
git checkout is.
define our own os.path.relpath, to maintain support for python-2.5
Document no-version-until-first-tag problem (issue #12).
release 0.8
bump to 0.8+ while between releases