So what a lot of projects do in this situation is to make the default recommended way to install the package include all extras, see uvicorn for example:

pip install 'uvicorn[standard]'

And even the FastAPI docs prescribe this.

Another popular package that does this is psycopg:

pip install "psycopg[binary]"

This could be a nice middle ground for openapi-python-client, so the README would simply state something like:

To install openapi-python-client with the standard set of features, run:

pip install openapi-python-client[standard]

That way, when users come to the project, they are always shown a good default experience with all of the tools you would like to support?

Oh that's a good idea, and we could make it a breaking change so hopefully folks read the changelog and add the features as needed. Would also need to tweak the GitHub Action so that it adds the features automatically, but only for new enough versions of the generator 🤔.

Any updates on this? Just stumbled upon this issue myself. I had this project on 0.20.0 as a dependency while my project has the newest Ruff version, which caused a conflict. I updated to 0.21.5, but I shouldn't be forced to IMO

@dbanty We just hit this problem again where when we updated our dependencies, Ruff updated to 0.8.x first and then:

 - Downgrading httpx (0.27.2 -> 0.26.0)
 - Updating ruff (0.7.2 -> 0.8.2)
 - Downgrading typer (0.12.5 -> 0.9.4)
 - Downgrading openapi-python-client (0.21.6 -> 0.17.3)

This is also a ongoing discussions to propose a way to define default extras, which would also solve this problem if the proposal is accepted and implemented

• https://discuss.python.org/t/adding-a-default-extra-require-environment/4898/174

@dbanty I think this is a very pragmatic move and I appreciate the careful consideration of trade offs you are taking.