<div><span style="color: rgb(160, 160, 168); ">On Tuesday, August 28, 2012 at 9:09 AM, Nick Coghlan wrote:</span></div>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div>On Tue, Aug 28, 2012 at 10:57 PM, Daniel Holth <<a href="mailto:dholth@gmail.com">dholth@gmail.com</a>> wrote:</div><blockquote type="cite"><div><div>How about</div><div><br></div><div>Extensions are fields that start with a pypi-registered name followed</div><div>by a hyphen. A file that contains extension fields declares them with</div><div>Extension: name :</div><div><br></div><div>Extension: pypiname</div><div>pypiname-Field: value</div></div></blockquote><div><br></div><div>The repetition seems rather annoying. Compare the two section based</div><div>variants I just posted to:</div><div><br></div><div> Extension: wheel</div><div> wheel-Version: 0.9</div><div> wheel-Packager: bdist_wheel-0.1</div><div> wheel-Root-Is-Purelib: true</div><div><br></div><div>It does have the advantage that tools for manipulating the format can</div><div>remain dumber, but that doesn't seem like *that* much of an advantage,</div><div>especially since any such benefit could be eliminated completely by</div><div>just switching to a completely standard ConfigParser format by putting</div><div>the PEP defined settings into a [python] section.</div><div><br></div></div></div></span></blockquote><div>METADATA files are not ini files. </div><div><br>
</div>