Overlap of typer and typer-slim causes package managemers to fail

[konstin]

First Check

• I added a very descriptive title here.
• I used the GitHub search to find a similar question and didn't find it.
• I searched the Typer documentation, with the integrated search.
• I already searched in Google "How to X in Typer" and didn't find any information.
• I already read and followed all the tutorials in the docs and didn't find an answer.
• I already checked if it is not related to Typer but to Click.

Commit to Help

• I commit to help with one of those options 👆

Example Code

virtualenv .venv
source .venv/bin/activate
pip install typer
pip install typer-slim
python -c "import typer" # OK
pip uninstall typer # We got typer-slim, no need to have typer too
python -c "import typer" # ERROR

# MRE for uv: https://github.com/pimlock/uv-bug-repro

Description

This is the upstream version of astral-sh/uv#17645. When a user has both typer and typer-slim in their dependency tree, one will overwrite the other, with the consequence that uninstalling one will partially uninstall the other.

This is a problem with both pip and uv. Python package management doesn't support packages overlapping, depending on the installer it may even lead to corrupted files (parallel writing to the same files). Since a dependency tree may include both typer and typer-slim, those conflicts can happen silently, leading to hard-to-debug package management errors that only show up as runtime crashes.

I read #786 but unfortunately I don't follow why both packages include the same files, instead of only one package.

---

More of a meta comment, but I was surprised there is no dedicated bug reporting option, but only the funnel into the question flow.

Operating System

Linux

Operating System Details

Ubuntu 22.04

Typer Version

0.21.1

Python Version

3.14.0

Additional Context

No response

[svlandeg]

Thanks for the report @konstin, we'll look into this 🙏

[svlandeg]

Issue to track this is here: #1503 (yes the process is a bit convoluted, but we otherwise get too many "bug reports" that really aren't bugs, so this way we try to manage the issue tracker a bit)

[konstin]

Issue to track this is here: #1503

Thanks for porting this over

yes the process is a bit convoluted, but we otherwise get too many "bug reports" that really aren't bugs, so this way we try to manage the issue tracker a bit

It's not the discussion process (I see that you want to keep the issues actionable for the project), it's that I got a bit alienated by the discussion form implying I'm asking for help and should participate in the forum, when I was trying to upstream something causing problems for typer users that I had investigated and minimized.

[svlandeg]

(...) it's that I got a bit alienated by the discussion form implying I'm asking for help and should participate in the forum, when I was trying to upstream something causing problems for typer users that I had investigated and minimized.

Yep, I agree that's not very inviting for reporting bugs/issues 😕

[tiangolo]

It's not the discussion process (I see that you want to keep the issues actionable for the project), it's that I got a bit alienated by the discussion form implying I'm asking for help and should participate in the forum, when I was trying to upstream something causing problems for typer users that I had investigated and minimized.

Thanks for the feedback! It's definitely not targetted at you, but trying to push people to try and come and help if they want to get free support, which is what happens most of the cases. 😅

Let me think about that part, maybe it can be rephrased.

---

Also, I added some more context on why typer-slim in that issue. #1503 (comment)