fix(types): use in_memory prompt_cache_retention literal#2989
Open
theamodhshetty wants to merge 1 commit intoopenai:mainfrom
Open
fix(types): use in_memory prompt_cache_retention literal#2989theamodhshetty wants to merge 1 commit intoopenai:mainfrom
theamodhshetty wants to merge 1 commit intoopenai:mainfrom
Conversation
1 task
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
1 participant
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.
Summary
"in-memory"prompt cache retention literal with"in_memory"across the Python SDK type surfaceWhy
The SDK currently types
prompt_cache_retentionas"in-memory" | "24h", but the API expects"in_memory" | "24h". That makes the typed value fail at runtime and also leaves the generated request helpers internally inconsistent.Testing
./.venv/bin/ruff check src/openai/resources/chat/completions/completions.py src/openai/resources/responses/responses.py src/openai/types/chat/completion_create_params.py src/openai/types/responses/response.py src/openai/types/responses/response_create_params.py src/openai/types/responses/responses_client_event.py src/openai/types/responses/responses_client_event_param.py tests/api_resources/chat/test_completions.py tests/api_resources/test_responses.py./.venv/bin/pyright -p pyproject.toml src/openai/resources/chat/completions/completions.py src/openai/resources/responses/responses.py src/openai/types/chat/completion_create_params.py src/openai/types/responses/response.py src/openai/types/responses/response_create_params.py src/openai/types/responses/responses_client_event.py src/openai/types/responses/responses_client_event_param.py tests/api_resources/chat/test_completions.py tests/api_resources/test_responses.py./.venv/bin/mypy src/openai/resources/chat/completions/completions.py src/openai/resources/responses/responses.py src/openai/types/chat/completion_create_params.py src/openai/types/responses/response.py src/openai/types/responses/response_create_params.py src/openai/types/responses/responses_client_event.py src/openai/types/responses/responses_client_event_param.pyNotes
I also updated the affected generated API-resource tests, but I did not run those end-to-end locally because this checkout does not currently have the repo mock server running on
127.0.0.1:4010.