➜

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, mark.dickinson, python-dev, vstinner
Date 2014-06-03.23:17:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1401837475.07.0.725621843486.issue21326@psf.upfronthosting.co.za>
In-reply-to
Content 
I fixed the issue in Python 3.5 by adding a new BaseEventLoop.is_closed() method. Calling run_forever() or run_until_complete() now raises an error.

I don't know yet if this issue should be fixed in Python 3.4. If it should be fixed, I don't know how it should be fixed. Guido was unhappy with subclasses of BaseEventLoop accessing the private attribute BaseEventLoop._closed in the review of my patch.
History
Date User Action Args
2014-06-03 23:17:55vstinnersetrecipients: + vstinner, gvanrossum, mark.dickinson, python-dev
2014-06-03 23:17:55vstinnersetmessageid: <1401837475.07.0.725621843486.issue21326@psf.upfronthosting.co.za>
2014-06-03 23:17:55vstinnerlinkissue21326 messages
2014-06-03 23:17:54vstinnercreate