<br><br><div class="gmail_quote">On 5 March 2012 18:43, Paul Moore <span dir="ltr"><<a href="mailto:p.f.moore@gmail.com">p.f.moore@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
[Resending because I don't think the first try made it to the list...]<br>
<br>
I'm trying to identify which distributions in PyPI need to be made<br>
available in binary format for people without C compilers (i.e.,<br>
distributions including C extensions). I could use the classifier<br>
information, but as that is user-supplied, it is not 100% reliable[1].<br>
(Also, it's not in the data set I have available, although that's a<br>
fixable issue). I'm only interested in existing binary distributions<br>
(eggs and wininst/msi packages) on PyPI.<br>
<br>
The problem is that simply assuming that because a distribution<br>
provides binary installers, or even version-specific installers, is<br>
not enough. For example, look at PyParsing - it provides a<br>
version-specific wininst installer for every Python version, but it's<br>
a pure Python package, and can easily be installed from source.<br>
<br>
I can't see a way of reliably establishing whether a distribution is<br>
"pure Python", and yet distutils/packaging clearly has that<br>
information available when building. Would it be worthwhile adding a<br>
"pure Python" flag to the PyPI classifiers, which could be<br>
automatically populated by packaging? We'd still be reliant on people<br>
who manually maintain metadata getting it correct, but it would help<br>
in many cases (and in particular, in those cases where projects do<br>
regularly upload binary distributions).<br></blockquote><div><br></div><div>+1</div><div><br></div><div>It's useful information for users - if only source distributions are available for packages that require compilation some users can't use them (typically Windows users), so a pure-python flag would be helpful.</div>
<div><br></div><div>Michael</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Alternatively, if there is a way of reliably identifying those<br>
packages that can't be installed from source by someone without a<br>
compiler, I'd be interested to know.<br>
<br>
Thanks,<br>
Paul.<br>
_______________________________________________<br>
Distutils-SIG maillist - <a href="mailto:Distutils-SIG@python.org">Distutils-SIG@python.org</a><br>
<a href="http://mail.python.org/mailman/listinfo/distutils-sig" target="_blank">http://mail.python.org/mailman/listinfo/distutils-sig</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><pre cols="72"><a href="http://www.voidspace.org.uk/" target="_blank">http://www.voidspace.org.uk/</a><br><br>May you do good and not evil<br>May you find forgiveness for yourself and forgive others<br>
May you share freely, never taking more than you give.<br>-- the sqlite blessing <a href="http://www.sqlite.org/different.html" target="_blank">http://www.sqlite.org/different.html</a></pre>
<br>