<div dir="ltr"><div class="gmail_quote">On Mon, Dec 19, 2011 at 1:05 PM, Michael Foord <span dir="ltr"><<a href="mailto:fuzzyman@gmail.com" target="_blank">fuzzyman@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_quote"><div><br></div><div>The use of trove classifiers at all isn't compulsory on PyPI, so although I agree it would be *preferable* for all authors to use them correctly I don't think PyPI is going to require it any time soon.<br>
<br><br></div></div></blockquote><div><br></div><div>Are we happy that it isn't compulsory? I mean, there are a lot of compulsory lines in <a href="http://setup.py/cfg">setup.py/cfg</a>, why not require a compatibility tag?</div>
<div><br></div><div>From a backwards compatibility standpoint, I guess a warning could be emitted for a year or 2 until the compatibility classifiers are actually mandatory.</div><div><br></div><div>I'm sure I'm not the only one who's struggled with eg Scapy working only on 2.6 and not 2.7, which is only a minor occurrence compared to the great py3k divide.</div>
<div><br></div><div><br></div><div>Yuval Greenfield</div></div></div>