-
-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature]: Make outlines
dependency optional
#3794
Comments
Alternatively we can relax the outlines version to not to pin it or set it Once we have multiple guided decoding backends I think the packages can be optional. |
That could work! However, note that some of the imports from outlines (RegexFSM for instance) is currently deprecated and will be removed in June, causing ImportErrors in vLLM if nothing changes. But it would at least work until then :) A quick hotfix could maybe be to relax the versioning and move the outlines imports in guided_logits_processors.py into the classes, to avoid problems if you aren't using that module? |
The update ticket: #3715 |
This issue has been automatically marked as stale because it has not had any activity within 90 days. It will be automatically closed if no further activity occurs within 30 days. Leave a comment if you feel this issue should remain open. Thank you! |
@simon-mo An upper bound on |
can't agree more - using this antique version of outlines breaks all my dependency management. This should be discouraged within vllm PR reviews. |
We will support the latest versions of outlines with this PR #10576 |
🚀 The feature, motivation and pitch
I'm using a newer version of
outlines
than v0.0.34, and my application needs the fixes implemented in newer versions of that package. It would be great ifvllm
could make its structured generation dependencies optional, as I'm not using the internalvllm
structured generation, but rather using the logits processors fromoutlines
directly.Alternatives
No response
Additional context
This prevents me from updating to
vllm==0.4.0
.The text was updated successfully, but these errors were encountered: