Muuntuu
Transforms (Finnish: muuntuu) helper tool.
Usage:
❯ muuntuu
usage: muuntuu [-h] [--source FILE] [--target FILE] [--debug] [--policy-writer POLICY_WRITER]
[--general-offset GEN_OFFSET] [--mapping-offset MAP_OFFSET] [--sequence-offset SEQ_OFFSET]
[--width WIDTH] [--default-flow-style] [--sort-base] [--force] [--quiet] [--version]
[SOURCE_FILE] [TARGET_FILE]
Transforms (Finish: muuntuu) helper tool.
positional arguments:
SOURCE_FILE JSON or YAML source as positional argument
TARGET_FILE JSON or YAML target as positional argument
options:
-h, --help show this help message and exit
--source FILE, -s FILE
JSON or YAML source
--target FILE, -t FILE
JSON or YAML target
--debug, -d work in debug mode (default: False), overwrites any environment variable MUUNTUU_DEBUG value
--policy-writer POLICY_WRITER
[YAML only] select writer policy from (safe, r[ound-]t[rip], or "empty") (default: safe)
--general-offset GEN_OFFSET
general offset (indent) on output (default: 2) - verify the amount yourself, please
--mapping-offset MAP_OFFSET
[YAML only] mapping offset (indent) on output (default: 2) - verify the amount yourself, please
--sequence-offset SEQ_OFFSET
[YAML only] sequence offset (indent) on output (default: 2) - verify the amount yourself, please
--width WIDTH [YAML only] constrain width on output (default: 150) - verify the amount yourself, please
--default-flow-style [YAML only] select default flow style on output (default: False)
--sort-base [YAML only] sort base mapping type on output (default: False)
--force, -f overwrite existing targets (default: False)
--quiet, -q work in quiet mode (default: False)
--version, -V display version and exit
Note: some combinations of writer policy, offsets, and width may lead to invalid YAML as documented in
test/fixtures/offsets-width.yamlwhere the options--general-offset 3 --mapping-offset 1 --policy-writer rt --sequence-offset 2 --width 20were used when deriving fromtest/fixtures/offsets-width.yaml:
foo:
bar:
- baz
- quux1 asd asd
asd adssssssss
- quux2
- quux3
Version
❯ muuntuu --vesion
2025.9.14
Status
Prototype.
Metadata
Release files for muuntuu 2025.12.5
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 |
|---|---|---|---|---|
| muuntuu-2025.12.5.tar.gz | 10.7 kB | Without provenance | Details for muuntuu-2025.12.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| muuntuu-2025.12.5-py3-none-any.whl | Python 3 | none | any | Details for muuntuu-2025.12.5-py3-none-any.whl |
Total release size: 18.6 kB
Release files / muuntuu-2025.12.5.tar.gz
| Download URL | muuntuu-2025.12.5.tar.gz |
|---|---|
| Size | 10.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9d7138a31b92b9937dac654568fa1706ac8d410fc6cdda6961bfcff77d24aa81
|
|
BLAKE2b-256 checksum How to use checksums |
07baae544eabb5d75d7e3bded43543d5f8cd5b05012877ea150f1dec285075cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.2
|
Release files / muuntuu-2025.12.5-py3-none-any.whl
| Download URL | muuntuu-2025.12.5-py3-none-any.whl |
|---|---|
| Size | 7.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dcaaad0106a4c6000880369479d96eee3df06a6a9e9370977de1b8efe786f975
|
|
BLAKE2b-256 checksum How to use checksums |
8bd3cd26e77bd199380680540d94273193e4c55838d6fe1854d4def5e7546d21
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.2
|
Security for muuntuu 2025.12.5
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.