"Martin v. Löwis" wrote: >> For such packages: send out an email to the package maintainer informing >> him about the problem and instructing him to fix the problem within N >> days. >> >> After N days: recheck the package state and unregister the package if >> necessary. >> >> Or perhaps a less rude approach: introduce status field for each package >> (ACTIVE/INACTIVE) and set the state to INACTIVE when the package does >> not comply with this policy. Inactive packages won't be listed on PyPI >> and won't be searchable on PyPI. Inactive status should be visible >> to the author (in logged-in state) with some warning "Package is >> inactive..please upload your sdist....). > > Ok. If nobody opposes to this right now, it's fine with me as well. > However, I won't be able to work on this for several months to come. > > IMO, it's a waste of energy: if a package is useless, just don't use it, > and be done. There are many packages on PyPI that are useless to me > despite having a source release.
Agreed. PyPI can't replace the due-diligence that every package user has to apply before making a choice to invest time into using it. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Jun 17 2010) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2010-07-19: EuroPython 2010, Birmingham, UK 31 days to go ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ _______________________________________________ Catalog-SIG mailing list [email protected] http://mail.python.org/mailman/listinfo/catalog-sig
