This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2012年06月06日 09:05 by pieleric, last changed 2022年04月11日 14:57 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| future-fix-attribute.patch | pieleric, 2012年06月06日 09:05 | Patch to fix access to non-existing "future" attribute | review | |
| Messages (3) | |||
|---|---|---|---|
| msg162398 - (view) | Author: Éric Piel (pieleric) | Date: 2012年06月06日 09:05 | |
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. |
|||
| msg162602 - (view) | Author: Roundup Robot (python-dev) (Python triager) | Date: 2012年06月11日 03:03 | |
New changeset 68d7c0be5890 by Brian Quinlan in branch 'default': #15015: Fix accessing an non-existing attribute. http://hg.python.org/cpython/rev/68d7c0be5890 |
|||
| msg162603 - (view) | Author: Brian Quinlan (bquinlan) * (Python committer) | Date: 2012年06月11日 03:06 | |
Thanks for the patch! |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022年04月11日 14:57:31 | admin | set | github: 59220 |
| 2012年06月11日 03:06:31 | bquinlan | set | status: open -> closed resolution: fixed messages: + msg162603 |
| 2012年06月11日 03:03:52 | python-dev | set | nosy:
+ python-dev messages: + msg162602 |
| 2012年06月06日 20:26:16 | bquinlan | set | assignee: bquinlan |
| 2012年06月06日 13:05:15 | r.david.murray | set | nosy:
+ bquinlan stage: patch review type: behavior versions: + Python 3.3, - Python 3.4 |
| 2012年06月06日 09:05:29 | pieleric | create | |