4
I am thinking about keeping changeset headers in YAML_, as a nice
7
* Standard data format, so we don't need to invent, write and debug
10
* More concise than XML, which is useful if we're storing a few.
12
* Reasonably readable for humans; thus suitable for sending in email
13
and giving people at least some chance to read and understand it.
14
Seeing this at the top of a patch would not be actively horrible as
15
long as we keep it reasonably small; that's not true for XML.
17
* Since YAML documents have a document header and terminator ('---'
18
and '...') we can pick them out of a text document and append
19
text patches directly afterwards.
21
* Fits well with Python internal data structures.
23
* There are parsers for various languages, so people can write their
24
own implementation if they really want.
26
* There is space to specify a document format/version at the top
27
(though this is not currently handled in ydump).
29
The ydump module is pretty primitive, but it should have enough.
31
.. _YAML: http://www.yaml.org/
37
On the whole, I think this is not a good idea. It is a nicer syntax
38
for XML, but there are less bindings, and it does not achieve the goal
39
of having the storage format look reassuring and giving confidence
40
that the data could be retrieved by an alternative implementation.
b'\\ No newline at end of file'
added
removed
doc/yaml.txt
