An extension for [colcon-core](https://github.com/colcon/colcon-core) to allow running from any subfolder of a workspace.
This package allows running colcon from any subfolder of a colcon workspace, but reusing existing build, install, and log folders from the root folder of the workspace.
The root of the workspace is determined by looking for the .colcon_root marker file, which is created on first invocation. Alternatively, the existence of build, install, and log folders indicates the root folder.
Package discovery is done relative to the current working directory. Thus, to build all packages in the current folder, just run colcon build. To build all packages in the workspace, specify the special token ROOT for the –base-paths argument: colcon build –base-paths ROOT.
1 maintainer
Metadata
1 maintainer
Release files for colcon-top-level-workspace 0.1.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 | Provenance | |
|---|---|---|---|---|
| colcon_top_level_workspace-0.1.0.tar.gz | 9.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| colcon_top_level_workspace-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.7 kB
Release files / colcon_top_level_workspace-0.1.0.tar.gz
| Download URL | colcon_top_level_workspace-0.1.0.tar.gz |
|---|---|
| Size | 9.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d0cf130ca9e404e92b149135b62225592a7c5a87f7f48618969def19ae4dac86
|
|
BLAKE2b-256 checksum How to use checksums |
c456a3ce8addc15d8d6d0e2d9f6607e0b61595932c5e95cb8a2f200e2d109000
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 9, 2025.
Transparency logRelease files / colcon_top_level_workspace-0.1.0-py3-none-any.whl
| Download URL | colcon_top_level_workspace-0.1.0-py3-none-any.whl |
|---|---|
| Size | 8.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ab044e9ebfb31147416c268a0dbb40c3be35824f9e680517eec19a8ddc1e061b
|
|
BLAKE2b-256 checksum How to use checksums |
fcbbd4cd5513757b5edb9c3b38f894959fca087912a804d44f352b68a93bc9ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 9, 2025.
Transparency logSecurity for colcon-top-level-workspace 0.1.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 2 files in this release have been uploaded with provenance metadata.
Attestation for colcon_top_level_workspace-0.1.0.tar.gz
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 9, 2025.
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.
