-
-
Notifications
You must be signed in to change notification settings - Fork 30.7k
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
Make getopt error message style more consistent #128129
base: main
Are you sure you want to change the base?
Conversation
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the |
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the |
I can agree with making the error message consistent but I wonder if there's any chance we break CI parsing the output of the module in case of an error. While If we accept changing the error message, we should probably make a NEWS entry (and perhaps a What's New entry) just so that users are notified, even if there's only one user (and in this case, this requires an issue). cc @serhiy-storchaka |
This is not related to the
So there is no single correct variant. But error messages starting with a lower-case were introduced not so long ago in 42aa93b (bpo-31650). Error messages starting with an upper-case were here from the beginning. So we can assume that it was an error in 42aa93b. cc @benjaminp |
Fixes this minor inconsistency:
vs.