This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author methane
Recipients Markus Järvisalo, docs@python, methane
Date 2018-04-09.07:48:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1523260103.83.0.682650639539.issue33246@psf.upfronthosting.co.za>
In-reply-to
Content
> "The primary objective of this revision is to bring YAML into compliance with JSON as an official subset."
>
> So it should be that YAML is a subset of JSON and not the other way around.

This sentence can be read as "JSON is subset of YAML" and "YAML is subset of JSON".
As reading the spec, it means former.

For example, http://yaml.org/spec/1.2/spec.html#id2759572 says:

> YAML can therefore be viewed as a natural superset of JSON, offering improved human readability and a more complete information model. This is also the case in practice; every JSON file is also a valid YAML file. This makes it easy to migrate from JSON to YAML if/when the additional features are required.
History
Date User Action Args
2018-04-09 07:48:23methanesetrecipients: + methane, docs@python, Markus Järvisalo
2018-04-09 07:48:23methanesetmessageid: <1523260103.83.0.682650639539.issue33246@psf.upfronthosting.co.za>
2018-04-09 07:48:23methanelinkissue33246 messages
2018-04-09 07:48:23methanecreate