make versioneer work on Windows

[chiiph]

Here's the output:

$ python setup.py build
Microsoft (R) C/C++ Optimizing Compiler Version 17.00.50727.1 for x86
Copyright (C) Microsoft Corporation.  All rights reserved.

Traceback (most recent call last):
  File "setup.py", line 386, in <module>
    version = UpdateVersion().run()
  File "setup.py", line 332, in run
    raise Exception("problem: couldn't get version information from revision con
trol history, and there is no version information in '%s'. Stopping." % (VERSION
_PY_FNAME,))
Exception: problem: couldn't get version information from revision control histo
ry, and there is no version information in 'src\pycryptopp\_version.py'. Stoppin
g.

[zooko]

Thanks for the bug report, chiiph! Could you please show the exact command-line that you used to get the master version? I ask because the error message seems to indicate that either "git" is not installed, or there's some other problem with using git to determine which version of pycryptopp you have there…

[chiiph]

Replying to zooko:

Thanks for the bug report, chiiph! Could you please show the exact command-line that you used to get the master version? I ask because the error message seems to indicate that either "git" is not installed, or there's some other problem with using git to determine which version of pycryptopp you have there…

Git is working perfectly so far with every other python package, but that doesn't mean it's 100% functional.

To get the repo I just did:

git clone https://github.com/tahoe-lafs/pycryptopp

[zooko]

Opened an issue on the versioneer issue tracker: ​https://github.com/warner/python-versioneer/issues/14

[warner]

Let's see, versioneer tries to be quiet about git errors, and for this problem I think we'll need to make it more verbose. I'm guessing that pycryptopp's bundled copy of versioneer is trying to run "git describe" and failing, but mostly likely because it's spelling "git" incorrectly, or is looking in the wrong place.

versioneer.py line 221 ought to notice that we're running on windows and arrange to invoke git.cmd instead of plain git. Could you try adding verbose=True to the invocation of run_command() on line 224? That should print more messages to stdout and might tell us what's going wrong.