setuptools 0.9.1 download link returns 404 Error

Originally reported by: notnoop (Bitbucket: notnoop, GitHub: notnoop)

---

Setuptools 0.9.1 direct download (https://pypi.python.org/packages/source/s/setuptools/setuptools-0.9.1.tar.gz taken from https://pypi.python.org/pypi/setuptools/0.9.1) link doesn't work anymore.

That causes pip install to fail as well:

(venv2)ubuntu@box6:~$ pip install --upgrade setuptools
Downloading/unpacking setuptools from https://pypi.python.org/packages/source/s/setuptools/setuptools-0.9.1.tar.gz#md5=7068dcbd9ea44139f5abeb65cb916f15
  HTTP error 404 while getting https://pypi.python.org/packages/source/s/setuptools/setuptools-0.9.1.tar.gz#md5=7068dcbd9ea44139f5abeb65cb916f15
  Could not install requirement setuptools from https://pypi.python.org/packages/source/s/setuptools/setuptools-0.9.1.tar.gz#md5=7068dcbd9ea44139f5abeb65cb916f15 because of error HTTP Error 404: Not Found
Could not install requirement setuptools from https://pypi.python.org/packages/source/s/setuptools/setuptools-0.9.1.tar.gz#md5=7068dcbd9ea44139f5abeb65cb916f15 because of HTTP error HTTP Error 404: Not Found for URL https://pypi.python.org/packages/source/s/setuptools/setuptools-0.9.1.tar.gz#md5=7068dcbd9ea44139f5abeb65cb916f15
Storing complete log in /home/ubuntu/.pip/pip.log

---

• Bitbucket: https://bitbucket.org/pypa/setuptools/issue/39

Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco):

---

Hi Mahmood - I don't know why you're getting a 404. I just checked the link indicated in the log (as well as the link provided by pypi), and I was able to retrieve the resource just fine. Could it be you have a proxy that's denying your connection? Perhaps you got a CDN mirror that wasn't yet refreshed, although that shouldn't be the case so many hours after the release.

Perhaps it was a transient problem?

Original comment by notnoop (Bitbucket: notnoop, GitHub: notnoop):

---

Thanks! Confirmed that it's working now on my end!

Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco):

---

I didn't change anything - it must have been a transient issue.