Nick Badger

I just got bit by this as well, and I wanted to chime in my two cents. First of all, it sounds (from the other discussions) that the original reason...

(1): awesome. If nobody gets around to it by then, I may be able to take care of that in the next few weeks, assuming someone can point me the...

(1): 👍 I'll see what I can do. (2): Gotcha, I didn't realize the policy was that loosely coupled with the loop. What about "The current context is defined by...

I'm not 100% sure, but I believe I'm seeing the same behavior. I'm trying to do ``CREATE DATABASE``, which **cannot** be within a transaction block, and postgres is telling me...

Ah, that reminds me about a particular plot-thickening. Before I reread the Trio docs and saw ``do_handshake``, I was reading a very small amount of data -- single digit bytes...

I didn't get a chance to look at this yet -- I've gotten really sucked into implementing the actual reverse proxy for HTTP, which has been... surprisingly tricky actually, I...

> I assume just calling object.__setattr__(exception, '__traceback__', ...) wouldn't work then? That would work, and it's actually a very common pattern (at least in my experience) when working with frozen...

Also, an example use case for why you might want to have frozen dataclass instances for exceptions: at my dayjob we're running... what could be concisely but not 100% accurately...

For what it's worth, I just ran into a use case, though it is probably indeed uncommon (at least based on how difficult it was to find google results about...

I just got bit by this too. Min viable reproduction, in case it's useful as a testcase somewhere (though probably not because of the added trio_asyncio dep): ```python import asyncio...