Make Ruff an optional dependency to avoid upper bound restriction #998
johnthagen
started this conversation in
General
Replies: 1 comment 5 replies
-
I see here why Ruff is a hard dependency: https://github.com/openapi-generators/openapi-python-client?tab=readme-ov-file#installation
It might be nice to make this optional? I do see the convenience, but for example, on our project we manage Ruff format ourselves as do perhaps others? And then if it were made optional the Ruff version wouldn't need to be restricted by |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently,
ruff
is listed as a hard dependency ofopenapi-python-client
:openapi-python-client/pyproject.toml
Line 17 in a73dfd4
But this means that if a user includes
openapi-python-client
as their own dev dependency (in order to lock its version with Poetry, for example), they can't upgrade to newer Ruff releases untilopenapi-python-client
does. This is made worse if they need to pin to an older version ofopenapi-python-client
due an incompatibility that arises (e.g., #926).We need to pin our
openapi-python-client
rather than usingpipx
to install it (as recommended in the README), because we need all developers on the team to always get the correct version that we've tested, thusopenapi-python-client
's dependencies will influence our project's dependencies.Could
ruff
be made anextras
so that it's optional?Beta Was this translation helpful? Give feedback.
All reactions