New submission from Éric Piel <e.a.b.p...@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) files: future-fix-attribute.patch keywords: patch messages: 162398 nosy: pieleric priority: normal severity: normal status: open 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 <rep...@bugs.python.org> <http://bugs.python.org/issue15015> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
