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
bpo-38731: Add --quiet option to py_compile CLI #17134
Conversation
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). CLA MissingOur records indicate the following people have not signed the CLA: For legal reasons we need all the people listed to sign the CLA before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. If you have recently signed the CLA, please wait at least one business day You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
Thanks for your time @gvsheva, and welcome to CPython! I assume that you've seen the bot's message about the CLA? |
I'm not sure about this solution.
I don't see that passing -q
from the command line is actually documented anywhere, and it would be the only argument that we parse out like this.
It probably makes the most sense to just remove the branching below that references quiet
and just always write the error messages.
This PR should also have a NEWS entry. Just something simple, like: Fix a crash during error handling in :meth:`py_compile.main`. |
All was done, but I can't understand why Travis CI build was failed. |
@gvsheva It looks like an issue on Travis's end, unrelated to your changes. Pushing to your branch or closing-and-reopening this PR (not making a new one) should re-trigger the build. |
Misc/NEWS.d/next/Library/2019-11-13-07-37-11.bpo-38731.9qmcSx.rst
Outdated
Show resolved
Hide resolved
I think that the original intent was to support setting quiet mode on the command line. IMO this PR should be accepted to fix 3.8, but the original feature should be completed on master branch. Could you notify the original issue about this? |
The original issue is https://bugs.python.org/issue22640 |
Misc/NEWS.d/next/Library/2019-11-13-07-37-11.bpo-38731.9qmcSx.rst
Outdated
Show resolved
Hide resolved
Yes, can you add a comment there? |
Co-Authored-By: Éric Araujo <merwok@netwok.org>
@berkerpeksag do you agree with me?
|
I have made the requested changes; please review again. |
Thanks for making the requested changes! @merwok, @nanjekyejoannah, @pablogsal, @berkerpeksag: please review the changes made to this pull request. |
I'll make some trivial changes (such as replacing 3.9 with 3.10) to avoid keeping this unmerged any longer and then merge, thanks! |
This is now ready to go. I've made some adjustments to tests (no need to run them twice) and other random tweaks. I've also made sure that tests are passed without porting CLI to argparse (minus tests related to the --quiet
option, of course) I'll submit another PR to fix the regression in 3.8 and 3.9.
Thank you! |
|
|
Fixing missed
quiet
variable inpy_compile.py
module.https://bugs.python.org/issue40456