Home Original page

bpo-33110: Catches errors raised when running add_done_callback on already completed futures. by martsa1 · Pull Request #13141 · python/cpython

…ready completed futures.

Wraps the callback call within the `add_done_callback` function within
concurrent.futures, in order to behave in an identical manner to
callbacks added to a running future are triggered once it has completed.

@blurb-it

brianquinlan

@martsa1

brianquinlan

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request

May 22, 2019 
…ady completed futures (pythonGH-13141)

Wrap the callback call within the `add_done_callback` function within concurrent.futures, in order to behave in an identical manner to callbacks added to a running future are triggered once it has completed.
(cherry picked from commit 2a3a2ec)

Co-authored-by: Sam Martin <ABitMoreDepth@users.noreply.github.com>

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request

May 22, 2019 
…ady completed futures (pythonGH-13141)

Wrap the callback call within the `add_done_callback` function within concurrent.futures, in order to behave in an identical manner to callbacks added to a running future are triggered once it has completed.
(cherry picked from commit 2a3a2ec)

Co-authored-by: Sam Martin <ABitMoreDepth@users.noreply.github.com>

miss-islington added a commit that referenced this pull request

May 22, 2019 
…ady completed futures (GH-13141)

Wrap the callback call within the `add_done_callback` function within concurrent.futures, in order to behave in an identical manner to callbacks added to a running future are triggered once it has completed.
(cherry picked from commit 2a3a2ec)

Co-authored-by: Sam Martin <ABitMoreDepth@users.noreply.github.com>