QQt
Wrapper for various PySide2/PyQt5 and PySide6/PyQt6 related packages.
Overview
TBD…
Usage
TBD…
Installation
Prerequisites:
Python 3.8 or higher
pip and setuptools
To install run:
python -m pip install --upgrade QQt
Development
Prerequisites:
Development is strictly based on tox. To install it run:
python -m pip install --upgrade tox
Visit Development page.
Installation from sources:
clone the sources:
git clone https://github.com/karpierz/QQt.git QQt
and run:
python -m pip install ./QQt
or on development mode:
python -m pip install --editable ./QQt
License
Copyright (c) 2012-2024 Adam KarpierzLicensed under the zlib/libpng LicensePlease refer to the accompanying LICENSE file.
Changelog
1.2.1 (2024-01-26)
Setup update (now based on tox >= 4.0).
Add support for PyPy 3.9 and 3.10
Copyright year update.
Cleanup.
1.2.0 (2023-11-22)
Add support for Python 3.12
Drop support for Python 3.7
Setup (dependencies) update.
1.1.1 (2023-02-28)
Add support for Python 3.8, 3.9, 3.10 and 3.11
Drop support for Python 3.6.
Setup general update and cleanup.
1.1.1rc7 (2020-10-18)
Drop support for Python 3.5
Setup general update and cleanup.
Setup: fix an improper dependencies versions.
Fixed docs setup.
1.1.0rc9 (2019-11-13)
- Requirements upgrade:PySide2 to at least 5.13.2PyQt5 to at least 5.13.2
Setup updates and cleanup.
1.1.0rc7 (2019-10-29)
- Requirements upgrade:PySide2 to at least 5.13.1PyQt5 to at least 5.13.1
Adding of (for now fake/empty) test case.
Setup updates and cleanup.
1.1.0rc2 (2019-08-02)
- Requirements upgrade:QtPy to at least 1.9.0PySide2 to at least 5.13.0PyQt5 to at least 5.13.0This allows to have applications that import PySide2 and PyQt5 at the same time(which is possible if both bindings are compiled for the same Qt version).
StreamEmitter class added.
1.0.0b5 (2019-06-10)
Adding setup extras PySide and PyQt for installing PySide2 or PyQt5 backends.
Fix a bug for PySide2 as backend.
Adding a monkey-patch for vtk.qt (vtk==8.1.x).
Fixes and cleanup of setup.
1.0.0b1 (2019-05-22)
First public release.
0.0.1a1 (2012-03-9)
Initial version.
1 maintainer
Metadata
1 maintainer
Release files for QQt 1.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| QQt-1.2.1.zip | 26.3 kB | Without provenance | Details for QQt-1.2.1.zip |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| QQt-1.2.1-py3-none-any.whl | Python 3 | none | any | Details for QQt-1.2.1-py3-none-any.whl |
Total release size: 40.0 kB
Release files / QQt-1.2.1.zip
| Download URL | QQt-1.2.1.zip |
|---|---|
| Size | 26.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5cfff0f13a1d1954d92823c4154e42692c0af02ba11c807bfe015bceebb37aa8
|
|
BLAKE2b-256 checksum How to use checksums |
8ee78592c2b2dc7f7c7433a8367bf3f2144f6668dcd335c0e5300804e149e2b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.7
|
Release files / QQt-1.2.1-py3-none-any.whl
| Download URL | QQt-1.2.1-py3-none-any.whl |
|---|---|
| Size | 13.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8bf4550edf2b745f3a9daeac1500318ec8d9eb0f4e57c7f61f37278403429da4
|
|
BLAKE2b-256 checksum How to use checksums |
9662fa1d0e32d030cef13baf9cc64907699bbd3db5b6336efd03a7f50606efae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.7
|
Security for QQt 1.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
