Fixing issues with openai integration on python 3.9 #918
Conversation
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
cretz
reviewed
Jun 23, 2025
cretz
approved these changes
Jun 25, 2025
tconley1428
added a commit
that referenced
this pull request
Aug 28, 2025
* Fixing issues with openai integration on python 3.9 * Restrict eval_type to python 3.9
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.
What was changed
Include
eval-type-backportwhen using OpenAI, fix a few type imports, unblock testsWhy?
The integration should work on all applicable python versions
Checklist
Closes Fix OpenAI extension issues on python 3.9-3.10 #914
How was this tested: