This inconsistency already exists for python itself. For instance python3.14 -c 'import ok' shows a colored traceback while python --help doesn't. I don't think it's a real issue here.
This inconsistency already exists for python itself. For instance python3.14 -c 'import ok' shows a colored traceback while python --help doesn't. I don't think it's a real issue here.
I'm suggesting that within a single tool, there should be consistency.
But it is consistent? python displays tracebacks with colors, so it doesn't matter here. python --help doesn't have colors while python -c "some_error" will render the tracaeback with colors.
For others, only --help could be colorized, but not all CLI tools are actually using argparse. I would say that it's fine to have the help not supporting colors.
Activity
mpkocher commented on Sep 28, 2025
This would be creating an inconsistency with the tool.
The command line interface doesn't support color (because it's using getopt). It's a bit odd if there isn't parity between the out and err cases.
gh-139374: colorize traceback when using `timeit` command-line interf…
picnixz commented on Sep 28, 2025
This inconsistency already exists for python itself. For instance python3.14 -c 'import ok' shows a colored traceback while python --help doesn't. I don't think it's a real issue here.
mpkocher commented on Sep 28, 2025
I'm suggesting that within a single tool, there should be consistency.
picnixz commented on Sep 28, 2025
But it is consistent? python displays tracebacks with colors, so it doesn't matter here. python --help doesn't have colors while python -c "some_error" will render the tracaeback with colors.
For others, only --help could be colorized, but not all CLI tools are actually using argparse. I would say that it's fine to have the help not supporting colors.