Message334109
Currently AbstractEventLoop.run_in_executor is specified as a coroutine, while BaseEventLoop.run_in_executor is actually a non-coroutine that returns a Future object. The behavior of BaseEventLoop.run_in_executor would be significantly different if changed to align with the interface . If run_in_executor is a coroutine then the provided func will not actually be scheduled until the coroutine is awaited, which conflicts with the statement in PEP 3156 that it "is equivalent to `wrap_future(executor.submit(callback, *args))`".
There has already been an attempt in bpo-32327 to convert this function to a coroutine. We should change the interface specified in `AbstractEventLoop` to indicate that `run_in_executor` is not a coroutine, which should help ensure it does not get changed in the future without full consideration of the impacts. |
|
Date |
User |
Action |
Args |
2019-01-21 02:59:21 | chrahunt | set | recipients:
+ chrahunt, asvetlov, yselivanov |
2019-01-21 02:59:18 | chrahunt | set | messageid: <1548039558.68.0.986540752255.issue35792@roundup.psfhosted.org> |
2019-01-21 02:59:18 | chrahunt | link | issue35792 messages |
2019-01-21 02:59:18 | chrahunt | create | |
|