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 methane
Recipients giampaolo.rodola, gvanrossum, methane, vstinner, yselivanov
Date 2016-07-12.08:50:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1468313403.61.0.601573175415.issue26081@psf.upfronthosting.co.za>
In-reply-to
Content
> asyncio uses loop.create_future() to create sockets.  I'd suggest you to create two base test classes: one that monkeypatches loop.create_future to return pure python Future in its setUp method; an another, that makes create_future to return a C version of the Future.

windows_events.py has some classes extends futures.Future.
Task extends Future.
There are some `isinstance(future, futures.Future)`.

So monkeypatching `baseevent.create_future` seems not enough.
I want a way to completely reload asyncio and test_asyncio packages with and without C future.
History
Date User Action Args
2016-07-12 08:50:03methanesetrecipients: + methane, gvanrossum, vstinner, giampaolo.rodola, yselivanov
2016-07-12 08:50:03methanesetmessageid: <1468313403.61.0.601573175415.issue26081@psf.upfronthosting.co.za>
2016-07-12 08:50:03methanelinkissue26081 messages
2016-07-12 08:50:03methanecreate