[PySide] [PyQt] user interface freezed when using concurrent.futures.ThreadPoolExecutor

michael h michaelkenth at gmail.com
Thu Dec 11 00:53:03 CET 2014

On Wed, Dec 10, 2014 at 12:07 AM, iMath <2281570025 at qq.com> wrote:

> I think the user interface shouldn't be freezed when using
> concurrent.futures.ThreadPoolExecutor here, but it doesn't meet my
> expectations,anyone can explain why ? any other solutions here to not let
> user interface freezed?‍
> code is here
> http://stackoverflow.com/questions/27393533/user-interface-freezed-when-using-concurrent-futures-threadpoolexecutor
>> <http://stackoverflow.com/questions/27393533/user-interface-freezed-when-using-concurrent-futures-threadpoolexecutor>
> _______________________________________________
> PyQt mailing list    PyQt at riverbankcomputing.com
> http://www.riverbankcomputing.com/mailman/listinfo/pyqt

It appears: concurrent.futures.as_completed yields futures as they
complete, so the main thread is blocked as it loops over this until all the
futures have completed.

You could use Qt's QNetworkAccessManager / QNetworkRequest, or perhaps you
want something like scrapy if you're trying to crawl websites (could
probably be integrated with a Qt app using qt4reactor)

What are you building?

- MH
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20141210/171ddf76/attachment.html>

More information about the PySide mailing list