-
Notifications
You must be signed in to change notification settings - Fork 310
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
Option to disable the progress bar or to specify stdout instead of stderr #268
Comments
Hello what should I do i have no clue of technology |
Same problem here... |
StackOverflow claims it's the PowerShell host (whatever it is) that interprets stderr output as a terrible terrible error happening somewhere: https://stackoverflow.com/questions/44632416/upload-using-twine-in-appveyor-using-ps |
Thanks for reporting this and I'm sincerely sorry for the delay. I lost track of this issue. I'd happily merge a pull request that does the right thing here (probably using the file argument to tqdm to specify stdout) |
Should prevent problems for people who use Twine from Appveyor. (Any output to stderr is helpfully treated as a failure by the PowerShell scripting host, and causes the entire Appveyor job to be marked as failed.) Fixes pypa#268.
It would be nice having an option to disable the progress bar in the
upload
command, or alternatively to have a way to specify it should be printed onstdout
instead ofstderr
(tqdm accepts afile
argument for that).My use case is the following: I'm using
twine
to upload wheels built onci.appveyor.com
, and even if the command succeeds (the wheels do appear on PyPI), theappveyor
log contains a red warning. I'm told that apparently the appveyor machinery (or Windows itself?) unconditionally considers anything written onstderr
as an error message.The text was updated successfully, but these errors were encountered: