trimeter
trimeter copied to clipboard
python-trio
(not ready yet) A simple but powerful job scheduler for Trio programs
Roadmap
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...
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,...
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...
The builtin `map` supports multiple iterables: ```python 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`...
It occurred to me that maybe `capture_outcome=True` should still allow `KeyboardInterrupt` to escape? Is this a real problem?
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?...
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...
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...
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 you...
Metadata
Owner
Metadata
(not ready yet) A simple but powerful job scheduler for Trio programs