Repository navigation
Conversation
camel-ai 0.2.90 imports `ChatCompletionMessageFunctionToolCall` from
`openai.types.chat`, which only exists in openai>=1.100.0, but camel-ai
still declares `openai>=1.86.0`. Our poetry.lock pinned openai 1.91.0, so
a fresh `poetry install` on a clean checkout produced an environment
where `import oasis` fails:
ImportError: cannot import name 'ChatCompletionMessageFunctionToolCall'
from 'openai.types.chat'
CI did not catch this because it uses `pip install -e .`, which ignores
the lock file and resolves the latest openai.
Add an explicit `openai = ">=1.100.0"` constraint and update the lock to
openai 3.16.2, the same version CI currently resolves and passes with.
Transitive changes are limited to what openai 3.x requires (anyio, jiter,
idna, and the new httpx2/httpcore2/truststore packages).
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
echo-yiyiyi
requested changes
Sep 30, 2026
echo-yiyiyi
left a comment
Member
There was a problem hiding this comment.
Thanks for your PR @bean-1129. Could you please also add the test for this problem?
Member
|
In addition, I am planning to move |
This branch has not been deployed
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
2 participants
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.
Problem
A fresh
poetry installon a clean checkout ofmainproduces an environment whereimport oasisfails:camel-ai==0.2.90imports that symbol, which only exists inopenai>=1.100.0, but camel-ai still declaresopenai>=1.86.0. Ourpoetry.locktherefore pinnedopenai==1.91.0, which satisfies camel-ai's constraint but breaks at import time.CI doesn't catch this because the workflow uses
pip install -e ., which ignorespoetry.lockand resolves the latest openai. Only contributors following the documented Poetry setup inCONTRIBUTING.mdhit it.Reproduce (on
main)Fix
openai = ">=1.100.0"constraint inpyproject.tomlwith a comment explaining why (camel-ai's declared minimum is too low).poetry.locktoopenai==3.16.2, the same version CI resolves and passes with today. Transitive changes are limited to what openai 3.x requires:anyio,jiter,idnabumps, and the newhttpx2/httpcore2/truststorepackages.distrois dropped as it is no longer a dependency of openai. Nothing else in the lock changed.Verified
poetry syncfrom the new lock installs andimport oasissucceeds.OPENAI_API_KEY, which is the pre-existing situation.pre-commit run --all-filespasses.Related: #220 (dependency bumps; this PR is intentionally narrow and only touches the openai constraint so it can land independently).
🤖 Generated with Claude Code