gh-126946: Improve error message in getopt.do_longs based on existing comment #126871
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Since this is a user facing change, I think it will need an issue and a news entry. You can open a new issue and edit the number into the title. If you haven't seen it already, take a look at Lifecycle of a pull request from the dev guide for specific tips on what to include in a PR for different types of changes. |
bombs-kim
changed the title
|
@brianschubert I've created an issue and added a NEWS entry. |
Misc/NEWS.d/next/Library/2024-11-18-16-43-11.gh-issue-126946.52Ou-B.rst
Outdated
Show resolved
Hide resolved
Co-authored-by: Brian Schubert <brianm.schubert@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR improves the error message in getopt.do_longs based on the existing comment