| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
Add a diagram that explains coroutines to the QtAsyncio documentation
instead of just linking readers to the YouTube video.
Pick-to: 6.7
Task-number: PYSIDE-769
Change-Id: I33cb381958313ce1ce2c01eae10eca073761af85
Reviewed-by: Shyamnath Premnadh <[email protected]>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Remove the optional application argument from the constructor of
QAsyncioEventLoopPolicy, as it is unnecessary. If a QCoreApplication or
other type of qApp was created outside of QtAsyncio, it will always be
retrieved by QCoreApplication.instance(), and therefore passing it as an
argument makes little sense.
Task-number: PYSIDE-769
Change-Id: Iac7a913a1c9d6ebbb0984fe11f8b5cda955baab1
Reviewed-by: Friedemann Kleint <[email protected]>
Reviewed-by: Christian Tismer <[email protected]>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
An argument handle_sigint determines whether QtAsyncio should handle
SIGINT (Ctrl+C) and shut down the event loop when it is received. The
default is False. This can be set to True if you want QtAsyncio to take
care of handling SIGINT instead of your program.
Pick-to: 6.6
Task-number: PYSIDE-769
Change-Id: Ie4364025448405f36158a8e997d90ae143961ba8
Reviewed-by: Cristian Maureira-Fredes <[email protected]>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A new optional argument quit_qapp can be passed to QtAsyncio.run()
to configure whether the QCoreApplication at the core of QtAsyncio
should be shut down when asyncio finishes. A special case where one
would want to disable this is test suites that want to reuse a single
QCoreApplication instance across all unit tests, which would fail if
this instance is shut down every time.
Pick-to: 6.6
Fixes: PYSIDE-2575
Task-number: PYSIDE-769
Change-Id: I49cd0a50311fb30cc50df9b7f6a6d73fe8c58613
Reviewed-by: Shyamnath Premnadh <[email protected]>
Reviewed-by: Friedemann Kleint <[email protected]>
|
|
|
Add a documentation page for QtAsyncio. As a pure Python module, the
build process is different from the other modules, as we don't want
shiboken to run for it - all we need is a simple rst compilation.
The "Copying docs..." step of "ninja apidoc" (see
sources/pyside6/doc/CMakeLists.txt) copies the entire
sources/pyside6/doc directory recursively into the build directory.
We can tap into this to make sure the rst will be in the correct
location for the sphinx compilation step.
Pick-to: 6.6
Task-number: PYSIDE-769
Task-number: PYSIDE-1112
Change-Id: Ia03a2a4505d745ca052f0edb529e85a8bfb9d552
Reviewed-by: Cristian Maureira-Fredes <[email protected]>
Reviewed-by: Friedemann Kleint <[email protected]>
|
