perky
A simple, Pythonic file format. Provides load, loads, dump, and
Decision gist · record as of 2026-08-14
Yes. Perky is actively maintained, has no known vulnerabilities, installs with minimal friction, and solves a real problem—config file parsing—with a genuinely different philosophy (explicit type handling, provenance tracking). It's suitable for projects that value human-readable config and precise error reporting. Start with it if you're tired of JSON's noise or TOML's complexity and want strings with location metadata. Not a fit if you need automatic type coercion or a mature ecosystem of tooling.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Low install friction; pure Python wheel.
- Active maintenance with recent release (29 days old).
- Single runtime dependency on big.
License · maintenance · safety
permissive license (permissive) — MIT license (permissive); no restrictions on use, modification, or distribution in proprietary or open-source projects.
last release 2026-07-16 (29 days) · last repo commit 2026-07-16 · 4 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 166,285 downloads/mo, #10,500 on PyPI
Alternatives
Verify before relying
pip install perky
import perky
config = perky.load('config.pky')
value = config['key']- Whether big.string provenance tracking adds meaningful overhead for large config files
- Performance characteristics compared to standard JSON or TOML parsers on typical workloads
- Stability guarantees before 1.0 release (deprecated transformation submodule removal timeline)
What it is and what it does
Perky is a configuration file format and parser designed as an alternative to INI, TOML, and JSON files. It supports only three data types—strings, dicts (mappings), and lists (sequences)—deliberately leaving type inference to the caller. The parser is written in pure Python and achieves >450k lines per second throughput. Every string parsed via load() carries provenance metadata (file, line, column) through the big.string subclass, allowing your own error messages to point back into the config file with the same precision as Perky's parser errors.
The format is line-oriented and minimal: no quotes required for simple values, optional leading whitespace, comments with #, and a pragma mechanism for extensibility. Perky supports Python 3.6+ and passes its test suite with 100% coverage. The implementation is roughly 1k lines of Python, reducing surface area for bugs. You handle all data transformation yourself—whether by hand, a library like Marshmallow, or custom validation—which aligns with the Zen of Python's principle of refusing to guess at types.
Use it for
- Parse application configuration files where you want human-readable syntax without JSON's verbosity or TOML's complexity
- Build error messages that point into config files by leveraging big.string provenance to show users exactly where validation failed
- Store nested configuration hierarchies (dicts and lists) without committing to a rigid schema or type system upfront
- Extend config file semantics with custom pragma handlers for domain-specific directives
- Replace hand-rolled INI or simple text parsers in existing Python projects with a standardized, well-tested format
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes.
Perky is actively maintained, has no known vulnerabilities, installs with minimal friction, and solves a real problem—config file parsing—with a genuinely different philosophy (explicit type handling, provenance tracking). It's suitable for projects that value human-readable config and precise error reporting. Start with it if you're tired of JSON's noise or TOML's complexity and want strings with location metadata. Not a fit if you need automatic type coercion or a mature ecosystem of tooling.
Install
perky on PyPI
Before you install
Low install friction; pure Python wheel. Active maintenance with recent release (29 days old). Single runtime dependency on big.
License in practice
MIT license (permissive); no restrictions on use, modification, or distribution in proprietary or open-source projects.
Quickstart
pip install perky
import perky
config = perky.load('config.pky')
value = config['key']Verify before relying
- Whether big.string provenance tracking adds meaningful overhead for large config files
- Performance characteristics compared to standard JSON or TOML parsers on typical workloads
- Stability guarantees before 1.0 release (deprecated transformation submodule removal timeline)
Package facts
| License | permissive license permissive |
| Python support | Supports the current Python release >=3.6 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 1 packagebig |
| Maintenance | Actively maintained 29 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 166,285 / month, #10,500 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Intended Audience :: DevelopersLicense :: OSI Approved :: MIT LicenseProgramming Language :: Python :: 3Programming Language :: Python :: 3.10Programming Language :: Python :: 3.11Programming Language :: Python :: 3.12Programming Language :: Python :: 3.13Programming Language :: Python :: 3.14Programming Language :: Python :: 3.6Programming Language :: Python :: 3.7Programming Language :: Python :: 3.8Programming Language :: Python :: 3.9 |
Evidence: perky-0.10-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “rcfile alternative to ini toml json”
- perkyPerky parses a minimal, human-friendly text file format for…
- fhconfparserReads configuration files in INI, TOML, or JSON format through a…
- anyconfigLoads, dumps, and merges configuration files in multiple formats…
Give your agent the search over MCP, or paste the wish link into any chat.
More Text Processing packages
A drop-in replacement for Python's standard `re` module that adds advanced regex features like nested sets, fuzzy matching, lookaround in conditionals, and full Unicode case-folding while maintaining backward compatibility.
pyparsing provides a library for building text parsers directly in Python code using composable grammar classes, handling quoted strings, whitespace variation, and embedded comments without regex or lex/yacc.
Install it if you need to parse text or define grammars programmatically.
fonttools manipulates font files in multiple formats (TrueType, OpenType, AFM, Type 1, Mac-specific) and includes TTX, a tool to convert fonts to and from XML text format.
Install it if you need to read, write, or manipulate fonts programmatically or via the TTX command-line tool.
Docutils converts plaintext documentation in reStructuredText format into multiple output formats including HTML, XML, and LaTeX using a modular processing system.
RapidFuzz provides fast fuzzy string matching using Levenshtein Distance and related metrics, implemented mostly in C++ with Python bindings for rapid similarity scoring and approximate string matching.
Install it if you need fuzzy string matching; it's a solid replacement for FuzzyWuzzy with better licensing and performance.
tinycss2 parses CSS strings into token and block objects, and generates CSS strings from those objects, following the CSS Syntax Level 3 specification without enforcing specific properties or values.
Install it if your project requires CSS tokenization or syntax manipulation.
See also json5 · hjson · compact-json · tabulate · tox-toml-fmt · iniconfig · anyconfig · commented-configparser · tomlrt · crudini