28 Feb 2004 12:23
Automatically hiding releases
Sebastien Bigaret <sbigaret <at> users.sourceforge.net>
2004-02-28 11:23:39 GMT
2004-02-28 11:23:39 GMT
Hi all,
I've just read "PyPI comes in handy, again" weblog entry:
http://www.mechanicalcat.net/richard/log/Python/PyPI_comes_in_handy__again
in Jeremy's Stuff, referenced yesterday in daily-python. Hopefully this
is the right place to discuss it.
As a naive PyPI user, I never realized that older release could be
hidden. Here is what happened: I read the tip-of-each-week Package
Index Tutorial by Jeremy Hylton (thanks!), then used it to modify
setup.py, finally registered to PyPI, and that's all. When something is
registered, I checked on PyPI that the entry is correct, but since I've
never logged in (nor need to) since the first time I registered, I never
had the opportunity to see that older release could be hidden, not to
say why they should.
I realize that hiding older releases makes the PyPI more pleasant and
efficient, just because a search result does not need to present the
same project's name x times. I presume that this is the case for most
projects. My point here is that, now that I know they can be hidden
I'll do it by hand, and I guess that if is better advertised and
explained, then other projects' maintainers would probably do so as
well --the discussion on this topic that can be found in the archives,
in August 2003 between Jeremy Hylton and Richard Jones, was also
informative to me.
So this is a +1 for single-visible-release use-case :) And probably
that, until a decision is made and the feature possibly gets coded, the
hiding feature for projects can be made more proeminent, and better
(Continue reading)
RSS Feed