ModuleNotFoundError: No module named 'typing_extensions' when using rich-click as a dependency

[JacobCallahan]

Hello,

When using rich-click as a dependency in our project, we encountered a ModuleNotFoundError for typing_extensions when running our CLI.

Steps to Reproduce

1. Create a new project with a pyproject.toml file.
2. Add rich-click as a dependency. The project also requires Python >= 3.10.

[project]
name = "my-cli"
requires-python = ">=3.10"
dependencies = [
    "click",
    "rich-click",
]

3. Create a simple CLI application that uses rich-click.
4. Install the project dependencies into a clean virtual environment using pip install ..
5. Run the CLI.

Expected Behavior

The CLI should run without any ModuleNotFoundError. All necessary transitive dependencies, including typing_extensions, should be automatically installed when rich-click is installed.

Actual Behavior

The application fails with the following traceback, indicating that typing_extensions is not installed:

    1 Traceback (most recent call last):
    2   File "<path_to_cli_entry_point>", line 5, in <module>
    3     from my_cli.commands import cli
    4   File "/path/to/my_cli/commands.py", line 2, in <module>
    5     import rich_click as click
    6   File "/path/to/venv/lib/python3.11/site-packages/rich_click/__init__.py", line 74, in <module>
    7     from rich_click.decorators import command as command
    8   File "/path/to/venv/lib/python3.11/site-packages/rich_click/decorators.py", line 6, in <module>
    9     from typing_extensions import Concatenate, ParamSpec
   10 ModuleNotFoundError: No module named 'typing_extensions'

Workaround

The issue was resolved by manually adding typing-extensions to our project's dependencies in pyproject.toml.

dependencies = [
    "click",
    "rich-click",
    "typing-extensions", # Manually added
]

It seems that rich-click has a dependency on typing_extensions but does not declare it in its own packaging metadata, forcing downstream projects to fix the transitive dependency
themselves.

Thank you!

[dwreeves]

Hmm, that's really weird. This might be an older version of rich-click, since from typing_extensions import Concatenate, ParamSpec doesn't occur on line 6 in the most recent version.

This weekend I will run your exact steps and report back.

Thanks for providing those steps and thanks for reporting this!

[dwreeves]

Hello @JacobCallahan!

I'm unable to recreate your issue.

As stated, I believe this is an old version of rich-click based on the traceback. I believe there was an old version of rich-click that did not include typing_extensions. This should have been fixed for both the latest version of 1.8.x, as well as for 1.9.x.

It is possible that you are running this older version of rich-click. Please let me know which version it is by running:

python -c "import rich_click; print(rich_click.__version__)"

---

Here were my recreation steps:

# cli.py
import rich_click as click

@click.command()
def foo():
    print("Testing 123")

foo()

# pyproject.toml
[project]
version = "1.0.0"
name = "my-cli"
requires-python = ">=3.10"
dependencies = [
    "click",
    "rich-click"
]

Command:

$ uv run --with . cli.py --help

This executes as expected:

 Usage: cli.py [OPTIONS]

╭─ Options ───────────────────────────────────────────────────────────────────────────────────────╮
│ --help  Show this message and exit.                                                             │
╰─────────────────────────────────────────────────────────────────────────────────────────────────╯

[JacobCallahan]

@dwreeves hmm i'm now unable to reproduce this, so uv's cache must have been holding on to an older version of the project. thanks for testing!