pip is error,TypeError: __call__() takes exactly 2

问题:

system

• centos 7.2
• Python 2.7.5

install

I install webhook

pip install webhook
### but hava error,then
yum install python-devel -y
## go on,pip doesn't workding
pip

error

Enter the command contain pip.Then

[root@location src]# pip
Traceback (most recent call last):
File "/usr/bin/pip", line 5, in <module>
from pkg_resources import load_entry_point
File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 72, in <module>
import packaging.requirements
File "/usr/lib/python2.7/site-packages/packaging/requirements.py", line 59, in <module>
MARKER_EXPR = originalTextFor(MARKER_EXPR())("marker")
TypeError: __call__() takes exactly 2 arguments (1 given)

So,what should I do?!

回答1:

UPDATE:

Please see the solution lower in this thread by Pedro Werneck instead of this one. It's the correct way to solve the problem.

---

Preface: I do not recommend this!

This seems to work, but I have no idea what the consequences could be. This is cargo cult programming at its best! I'm only adding it here in case it can help someone in a bind.

I made changes to the file requirements.py where the error occurred. For @hysg, that would be this file:

/usr/lib/python2.7/site-packages/packaging/requirements.py

On me on OS X, it's here:

/Library/Python/2.7/site-packages/packaging/requirements.py

I modified the the offending line by removing the parentheses for the call to MARKER_EXPR, as demonstrated below:

#MARKER_EXPR = originalTextFor(MARKER_EXPR())("marker")
MARKER_EXPR = originalTextFor(MARKER_EXPR)("marker")

And that worked.

Again, please be careful! I don't know what I'm doing and this could potentially cause more harm than good.

回答2:

I had the same problem on a fresh virtualenv and apparently this is a conflict between the version requirements for packaging, pip and pyparsing with the new setuptools. What worked for me was to pin down the old one.

pip install setuptools==33.1.1

Update:

As another answer pointed out, pip has already fixed the bug, so you should try upgrading it instead of using the workaround above.

python -m pip install --upgrade --force pip 

回答3:

this is work well：

python -m pip install --upgrade --force pip 
pip install setuptools==33.1.1

回答4:

This is what worked for me:

pip install setuptools==33.1.1

It downgraded setuptools from 35.0.1 to 33.1.1 and pyparsing 1.5.7 installed!

回答5:

Use the following command to upgrade pip, which has the bug fixed:

python -m pip install --upgrade --force pip 

It worked for me (centos 7, python 2.7).

For more details: GitHub

回答6:

I applied the fix

pip install setuptools==33.1.1

and it solved the problem for OSX 10.10.5 (Yosemite)

回答7:

I ran into the same problem on a new virtualenv trying to install. I'm running python 2.7.11 and found the two commands belows solve the versioning problem with setuptools:

This forces a pip upgrade, which has a fix for the bug, but doesn't reinstall setup tools, so I was still running on setuptools version 35.0.1

python -m pip install --upgrade --force pip

This sets setuptools to an older version.

pip install setuptools==33.1.1

After this, I successfully installed my requirements.

回答8:

None of the other uninstall/reinstall/force answers worked for me, but on OS X 10.10.5 with the system Python 2.7.10, I was able to do:

pip uninstall packaging pip
easy_install pip # this installed pip 1.4.1
pip install --upgrade pip # and this upgraded to the current pip

and I was then able to import pkg_resources without a problem.

Should really learn to stop messing with the system Python…

回答9:

Actually, I had a problem that OS/system which means root, not sudo, has been the owner of the pip2 package. But after I had executed this command:

sudo apt-get remove python-pip

it worked like a charm.
Noting, of course that I have a debian distribution.

And then I used what Pedro suggested:

sudo pip install setuptools==33.1.1

回答10:

It worked for me too (centos 7, python 2.7).

python -m pip install --upgrade --force pip 
pip install setuptools==33.1.1