-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pip: main not found - CentOS 7 #5222
Comments
Seems to be very similar to #5221 But here the
Seems like if I create a new |
pip 1.4.1 is very out of date. Modern pip does not use easy_install, and we wouldn't recommend its use. Again, the recommendation is to not upgrade your system packages except using vendor-supplied packages. I'd hope CentOS (Red Hat?) are on top of this, but either way I'm sure they'll have it sorted before they release a supported pip 10 package. In the meantime you can use virtualenvs if you need pip 10. |
This was indeed for a virtualenv , not for the system. But seems like creating the venv again fixed it |
@AbdealiJK Can you elaborate more how do you fix it? I ran the pip3 install awscli --upgrade --user and got this:
|
@vincent6767 seems like you've updated the system pip which is not a good idea. I had created a new virtualenv with |
@AbdealiJK Thanks! I'm going to try your solution. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Description:
When using the latest pip on an existing CentOS 7 we created a virtualenv using the system python and then did a
pip install -U pip
to get the latest pip version for wheel support and so on.This has been working for the past few releases.
This gives an error now that the
main
function is not found in pip. WHen I do a:It still gives that main function is not found.
On checking the code, it does look like the
main
has been removed - https://github.com/pypa/pip/blob/4db471fd8f25dd644fb7079b222cb1d54a83a465/src/pip/__init__.pyBut this does not seem to have reflected in the pip binary file inside the virtualenv with the upgrade.
The text was updated successfully, but these errors were encountered: