A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated.

Once you have made the requested changes, please leave a comment on this pull request containing the phraseI have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

Please don't merge this. I'm not sure i want them to be exposed.

@1st1 thank you for sharing your worries.
I'll assign you to the PR.
You will decide, ok?

@1st1, just wondering if there is any update for this idea? Should the PR be closed so that the discussion can happen on the bug tracker first? Thanks!

We need to consider this carefully. Exposing these fields pins the current implementation and might prevent us from evolving it. It's also unclear if it's possible to implement this in PyPy et al

Another way of fixing the issue described inbpo-32810 without adding extra field names is to exposeasync_generator.ag_* asasync_generator_asend.cr_* (andasync_generator_athrow.cr_*), i.e:

• async_generator_asend.cr_await ->async_generator_asend.ags_gen.ag_await
• async_generator_asend.cr_code ->async_generator_asend.ags_gen.ag_code
• async_generator_asend.cr_frame ->async_generator_asend.ags_gen.ag_frame
• async_generator_asend.cr_running ->async_generator_asend.ags_gen.ag_running
• async_generator_athrow.cr_await ->async_generator_athrow.agt_gen.ag_await
• async_generator_athrow.cr_code ->async_generator_athrow.agt_gen.ag_code
• async_generator_athrow.cr_frame ->async_generator_athrow.agt_gen.ag_frame
• async_generator_athrow.cr_running ->async_generator_athrow.agt_gen.ag_running

Retrieving the stack can then be implemented by simply walking up the chain of coroutines usingcr_await andcr_frame. This would work transparently whether the stack contains async generators or not.

https://bugs.python.org/issue32810 is closed. What is the status of this PR?

I fixed the merge conflicts, but the tests are failing all over the place. It looks to me the assumptions in the test in6024d01 from 2018 won't hold in 2023.

I am just closing this. In 2018@1st1 didn't like the idea of exposing these fields. Here we are 6 years later and the only reason we're back looking at this is that someone decided to audit the OP's PRs.