Restore relaxation of openai version range, lost after refactor #8112
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.
Recently, #8075 was opened to note that limiting openai to version 1.61.0 was causing problems.
This was fixed for 2.6.18 in #8084 . However that change only changed one of two entries in
pyproject.toml
that defines the openai range, as there were parallel configurations of dependencies for poetry and uv.Then, just before 2.6.19, this PR removed the poetry-oriented dependencies, including the openai change:
0363c2e#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711L36-L106
Now,
pyproject.toml
is left with the other copy which still has the version limit of 1.61.0:https://github.com/stanfordnlp/dspy/blob/main/pyproject.toml#L27
This just completes the intent of the original change by removing the version limit on openai.
CC @okhat @chenmoneygithub