borco-pyside
Generic, reusable PySide6/Qt classes and utilities.
Status
Pre-alpha. This package is not rehuco-specific — it is a home for generic, reusable Qt code. It is currently
developed inside the rehuco monorepo and will later move to its own repository.
If you use borco-pyside from PyPI, this move will be handled automatically.
What it is
borco-pyside holds general-purpose building blocks that depend on PySide6/Qt. GUI-free counterparts live in
borco-core. It is the successor of an earlier standalone PySide utility library.
Currently provides:
borco_pyside.core— application-lifecycle primitives:ApplicationSingleton(single-instance guard forwarding argv to the first process),ConnectionList,SimpleProperty/TypedProperty.borco_pyside.dialogs— a modeless, dockable dialog framework:DockableDialog,DockableDialogFrame,DockableDialogManager.borco_pyside.file_browser—reveal_in_file_browser, showing a path in Explorer, Finder or the Linux file manager.borco_pyside.logging— logging for a GUI app:LogBridge,LogModel,LogWidget,LogView, plus console setup viasetup_console_logging.borco_pyside.platforms— platform-specific modules, each imported only on its own platform (e.g.platforms.windows.window_activation).borco_pyside.qtads— generic helpers forpyside6-qtads(QtAds):QtAdsFocusTracker(which dock is current, per manager),QtAdsMaximizeHandler(a maximize toggle on every dock's tab),QtAdsAutoHideButtonSuppressor,QtAdsPinSideHandler,QtAdsFloatingShowGuard,tab_close_button,tab_label,tab_maximize_button.borco_pyside.recycle_bin— moving a file to the Recycle Bin / Trash throughsend2trash, behind oneRecycleBinsingleton; refuses withNoRecycleBinErrorwhen no bin is reachable for the path (on Windows, decided per drive up front viaSHQueryRecycleBinW) rather than deleting permanently.borco_pyside.theming— theme switching, SVG recoloring, and themed action icons:ThemeManager,ThemeMenu,ThemeModel,ActionIconThemeHandler.borco_pyside.widgets— reusable widgets:ItemListEditor,MessageBanner,Rating,RichTextView,StringListEditor,UnboundedSpinBox, and other small building blocks.
Installation
pip install borco-pyside
Metadata
Release files for borco-pyside 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| borco_pyside-0.2.0.tar.gz | 267.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| borco_pyside-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 440.4 kB
Release files / borco_pyside-0.2.0.tar.gz
| Download URL | borco_pyside-0.2.0.tar.gz |
|---|---|
| Size | 267.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2fb94331417c35fb2e27d4f1c466d9cfbbbfbed8850ad36e7aa309d2083e6cf9
|
|
BLAKE2b-256 checksum How to use checksums |
ecfaa81962772034378319b71670db72f23b7a38b5abac41b5eb063f0fddd29b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 27, 2026.
Transparency logRelease files / borco_pyside-0.2.0-py3-none-any.whl
| Download URL | borco_pyside-0.2.0-py3-none-any.whl |
|---|---|
| Size | 173.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ab4558a37efcff64a8acc88d168ddab77eaec4b2d224b873980d9739d970445d
|
|
BLAKE2b-256 checksum How to use checksums |
d4eac510a2eb21c526f9d3187fa2583cc14c2b9912d7e250afa16aea1b040642
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 27, 2026.
Transparency log