fix: use correct default factory for headers and preserve subclass types in replace() #1180
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 kind of change does this PR introduce?
Bug fix
What is the current behavior?
headers
field usesDEFAULT_HEADERS.copy
directly, which evaluates at module load time. This can lead to shared state across instances.replace()
method instantiatesClientOptions()
directly, breaking subclass behavior forAsyncClientOptions
andSyncClientOptions
.What is the new behavior?
headers
field now uses a lambda to ensure a fresh copy ofDEFAULT_HEADERS
per instance.replace()
method now usestype(self)()
to preserve subclass overrides.Additional context
This PR only addresses the bugs listed above.