[issue18212] No way to check whether Future is finished?

Change by Irit Katriel : -- resolution: -> rejected stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue18212] No way to check whether Future is finished?

Ram Rachum added the comment: What do you think about exposing this directly? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18212 ___ ___

[issue18212] No way to check whether Future is finished?

Josh Rosenberg added the comment: Have an idea for a name? It already has a done method, which happens to cover the case of a Future having completed successfully, completed due to an exception or having been cancelled. Simply calling it finished(), completed() etc. isn't markedly different

[issue18212] No way to check whether Future is finished?

Josh Rosenberg added the comment: Ugh. Left out a key word: I see this as making it even easier to do threading *badly*, rather than a legitimate improvement. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18212

[issue18212] No way to check whether Future is finished?

New submission from Ram Rachum: I have a `Future` and I want to check whether it's in finished state. It seems like I don't have a method to do that, right? (I could emulate the existing methods for checking Future state, but that would mean fiddling with private variables.) Why not just

[issue18212] No way to check whether Future is finished?

Richard Oudkerk added the comment: Do you want something like f.done() and not f.cancelled() and f.exception() is None -- nosy: +sbt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18212

[issue18212] No way to check whether Future is finished?

Ram Rachum added the comment: I guess that'd be equivalent, yes. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18212 ___ ___ Python-bugs-list