-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Migrate openai from 1.x to 2.2.0 #1874
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
Conversation
need to resolve mypy errors |
4abe5fa
to
e4fe1e0
Compare
.python-version | ||
.env* | ||
.venv | ||
.venv* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just to do python 3.9 more easily
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can actually remove 3.9 support soon, it is EOL this month
) from _e | ||
|
||
from openai import NOT_GIVEN, AsyncStream, NotGiven | ||
from openai import AsyncStream, NotGiven, omit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not_given still exists for backward-compatibility but migrating to omit lets this code base fully align with any patterns
@rm-openai now this PR is ready. all the things are internal changes; no public interface level breaking changes. that said, given the code changes and incompatibility with openai 1.x series, releasing a new minor version should be necessary |
.python-version | ||
.env* | ||
.venv | ||
.venv* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can actually remove 3.9 support soon, it is EOL this month
This pull request resolves #1867 This is a blocker for developers trying ChatKit Python server SDK, so we should release a new version including this bump as early as possible.
I've confirmed migrating to 2.x major version does not bring any incompatibility issues with examples in this repo.