Pip is not working: ImportError: No module named 'pip._internal'












32














Running pip or pip3 results with:



Traceback (most recent call last):
File "/home/myuser/.local/bin/pip", line 7, in <module>
from pip._internal import main
ImportError: No module named 'pip._internal'


I had issues with this, and uninstalled pip3, but when i try to install it again using



sudo apt-get -y install python3-pip


it does install, but then running pip or pip3 i get the same error.



#which pip3
/home/myuser/.local/bin/pip3









share|improve this question




















  • 2




    I have a similar problem after upgrading from pip 9.0.2 to pip-10.0.0. Ubuntu 16.04LTS here.
    – Dave
    Apr 15 at 11:19






  • 2




    You should not upgrade to pip 10 on Ubuntu, because the system version installed through apt is modified in a way not compatible to pip 10. See github.com/pypa/pip/issues/5221 @Dave
    – Byte Commander
    Apr 15 at 12:27












  • macOS 10.13.4, same problem after upfgrade to pip 10
    – Benjamin R
    Apr 21 at 4:38






  • 1




    Temporary workaround: python3 -m pip install --user <package>
    – Benjamin R
    Apr 21 at 22:14






  • 1




    if you have easy_install (comes from python-setuptools package), you can do sudo easy_install pip (or sudo easy_install3 pip for python3-only, etc.)
    – Marek Sebera
    May 25 at 14:40
















32














Running pip or pip3 results with:



Traceback (most recent call last):
File "/home/myuser/.local/bin/pip", line 7, in <module>
from pip._internal import main
ImportError: No module named 'pip._internal'


I had issues with this, and uninstalled pip3, but when i try to install it again using



sudo apt-get -y install python3-pip


it does install, but then running pip or pip3 i get the same error.



#which pip3
/home/myuser/.local/bin/pip3









share|improve this question




















  • 2




    I have a similar problem after upgrading from pip 9.0.2 to pip-10.0.0. Ubuntu 16.04LTS here.
    – Dave
    Apr 15 at 11:19






  • 2




    You should not upgrade to pip 10 on Ubuntu, because the system version installed through apt is modified in a way not compatible to pip 10. See github.com/pypa/pip/issues/5221 @Dave
    – Byte Commander
    Apr 15 at 12:27












  • macOS 10.13.4, same problem after upfgrade to pip 10
    – Benjamin R
    Apr 21 at 4:38






  • 1




    Temporary workaround: python3 -m pip install --user <package>
    – Benjamin R
    Apr 21 at 22:14






  • 1




    if you have easy_install (comes from python-setuptools package), you can do sudo easy_install pip (or sudo easy_install3 pip for python3-only, etc.)
    – Marek Sebera
    May 25 at 14:40














32












32








32


14





Running pip or pip3 results with:



Traceback (most recent call last):
File "/home/myuser/.local/bin/pip", line 7, in <module>
from pip._internal import main
ImportError: No module named 'pip._internal'


I had issues with this, and uninstalled pip3, but when i try to install it again using



sudo apt-get -y install python3-pip


it does install, but then running pip or pip3 i get the same error.



#which pip3
/home/myuser/.local/bin/pip3









share|improve this question















Running pip or pip3 results with:



Traceback (most recent call last):
File "/home/myuser/.local/bin/pip", line 7, in <module>
from pip._internal import main
ImportError: No module named 'pip._internal'


I had issues with this, and uninstalled pip3, but when i try to install it again using



sudo apt-get -y install python3-pip


it does install, but then running pip or pip3 i get the same error.



#which pip3
/home/myuser/.local/bin/pip3






python pip






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 15 at 11:25









Yaron

8,84871939




8,84871939










asked Apr 15 at 10:44









user3087079

161125




161125








  • 2




    I have a similar problem after upgrading from pip 9.0.2 to pip-10.0.0. Ubuntu 16.04LTS here.
    – Dave
    Apr 15 at 11:19






  • 2




    You should not upgrade to pip 10 on Ubuntu, because the system version installed through apt is modified in a way not compatible to pip 10. See github.com/pypa/pip/issues/5221 @Dave
    – Byte Commander
    Apr 15 at 12:27












  • macOS 10.13.4, same problem after upfgrade to pip 10
    – Benjamin R
    Apr 21 at 4:38






  • 1




    Temporary workaround: python3 -m pip install --user <package>
    – Benjamin R
    Apr 21 at 22:14






  • 1




    if you have easy_install (comes from python-setuptools package), you can do sudo easy_install pip (or sudo easy_install3 pip for python3-only, etc.)
    – Marek Sebera
    May 25 at 14:40














  • 2




    I have a similar problem after upgrading from pip 9.0.2 to pip-10.0.0. Ubuntu 16.04LTS here.
    – Dave
    Apr 15 at 11:19






  • 2




    You should not upgrade to pip 10 on Ubuntu, because the system version installed through apt is modified in a way not compatible to pip 10. See github.com/pypa/pip/issues/5221 @Dave
    – Byte Commander
    Apr 15 at 12:27












  • macOS 10.13.4, same problem after upfgrade to pip 10
    – Benjamin R
    Apr 21 at 4:38






  • 1




    Temporary workaround: python3 -m pip install --user <package>
    – Benjamin R
    Apr 21 at 22:14






  • 1




    if you have easy_install (comes from python-setuptools package), you can do sudo easy_install pip (or sudo easy_install3 pip for python3-only, etc.)
    – Marek Sebera
    May 25 at 14:40








2




2




I have a similar problem after upgrading from pip 9.0.2 to pip-10.0.0. Ubuntu 16.04LTS here.
– Dave
Apr 15 at 11:19




I have a similar problem after upgrading from pip 9.0.2 to pip-10.0.0. Ubuntu 16.04LTS here.
– Dave
Apr 15 at 11:19




2




2




You should not upgrade to pip 10 on Ubuntu, because the system version installed through apt is modified in a way not compatible to pip 10. See github.com/pypa/pip/issues/5221 @Dave
– Byte Commander
Apr 15 at 12:27






You should not upgrade to pip 10 on Ubuntu, because the system version installed through apt is modified in a way not compatible to pip 10. See github.com/pypa/pip/issues/5221 @Dave
– Byte Commander
Apr 15 at 12:27














macOS 10.13.4, same problem after upfgrade to pip 10
– Benjamin R
Apr 21 at 4:38




macOS 10.13.4, same problem after upfgrade to pip 10
– Benjamin R
Apr 21 at 4:38




1




1




Temporary workaround: python3 -m pip install --user <package>
– Benjamin R
Apr 21 at 22:14




Temporary workaround: python3 -m pip install --user <package>
– Benjamin R
Apr 21 at 22:14




1




1




if you have easy_install (comes from python-setuptools package), you can do sudo easy_install pip (or sudo easy_install3 pip for python3-only, etc.)
– Marek Sebera
May 25 at 14:40




if you have easy_install (comes from python-setuptools package), you can do sudo easy_install pip (or sudo easy_install3 pip for python3-only, etc.)
– Marek Sebera
May 25 at 14:40










3 Answers
3






active

oldest

votes


















64














After upgrading pip (or pip3, in this case) if the following occurs:



$ ~ pip3 -V
Traceback (most recent call last):
File "/usr/local/bin/pip", line 7, in <module>
from pip._internal import main
ModuleNotFoundError: No module named 'pip._internal'


Force a reinstall of pip:



curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py
python3 get-pip.py --force-reinstall


Verify install:



$ ~ pip3 -V
pip 10.0.1 from /usr/local/lib/python3.6/site-packages/pip (python 3.6)


Now pip3 install <package> and pip3 install --user <package> (for user-level installs) will work correctly.



There should never, ever be any reason you need to run pip in elevated mode.



(note: For Python 2.7, just replace python for python3, and pip for pip3)



Had same problem on macOS as well, it's a common issue across platforms.






share|improve this answer

















  • 1




    Works for pip2.7 too! Thanks.
    – YongHao Hu
    Apr 24 at 9:10






  • 1




    works as fine for the raspberry too
    – gtatr
    Jul 11 at 19:53






  • 1




    you, sir, are a hero. had this problem on solus and it worked like a charm.
    – cirrusio
    Jul 18 at 3:16






  • 1




    @endolith Okay, now you want to use sudo rm -rf /usr/bin/pip3 – purge that existing directory first, then install from scratch. It's a permissions problem on that directory, but it's better to reset in these circumstances I believe, you can always easily reinstall whatever packages you lose again. If that doesn't work, nuke your Python 3 install, too, then reboot.
    – Benjamin R
    Aug 23 at 8:57








  • 1




    @endolith Hi, it depends on what your OS (and distro, if Linux) is. Let me know and I’ll try to point you in the right direction. p.s. We’ve all been in your position more times than most of us like to admit :)
    – Benjamin R
    Aug 24 at 14:35





















4














This command also works, it reinstalls the pip:



sudo easy_install pip






share|improve this answer

















  • 2




    That's the easiest answer!
    – Serge Stroobandt
    Aug 8 at 17:16






  • 1




    Worked like a wonder on Ubuntu
    – user2849789
    Sep 9 at 0:53





















1














I got the same problem as you just now, I found the reason is that you are working without superuser privilege since some internal python packages or modules are installed under superuser privilege.



So you can try by fist entering sudo su, then enter your password, and run pip install, it might help.






share|improve this answer

















  • 2




    You should never, ever need to run pip with elevated permissions. Use --user flag instead, as in: pip3 install --user <package>
    – Benjamin R
    Apr 21 at 4:44






  • 1




    However, when I run without superuser permission, I still got the information like pip3 install --user Traceback (most recent call last): File "/usr/local/bin/pip3", line 7, in <module>\ from pip._internal import main ImportError: No module named 'pip._internal' Could you please help me to figure out why this always happen?
    – Yuke
    Apr 22 at 5:21








  • 2




    Ok, I found out why, if from pip._internal import main error happen, in my solution, 1) curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py 2) python3 get-pip.py --user --force-reinstall, and then you can run pip without superuser permission, Thank you very much for your advice, it helps a lot !
    – Yuke
    Apr 22 at 5:36












  • My pleasure! Look, I learned the hard way to be careful about using sudo willy-nilly (destroyed my OS multiple times!)
    – Benjamin R
    Apr 23 at 7:34










  • Hmmm askubuntu.com/a/802594/5032
    – endolith
    Aug 21 at 10:40











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1025189%2fpip-is-not-working-importerror-no-module-named-pip-internal%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























3 Answers
3






active

oldest

votes








3 Answers
3






active

oldest

votes









active

oldest

votes






active

oldest

votes









64














After upgrading pip (or pip3, in this case) if the following occurs:



$ ~ pip3 -V
Traceback (most recent call last):
File "/usr/local/bin/pip", line 7, in <module>
from pip._internal import main
ModuleNotFoundError: No module named 'pip._internal'


Force a reinstall of pip:



curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py
python3 get-pip.py --force-reinstall


Verify install:



$ ~ pip3 -V
pip 10.0.1 from /usr/local/lib/python3.6/site-packages/pip (python 3.6)


Now pip3 install <package> and pip3 install --user <package> (for user-level installs) will work correctly.



There should never, ever be any reason you need to run pip in elevated mode.



(note: For Python 2.7, just replace python for python3, and pip for pip3)



Had same problem on macOS as well, it's a common issue across platforms.






share|improve this answer

















  • 1




    Works for pip2.7 too! Thanks.
    – YongHao Hu
    Apr 24 at 9:10






  • 1




    works as fine for the raspberry too
    – gtatr
    Jul 11 at 19:53






  • 1




    you, sir, are a hero. had this problem on solus and it worked like a charm.
    – cirrusio
    Jul 18 at 3:16






  • 1




    @endolith Okay, now you want to use sudo rm -rf /usr/bin/pip3 – purge that existing directory first, then install from scratch. It's a permissions problem on that directory, but it's better to reset in these circumstances I believe, you can always easily reinstall whatever packages you lose again. If that doesn't work, nuke your Python 3 install, too, then reboot.
    – Benjamin R
    Aug 23 at 8:57








  • 1




    @endolith Hi, it depends on what your OS (and distro, if Linux) is. Let me know and I’ll try to point you in the right direction. p.s. We’ve all been in your position more times than most of us like to admit :)
    – Benjamin R
    Aug 24 at 14:35


















64














After upgrading pip (or pip3, in this case) if the following occurs:



$ ~ pip3 -V
Traceback (most recent call last):
File "/usr/local/bin/pip", line 7, in <module>
from pip._internal import main
ModuleNotFoundError: No module named 'pip._internal'


Force a reinstall of pip:



curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py
python3 get-pip.py --force-reinstall


Verify install:



$ ~ pip3 -V
pip 10.0.1 from /usr/local/lib/python3.6/site-packages/pip (python 3.6)


Now pip3 install <package> and pip3 install --user <package> (for user-level installs) will work correctly.



There should never, ever be any reason you need to run pip in elevated mode.



(note: For Python 2.7, just replace python for python3, and pip for pip3)



Had same problem on macOS as well, it's a common issue across platforms.






share|improve this answer

















  • 1




    Works for pip2.7 too! Thanks.
    – YongHao Hu
    Apr 24 at 9:10






  • 1




    works as fine for the raspberry too
    – gtatr
    Jul 11 at 19:53






  • 1




    you, sir, are a hero. had this problem on solus and it worked like a charm.
    – cirrusio
    Jul 18 at 3:16






  • 1




    @endolith Okay, now you want to use sudo rm -rf /usr/bin/pip3 – purge that existing directory first, then install from scratch. It's a permissions problem on that directory, but it's better to reset in these circumstances I believe, you can always easily reinstall whatever packages you lose again. If that doesn't work, nuke your Python 3 install, too, then reboot.
    – Benjamin R
    Aug 23 at 8:57








  • 1




    @endolith Hi, it depends on what your OS (and distro, if Linux) is. Let me know and I’ll try to point you in the right direction. p.s. We’ve all been in your position more times than most of us like to admit :)
    – Benjamin R
    Aug 24 at 14:35
















64












64








64






After upgrading pip (or pip3, in this case) if the following occurs:



$ ~ pip3 -V
Traceback (most recent call last):
File "/usr/local/bin/pip", line 7, in <module>
from pip._internal import main
ModuleNotFoundError: No module named 'pip._internal'


Force a reinstall of pip:



curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py
python3 get-pip.py --force-reinstall


Verify install:



$ ~ pip3 -V
pip 10.0.1 from /usr/local/lib/python3.6/site-packages/pip (python 3.6)


Now pip3 install <package> and pip3 install --user <package> (for user-level installs) will work correctly.



There should never, ever be any reason you need to run pip in elevated mode.



(note: For Python 2.7, just replace python for python3, and pip for pip3)



Had same problem on macOS as well, it's a common issue across platforms.






share|improve this answer












After upgrading pip (or pip3, in this case) if the following occurs:



$ ~ pip3 -V
Traceback (most recent call last):
File "/usr/local/bin/pip", line 7, in <module>
from pip._internal import main
ModuleNotFoundError: No module named 'pip._internal'


Force a reinstall of pip:



curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py
python3 get-pip.py --force-reinstall


Verify install:



$ ~ pip3 -V
pip 10.0.1 from /usr/local/lib/python3.6/site-packages/pip (python 3.6)


Now pip3 install <package> and pip3 install --user <package> (for user-level installs) will work correctly.



There should never, ever be any reason you need to run pip in elevated mode.



(note: For Python 2.7, just replace python for python3, and pip for pip3)



Had same problem on macOS as well, it's a common issue across platforms.







share|improve this answer












share|improve this answer



share|improve this answer










answered Apr 21 at 5:07









Benjamin R

977714




977714








  • 1




    Works for pip2.7 too! Thanks.
    – YongHao Hu
    Apr 24 at 9:10






  • 1




    works as fine for the raspberry too
    – gtatr
    Jul 11 at 19:53






  • 1




    you, sir, are a hero. had this problem on solus and it worked like a charm.
    – cirrusio
    Jul 18 at 3:16






  • 1




    @endolith Okay, now you want to use sudo rm -rf /usr/bin/pip3 – purge that existing directory first, then install from scratch. It's a permissions problem on that directory, but it's better to reset in these circumstances I believe, you can always easily reinstall whatever packages you lose again. If that doesn't work, nuke your Python 3 install, too, then reboot.
    – Benjamin R
    Aug 23 at 8:57








  • 1




    @endolith Hi, it depends on what your OS (and distro, if Linux) is. Let me know and I’ll try to point you in the right direction. p.s. We’ve all been in your position more times than most of us like to admit :)
    – Benjamin R
    Aug 24 at 14:35
















  • 1




    Works for pip2.7 too! Thanks.
    – YongHao Hu
    Apr 24 at 9:10






  • 1




    works as fine for the raspberry too
    – gtatr
    Jul 11 at 19:53






  • 1




    you, sir, are a hero. had this problem on solus and it worked like a charm.
    – cirrusio
    Jul 18 at 3:16






  • 1




    @endolith Okay, now you want to use sudo rm -rf /usr/bin/pip3 – purge that existing directory first, then install from scratch. It's a permissions problem on that directory, but it's better to reset in these circumstances I believe, you can always easily reinstall whatever packages you lose again. If that doesn't work, nuke your Python 3 install, too, then reboot.
    – Benjamin R
    Aug 23 at 8:57








  • 1




    @endolith Hi, it depends on what your OS (and distro, if Linux) is. Let me know and I’ll try to point you in the right direction. p.s. We’ve all been in your position more times than most of us like to admit :)
    – Benjamin R
    Aug 24 at 14:35










1




1




Works for pip2.7 too! Thanks.
– YongHao Hu
Apr 24 at 9:10




Works for pip2.7 too! Thanks.
– YongHao Hu
Apr 24 at 9:10




1




1




works as fine for the raspberry too
– gtatr
Jul 11 at 19:53




works as fine for the raspberry too
– gtatr
Jul 11 at 19:53




1




1




you, sir, are a hero. had this problem on solus and it worked like a charm.
– cirrusio
Jul 18 at 3:16




you, sir, are a hero. had this problem on solus and it worked like a charm.
– cirrusio
Jul 18 at 3:16




1




1




@endolith Okay, now you want to use sudo rm -rf /usr/bin/pip3 – purge that existing directory first, then install from scratch. It's a permissions problem on that directory, but it's better to reset in these circumstances I believe, you can always easily reinstall whatever packages you lose again. If that doesn't work, nuke your Python 3 install, too, then reboot.
– Benjamin R
Aug 23 at 8:57






@endolith Okay, now you want to use sudo rm -rf /usr/bin/pip3 – purge that existing directory first, then install from scratch. It's a permissions problem on that directory, but it's better to reset in these circumstances I believe, you can always easily reinstall whatever packages you lose again. If that doesn't work, nuke your Python 3 install, too, then reboot.
– Benjamin R
Aug 23 at 8:57






1




1




@endolith Hi, it depends on what your OS (and distro, if Linux) is. Let me know and I’ll try to point you in the right direction. p.s. We’ve all been in your position more times than most of us like to admit :)
– Benjamin R
Aug 24 at 14:35






@endolith Hi, it depends on what your OS (and distro, if Linux) is. Let me know and I’ll try to point you in the right direction. p.s. We’ve all been in your position more times than most of us like to admit :)
– Benjamin R
Aug 24 at 14:35















4














This command also works, it reinstalls the pip:



sudo easy_install pip






share|improve this answer

















  • 2




    That's the easiest answer!
    – Serge Stroobandt
    Aug 8 at 17:16






  • 1




    Worked like a wonder on Ubuntu
    – user2849789
    Sep 9 at 0:53


















4














This command also works, it reinstalls the pip:



sudo easy_install pip






share|improve this answer

















  • 2




    That's the easiest answer!
    – Serge Stroobandt
    Aug 8 at 17:16






  • 1




    Worked like a wonder on Ubuntu
    – user2849789
    Sep 9 at 0:53
















4












4








4






This command also works, it reinstalls the pip:



sudo easy_install pip






share|improve this answer












This command also works, it reinstalls the pip:



sudo easy_install pip







share|improve this answer












share|improve this answer



share|improve this answer










answered Jul 10 at 14:39









Carlos Dutra

714




714








  • 2




    That's the easiest answer!
    – Serge Stroobandt
    Aug 8 at 17:16






  • 1




    Worked like a wonder on Ubuntu
    – user2849789
    Sep 9 at 0:53
















  • 2




    That's the easiest answer!
    – Serge Stroobandt
    Aug 8 at 17:16






  • 1




    Worked like a wonder on Ubuntu
    – user2849789
    Sep 9 at 0:53










2




2




That's the easiest answer!
– Serge Stroobandt
Aug 8 at 17:16




That's the easiest answer!
– Serge Stroobandt
Aug 8 at 17:16




1




1




Worked like a wonder on Ubuntu
– user2849789
Sep 9 at 0:53






Worked like a wonder on Ubuntu
– user2849789
Sep 9 at 0:53













1














I got the same problem as you just now, I found the reason is that you are working without superuser privilege since some internal python packages or modules are installed under superuser privilege.



So you can try by fist entering sudo su, then enter your password, and run pip install, it might help.






share|improve this answer

















  • 2




    You should never, ever need to run pip with elevated permissions. Use --user flag instead, as in: pip3 install --user <package>
    – Benjamin R
    Apr 21 at 4:44






  • 1




    However, when I run without superuser permission, I still got the information like pip3 install --user Traceback (most recent call last): File "/usr/local/bin/pip3", line 7, in <module>\ from pip._internal import main ImportError: No module named 'pip._internal' Could you please help me to figure out why this always happen?
    – Yuke
    Apr 22 at 5:21








  • 2




    Ok, I found out why, if from pip._internal import main error happen, in my solution, 1) curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py 2) python3 get-pip.py --user --force-reinstall, and then you can run pip without superuser permission, Thank you very much for your advice, it helps a lot !
    – Yuke
    Apr 22 at 5:36












  • My pleasure! Look, I learned the hard way to be careful about using sudo willy-nilly (destroyed my OS multiple times!)
    – Benjamin R
    Apr 23 at 7:34










  • Hmmm askubuntu.com/a/802594/5032
    – endolith
    Aug 21 at 10:40
















1














I got the same problem as you just now, I found the reason is that you are working without superuser privilege since some internal python packages or modules are installed under superuser privilege.



So you can try by fist entering sudo su, then enter your password, and run pip install, it might help.






share|improve this answer

















  • 2




    You should never, ever need to run pip with elevated permissions. Use --user flag instead, as in: pip3 install --user <package>
    – Benjamin R
    Apr 21 at 4:44






  • 1




    However, when I run without superuser permission, I still got the information like pip3 install --user Traceback (most recent call last): File "/usr/local/bin/pip3", line 7, in <module>\ from pip._internal import main ImportError: No module named 'pip._internal' Could you please help me to figure out why this always happen?
    – Yuke
    Apr 22 at 5:21








  • 2




    Ok, I found out why, if from pip._internal import main error happen, in my solution, 1) curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py 2) python3 get-pip.py --user --force-reinstall, and then you can run pip without superuser permission, Thank you very much for your advice, it helps a lot !
    – Yuke
    Apr 22 at 5:36












  • My pleasure! Look, I learned the hard way to be careful about using sudo willy-nilly (destroyed my OS multiple times!)
    – Benjamin R
    Apr 23 at 7:34










  • Hmmm askubuntu.com/a/802594/5032
    – endolith
    Aug 21 at 10:40














1












1








1






I got the same problem as you just now, I found the reason is that you are working without superuser privilege since some internal python packages or modules are installed under superuser privilege.



So you can try by fist entering sudo su, then enter your password, and run pip install, it might help.






share|improve this answer












I got the same problem as you just now, I found the reason is that you are working without superuser privilege since some internal python packages or modules are installed under superuser privilege.



So you can try by fist entering sudo su, then enter your password, and run pip install, it might help.







share|improve this answer












share|improve this answer



share|improve this answer










answered Apr 16 at 3:34









Yuke

212




212








  • 2




    You should never, ever need to run pip with elevated permissions. Use --user flag instead, as in: pip3 install --user <package>
    – Benjamin R
    Apr 21 at 4:44






  • 1




    However, when I run without superuser permission, I still got the information like pip3 install --user Traceback (most recent call last): File "/usr/local/bin/pip3", line 7, in <module>\ from pip._internal import main ImportError: No module named 'pip._internal' Could you please help me to figure out why this always happen?
    – Yuke
    Apr 22 at 5:21








  • 2




    Ok, I found out why, if from pip._internal import main error happen, in my solution, 1) curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py 2) python3 get-pip.py --user --force-reinstall, and then you can run pip without superuser permission, Thank you very much for your advice, it helps a lot !
    – Yuke
    Apr 22 at 5:36












  • My pleasure! Look, I learned the hard way to be careful about using sudo willy-nilly (destroyed my OS multiple times!)
    – Benjamin R
    Apr 23 at 7:34










  • Hmmm askubuntu.com/a/802594/5032
    – endolith
    Aug 21 at 10:40














  • 2




    You should never, ever need to run pip with elevated permissions. Use --user flag instead, as in: pip3 install --user <package>
    – Benjamin R
    Apr 21 at 4:44






  • 1




    However, when I run without superuser permission, I still got the information like pip3 install --user Traceback (most recent call last): File "/usr/local/bin/pip3", line 7, in <module>\ from pip._internal import main ImportError: No module named 'pip._internal' Could you please help me to figure out why this always happen?
    – Yuke
    Apr 22 at 5:21








  • 2




    Ok, I found out why, if from pip._internal import main error happen, in my solution, 1) curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py 2) python3 get-pip.py --user --force-reinstall, and then you can run pip without superuser permission, Thank you very much for your advice, it helps a lot !
    – Yuke
    Apr 22 at 5:36












  • My pleasure! Look, I learned the hard way to be careful about using sudo willy-nilly (destroyed my OS multiple times!)
    – Benjamin R
    Apr 23 at 7:34










  • Hmmm askubuntu.com/a/802594/5032
    – endolith
    Aug 21 at 10:40








2




2




You should never, ever need to run pip with elevated permissions. Use --user flag instead, as in: pip3 install --user <package>
– Benjamin R
Apr 21 at 4:44




You should never, ever need to run pip with elevated permissions. Use --user flag instead, as in: pip3 install --user <package>
– Benjamin R
Apr 21 at 4:44




1




1




However, when I run without superuser permission, I still got the information like pip3 install --user Traceback (most recent call last): File "/usr/local/bin/pip3", line 7, in <module>\ from pip._internal import main ImportError: No module named 'pip._internal' Could you please help me to figure out why this always happen?
– Yuke
Apr 22 at 5:21






However, when I run without superuser permission, I still got the information like pip3 install --user Traceback (most recent call last): File "/usr/local/bin/pip3", line 7, in <module>\ from pip._internal import main ImportError: No module named 'pip._internal' Could you please help me to figure out why this always happen?
– Yuke
Apr 22 at 5:21






2




2




Ok, I found out why, if from pip._internal import main error happen, in my solution, 1) curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py 2) python3 get-pip.py --user --force-reinstall, and then you can run pip without superuser permission, Thank you very much for your advice, it helps a lot !
– Yuke
Apr 22 at 5:36






Ok, I found out why, if from pip._internal import main error happen, in my solution, 1) curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py 2) python3 get-pip.py --user --force-reinstall, and then you can run pip without superuser permission, Thank you very much for your advice, it helps a lot !
– Yuke
Apr 22 at 5:36














My pleasure! Look, I learned the hard way to be careful about using sudo willy-nilly (destroyed my OS multiple times!)
– Benjamin R
Apr 23 at 7:34




My pleasure! Look, I learned the hard way to be careful about using sudo willy-nilly (destroyed my OS multiple times!)
– Benjamin R
Apr 23 at 7:34












Hmmm askubuntu.com/a/802594/5032
– endolith
Aug 21 at 10:40




Hmmm askubuntu.com/a/802594/5032
– endolith
Aug 21 at 10:40


















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1025189%2fpip-is-not-working-importerror-no-module-named-pip-internal%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Quarter-circle Tiles

build a pushdown automaton that recognizes the reverse language of a given pushdown automaton?

Mont Emei