You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some users where local evaluation doesn't work, request blocking in python makes things much slower. Consider an async version of the library in this case
This is an optional library you can install if you're working with Python. It uses an internal queue to make calls fast and non-blocking. It also batches requests and flushes asynchronously, making it perfect to use in any part of your web app or other server side application that needs performance.
Does this mean we don't really need async for this library?
For some users where local evaluation doesn't work, request blocking in python makes things much slower. Consider an async version of the library in this case
This is an optional library you can install if you're working with Python. It uses an internal queue to make calls fast and non-blocking. It also batches requests and flushes asynchronously, making it perfect to use in any part of your web app or other server side application that needs performance.
Does this mean we don't really need async for this library?
Yes — it’s already asynchronous in behavior. Events are queued and sent on background threads, so capture() is non-blocking, just not async/await.
A true async client would mainly help for flag evaluation or async-native runtimes (FastAPI/asyncio), not basic event capture.
Activity
Paillat-dev commentedon Jun 17, 2024
Yes please
benrapport commentedon Aug 13, 2024
+1!
sumersao commentedon Aug 13, 2024
Please this would be a life saving!
skulltech commentedon Aug 28, 2024
This would be much appreciated!
Does this mean we don't really need async for this library?
michaelfeil commentedon Oct 9, 2024
+1
preardon commentedon Sep 3, 2025
+1
m1chll commentedon Oct 5, 2025
+1
autoluminescent commentedon Oct 8, 2025
+1
r-sniper commentedon Nov 17, 2025
Is the Zendesk request public, cause I see a not found page here
Joao-Tiago-Almeida commentedon Dec 18, 2025
+1
JasonLovesDoggo commentedon Dec 18, 2025
Yes — it’s already asynchronous in behavior. Events are queued and sent on background threads, so capture() is non-blocking, just not async/await.
A true async client would mainly help for flag evaluation or async-native runtimes (FastAPI/asyncio), not basic event capture.
natansil commentedon Feb 4, 2026
+1
marandaneto commentedon Aug 31, 2026
#899
exmaples here #899 (comment)