-
-
Notifications
You must be signed in to change notification settings - Fork 580
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
--check doesn't print to stderr as the documentation says #1429
Comments
Hi @tdhopper! Thanks for pointing out the inconsistency! I did some digging to see why this was, and it looks like originally it did print to stderr, and then intentionally was changed (here: be10c4a) as a result of the discussion here: #156. . Personally, looking back on it, I think the wrong course of action was taking and that errors (and only the errors) should have been sent to stderr and the documentation should be made consist, I'll take the opportunity in the next minor release to fix this behaviour. Thanks for shedding light on a ~6 year old bug that's probably caused confusion for many! ~Timothy |
I already noticed this inconsistency when added the colored output code, but didn't want to break backward compatibility and left a TODO to make the changes later on. I haven't noticed that the documentation say we should print to |
This change has just been deployed to PyPI in version 5.5.0 Thanks! ~Timothy |
Thanks for jumping on it! |
PyCQA/isort#1429 fixed `--check`'s output so that the error message and diff output are separated into STDERR and STDOUT rather than combined in STDOUT. This means we need to update our diff parsing function accordingly. Also fix the version parsing routine to read from STDOUT. This was busted for at least a few versions.
PyCQA/isort#1429 fixed --check's output so that the error message and diff output are separated into STDERR and STDOUT rather than combined in STDOUT. This means we need to update our diff parsing function accordingly. Also fix the version parsing routine to read from STDOUT. This was busted for at least a few versions.
I believe I'm correct that running
--check
prints the required changes tostdout
despite what the README says.The text was updated successfully, but these errors were encountered: