Issue #52 invalid

Website should list all versions of a package instead of latest uploaded one

created an issue

As far as I can see there is no more possibility in the web interface to list all versions of a package. Instead only the latest uploaded artifact is visible.

E.g. for rsb-python we are maintaining parallel releases of the 0.7 and 0.9 release line. This now always results in an unsatisfactory listing of the package. Either only 0.7 is visible despite the fact that a more recent release is available because we uploaded a fix for the 0.7 release line or only 0.9 is visible and people using the older release wonder were it is.

Comments (10)

  1. languitar reporter

    As far as I can tell, this option is only available as a package maintainer. But also as a user of a package I would like to be able to find out which releases are available. As it often happens that a package doesn't work with the most recent upstream version, such information is really important.

  2. languitar reporter

    That's what I see. ;) But right now finding out which versions are available at all is only possible by wild version number guessing. I also cannot see that pip itself provides a way to get this information.

  3. p

    Currently PyPI doesn't provide that information to users, leaving it up to package authors which versions to expose.

    Yes, this is why this enhancement ticket was created.

    As a user I sometimes need to retrieve an old version of a particular package. Said version is on pypi yet it is impossible to get at.

  4. Nick Timkovich

    Why are packages hidden on (I believe that end-developers have no option to browse hidden old versions, I may be mistaken), but still accessible via specifying a version to pip or the like? If it's so dangerous as to make it an "unversion" on PyPI, why even allow people to install it? I'm being a bit hyperbolic, but if I want to see old versions, let me.

    For example, I can see 2 versions of distribute at , the latest 0.6 and 0.7 versions when logged in (don't even know if that makes a difference). However, I can also go to to look at an old version that I wouldn't be able to find on PyPI without knowing it existed beforehand. I could brute force looking by checking for many values of x and y, but if I have a reason to look at an old version (e.g. for release notes), why is it so onerous to do so?

  5. Donald Stufft

    Because PyPI legacy (the current code base, and what's being tracked by this repository) is essentially EOL'd except for bug fixes or things that we don't feel are too risky or too much work. There is work going into revamping PyPI with a PyPI 2.0 with a much cleaner code base developed with modern methodologies and tests and all sorts of niceties. So it's invalid because it's how PyPI legacy was designed.

    This isn't a problem in the new system, but that's not ready to go live yet.

  6. Nick Timkovich

    Ah, I was clueless as to a PyPI 2.0. Distutils, distribute, setuptools, distutils2 and all that jazz still gives me a headache; I have no idea what's going on with Python packaging/distribution as of late. There's so much information from 1-2 years ago about what should have happened 1-2 years later (now) that's apparently nothing but a pipe dream.

  7. Log in to comment