dtab

Config files made of tab-separated paths. One line is one path into a tree.

objects	l1,l2 light
deltas	l1	position	x 1	y .5
	z -2

import dtab
dtab.parse(open("scene.dtab").read())
# {'objects': {'l1': 'light', 'l2': 'light'},
#  'deltas': {'l1': {'position': {'x': '1', 'y': '.5', 'z': '-2'}}}}

Why

• Less to look at. No braces, quotes, or commas between values. A file with its tabs aligned reads like pseudocode, and is easy to write by hand, even on paper.

• Simple. Six rules, one pass, about 70 lines per implementation.

• Everything is addressable. There are no lists, so every value has a dotted path: config.deltas.l1.position.x works with EasyDict in Python and plain property access in JavaScript.

• You choose the shape. Lines stack, and c,d writes one value under several keys, so the same tree can be written wide, deep, or on one line, trading horizontal space for vertical. These are the same file:

  a	b	c x
  a	b	d x
  

  a
  	b
  		c x
  		d x
  

  a	b	c,d x
  

Rules

• Tabs separate the steps of a path. deltas l1 position walks three keys down. Several tabs in a row count as one, so you can align columns.
• An entry with a space is key value. It sets the key and stays at the same level, so x 1 y .5 sets two keys.
• An indented line continues the path of the line above it.
• Writing a key again replaces it. Writing into an object merges.
• a,b writes the same value under a and under b.
• An entry that starts with a space is a comment.

Every value is a string. Cast the ones you need. Keys are identifiers (letters, digits, underscores), so attribute access like config.deltas.l1 works with EasyDict and friends.

Install

API

• parse(text) returns nested dicts (Python) or plain objects (JavaScript). Raises on an invalid key, with the line number.
• stringify(tree) writes the tree back out, one key per line.
• Command line: dtab scene.dtab prints the tree as JSON.