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.

Author vstinner
Recipients gvanrossum, python-dev, vstinner, yselivanov
Date 2015-01-14.16:16:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1421252201.24.0.852391666981.issue23197@psf.upfronthosting.co.za>
In-reply-to
Content
Ok, I commited my changes to Python 3.4, Python 3.5 and Tulip. All calls to set_result/set_exception should now be protected by a check on the future state.

There is now a new class of bugs, but it's a different issue:
https://code.google.com/p/tulip/issues/detail?id=218

I close this issue.
History
Date User Action Args
2015-01-14 16:16:41vstinnersetrecipients: + vstinner, gvanrossum, python-dev, yselivanov
2015-01-14 16:16:41vstinnersetmessageid: <1421252201.24.0.852391666981.issue23197@psf.upfronthosting.co.za>
2015-01-14 16:16:41vstinnerlinkissue23197 messages
2015-01-14 16:16:41vstinnercreate