[issue32810] Expose ags_gen and agt_gen in asynchronous generators

Change by David Beazley : -- stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mail

[issue32810] Expose ags_gen and agt_gen in asynchronous generators

George Zhang added the comment: Also, while the PEP first introducing asynchronous generators stated that its .asend() and .athrow() methods will return a "coroutine-like object", it doesn't allow any introspection into its state or parent async generator. My workaround was to wrap the .asen

[issue32810] Expose ags_gen and agt_gen in asynchronous generators

Joshua Oreman added the comment: I also ran into this. My workaround was to use gc.get_referents() on the async_generator_asend object, which returns a one-element list containing the async generator object. I don't know if this is guaranteed or just happened to work in the cases I was using

[issue32810] Expose ags_gen and agt_gen in asynchronous generators

Yury Selivanov added the comment: Please don't merge the PR. I'll need some time to think about this before giving it a green light. -- ___ Python tracker ___ ___

[issue32810] Expose ags_gen and agt_gen in asynchronous generators

Zackery Spytz added the comment: I've created a PR for this issue. -- nosy: +ZackerySpytz versions: +Python 3.8 -Python 3.7 ___ Python tracker ___

[issue32810] Expose ags_gen and agt_gen in asynchronous generators

Change by Zackery Spytz : -- keywords: +patch pull_requests: +10403 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-l

[issue32810] Expose ags_gen and agt_gen in asynchronous generators

Change by Keith Dart : -- nosy: +kdart ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.or

[issue32810] Expose ags_gen and agt_gen in asynchronous generators

Change by Xavier G. Domingo : -- nosy: +xgdomingo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue32810] Expose ags_gen and agt_gen in asynchronous generators

David Beazley added the comment: I've attached a file that illustrates the issue. (Side thought: this would be nice to have in inspect or traceback) -- Added file: https://bugs.python.org/file47434/agen.py ___ Python tracker

[issue32810] Expose ags_gen and agt_gen in asynchronous generators

Andrew Svetlov added the comment: Make sense at first glaze. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue32810] Expose ags_gen and agt_gen in asynchronous generators

Change by Pablo Galindo Salgado : -- components: +asyncio ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue32810] Expose ags_gen and agt_gen in asynchronous generators

Change by Nathaniel Smith : -- nosy: +asvetlov, giampaolo.rodola, njs, yselivanov ___ Python tracker ___ ___ Python-bugs-list mailing

[issue32810] Expose ags_gen and agt_gen in asynchronous generators

Change by Yarko Tymciurak : -- nosy: +yarkot ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue32810] Expose ags_gen and agt_gen in asynchronous generators

New submission from David Beazley : Libraries such as Curio and asyncio provide a debugging facility that allows someone to view the call stack of generators/coroutines. For example, the _task_get_stack() function in asyncio/base_tasks.py. This works by manually walking up the chain of corou