Some way to limit which versions of openapi-python-client
can be used
#1001
dbanty
started this conversation in
Feature request
Replies: 1 comment 1 reply
-
@johnthagen does that about capture the issue? Is there any more detail you can provide on the problem to be solved? Right now, I'm thinking that maybe we add a way to limit |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The recommended way to install
openapi-python-client
is viapipx
, since this avoids the common issue of conflicting dependencies. Internally,openapi-python-client
uses some very common tools/libraries (notably Ruff, HTTPX, and Pydantic at the time of writing). If installed as a dev dependency rather than a standalone tool (a lapipx
), users are now locked toopenapi-python-client
's version choices, even if they're not using those dependencies (HTTPX is only needed for downloading from URLs which not everyone does, Ruff is used as a post_hook, which folks can opt out of).On the one hand, there may be a technique to eliminate the dependency conflicts by vendoring dependencies or releasing a more advanced version of
openapi-python-client
where as much as possible is optional—that's not what this thread is about, that can be discussed in #998.On the other—maybe there's a way to remove the need to include
openapi-python-client
as a dev dependency so more people can use isolated environments. The main reason I know of to include it as a dev dependency instead of standalone is to coordinate which version is used across team members. This could be:Let's discuss!
Beta Was this translation helpful? Give feedback.
All reactions