On Tuesday, 19 February 2013, M.-A. Lemburg  wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
The only tool in wide spread use that understands part of the 1.2 data<br><span style>is setuptools/distribute, but it can only understand the Requires-Dist</span><br style><span style>field of that version of the spec (only because the 1.1 Requires field was</span><br style>
<span style>deprecated) and interprets a Provides-Extra field which isn&#39;t</span><br style><span style>even standard. All other 1.2 fields are ignored.</span><br style><span style>setuptools/distribute still writes 1.1 meta-data.</span><br style>
<br style><span style>I&#39;ve never seen environment markers being used or supported</span><br style><span style>in the wild.</span><br style><br style><span style>I&#39;m not against modernizing the format, but given that version 1.2</span><br style>
<span style>has been out for around 8 years now, without much following,</span><br style><span style>I think we need to make the implementation bit a requirement</span><br style><span style>before accepting the PEP.</span><br>

</blockquote><div><br></div><div>The wheel project uses metadata 2.0 and environment markers - indeed, the PEP was written to formalise what wheel was implementing (specifically so that pip was happy to incorporate support). Standard library support was hampered by the difficulty of changing Distutils - an issue which may have gone away now.</div>
<div><br></div><div>I agree that standard library support would be good, either via Distutils or by incorporating distlib, but I don&#39;t think it is essential for acceptance.</div><div><br></div><div>Paul<span></span> </div>
<div> </div>