pip3.exe accesses Python 2 install
I'm trying to use Python 3's pip from the command line in Windows 10. pip3 is in my Python 3 install; however, when called it apparently points to my Python 2 install. Why might pip3.exe live in a different Python installation than the one it actually modifies, and how could I resolve the discrepancy?
(I know other ways to use Python 3's pip, such as python3 -m pip, and that's not what I'm asking).
windows command-line path
asked Feb 12 at 1:02
JoshuaFJoshuaF
1015
add a comment |
I'm trying to use Python 3's pip from the command line in Windows 10. pip3 is in my Python 3 install; however, when called it apparently points to my Python 2 install. Why might pip3.exe live in a different Python installation than the one it actually modifies, and how could I resolve the discrepancy?
(I know other ways to use Python 3's pip, such as python3 -m pip, and that's not what I'm asking).
windows command-line path
asked Feb 12 at 1:02
JoshuaFJoshuaF
1015
2
Do you have both installations in your PATH variable?
– Ramhound
Feb 12 at 1:35
Yes, I do (which is whywhere pythonfound both). I don't think there's even apip3.exein my python 2 install, but in any case would that explain why the filewherefound was not the one executed?
– JoshuaF
Feb 13 at 6:03
add a comment |
I'm trying to use Python 3's pip from the command line in Windows 10. pip3 is in my Python 3 install; however, when called it apparently points to my Python 2 install. Why might pip3.exe live in a different Python installation than the one it actually modifies, and how could I resolve the discrepancy?
(I know other ways to use Python 3's pip, such as python3 -m pip, and that's not what I'm asking).
windows command-line path
asked Feb 12 at 1:02
JoshuaFJoshuaF
1015
I'm trying to use Python 3's pip from the command line in Windows 10. pip3 is in my Python 3 install; however, when called it apparently points to my Python 2 install. Why might pip3.exe live in a different Python installation than the one it actually modifies, and how could I resolve the discrepancy?
(I know other ways to use Python 3's pip, such as python3 -m pip, and that's not what I'm asking).
windows command-line path
windows command-line path
asked Feb 12 at 1:02
JoshuaFJoshuaF
1015
asked Feb 12 at 1:02
JoshuaFJoshuaF
1015
edited Feb 27 at 2:54
JoshuaF
asked Feb 12 at 1:02
JoshuaFJoshuaF
1015
asked Feb 12 at 1:02
JoshuaFJoshuaF
1015
asked Feb 12 at 1:02
JoshuaFJoshuaF
1015
1015
2
Do you have both installations in your PATH variable?
– Ramhound
Feb 12 at 1:35
Yes, I do (which is whywhere pythonfound both). I don't think there's even apip3.exein my python 2 install, but in any case would that explain why the filewherefound was not the one executed?
– JoshuaF
Feb 13 at 6:03
add a comment |
2
Do you have both installations in your PATH variable?
– Ramhound
Feb 12 at 1:35
Yes, I do (which is whywhere pythonfound both). I don't think there's even apip3.exein my python 2 install, but in any case would that explain why the filewherefound was not the one executed?
– JoshuaF
Feb 13 at 6:03
2
2
Do you have both installations in your PATH variable?
– Ramhound
Feb 12 at 1:35
Do you have both installations in your PATH variable?
– Ramhound
Feb 12 at 1:35
Yes, I do (which is why
where python found both). I don't think there's even a pip3.exe in my python 2 install, but in any case would that explain why the file where found was not the one executed?– JoshuaF
Feb 13 at 6:03
Yes, I do (which is why
where python found both). I don't think there's even a pip3.exe in my python 2 install, but in any case would that explain why the file where found was not the one executed?– JoshuaF
Feb 13 at 6:03
add a comment |
1 Answer
1
active
oldest
votes
It was actually my pip executable that was broken -- calling pip3.exe in my Python 3 directory still somehow accessed my Python 2 install, but python3 -m pip actually accessed pip for Python 3 as expected.
Upgrading/reinstalling Python 3's pip with python3 -m pip install --upgrade pip seems to have fixed it!
answered Feb 27 at 2:42
JoshuaFJoshuaF
1015
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1404655%2fpip3-exe-accesses-python-2-install%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It was actually my pip executable that was broken -- calling pip3.exe in my Python 3 directory still somehow accessed my Python 2 install, but python3 -m pip actually accessed pip for Python 3 as expected.
Upgrading/reinstalling Python 3's pip with python3 -m pip install --upgrade pip seems to have fixed it!
answered Feb 27 at 2:42
JoshuaFJoshuaF
1015
add a comment |
It was actually my pip executable that was broken -- calling pip3.exe in my Python 3 directory still somehow accessed my Python 2 install, but python3 -m pip actually accessed pip for Python 3 as expected.
Upgrading/reinstalling Python 3's pip with python3 -m pip install --upgrade pip seems to have fixed it!
answered Feb 27 at 2:42
JoshuaFJoshuaF
1015
add a comment |
It was actually my pip executable that was broken -- calling pip3.exe in my Python 3 directory still somehow accessed my Python 2 install, but python3 -m pip actually accessed pip for Python 3 as expected.
Upgrading/reinstalling Python 3's pip with python3 -m pip install --upgrade pip seems to have fixed it!
answered Feb 27 at 2:42
JoshuaFJoshuaF
1015
It was actually my pip executable that was broken -- calling pip3.exe in my Python 3 directory still somehow accessed my Python 2 install, but python3 -m pip actually accessed pip for Python 3 as expected.
Upgrading/reinstalling Python 3's pip with python3 -m pip install --upgrade pip seems to have fixed it!
answered Feb 27 at 2:42
JoshuaFJoshuaF
1015
answered Feb 27 at 2:42
JoshuaFJoshuaF
1015
answered Feb 27 at 2:42
JoshuaFJoshuaF
1015
answered Feb 27 at 2:42
JoshuaFJoshuaF
1015
1015
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1404655%2fpip3-exe-accesses-python-2-install%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
2
Do you have both installations in your PATH variable?
– Ramhound
Feb 12 at 1:35
Yes, I do (which is why
where pythonfound both). I don't think there's even apip3.exein my python 2 install, but in any case would that explain why the filewherefound was not the one executed?– JoshuaF
Feb 13 at 6:03