Refactor create_client functions to call constructor directly #805
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?
Refactor changes discussed in #798
What is the current behavior?
Right now,
acreate_client
is a re-import of the_async.client.create_client
function. This function, in its body, calls theAsyncClient.create
asynchronous class method (see source code). This method itself callsAsyncClient.__init__
(see source code). This chain of function calls, passing the same arguments with the same names three times until it reaches the destination constructor, seems to introduce some unnecessary abstractions.What is the new behavior?
Both
_async.client.create_client
and_sync.client.create_client
directly call the corresponding class's constructors (AsyncClient.__init__
andSyncClient.__init__
).Meta
Closes #798