fix: make AsyncUnleashClient a top level import - #442
Merged
Merged
Conversation
That way, users can do "from UnleashClients import AsyncUnleashClient" like they already do for the sync one. The shenanigans with typechecking are there so that aiohttp is not suddenly mandatory for users that are already importing the sync client.
sighphyre
approved these changes
Sep 30, 2026
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
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.
While testing the SDK I've found that
AsyncUnleashClientis not a top-level export.With these changes, users should be able to do
from UnleashClient import AsyncUnleashClientwithout issues. And the type checking is there to guarantee that users that are already importing UnleashClient aren't suddenly required to install aiohttp.Stack created with GitHub Stacks CLI • Give Feedback 💬