Opened at 2012-12-27T00:30:28Z
Last modified at 2016-03-26T22:44:28Z
#1896 closed defect
setuptools will download and use release candidates of dependencies, not just releases — at Initial Version
| Reported by: | davidsarah | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 1.11.0 |
| Component: | packaging | Version: | 1.9.2 |
| Keywords: | setuptools packaging pip | Cc: | |
| Launchpad Bug: |
Description
In a recent build for FreeStorm? CentOS6-amd64:
Searching for pyasn1>=0.0.8a Reading http://pypi.python.org/simple/pyasn1/ Reading http://sourceforge.net/projects/pyasn1/ Found link: http://sourceforge.net/projects/pyasn1/files/pyasn1/0.1.6/pyasn1-0.1.6rc0.tar.gz/download Found link: http://sourceforge.net/projects/pyasn1/files/pyasn1/0.1.5/pyasn1-0.1.5.tar.gz/download [...] Best match: pyasn1 0.1.6rc0 Downloading http://sourceforge.net/projects/pyasn1/files/pyasn1/0.1.6/pyasn1-0.1.6rc0.tar.gz/download error: Can't download http://sourceforge.net/projects/pyasn1/files/pyasn1/0.1.6/pyasn1-0.1.6rc0.tar.gz/download: 503 Service Unavailable
A release candidate should never be a "best match" for a dependency; that is just asking for trouble. In this case the build failed because the release candidate wasn't actually downloadable, but even if it had been, we only want to use releases.
Related: #1753, #1582, #1220, #1452.
setuptools delenda est.
Note: See
TracTickets for help on using
tickets.
