[Python-Dev] PyPI comments and ratings, *really*?

Olemis Lang olemis at gmail.com
Thu Nov 12 16:50:23 CET 2009

On Thu, Nov 12, 2009 at 9:32 AM, Jesse Noller <jnoller at gmail.com> wrote:
> On Thu, Nov 12, 2009 at 9:25 AM, Barry Warsaw <barry at python.org> wrote:
>> On Nov 12, 2009, at 8:06 AM, Jesse Noller wrote:
>>> Frankly, I agree with him. As implemented, I *and others* think this
>>> is broken. I've taken the stance of not publishing things to PyPi
>>> until A> I find the time to contribute to make it better or B> It
>>> changes.
>> That's distressing.  For better or worse PyPI is the central repository of
>> 3rd party packages.  It should be easy, desirable, fun and socially
>> encouraged to get your packages there.
>> I personally think a ratings system can be useful, but you should be able to
>> opt-out of it if you want.  Or just write such awesome software that the
>> bogus bad reviews will be buried by an avalanche of kudos.
>> -Barry
> I completely and totally agree with you. That's why it's a
> self-imposed thing for me, I want to help, but don't have the time. In
> the same breath, I don't want to support it as-is.
> PyPI isn't a place to file bugs, complain something didn't work for
> you if you didn't even have the common decency in some cases to email
> them. Being unable, as an author, to remove, moderate, or even respond
> to issues there bothers me quite a bit.


> Heck, I would even be for requiring packages have a mailing list and /
> or bug tracker to even upload, rather than comments. At least then the
> authors or maintainers have a fighting chance.

Intention = suggestion + crazy idea => for a better PyPI

But there's probably a chance to display what people said in the
project's site . If PyPI would be able to retrieve that information
from the project's site (e.g. that'd be possible for Trac and other
PMS via RPC ) and also some of the aforementioned (Jesse's) issues
might be solved with added benefits (data being cached and discarded
from time to time, better performance, less DB space, ...) or not .

IMO, what's missing in my reasoning is whether there is a common std
API for e.g. issues . But there's a popular API for wikis (i.e.
WikiRPC) so probably there's something std (I repeat, that I don't
know :-/ ) out there . At least Trac's TicketRPC is very simple (i.e.
two simple methods) and extensible (e.g. custom ticket fields ;o)

PS: I don't really know the exact details of the impl of votes and
comments in PyPI.



Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article:

More information about the Python-Dev mailing list