Nathaniel J. Smith

good point -- feel free to consider them as MIT licensed. do you have something you want to use them for? just interested to hear what people are doing On...

to be clear: this is literally just `black trio_websocket tests`, no configuration, no other edits.

OK the last two commits did actually change things in trivial ways to get the lint passing. Still no semantic changes, or even syntactic ones.

There should probably also be a mechanism to cap the amount of data that trio-websocket will buffer internally, probably enabled by default with some reasonably limit and a configuration knob...

> I don't think it's possible to make network tests 100% determinstic, so a last resort we can add tests that force cover of problematic areas like lines 842-844 shown...

Have you tried profiling? I find vmprof particularly useful because it combines low-overhead, useful visualization, and a nice web interface so you can share profiles with other people. (Do be...

Oh yeah, good idea! (And we should use the terms `asyncio.gather` and `Promise.all` in the headline, because people seem to be looking for those.)

Oh, see also #421, which is a partial duplicate and has some more discussion of the nursery-based examples.

Oh duh, here's another one: an example of implementing a custom protocol, by combining a sansio protocol with the stream interface. (Probably some simple line-oriented or netstring-oriented thing. This is...

Something like @jab's HTTP CONNECT proxy from https://github.com/python-trio/trio/pull/489#issuecomment-379455747 might be interesting too. (Possibly rewritten to use h11 ;-).)