issues Search Results · repo:python-trio/trimeter language:Python
Filter by
12 results
(77 ms)12 results
inpython-trio/trimeter (press backspace or delete to remove)Hi,
Every once in a while I come back to this repo because the package looks really promising. But every time it s not ready
yet. Would you be able to give a summary of where it s at and what s missing ...
Midnighter
- 2
- Opened on Nov 6, 2020
- #19
altendky@p1:~/repos/trimeter$ venv/bin/python -m pep517.build --binary --out-dir dist/ .
Traceback (most recent call last):
File /home/altendky/.pyenv/versions/3.8.5/lib/python3.8/runpy.py , line 194, ...
altendky
- Opened on Sep 2, 2020
- #17
It occurred to me that maybe capture_outcome=True should still allow KeyboardInterrupt to escape? Is this a real
problem?
njsmith
- Opened on Oct 7, 2018
- #10
Right now we only have a small set of built-in meters. It would be nice to allow people to define their own meters, I
think. I could be wrong though? I m not actually sure what the use cases for this would ...
njsmith
- Opened on Oct 7, 2018
- #9
It would be nice if we could say at most 50 tasks fetching URLs at once, and at most 5 of those for any given hostname .
So that might look something like:
await run_on_each(fetch, urls, max_at_once=50, ...
njsmith
- Opened on Oct 7, 2018
- #8
The builtin map supports multiple iterables:
In [1]: list(map(lambda x, y: x + y, [1, 2, 3], [4, 5, 6]))
Out[1]: [5, 7, 9]
(The map in concurrent.futures does too, but multiprocessing.Pool.map ...
njsmith
- 1
- Opened on Oct 7, 2018
- #7
Should there be an initial burst? Or an option to control that?
On the one hand, if you assume that we re starting from a blank slate, where everything s been idle infinitely far in
the past, then it ...
njsmith
- Opened on Oct 7, 2018
- #6
Right now, the incremental result reporting always reports results as they re ready, so the order of the output doesn t
necessarily match the order of the input. (Except for run_all, since it s not incremental ...
njsmith
- 2
- Opened on Oct 7, 2018
- #5
Right now they re all named worker, which is pretty useless.
In run_on_each, we could easily name them like f {async_fn.__name__} #{index} , which seems reasonable.
But that wouldn t help run_all, where ...
njsmith
- Opened on Oct 7, 2018
- #4
In my initial draft, I have 3 functions:
- run_on_each: concurrent map, with results optionally directed to a SendChannel, no return value
- amap: concurrent map, async with calling convention, with ...
njsmith
- 2
- Opened on Oct 7, 2018
- #3

Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip!
Restrict your search to the title by using the in:title qualifier.
Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip!
Restrict your search to the title by using the in:title qualifier.