Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions README.rst
Original file line number Diff line number Diff line change
Expand Up @@ -36,8 +36,8 @@ The QTrio project's goal is to bring the friendly concurrency of Trio using Pyth
``async`` and ``await`` syntax together with the GUI features of Qt to enable more
correct code and a more pleasant developer experience. QTrio is `permissively licensed
<https://github.com/altendky/qtrio/blob/main/LICENSE>`__ to avoid introducing
restrictions beyond those of the underlying Python Qt library you choose. Both PySide2
and PyQt5 are supported.
restrictions beyond those of the underlying Python Qt library you choose. PyQt5, PyQt6,
PySide2, and PySide6 are supported.

By enabling use of ``async`` and ``await`` it is possible in some cases to write
related code more concisely and clearly than you would get with the signal and slot
Expand Down Expand Up @@ -176,8 +176,8 @@ really containing the activity.
:target: `repository`_
:alt: Repository

.. _tests: https://github.com/altendky/qtrio/actions?query=branch%3Amaster
.. |tests badge| image:: https://img.shields.io/github/workflow/status/altendky/qtrio/CI/main?color=seagreen&logo=GitHub-Actions&logoColor=whitesmoke
.. _tests: https://github.com/altendky/qtrio/actions?query=branch%3Amain
.. |tests badge| image:: https://img.shields.io/github/actions/workflow/status/altendky/qtrio/ci.yml?branch=main&color=seagreen&logo=GitHub-Actions&logoColor=whitesmoke
:target: `tests`_
:alt: Tests

Expand Down
6 changes: 3 additions & 3 deletions docs/source/development/testing.rst
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ You can run ``pytest``, ``black``, and ``sphinx`` directly from your own install

python -m venv testvenv
testvenv/bin/python -m pip install --upgrade pip setuptools wheel
testvenv/bin/python -m pip install --editable .[pyside2,p-checks,p-docs,p-tests]
testvenv/bin/python -m pip install --editable .[pyside6,p-checks,p-docs,p-tests]
testvenv/bin/pytest --pyargs qtrio

The CI test script, ``ci.sh``, in the project root will run ``pytest`` with ``coverage``
Expand Down Expand Up @@ -56,8 +56,8 @@ The documentation can be built with ``sphinx``.

python -m venv testvenv
testvenv/bin/python -m pip install --upgrade pip setuptools wheel
testvenv/bin/python -m pip install --editable .[pyside2,p-docs]
source testenv/bin/activate
testvenv/bin/python -m pip install --editable .[pyside6,p-docs]
source testvenv/bin/activate
cd docs/
make html --always-make

Expand Down
4 changes: 3 additions & 1 deletion docs/source/getting_started.rst
Original file line number Diff line number Diff line change
Expand Up @@ -27,13 +27,15 @@ are available for installing optional dependencies or applying version constrain
- ``cli`` - For CLI usage, presently just examples.
- ``examples`` - For running examples.
- ``pyqt5`` - For running with PyQt5, primarily to apply any version constraints.
- ``pyqt6`` - For running with PyQt6, primarily to apply any version constraints.
- ``pyside2`` - For running with PySide2, primarily to apply any version constraints.
- ``pyside6`` - For running with PySide6, primarily to apply any version constraints.

A normal installation might look like:

.. code-block:: bash

$ myenv/bin/pip install qtrio[pyside2]
$ myenv/bin/pip install qtrio[pyside6]

Overview
--------
Expand Down
3 changes: 1 addition & 2 deletions docs/source/history.rst
Original file line number Diff line number Diff line change
Expand Up @@ -11,8 +11,7 @@ QTrio 0.8.0 (2026-07-22)
Breaking changes
~~~~~~~~~~~~~~~~

- QTrio now requires Python 3.10 or newer. Support for Python 3.7, 3.8, and 3.9 has been removed. (`#286 <https://github.com/altendky/qtrio/issues/286>`__)

- QTrio now requires Python 3.10 or newer. Support for Python 3.7, 3.8, and 3.9 has been removed. PySide2 remains supported, but is untested. (`#286 <https://github.com/altendky/qtrio/issues/286>`__)

Features
~~~~~~~~
Expand Down
4 changes: 2 additions & 2 deletions qtrio/_core.py
Original file line number Diff line number Diff line change
Expand Up @@ -163,8 +163,8 @@ class Emission:
Note:
Each time you access a signal such as ``a_qobject.some_signal`` you get a
different signal instance object so the ``signal`` attribute generally will not
be the same object. A signal instance is a ``QtCore.SignalInstance`` in
PySide2 or ``QtCore.pyqtBoundSignal`` in PyQt5.
be the same object. A signal instance is a ``QtCore.SignalInstance`` in PySide or
``QtCore.pyqtBoundSignal`` in PyQt.
"""

signal: "QtCore.SignalInstance"
Expand Down
2 changes: 1 addition & 1 deletion setup.cfg
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ project_urls =
description = a library bringing Qt GUIs together with ``async`` and ``await`` via Trio
long_description = file: README.rst
long_description_content_type = text/x-rst
keywords = async, io, Trio, GUI, Qt, PyQt5, PySide2
keywords = async, io, Trio, GUI, Qt, PyQt5, PyQt6, PySide2, PySide6
classifiers =
License :: OSI Approved :: MIT License
License :: OSI Approved :: Apache Software License
Expand Down
Loading