This release is a pre-release and may not be stable for production use.
qtbricks
Python Qt components: widgets and utils, focussing on scientific GUIs.
Welcome! This is qtbricks, a Python package collecting a growing series of “real-world” GUI widgets and related tools written with and for PySide6, the official Python bindings for Qt6.
Do you want or need to create complex GUIs with Python and Qt but don’t want to spend too much time reimplementing seemingly basic widgets and functionality? Are you overwhelmed by the complexity of GUI programming and just want to focus on the actual tasks that need to get done? So do we, and that’s how qtbricks was born. Separate the GUI from the business logic in your code, provide a series of high-level GUI widgets for (admittedly complex) standard tasks, focus on as readable and as Pythonic code as possible. And yes, it has a clear focus on GUIs for scientific data analysis tasks.
Features
A list of features:
Highly modular code: each widget is as self-contained as possible
User-friendly: obvious behaviour, no surprises, hints (via tooltips) included
Separation of concerns: widgets handle the GUI stuff and expose a programmatic API
Designed with code readability in mind
And to make it even more convenient for users and future-proof:
Open source project written in Python (>= 3.7)
Developed fully test-driven (well, not yet…)
Extensive user and API documentation
Installation
To install the qtbricks package on your computer (sensibly within a Python virtual environment), open a terminal (activate your virtual environment), and type in the following:
pip install qtbricks
License
This program is free software: you can redistribute it and/or modify it under the terms of the BSD License.
A note on the name
Why “qtbricks”? What is in a name? A name should answer the important questions (What is it? What does it?), should be easy to remember and reasonably unique to be searchable (findable!) on the web. Bricks are basic building blocks, more generic than the term “widget” in a GUI context, and after all, bricks seem to have a natural connection to windows, haven’t they?
1 maintainer
Metadata
1 maintainer
Release files for qtbricks 0.1.0rc3
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 | |
|---|---|---|---|---|
| qtbricks-0.1.0rc3.tar.gz | 82.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| qtbricks-0.1.0rc3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 198.5 kB
Release files / qtbricks-0.1.0rc3.tar.gz
| Download URL | qtbricks-0.1.0rc3.tar.gz |
|---|---|
| Size | 82.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
25d56664dfc66539dd5e4b719f6a2af620435432cefc630d7716ab1251fd5cd5
|
|
BLAKE2b-256 checksum How to use checksums |
90240fa2fc7b9670f969e2960ed298e9e9d927d50f405937b6046d51b0413f3f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.2
|
Release files / qtbricks-0.1.0rc3-py3-none-any.whl
| Download URL | qtbricks-0.1.0rc3-py3-none-any.whl |
|---|---|
| Size | 115.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b60003e00b4799a3d386cd62822a7ed92fa73fe6895432e641196137f62f1bac
|
|
BLAKE2b-256 checksum How to use checksums |
df4c0b99a98ec8b444a9463dc7941919d30af3e334a9fbec5ceeb8e33b7d3995
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.2
|
Security for qtbricks 0.1.0rc3
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.
