Nathaniel J. Smith

@tgoodlet ah, yeah, what you're hitting is a different frustrating problem. The problem is that neither you nor Python are taking responsibility for making sure your async generator object gets...

BTW @smurfix, I'd still be interested in seeing how you managed to trigger the original issue in real code, in case you still remember. You say it's a common mistake,...

#746 was a duplicate of this. @oremanj, can you give an example of what you were doing when you ran into this? I'm still having trouble getting an intuition for...

Yeah, it's trivial to teach `MultiError.split` and `MultiError.catch` to work on non-`MultiError` exceptions – in fact they already do, in the prototype – but it's less trivial to find all...

The discussion in https://github.com/python-trio/pytest-trio/pull/77 managed to isolate a case where this could happen accidentally in real-world code. That example seems to rely on a combination of multiple factors: two nested...

> However, this does bring to mind a sneaky option that I kind of like: dynamically create a new type that derives from both trio.Cancelled and the propagating exception, fill...

gevent monkey patches like, every io routine in the standard library. Idk what exactly the interaction is that's breaking trio but it's super unsurprising that something is breaking, because you're...

It has become less common, though, now that many projects provide self-contained wheels.

It can be useful, but it's also confusing and can cause problems, and not just for discoverability. If two packages have different names, but provide the same import name, then...

I suppose that standardizing `top-level.txt` could be the mechanism for adding that information to the standard metadata.