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
This would open a big opportunity to implement new features like htop-like coroutine live monitor with metrics like "most/least recently yielded tasks", "active duration", etc.
The problem is that asyncio and trio has completely different instrumentation interface (asyncio.set_task_factory() and trio.lowlevel) and asyncio lacks many of detailed information available in trio.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Trio has a very detailed low-level APIs to instrument the event loop and tasks for fine-grained debugging.
ref) https://trio.readthedocs.io/en/stable/reference-lowlevel.html
This would open a big opportunity to implement new features like htop-like coroutine live monitor with metrics like "most/least recently yielded tasks", "active duration", etc.
The problem is that asyncio and trio has completely different instrumentation interface (
asyncio.set_task_factory()
andtrio.lowlevel
) and asyncio lacks many of detailed information available in trio.How could we embrace both event loop frameworks?
Beta Was this translation helpful? Give feedback.
All reactions