-
-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VCS not found message could be friendlier #21
Comments
Agreed. |
Ok, what is surprising to me is that WindowsError is not a subclass of OSError, because I already have error handling for this that looks like try:
pipe = subprocess.Popen(command, stdout=subprocess.PIPE,
stderr=subprocess.STDOUT)
except OSError as e:
raise Failure("could not run %s: %s" % (command, e)) http://docs.python.org/2.7/library/exceptions#exceptions.WindowsError says WindowsError is a subclass of OSError. I am confused. |
Python 3.2 docs say the same: http://docs.python.org/3.2/library/exceptions#WindowsError Python 3.3 says it was merged into OSError: http://docs.python.org/3.3/library/exceptions#OSError |
On the plus side, I managed to reproduce this uncaught WindowsError: |
No, scratch that, that's a different place in the code (and one where I'm not catching OSError). |
I cannot reproduce this. I open Git Bash on a Windows machine and run
i.e. the error is caught correctly. I would dearly love to know how you managed :) |
Sure :) Start > Run > cmd.exe
py32.bat:
In the console output above, I redefined path explicitly in order rule out contamination from another directory. I get the same result with python 2.7. |
I have reproduced this! In Git Bash, with Python 2.7
|
Oh I am so stupid. The bug is present in the last release (0.17) but fixed in git master (in commit 29b0d59, with the so-clear commit message "Start improving test coverage"). |
"Oh I am so stupid." ahh, but now you know it, so are wise. :-) |
It would be nice if the a friendlier message was printed when the source code control program is not available, e.g.
bzr not found
instead of:The text was updated successfully, but these errors were encountered: