Matthias Urlichs
Matthias Urlichs
The way to handle this pattern reliably is to convince upstream not to use it in the first place. Yes, trio-asyncio could possibly add a workaround (or two or three...
Should be fixed in a13014d
@njsmith You're right in that `aio_as_trio` etc. are a bit cumbersome (though I got quite used to it). The problem I have with `run_asyncio` etc. (and I've gotten some feedback...
Yeah, I had that idea originally, but postponed it – as it turns out it's 3.7+ only, because it needs context management from asyncio.
Tried that. Ran into a couple of interesting cases where this is not as easy as it seems. But I'll re-check soon(ish).
Update: use sniffio to do that
Why don't you re-package the Segger code as a git repository yourself (or clone (and update?) https://github.com/PromyLOPh/rtt)? Did you ask them to please publish their code to github?
Well, it's the same query (or set of queries) every time and the system eventually runs out of memory when I do this, so no, this is memory directly allocated...
Works. Please apply!
In the meantime I'd like to promote my asyncari module. I have used it to implement a parallel phone call test system, among other ideas. https://github.com/smurfix/asyncari https://github.com/noris-network/calltest.git It depends on...