[issue15015] Access to non-existing "future" attribute in error path of futures

Brian Quinlan added the comment: Thanks for the patch! -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Pyt

[issue15015] Access to non-existing "future" attribute in error path of futures

Roundup Robot added the comment: New changeset 68d7c0be5890 by Brian Quinlan in branch 'default': #15015: Fix accessing an non-existing attribute. http://hg.python.org/cpython/rev/68d7c0be5890 -- nosy: +python-dev ___ Python tracker

[issue15015] Access to non-existing "future" attribute in error path of futures

Changes by Brian Quinlan : -- assignee: -> bquinlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue15015] Access to non-existing "future" attribute in error path of futures

Changes by R. David Murray : -- nosy: +bquinlan stage: -> patch review type: -> behavior versions: +Python 3.3 -Python 3.4 ___ Python tracker ___ __

[issue15015] Access to non-existing "future" attribute in error path of futures

New submission from Éric Piel : 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. Neverthele