gh-141571: Avoid redundant early _set_color() call in HelpFormatter #141611
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 fixes a redundant color initialization in argparse.HelpFormatter.
Currently,
HelpFormatter.__init__()calls_set_color(color)immediately,and then
_get_formatter()calls_set_color(self.color)again.This results in duplicate environment checks and redundant calls to
_colorize.can_colorize(), especially whencolor=False.This patch removes the early
_set_color(color)callin __init__and insteadstores the value in
self._color. The actual color initialization is nowperformed only once in
_get_formatter(), preserving existing behavior whileavoiding duplicate work.
A NEWS entry for gh-141571 has been added.