Showing content from http://mail.python.org/pipermail/python-dev/attachments/20120828/13350c22/attachment.html below:
<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><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></span></blockquote><div>To be more specific, there is setup.cfg (which I dislike for other reasons), and</div><div>then there is METADATA. setup.cfg is an ini file but METADATA is a simple</div><div>key: value file with a flat namespace so any namespacing you want to do in</div><div>METADATA needs to be done at the key level. You could translate:</div><div><br></div><div>[setuptools]</div><div>requires-dist=foo</div><div><br></div><div>in a setup.cfg into</div><div><br></div><div>setuptools-requires-dist: foo</div><div><br></div><div>in METADATA, but I'm not sure if that would be beneficial or not. </div><div><br>
</div>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4