literalizer
literalizer converts JSON, JSON5, YAML, and TOML data structures to native language literal syntax.
Supported languages
Ada, Bash, C, C#, C++, Clojure, COBOL, Common Lisp, Crystal, D, Dart, Dhall, Elixir, Elm, Erlang, F#, Forth, Fortran, Gleam, Go, Groovy, Haskell, Haxe, HCL, Java, JavaScript, JSON5, Jsonnet, Julia, Kotlin, Lua, MATLAB, Mojo, Nim, Nix, Norg, Objective-C, OCaml, Occam-pi, Odin, Perl, PHP, PowerShell, PureScript, Python, R, Racket, Raku, Roc, Ruby, Rust, Scala, Scheme, SML, Swift, SystemVerilog, Tcl, TOML, TypeScript, V, Visual Basic, Wren, YAML, Zig.
Installation
Requires Python 3.12+.
pip install literalizer
Usage
Pass your data, its format, and a target language:
"""Minimal example of using literalizer."""
from literalizer import InputFormat, literalize
from literalizer.languages import Python
result = literalize(
source='{"x": 1}',
input_format=InputFormat.JSON,
language=Python(),
)
# result.code:
# {
# "x": 1,
# }
Configure the language to control how individual data types are rendered. Comments in the source are preserved using the target language’s comment syntax:
"""Layering format options on top of the minimal call."""
from literalizer import InputFormat, literalize
from literalizer.languages import Go
yaml_config = """\
# Server configuration
host: localhost # default host
port: 8080
released: 2026-06-02
"""
result = literalize(
source=yaml_config,
input_format=InputFormat.YAML,
language=Go(date_format=Go.date_formats.ISO),
)
# result.code (backslash-t denotes a tab):
# map[string]any{
# \t// Server configuration
# \t"host": "localhost", // default host
# \t"port": 8080,
# \t"released": "2026-06-02",
# }
Use cases
CLI
A command-line interface is available at literalizer-cli.
Sphinx extension
A Sphinx extension is available at sphinx-literalizer.
Full documentation
See the full documentation for more information including how to contribute.
Metadata
Release files for literalizer 2026.9.16
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| literalizer-2026.9.16.tar.gz | 4.6 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| literalizer-2026.9.16-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.6 MB
Release files / literalizer-2026.9.16.tar.gz
| Download URL | literalizer-2026.9.16.tar.gz |
|---|---|
| Size | 4.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
311a6e6fbc8ff48ef751a16e85a0a7052a25784bb45056aaa5a94d7b7b4c53ca
|
|
BLAKE2b-256 checksum How to use checksums |
39f86fdbb45349e2b543b7c1406f80727f439b44522b76d38d070c2498153764
|
| 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 16, 2026.
Transparency logRelease files / literalizer-2026.9.16-py3-none-any.whl
| Download URL | literalizer-2026.9.16-py3-none-any.whl |
|---|---|
| Size | 1.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ed4d117ad8d06fff18a4479b640cfa2a4987f9015f79adedcb71daca10806c97
|
|
BLAKE2b-256 checksum How to use checksums |
8e0bd6c4b011e7fd5798029675f81e404c894e527d49f92eeddfb9ed5c475fa1
|
| 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 16, 2026.
Transparency log