qgis-sdk-tools
The qgis-sdk command: new, check, test, dev, build, bridge,
processing and targets.
Scaffolds a loadable plugin project with a declared native dialog and, optionally, a Vite web page; reports what would stop a project from loading in QGIS or from being tested without it; runs its tests QGIS-free or inside QGIS; starts it from source in a real QGIS Desktop with reload on save; generates the typed page-side schema and the Processing catalogue; and writes an installable ZIP with the runtime vendored inside. The tools never install anything into a QGIS.
Status:
0.7.0, experimental0.x. The tools version freely; each release names theqgis-sdk-runtimerange it was tested with.
Installation
pip install qgis-sdk # the developer kit: runtime + tools
pip install qgis-sdk-tools # the command alone, with the runtime it tested
Example
qgis-sdk new field_tools --title "Field Tools" --web react # pyproject.toml, the plugin, a dialog, tests/, web/
qgis-sdk check field_tools # pyproject, syntax, imports, UI rules, runtime version
qgis-sdk test field_tools # pytest QGIS-free; --target qgis|desktop for the native layers
qgis-sdk dev field_tools # inside QGIS Desktop, reloading on save, Vite with HMR
qgis-sdk bridge generate --out web/src/bridge.schema.ts # the typed schema QgisSdk.fromBridgeSchema reads
qgis-sdk processing generate --provider native --web-out web/src/processing.schema.ts
qgis-sdk build field_tools # dist/field_tools-<version>.zip, metadata.txt and classFactory rendered
qgis-sdk targets # the support matrix, and where this host stands in it
Documentation
- Python package guide -
the scaffold, project checks and their rule ids,
test,dev,build, the generators, release and migration notes. - Workspace, harnesses and qualification evidence - the support matrix and how each command is qualified.
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for qgis-sdk-tools 0.7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| qgis_sdk_tools-0.7.0-py3-none-any.whl | Python 3 | none | any | Details for qgis_sdk_tools-0.7.0-py3-none-any.whl |
Release files / qgis_sdk_tools-0.7.0-py3-none-any.whl
| Download URL | qgis_sdk_tools-0.7.0-py3-none-any.whl |
|---|---|
| Size | 121.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
862f1118f3217f984f9a705e7b5ac37b09fce870ff527eefb4b5912fb13fb6a5
|
|
BLAKE2b-256 checksum How to use checksums |
c6e8bada670bc623e7fd39ad97094320e1e9d4a9493eb6cc515311e573e4d8be
|
| 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 Oct 27, 2026.
Transparency logSecurity for qgis-sdk-tools 0.7.0
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.
Full provenance
All 1 file in this release has been uploaded with provenance metadata.
Attestation for qgis_sdk_tools-0.7.0-py3-none-any.whl
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 Oct 27, 2026.
Transparency logA 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.
