[Python-ideas] Package reputation system

Alexander Walters tritium-list at sdamon.com
Fri Apr 1 10:42:30 EDT 2016

On 4/1/2016 09:07, Nick Coghlan wrote:
> And so do Linux distributions.
> There's a reason there are so many of the latter: "good" choices
> depend a great deal on what you're doing, which means there's no point
> in trying to come up with the "one true reputation system" for
> software components. djangopackages.com does a relatively good job for
> the Django ecosystem, but the simple fact of using Django puts you far
> enough down the path towards solving a particular kind of problem (web
> service design with a rich user permission system backed by a
> relational database) that a community driven rating system can work.
> By contrast, I think Python itself covers too many domains for a
> common rating system to be feasible - "good for education" is not the
> same as "good for sysadmin tasks" is not the same as "good for data
> analysis" is not the same as "good for network service development",
> etc.
> Cheers,
> Nick.
Not that this was the original proposal, but there can be such a thing 
as a universal 'bad' package, though.  So about the only thing that a 
universal package rating system can do effectively is shame developers.  
I don't think we want that.

More information about the Python-ideas mailing list