This release is a pre-release and may not be stable for production use.
Kleinkram: CLI
Install the package
pip install kleinkram
Run the CLI
klein
Usage
Here are some basic examples of how to use the CLI.
Listing Files
To list all files in a mission:
klein list -p project-name -m mission-name
Uploading Files
To upload all *.bag files in the current directory to a mission:
klein upload -p project-name -m mission-name *.bag
If you would like to create a new mission on upload use the --create flag.
Downloading Files
To download all files from a mission and save them out:
klein download -p project-name -m mission-name --dest out
You can additionally specify filenames or ids if you only want to download specific files.
Instead of downloading files from a specified mission you can download arbitrary files by specifying their ids:
klein download --dest out *id1* *id2* *id3*
For more information consult the documentation.
Development
Clone the repo
git clone git@github.com:leggedrobotics/kleinkram.git
cd kleinkram/cli
Setup the environment
virtualenv -ppython3.8 .venv
source .venv/bin/activate
pip install -e . -r requirements.txt
Install pre-commit hooks
pre-commit install
Run the CLI
klein --help
Run Tests
to run unit tests:
pytest -m "not slow"
to run all tests (including e2e and integration tests):
pytest
For the latter you need to have an instance of the backend running locally.
See instructions in the root of the repository for this.
On top of that these tests require particular files to be present in the cli/data/testing directory.
To see the exact files that are required, see cli/testing/backend_fixtures.py.
You also need to make sure to be logged in with the cli with klein login.
1 maintainer
Metadata
1 maintainer
Release files for kleinkram 0.54.0.dev20251119141012
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 |
|---|---|---|---|---|
| kleinkram-0.54.0.dev20251119141012.tar.gz | 50.9 kB | Without provenance | Details for kleinkram-0.54.0.dev20251119141012.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| kleinkram-0.54.0.dev20251119141012-py3-none-any.whl | Python 3 | none | any | Details for kleinkram-0.54.0.dev20251119141012-py3-none-any.whl |
Total release size: 117.4 kB
Release files / kleinkram-0.54.0.dev20251119141012.tar.gz
| Download URL | kleinkram-0.54.0.dev20251119141012.tar.gz |
|---|---|
| Size | 50.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5a4232522cdd5981b6a029eedf061507e41ff88a8c0096e6cb8663eb9e1a753f
|
|
BLAKE2b-256 checksum How to use checksums |
180c75a6e859225a33759d828eba071c3d74f885d6801390a5ab50e4e0c17264
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / kleinkram-0.54.0.dev20251119141012-py3-none-any.whl
| Download URL | kleinkram-0.54.0.dev20251119141012-py3-none-any.whl |
|---|---|
| Size | 66.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
235db3f60e075d39094eb9630c82bbce313cea39453fed8772d4a431a7b6d233
|
|
BLAKE2b-256 checksum How to use checksums |
05b4451bd6b3e8e7a8968f105f4f94cfe475575116d57cd316789402e4c8a84b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for kleinkram 0.54.0.dev20251119141012
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.
