[issue22729] concurrent.futures `wait` and `as_completed` depend on private api

Brian Quinlan added the comment: How did the experiment go? Are people still interested in this? -- ___ Python tracker ___ ___

[issue22729] concurrent.futures `wait` and `as_completed` depend on private api

Ben Mather added the comment: @Nathaniel RE `remove_done_callback`: This was added as an optimisation to allow the `as_completed` iterator to remove callbacks for future that it has visited instead of having to store a separate set of visited futures and ignore them

[issue22729] concurrent.futures `wait` and `as_completed` depend on private api

Change by Antoine Pitrou : -- versions: +Python 3.7 -Python 3.4, Python 3.5, Python 3.6 ___ Python tracker ___

[issue22729] concurrent.futures `wait` and `as_completed` depend on private api

Ben Mather added the comment: The patch is indeed a little outdated, but I would be happy to pick it and get it working again. First we need a resolution to #22630 though. Currently calling `cancel` will invoke callbacks, but waiters won't be triggered until

[issue22729] concurrent.futures `wait` and `as_completed` depend on private api

Antoine Pitrou added the comment: This looks like a good idea. Unfortunately, the patch is most certainly outdated. -- ___ Python tracker

[issue22729] concurrent.futures `wait` and `as_completed` depend on private api

Gregory P. Smith added the comment: any thoughts on this Antoine? -- nosy: +gregory.p.smith, pitrou title: `wait` and `as_completed` depend on private api -> concurrent.futures `wait` and `as_completed` depend on private api ___