Closed bradharmon closed 11 years ago
Fair call. I suppose the stderr should be consumed and combined with the exception, and presented by the exception's __str__
. I likely won't have any time in the near future to fix this, so if you feel up to it please send a pull request. Otherwise I'll fix it later.
I lied - found a few minutes, fixed now.
It seems that maybe some debug code has been left in pushy. I'm coming across a situation where I want to try and use a specific python binary, and catch the exception if it doesn't exist.
If the first pushy connection fails, stderr gets plastered with output because of client.py:395-401
client.py:395-401
I do like that I can tell the reason for the exception due to displaying the output from the remote command as seen above (versus just re-raising an exception that is non-obvious), but I also think I should be able to catch the exception without spamming stderr.