pip: Install Error in Synology DSM 6.0

Pip version:
Python version:
Operating System:

Description:

PIP Install Error

What I’ve run:

ash-4.3# curl -k https://bootstrap.pypa.io/get-pip.py | python
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 1487k  100 1487k    0     0  1336k      0  0:00:01  0:00:01 --:--:-- 1337k
Traceback (most recent call last):
  File "<stdin>", line 19154, in <module>
  File "<stdin>", line 194, in main
  File "<stdin>", line 82, in bootstrap
  File "/tmp/tmpnYy5RP/pip.zip/pip/__init__.py", line 15, in <module>
  File "/tmp/tmpnYy5RP/pip.zip/pip/vcs/subversion.py", line 9, in <module>
  File "/tmp/tmpnYy5RP/pip.zip/pip/index.py", line 30, in <module>
  File "/tmp/tmpnYy5RP/pip.zip/pip/wheel.py", line 32, in <module>
  File "/tmp/tmpnYy5RP/pip.zip/pip/pep425tags.py", line 335, in <module>
  File "/tmp/tmpnYy5RP/pip.zip/pip/pep425tags.py", line 307, in get_supported
  File "/tmp/tmpnYy5RP/pip.zip/pip/pep425tags.py", line 163, in is_manylinux1_compatible
  File "/tmp/tmpnYy5RP/pip.zip/pip/pep425tags.py", line 187, in have_compatible_glibc
ValueError: invalid literal for int() with base 10: '20-2014'

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 29 (13 by maintainers)

Commits related to this issue

Make have_compatible_glibc more robust against unusual version strings Downstream forks/redistributors of glibc apparently sometimes add junk onto the end of the version number -- e.g. Linaro glibc m... — committed to njsmith/pip by njsmith 8 years ago

Most upvoted comments

In this case you could also “fix” pip on your machine without upgrading or downgrading by adding a file called _manylinux.py into your site packages directory or sys.path that contains the line manylinux1_compatible=False.

On Fri, Mar 25, 2016 at 1:21 PM, jschlade notifications@github.com wrote:

@njsmith https://github.com/njsmith thank you for the 411. Looks like I could upgrade to 8.0.3 and wait for this fix. It’s just an old habit that I always upgrade my packages to the latest releases… as I’ve never had an issue like this. 😃

Another piece of food for thought is, if pip is now that way to install packages, if pip breaks like this, there’s no way to revert back to an older release. I had no choice but to hack my Python 3.5.1 site-packages directory and rm -fR pip and pip-8.x.x.dist-info directories and then do python -m ensurepip again to get to a version of pip that works. I’m not sure if this was the right way but it worked for me.

So it would be good to let users know what the correct, forcible way to remove pip is, if needed, in case of emergencies.

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/pypa/pip/issues/3588#issuecomment-201376149

-Robert

rmcgibbo on Mar 25, 2016

I have the exact same problem on synology

sortik on Mar 30, 2016