GH-101111: Disambigaute origin of const for store_const and append_const #101121
Conversation
This file contains hidden or 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
…end_const While the documentation for `optparse` mentioned that both `store_const` and `append_const` store a constant value, it was not clear where this value was coming from. A link to `Option.const` makes this explicit.
|
I had a look at some other documentation pull requests, and it looks like there is no need to create a news snippet via blurb.it. Please tell if otherwise. |
ambv
added
needs backport to 3.10
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this pull request
Jan 20, 2023
…end_const (pythonGH-101121) While the documentation for `optparse` mentioned that both `store_const` and `append_const` store a constant value, it was not clear where this value was coming from. A link to `Option.const` makes this explicit. (cherry picked from commit 9a15513) Co-authored-by: Jürgen Gmach <[email protected]>
|
GH-101203 is a backport of this pull request to the 3.11 branch. |
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this pull request
Jan 20, 2023
…end_const (pythonGH-101121) While the documentation for `optparse` mentioned that both `store_const` and `append_const` store a constant value, it was not clear where this value was coming from. A link to `Option.const` makes this explicit. (cherry picked from commit 9a15513) Co-authored-by: Jürgen Gmach <[email protected]>
|
GH-101204 is a backport of this pull request to the 3.10 branch. |
ambv
pushed a commit
that referenced
this pull request
Jan 20, 2023
…pend_const (GH-101121) (#101203) (cherry picked from commit 9a15513) While the documentation for `optparse` mentioned that both `store_const` and `append_const` store a constant value, it was not clear where this value was coming from. A link to `Option.const` makes this explicit. Co-authored-by: Jürgen Gmach <[email protected]>
ambv
pushed a commit
that referenced
this pull request
Jan 20, 2023
…pend_const (GH-101121) (#101204) (cherry picked from commit 9a15513) While the documentation for `optparse` mentioned that both `store_const` and `append_const` store a constant value, it was not clear where this value was coming from. A link to `Option.const` makes this explicit. Co-authored-by: Jürgen Gmach <[email protected]>
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.
While the documentation for
optparsementioned that bothstore_constandappend_conststore a constant value, it was not clear where this value was coming from.A link to
Option.constmakes this explicit.optparse-> information aboutstore_constis a bit vague #101111