<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On May 11, 2016, at 9:46 AM, Nicholas Chammas <<a href="mailto:nicholas.chammas@gmail.com" class="">nicholas.chammas@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="markdown-here-wrapper" style=""><p style="margin:0px 0px 1.2em!important" class="">On Tue, May 10, 2016 at 11:15 AM Donald Stufft <a href="http://mailto:donald@stufft.io/" class="">donald@stufft.io</a> wrote:</p><div style="margin: 0px 0px 1.2em !important;" class=""><br class="webkit-block-placeholder"></div><div class="markdown-here-exclude"><div class=""><br class="webkit-block-placeholder"></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br class="">
> On May 10, 2016, at 11:00 AM, Antoine Pitrou <<a href="mailto:solipsis@pitrou.net" target="_blank" class="">solipsis@pitrou.net</a>> wrote:<br class="">
><br class="">
> (as an aside, if there's the question of forking an existing parser<br class="">
> implementation for better vendorability, forking a YAML parser may be<br class="">
> more useful to third-party folks than forking a TOML parser :-))<br class="">
<br class="">
<br class="">
I’m seeing what I can come up with (<a href="https://github.com/dstufft/yaml" rel="noreferrer" target="_blank" class="">https://github.com/dstufft/yaml</a>) though<br class="">
I don’t know that I feel like actually maintaining whatever it is I end up<br class="">
figuring out there.<br class=""></blockquote><div class=""><br class="webkit-block-placeholder"></div></div><div style="margin: 0px 0px 1.2em !important;" class=""><br class="webkit-block-placeholder"></div><p style="margin:0px 0px 1.2em!important" class="">Did you intend to fork from <a href="https://github.com/yaml/pyyaml" class="">https://github.com/yaml/pyyaml</a>? I believe the latest PyYAML is actually hosted on BitBucket:</p><p style="margin:0px 0px 1.2em!important" class=""><a href="https://bitbucket.org/xi/pyyaml/" class="">https://bitbucket.org/xi/pyyaml/</a></p><div class=""><br class=""></div></div></div></div></blockquote><div><br class=""></div><div>Yea, there was only a very tiny, mostly meaningless delta between Github and bitbucket and I’m lazy.</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="markdown-here-wrapper" style=""><p style="margin:0px 0px 1.2em!important" class="">Also, a better starting point than PyYAML may be this existing fork of the library, ruamel.yaml:</p><p style="margin:0px 0px 1.2em!important" class=""><a href="https://bitbucket.org/ruamel/yaml" class="">https://bitbucket.org/ruamel/yaml</a></p><p style="margin:0px 0px 1.2em!important" class="">The fork makes <a href="http://yaml.readthedocs.io/en/latest/pyyaml.html" class="">several</a> <a href="http://yaml.readthedocs.io/en/latest/detail.html#round-trip-including-comments" class="">changes</a> which may be relevant to you.</p><div class=""><br class=""></div></div></div></div></blockquote><div><br class=""></div>To be clear, my thing was a proof of concept to see how hard it would be to help inform the decision about what file format to use. The PEP has decided that TOML best represents the tradeoffs we want to make so my lib will likely just die on my GitHub :)<br class=""><div><br class=""></div></div><div class="">-----------------<br class="">Donald Stufft<br class="">PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
</div>
<br class=""></body></html>