René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Typer's `CliRunner.invoke()` method with `color=False` (the default) is not properly disabling ANSI color codes in the output during CI/CD testing","articleBody":"**Describe the bug**\nTyper's `CliRunner.invoke()` method with `color=False` (the default) is not properly disabling ANSI color codes in the output during testing. The output still contains escape sequences like `\\x1b[1m` and `\\x1b[0m`, causing test assertions to fail when checking for plain text strings.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n1. Create a Typer app with Rich integration (default behavior)\n2. Write a test using `typer.testing.CliRunner`\n3. Call `cli_runner.invoke(app, [\"--help\"])` (color=False is the default)\n4. Assert that plain text appears in `result.output`\n5. Test fails because output contains ANSI escape sequences\n\n**Minimal reproduction example:**\n```python\nimport typer\nfrom typer.testing import CliRunner\n\napp = typer.Typer()\n\n@app.command()\ndef hello():\n    \"\"\"Say hello.\"\"\"\n    typer.echo(\"Hello World!\")\n\ndef test_help():\n    runner = CliRunner()\n    result = runner.invoke(app, [\"--help\"])\n    # This should work but fails due to ANSI codes\n    assert \"Usage:\" in result.output\n\n# Output contains: '\\x1b[1m                                                                                \\x1b[0m\\n\\x1b[1m \\x1b[0m\\x1b[1...'\n```\n\n**Expected behavior**\nWhen `color=False` is set (or defaulted), the `CliRunner` should produce plain text output without any ANSI escape sequences, making it suitable for string matching in tests.\n\n**Environment:**\n- Typer version: 0.16.0\n- Python version: 3.12.11\n- OS: Linux (GitHub Actions environment)\n- Rich integration: Enabled (default)\n\n**Logs**\n```\nAssertionError: assert 'Usage: codeanalyzer [OPTIONS] COMMAND [ARGS]...' in '\\x1b[1m                                                                                \\x1b[0m\\n\\x1b[1m \\x1b[0m\\x1b[1...   \\x1b[2m│\\x1b[0m\\n\\x1b[2m╰──────────────────────────────────────────────────────────────────────────────╯\\x1b[0m\\n\\n'\n\nRaw output contains escape sequences:\n- \\x1b[1m (bold)\n- \\x1b[0m (reset)\n- \\x1b[2m (dim)\n```\n\n**Current Workaround**\n```python\nimport re\n\ndef strip_ansi(text):\n    return re.sub(r'\\x1b\\[[0-9;]*[mK]', '', text)\n\ndef test_help():\n    runner = CliRunner()\n    result = runner.invoke(app, [\"--help\"])\n    clean_output = strip_ansi(result.output)\n    assert \"Usage:\" in clean_output\n```\n\n**Additional context**\n- This issue primarily manifests in CI environments (GitHub Actions) but may also occur locally depending on terminal capabilities\n- The issue appears to be related to Rich's automatic color detection overriding the `color=False` parameter\n- Other CLI testing frameworks (like Click's CliRunner) properly respect the color parameter\n- Setting environment variables like `NO_COLOR=1` or `TERM=dumb` may provide additional workarounds but shouldn't be necessary when `color=False` is explicitly set","author":{"url":"https://github.com/rahlk","@type":"Person","name":"rahlk"},"datePublished":"2025-07-11T14:49:04.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/9/codeanalyzer-python/issues/9"}