PolyLLM OpenAI Plugin for Python

from polyllm_core import create_llm
from polyllm_openai import OpenAIPlugin

llm = create_llm(plugins=[OpenAIPlugin()], providers={"openai": {"api_key": "..."}})
response = await llm.chat("openai:gpt-4o-mini", messages=[{"role": "user", "content": "你好"}])

Metadata

Release files for polyllm-ollama 0.6.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for polyllm-ollama 0.6.0
File	Size	Uploaded	Provenance
polyllm_ollama-0.6.0.tar.gz	5.6 kB	Oct 25, 2026	With provenance	Details

Built distribution (wheel)

Table of built distributions (wheels) for polyllm-ollama 0.6.0
File	Interpreter	ABI	Platform	Reset
polyllm_ollama-0.6.0-py3-none-any.whl 5.8 kB Oct 25, 2026 With provenance	Python 3	none	any	Details

Total release size: 11.4 kB

Release files / polyllm_ollama-0.6.0.tar.gz

Download URL	polyllm_ollama-0.6.0.tar.gz
Size	5.6 kB
Tags	Source
SHA-256 checksum How to use checksums	`fbd6951f1db862193a92ef566289df1adb4134a7b54ac36e53a33e3438859fa4`
BLAKE2b-256 checksum How to use checksums	`ebc5dc21110a7a4b1bc5815e0f75e4155bf1eda7c5a923a06815ed1ee290347f`
Upload date	Oct 25, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/you-want/PolyLLM
Publishing commit: github.com/you-want/PolyLLM/tree/1d7a8cf08081c6d0d4aef828a19390235bd9cf4a

Workflow

Publishing configuration: github.com/you-want/PolyLLM/blob/1d7a8cf08081c6d0d4aef828a19390235bd9cf4a/.github/workflows/release-python.yml
Publishing logs: github.com/you-want/PolyLLM/actions/runs/40192141129/attempts/1

Artifact

Subject: polyllm_ollama-0.6.0.tar.gz
SHA-256 checksum: fbd6951f1db862193a92ef566289df1adb4134a7b54ac36e53a33e3438859fa4 Verifying attestations

Release files / polyllm_ollama-0.6.0-py3-none-any.whl

Download URL	polyllm_ollama-0.6.0-py3-none-any.whl
Size	5.8 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`33812da5077728bdd044abbdc9ee29f64084245ed94bfa295f515d24711e3a13`
BLAKE2b-256 checksum How to use checksums	`920684c803a02e28cf6d375090a18f6452a92da6a80db1f103ea0852af2240e3`
Upload date	Oct 25, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/you-want/PolyLLM
Publishing commit: github.com/you-want/PolyLLM/tree/1d7a8cf08081c6d0d4aef828a19390235bd9cf4a

Workflow

Publishing configuration: github.com/you-want/PolyLLM/blob/1d7a8cf08081c6d0d4aef828a19390235bd9cf4a/.github/workflows/release-python.yml
Publishing logs: github.com/you-want/PolyLLM/actions/runs/40192141129/attempts/1

Artifact

Subject: polyllm_ollama-0.6.0-py3-none-any.whl
SHA-256 checksum: 33812da5077728bdd044abbdc9ee29f64084245ed94bfa295f515d24711e3a13 Verifying attestations

Security for polyllm-ollama 0.6.0

Report project as malware

Provenance

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Attestation for polyllm_ollama-0.6.0.tar.gz

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/you-want/PolyLLM
Publishing commit: github.com/you-want/PolyLLM/tree/1d7a8cf08081c6d0d4aef828a19390235bd9cf4a

Workflow

Publishing configuration: github.com/you-want/PolyLLM/blob/1d7a8cf08081c6d0d4aef828a19390235bd9cf4a/.github/workflows/release-python.yml
Publishing logs: github.com/you-want/PolyLLM/actions/runs/40192141129/attempts/1

Artifact

Subject: polyllm_ollama-0.6.0.tar.gz
SHA-256 checksum: fbd6951f1db862193a92ef566289df1adb4134a7b54ac36e53a33e3438859fa4 Verifying attestations

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.