Author aeros
Recipients aeros, asvetlov, primal, yselivanov
Date 2020-01-26.09:01:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1580029280.59.0.895121797291.issue32309@roundup.psfhosted.org>
In-reply-to
Content
> So, I just had an interesting idea... what if ThreadPool.run() returned a Task instead of a coroutine object?

After having some time to think this over, I prefer the current behavior. I don't think there would be significant enough improvement from returning a Task instead, and it would likely result in an overall performance loss.

Also, as a general update on the project, I'm close to being ready to open a PR to implement asyncio.ThreadPool. I finished the basic implementation and added a decent number of new tests to ensure its functionality. Here's my current progress: https://github.com/python/cpython/compare/master...aeros:asyncio-threadpool

I just need to work on adding the new documentation, and more specifically finding a good place for it in the current asyncio docs. Do you have any ideas for that, Yury? I figured that you might already have a preference in mind.
History
Date User Action Args
2020-01-26 09:01:20aerossetrecipients: + aeros, asvetlov, yselivanov, primal
2020-01-26 09:01:20aerossetmessageid: <1580029280.59.0.895121797291.issue32309@roundup.psfhosted.org>
2020-01-26 09:01:20aeroslinkissue32309 messages
2020-01-26 09:01:20aeroscreate