Add support for NO_COLOR and FORCE_COLOR

[hugovk]

Fixes #7464.

PY_COLORS is pytest-specific and comes first (#7464 (comment)).

Then NO_COLOR takes precendece over FORCE_COLOR (like tartley/colorama#230).

Then check the other rules.

Also includes the Jython removal from #7462.

[nicoddemus]

Looks good!

Would you mind add a small explanation to those variables and PY_COLORS to reference.rst under Environment Variables? Thanks!

[hugovk]

Would you mind add a small explanation to those variables and PY_COLORS to reference.rst under Environment Variables? Thanks!

Added!

• https://pytest--7466.org.readthedocs.build/en/7466/reference.html#environment-variables

Should they be in alphabetical order? For example, before:

• PYTEST_ADDOPTS
• PYTEST_DEBUG
• PYTEST_PLUGINS
• PYTEST_DISABLE_PLUGIN_AUTOLOAD
• PYTEST_CURRENT_TEST
• PY_COLORS
• NO_COLOR
• FORCE_COLOR

After:

• FORCE_COLOR
• NO_COLOR
• PYTEST_ADDOPTS
• PYTEST_CURRENT_TEST
• PYTEST_DEBUG
• PYTEST_DISABLE_PLUGIN_AUTOLOAD
• PYTEST_PLUGINS
• PY_COLORS

[nicoddemus]

Should they be in alphabetical order?

Good catch, I think so, perhaps except keeping the pytest-specific ones separated from the others:

• PYTEST_ADDOPTS
• PYTEST_CURRENT_TEST
• PYTEST_DEBUG
• PYTEST_DISABLE_PLUGIN_AUTOLOAD
• PYTEST_PLUGINS

Also the non-pytest specific could be order by precedence perhaps?

• PY_COLORS
• NO_COLOR
• FORCE_COLOR

What do you think?

[hugovk]

Done!

[nicoddemus]

Awesome, thanks @hugovk!

[nicoddemus]

Thanks @hugovk!

[blueyed]

This could/should use an internal reference (Python uses using-on-envvars).
In general (internal) documentation links should not go through external resources/protocols.

[nicoddemus]

True, that escaped my mind, thanks. 👍

[nicoddemus]

Done: #7474

Thanks again