Twine: Twine writes output to stderr even when not an error

[jonathanunderwood]

It seems that twine writes all of its informational output to stderr. This is a problem for situations which regard any output on stderr as a sign of a failure. One such situation is using twine to upload wheels from the AppVeyor service, where twine is invoked from PowerShell. PowerShell regards any output on stderr to be a failure case.

Please only write errors to stderr, and informational output to stdout.

See:
https://q-a-assistant.com/computer-internet-technology/1535005_upload-using-twine-in-appveyor-using-ps.html

[jonathanunderwood]

Ah, I see this was fixed in #279 in November. Any ETA on a release?

[lelit]

Please? 🙏

[brainwane]

Thanks for reporting the issue! In #306 I am working on getting a new release out.

[brainwane]

https://test.pypi.org/project/twine/1.10.0rc1/ is a release candidate for Twine 1.10.0 which I'm planning to release early next week. Please see the changelog for detailed notes under "Next feature release".

I believe this is how you test it out:

pip install --upgrade --pre --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple twine

[brainwane]

Twine 1.10.0 is now out so I'm closing this. Thanks.