Some releases of Versioneer change the way your setup.py and setup.cfg must be configured. This document contains a list of releases where, when upgrading from an older release, you must make changes in your project.
Nothing special.
Starting with this version, Versioneer is configured with a [versioneer]
section in your setup.cfg file. Earlier versions required the setup.py to
set attributes on the versioneer module immediately after import. The new
version will refuse to run (raising an exception during import) until you
have provided the necessary setup.cfg section.
In addition, the Versioneer package provides an executable named
versioneer, and the installation process is driven by running versioneer install. In 0.14 and earlier, the executable was named
versioneer-installer and was run without an argument.
0.14 changes the format of the version string. 0.13 and earlier used hyphen-separated strings like "0.11-2-g1076c97-dirty". 0.14 and beyond use a plus-separated "local version" section strings, with dot-separated components, like "0.11+2.g1076c97". PEP440-strict tools did not like the old format, but should be ok with the new one.
Nothing special.
You must add a versioneer.VCS = "git" to your setup.py before re-running
setup.py setup_versioneer. This will enable the use of additional
version-control systems (SVN, etc) in the future.