Add vLLM community provider information to the plugin registry#244
Merged
aksg87 merged 4 commits intogoogle:mainfrom Sep 16, 2025
Merged
Add vLLM community provider information to the plugin registry#244aksg87 merged 4 commits intogoogle:mainfrom
aksg87 merged 4 commits intogoogle:mainfrom
Conversation
- Implement VLLMLanguageModel provider with direct vLLM integration - Support GPU memory control and batch processing - Include comprehensive test suite and usage examples - Add proper error handling and memory optimization - Support for various vLLM parameters and configurations
- Add langextract-vllm plugin entry - Fix issue link format (google#236) - Plugin supports local and distributed model serving with vLLM
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Add vLLM community provider information to the plugin registry
Related to #236
Related to #236
Documentation
How Has This Been Tested?
N/A
Checklist:
I have read and acknowledged Google's Open Source
Code of conduct.
I have read the
Contributing
page, and I either signed the Google
Individual CLA
or am covered by my company's
Corporate CLA.
I have discussed my proposed solution with code owners in the linked
issue(s) and we have agreed upon the general approach.
I have made any needed documentation changes, or noted in the linked
issue(s) that documentation elsewhere needs updating.
I have added tests, or I have ensured existing tests cover the changes
I have followed
Google's Python Style Guide
and ran pylint over the affected code.