Kaleb Barrett
Kaleb Barrett
Yeah, Ill try to find time for it in 2.1. There's a lot going on.
I've decided to change the implementation to instead do a regular cancel and then once we get to `__aexit__` to uncancel.
Well I realize now why asyncio makes cancellation and uncancellation a count instead of a boolean flag: nested TaskManagers.
Moved the docs to `coroutines.rst`.
@marlonjames Added per-Task `continue_on_error`. Still need to add tests. I changed the `fork` method to support this with the following. `start_soon` just take an additional keyword argument. ```python async with...
Oooo, should the constructor's `continue_on_error` also act as the per-Task `continue_on_error` for the context block (parent Task)? I think I need just a bit more work/tests.
Split constructor `continue_on_error` into `default_continue_on_error` that defaults the value for all child tasks and `context_continue_on_error` which is the continue_on_error for the context block if there's a non-external-cancellation. @cmarqu I also...
noxfile.py `release_install` needs the new dependency added.
So I changed the interface around a bit so that `_start_soon` now takes Tasks and each caller is in charge of cleaning up newly-started coros if we aren't in a...
Consider adding code to clean up any lists of Exceptions or Tasks that aren't a part of the API to help the GC.