Take the FORCE_COLOR
and NO_COLOR
environment variables into account
#9128
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.
Support for
NO_COLOR
andFORCE_COLOR
(andPY_COLORS
, as an alias toFORCE_COLOR
)environment variables has been added. When running
pylint
, the reporter that reportsto
stdout
will be modified according to the requested mode.The order is:
NO_COLOR
FORCE_COLOR
,PY_COLORS
--output=...
.Signed-off-by: Stavros Ntentos 133706+stdedos@users.noreply.github.com
skip-news
if the change does not need to be in the changelog.towncrier create <IssueNumber>.<type>
which will beincluded in the changelog.
<type>
can be one of the types defined in./towncrier.toml
.If necessary you can write details or offer examples on how the new change is supposed to work.
tox -e docs
Don't hesitate to open multiple PRs if the change requires it. If your review is so
big it requires to actually plan and allocate time to review, it's more likely
that it's going to go stale.
and preferred name in
script/.contributors_aliases.json
Type of Changes
Description
Fixes #3995