[New-bugs-announce] [issue15015] Access to non-existing "future" attribute in error path of futures
report at bugs.python.org
Wed Jun 6 11:05:29 CEST 2012
New submission from Éric Piel <e.a.b.piel at tudelft.nl>:
concurrent.futures.Future.set_running_or_notify_cancel() has a reference to self.future, although Future has no future attribute. It's probably due to a copy/paste error. As it's in an error handling code path, most of the time the code is never used. Nevertheless it's worthy to fix it so that the right exception happens in case of error. This was detected by pylint.
Attaching a patch that fixes the error.
components: Library (Lib)
title: Access to non-existing "future" attribute in error path of futures
versions: Python 3.4
Added file: http://bugs.python.org/file25844/future-fix-attribute.patch
Python tracker <report at bugs.python.org>
More information about the New-bugs-announce