Joshua Oreman

Another use: Trio wants to clean up async generators in one way (#265); asyncio uses a different approach. trio-asyncio should use the right set of async generator semantics for the...

I was imagining that the global asyncgen hooks (presumably installed by Trio) would check the scopevar for an optional override of "what hooks to use in this context". That way...

> I'd recommend to simply add a `with_value_of(contextvar,func,*args)` method to the nursery. That method would grab the contextvar's value from the nursery's context, sets the contextvar to it, and call...

An unresolved question: what should happen around `nursery.start()` when tasks can move from one scope to another? For some uses of scopevars (like "here is your trio-asyncio loop") you want...

> Also, I'm not sure "scope" is the best name here... a lot of things are scopes :-). Maybe TreeVar? Agreed that that's a much better name! > Consider the...

This is a fascinating corner of TCP and I appreciate your bringing it to our attention! I spent some time reading through the resources you linked to. As I understand...

Nuitka apparently produces coroutine objects that don't have an associated frame. This is not in keeping with standard Python behavior, and breaks Trio's KeyboardInterrupt protection mechanism. (In general, producing a...

Some thoughts from more experience working with not-in-memory channels: * `send_nowait` and `receive_nowait` seem cumbersome to have as required methods -- do we expect them to ever be useful for...

> What if `open_memory_channel` returned a pair of _bidirectional_ channels? Intriguing! If we expect most applications to still be unidirectional, we run into the problem that different users might pick...

> If producers only call send, and consumers only call receive, then I think the closure tracking ends up working exactly the same way? You don't need half-close. If you...