I guess the other option for an exception would be
OSError(EBADFD) or however you spell that. But ClosedResourceError probably makes more sense, because there isn't actually any syscall returning EBADFD
(I didn't try to validate the Condition usage)
@njsmith I didn't get the
NoneType issues solve. I changed what I was doing and it didn't crop up again. I'll open an issue for the proc kill thing. As for my use of conditions: I'm really unsure how to use condition in async code. In threaded coded, I'd lock over shared data, but in async if you don't have to await while touching shared data, do you need to hold the condition (or the underlying lock?).
And thanks for opening an issue for the process kill thing
Re:
Conditions: they're pretty tricky to use! You're right that you don't necessarily need to lock your data to prevent race conditions, because so many operations in async code are automatically atomic. (Though you still might want to use locking just to be explicit and avoid having to think too hard about which operations are atomic and which ones aren't.)
But there's an additional wrinkle for
Conditions, which is that you have to be careful not to miss notifications – if you're not in cond.wait when someone calls notify, then you'll never know that it happened. And the lock can sometimes help with this, because taking the lock also blocks anyone else from calling notify.
from
print(x)
Are you using
FdStream to talk to stdout?
maybe one of my deps touched stdout
It's not easy to read this table https://trio.readthedocs.io/en/stable/reference-io.html#abstract-base-classes
because of the scrollbar
I've seen on some project's docs (can't remember which) a thing that shows the full box when you mouse over it
for some wide code-block
those animations are so frickin dope
it might be worth looking through a list of plumbing products/terms. For the "renaming
Nursery" thread, I looked into arboreal terms for "branch point", but decided against suggesting the term they use
@jtrakk that was actually on an earlier draft of that list, but I took it out because of the computer usage of "bus" as a term for interchange/routing systems: https://en.wikipedia.org/wiki/Bus_(computing)
A few of these are interesting.
https://www.ussdams.org/resource-center/glossary/
Flume, Canal, Chute, Conduit, Intake, Siphon, Orifice.https://www.ussdams.org/resource-center/glossary/
embedded visualization framework for Python programs, based on Trio
https://github.com/groove-x/pura
(shared as proof of concept, not in pypi)
https://github.com/groove-x/pura
(shared as proof of concept, not in pypi)
just discovered this project today and thought it might be interesting to try to create some trio documentation with: https://mybinder.readthedocs.io/en/latest/using.html#generating-interactive-open-source-package-documentation
@wgwz oh yeah, binder is pretty cool! (I used to work with the folks working on it.) maybe it would be useful for our hypothetical future "cookbook" documentation? it does require using jupyter notebooks, and I'm not sure if our users are familiar with those or how much work it would take to integrate them into our sphinx docs. And it they take like ~30 seconds to start. So not something you can use to easily fiddle with examples directly while reading the docs.
What's the easiest way to run a bunch of tasks in a given order with at most n in parallel.
async def main():
async with trio.open_nursery() as nursery:
for i in range(1000):
nursery.start_soon(slow_lookup, i)In the example, other parts of the code are awaiting for a specific value j to be mapped to an i. Lower values of i are much more likely to map to any j, so I'd like to start them in order. Does that make sense?
