On 13 December 2011 13:50, Yuval Greenfield <[email protected]> wrote:
> I'm not sure this is the case, but easy_install/pip should check if > the package is python 3 compatible or not before installing. To quote > you: > > If a package is Python 3 compatible, or has a Python 3 > version/port/alternative distribution, shouldn't "The Python Package > Index" reflect the truth? > My initial reply went privately to Yuval (goddamn lists that don't have reply-to set correctly ;-). Anyway, even though the wall-of-shame states that it is based on the PyPI classifier, I think it would be less of a publicity own goal for the Python community, and would be much more *useful*, if packages that did support Python 3 showed up as green... All the best, Michael Foord > > Yuval Greenfield > > On Tue, Dec 13, 2011 at 3:39 PM, Michael Foord <[email protected]> wrote: > > > > > > On 13 December 2011 13:24, Yuval Greenfield <[email protected]> > wrote: > >> > >> On Tue, Dec 13, 2011 at 2:17 PM, Michael Foord <[email protected]> > wrote: > >> > On 13 December 2011 10:29, Yuval Greenfield <[email protected]> > >> > wrote: > >> >> Toshio Kuratomi is correct: > >> >> > Additionally, I'm not certain of the use case cited. Isn't the > >> >> > utility > >> >> > of > >> >> > a site like http://python3wos.appspot.com/ in seeing which > popular or > >> >> > widely depended upon packages have no python3 version? With that > in > >> >> > mind, > >> >> > the listing on that page wouldn't seem to depend on whether a > >> >> > package's > >> >> > author intends to port to python3. > >> >> > >> > > >> > unittest2 has a Python 3 port: unittest2py3k > >> > > >> > docutils is also Python 3 compatible (since version 0.6), even if > >> > they're > >> > not using the trove classifier. > >> > > >> > >> My initial response was to remove modules that had python 3 > >> equivalents on the wall. This makes sense for eg setuptools and jinja > >> as it wouldn't be accurate to give them a double green listing and > >> skew the percentage. > >> > >> Packages that have a single listing on the top 200 and have a python 3 > >> equivalent I should mark as green. I guess the best solution would be > >> to consolidate these packages. I'll work on it. > >> > >> Concerning docutils, I sent an email to Lea Wiemann > >> ([email protected]) and am cc-ing David Goodger for the trove > >> classifier though I don't think I can be held responsible for this > >> one. > > > > > > > > What do you mean by held responsible? If a package is Python 3 > compatible, > > or has a Python 3 version/port/alternative distribution, shouldn't "wall > of > > shame" (I *really* dislike the name for what it's worth and cringe every > > time I write it) reflect the truth? > > > > All the best, > > > > Michael > > > >> > >> > >> > >> Yuval Greenfield > > > > > > > > > > -- > > > > http://www.voidspace.org.uk/ > > > > May you do good and not evil > > May you find forgiveness for yourself and forgive others > > > > May you share freely, never taking more than you give. > > -- the sqlite blessing http://www.sqlite.org/different.html > > > > > -- http://www.voidspace.org.uk/ May you do good and not evil May you find forgiveness for yourself and forgive others May you share freely, never taking more than you give. -- the sqlite blessing http://www.sqlite.org/different.html
_______________________________________________ Catalog-SIG mailing list [email protected] http://mail.python.org/mailman/listinfo/catalog-sig
