dependabot-preview[bot] on pip
dependabot-preview[bot] on pip
Bump alembic from 1.4.0 to 1.5.… (compare)
pquentin on fedora-ci-deps
dependabot-preview[bot] on pip
Bump pytest from 6.1.2 to 6.2.1… (compare)
dependabot-preview[bot] on pip
dependabot-preview[bot] on master
Bump prompt-toolkit from 3.0.11… Merge pull request #1875 from p… (compare)
dependabot-preview[bot] on pip
dependabot-preview[bot] on master
Bump mypy from 0.790 to 0.800 … Merge pull request #1874 from p… (compare)
dependabot-preview[bot] on pip
Bump prompt-toolkit from 3.0.11… (compare)
FdStream
to talk to stdout?
Nursery
" thread, I looked into arboreal terms for "branch point", but decided against suggesting the term they use
Flume
, Canal
, Chute
, Conduit
, Intake
, Siphon
, Orifice
.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?
await nursery.start()
because with that the initial step of slow_lookup
must tell the loop that it may proceed with the next i
.
@njsmith yeah, that part in particular caught my eye. "interactive open source documentation" sounds great. hmm, yeah those are good points. although i do think the design of jupyter notebooks is pretty user-friendly. i think that even in the case of unfamiliarity with jupyter and low-level of experience with python, the barrier to figuring out how to use it would be fairly low.
to address all the points you made which are valid and i don't disagree with, perhaps the ~30 seconds to load up the notebook isn't that bad. i'm going assume that most users who would be interested in using these are users with less experience in trio than those who already know a lot about async python. when i read through the trio documentation, it takes me a while to get through. i think that is primarily a result of the density of topics. so this means for people like myself, i will already commit a hour or two to reading the documentation at a time.