Your python3 install is corruptedHow to fix “python installation is corrupted”?18.04--GnomeTerminal won't...
Does Dispel Magic work on Tiny Hut?
How badly should I try to prevent a user from XSSing themselves?
One verb to replace 'be a member of' a club
How to install cross-compiler on Ubuntu 18.04?
How to stretch the corners of this image so that it looks like a perfect rectangle?
Is it a bad idea to plug the other end of ESD strap to wall ground?
What is the most common color to indicate the input-field is disabled?
Can a virus destroy the BIOS of a modern computer?
how do we prove that a sum of two periods is still a period?
Is it possible to create a QR code using text?
Fair gambler's ruin problem intuition
Why is it a bad idea to hire a hitman to eliminate most corrupt politicians?
What is required to make GPS signals available indoors?
Venezuelan girlfriend wants to travel the USA to be with me. What is the process?
My ex-girlfriend uses my Apple ID to log in to her iPad. Do I have to give her my Apple ID password to reset it?
Rotate ASCII Art by 45 Degrees
Does int main() need a declaration on C++?
How exploitable/balanced is this homebrew spell: Spell Permanency?
Was the Stack Exchange "Happy April Fools" page fitting with the '90's code?
Ambiguity in the definition of entropy
Mathematica command that allows it to read my intentions
meaning of 腰を落としている
Description list Formatting using enumitem
GFCI outlets - can they be repaired? Are they really needed at the end of a circuit?
Your python3 install is corrupted
How to fix “python installation is corrupted”?18.04--GnomeTerminal won't startPython - pip pip2 pip3 pip3.5 packages are installed but cannot be imported in any Python sessioncant install python3 on ubuntuCan't upgrade from 15.10 to 16.04Can't install python3-pipTheano package is not importable in Python 3.6After removing python3.5 from dual boot Ubuntu 16.04.03 (Along with W10), not able to access ubuntu nowError While Installing IBM Watson TTSpython and pip not in syncUbuntu 18.04 no installation or update after upgrade from 16.04
I want to upgrade from Ubuntu 16.04.5 LTS
to 18.04
, so ran sudo do-release-upgrade
.
After downloading and extracting bionic.tar.gz
I get:
Can not upgrade
Your python3 install is corrupted. Please fix the '/usr/bin/python3'
symlink.
I saw How to fix "python installation is corrupted"? and so I did sudo ln -sf /usr/bin/python3.6 /usr/bin/python3
thinking that it would be a similar problem. But that didn't work (still same error message).
I have a few python versions:
ls /usr/lib | grep python
python2.7
python3
python3.5
python3.6
update-alternatives --display python3
python3 - auto mode
link best version is /usr/bin/python3.6
link currently points to /usr/bin/python3.6
link python3 is /usr/bin/python3
/usr/bin/python3.5 - priority 1
/usr/bin/python3.6 - priority 2
How do I fix python3
?
python3 do-release-upgrade
add a comment |
I want to upgrade from Ubuntu 16.04.5 LTS
to 18.04
, so ran sudo do-release-upgrade
.
After downloading and extracting bionic.tar.gz
I get:
Can not upgrade
Your python3 install is corrupted. Please fix the '/usr/bin/python3'
symlink.
I saw How to fix "python installation is corrupted"? and so I did sudo ln -sf /usr/bin/python3.6 /usr/bin/python3
thinking that it would be a similar problem. But that didn't work (still same error message).
I have a few python versions:
ls /usr/lib | grep python
python2.7
python3
python3.5
python3.6
update-alternatives --display python3
python3 - auto mode
link best version is /usr/bin/python3.6
link currently points to /usr/bin/python3.6
link python3 is /usr/bin/python3
/usr/bin/python3.5 - priority 1
/usr/bin/python3.6 - priority 2
How do I fix python3
?
python3 do-release-upgrade
1
And what about reinstallation (as mentioned in accepted answer)?
– Kulfy
Dec 23 '18 at 18:21
add a comment |
I want to upgrade from Ubuntu 16.04.5 LTS
to 18.04
, so ran sudo do-release-upgrade
.
After downloading and extracting bionic.tar.gz
I get:
Can not upgrade
Your python3 install is corrupted. Please fix the '/usr/bin/python3'
symlink.
I saw How to fix "python installation is corrupted"? and so I did sudo ln -sf /usr/bin/python3.6 /usr/bin/python3
thinking that it would be a similar problem. But that didn't work (still same error message).
I have a few python versions:
ls /usr/lib | grep python
python2.7
python3
python3.5
python3.6
update-alternatives --display python3
python3 - auto mode
link best version is /usr/bin/python3.6
link currently points to /usr/bin/python3.6
link python3 is /usr/bin/python3
/usr/bin/python3.5 - priority 1
/usr/bin/python3.6 - priority 2
How do I fix python3
?
python3 do-release-upgrade
I want to upgrade from Ubuntu 16.04.5 LTS
to 18.04
, so ran sudo do-release-upgrade
.
After downloading and extracting bionic.tar.gz
I get:
Can not upgrade
Your python3 install is corrupted. Please fix the '/usr/bin/python3'
symlink.
I saw How to fix "python installation is corrupted"? and so I did sudo ln -sf /usr/bin/python3.6 /usr/bin/python3
thinking that it would be a similar problem. But that didn't work (still same error message).
I have a few python versions:
ls /usr/lib | grep python
python2.7
python3
python3.5
python3.6
update-alternatives --display python3
python3 - auto mode
link best version is /usr/bin/python3.6
link currently points to /usr/bin/python3.6
link python3 is /usr/bin/python3
/usr/bin/python3.5 - priority 1
/usr/bin/python3.6 - priority 2
How do I fix python3
?
python3 do-release-upgrade
python3 do-release-upgrade
asked Dec 23 '18 at 17:54
mRcSchweringmRcSchwering
1235
1235
1
And what about reinstallation (as mentioned in accepted answer)?
– Kulfy
Dec 23 '18 at 18:21
add a comment |
1
And what about reinstallation (as mentioned in accepted answer)?
– Kulfy
Dec 23 '18 at 18:21
1
1
And what about reinstallation (as mentioned in accepted answer)?
– Kulfy
Dec 23 '18 at 18:21
And what about reinstallation (as mentioned in accepted answer)?
– Kulfy
Dec 23 '18 at 18:21
add a comment |
3 Answers
3
active
oldest
votes
You need to use the default Python 3 version for 16.04. That's 3.5, not 3.6. So run:
sudo ln -sf /usr/bin/python3.5 /usr/bin/python3
If that doesn't work, try reinstalling the python3
package.
sudo apt-get install --reinstall python3
By the way, update-alternatives --display python3
should give you update-alternatives: error: no alternatives for python3
. Different versions of Python are not alternatives in Ubuntu.
add a comment |
I just ran into this problem on Pop!_OS 18.04, trying to upgrade to 18.10, and it turns out that the problem lay in the symlink for /usr/bin/python
and not for /usr/bin/python3
. I had had /usr/bin/python3.6
configured as an alternative for python
(not python3
), and when I changed this, then I could run do-release-upgrade
as expected.
I wish the error message pointed to python
and not python3
.
Before, with the problem:
$ update-alternatives --display python
python - manual mode
link best version is /usr/bin/python3.6
link currently points to /usr/bin/python2.7
link python is /usr/bin/python
/usr/bin/python2.7 - priority 1
/usr/bin/python3.6 - priority 2
I fixed it this way:
$ sudo update-alternatives --remove-all python
$ sudo ln -sf /usr/bin/python2.7 /usr/bin/python
add a comment |
Basically the solution to this problem consists of making /usr/bin/python
point to the right version of Python your Ubuntu release expects (for instance, in 16.04 was Python2.7 and in 18.04 was Python3.6).
If you have several versions of Python installed in your system, you might be using update-alternatives
to manage them. It doesn't matter much your default alternative for Python is the right version your system expects (3.6 in Ubuntu 18.04), it won't work.
The reason why this doesn't work is that, when using update-alternatives
, /usr/bin/python3
points to /etc/alternatives/python3
, and it seems that's not exactly the same as making /usr/bin/python3
point to /usr/bin/python3.6
.
That's why the solution to this problem often consists of stop managing your Python3 versions with update-alternatives
and make /usr/bin/python3
point to the right version of Python3 your system expects.
New contributor
add a comment |
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
});
}
});
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%2faskubuntu.com%2fquestions%2f1104052%2fyour-python3-install-is-corrupted%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
You need to use the default Python 3 version for 16.04. That's 3.5, not 3.6. So run:
sudo ln -sf /usr/bin/python3.5 /usr/bin/python3
If that doesn't work, try reinstalling the python3
package.
sudo apt-get install --reinstall python3
By the way, update-alternatives --display python3
should give you update-alternatives: error: no alternatives for python3
. Different versions of Python are not alternatives in Ubuntu.
add a comment |
You need to use the default Python 3 version for 16.04. That's 3.5, not 3.6. So run:
sudo ln -sf /usr/bin/python3.5 /usr/bin/python3
If that doesn't work, try reinstalling the python3
package.
sudo apt-get install --reinstall python3
By the way, update-alternatives --display python3
should give you update-alternatives: error: no alternatives for python3
. Different versions of Python are not alternatives in Ubuntu.
add a comment |
You need to use the default Python 3 version for 16.04. That's 3.5, not 3.6. So run:
sudo ln -sf /usr/bin/python3.5 /usr/bin/python3
If that doesn't work, try reinstalling the python3
package.
sudo apt-get install --reinstall python3
By the way, update-alternatives --display python3
should give you update-alternatives: error: no alternatives for python3
. Different versions of Python are not alternatives in Ubuntu.
You need to use the default Python 3 version for 16.04. That's 3.5, not 3.6. So run:
sudo ln -sf /usr/bin/python3.5 /usr/bin/python3
If that doesn't work, try reinstalling the python3
package.
sudo apt-get install --reinstall python3
By the way, update-alternatives --display python3
should give you update-alternatives: error: no alternatives for python3
. Different versions of Python are not alternatives in Ubuntu.
answered Dec 23 '18 at 18:50
wjandreawjandrea
9,48842664
9,48842664
add a comment |
add a comment |
I just ran into this problem on Pop!_OS 18.04, trying to upgrade to 18.10, and it turns out that the problem lay in the symlink for /usr/bin/python
and not for /usr/bin/python3
. I had had /usr/bin/python3.6
configured as an alternative for python
(not python3
), and when I changed this, then I could run do-release-upgrade
as expected.
I wish the error message pointed to python
and not python3
.
Before, with the problem:
$ update-alternatives --display python
python - manual mode
link best version is /usr/bin/python3.6
link currently points to /usr/bin/python2.7
link python is /usr/bin/python
/usr/bin/python2.7 - priority 1
/usr/bin/python3.6 - priority 2
I fixed it this way:
$ sudo update-alternatives --remove-all python
$ sudo ln -sf /usr/bin/python2.7 /usr/bin/python
add a comment |
I just ran into this problem on Pop!_OS 18.04, trying to upgrade to 18.10, and it turns out that the problem lay in the symlink for /usr/bin/python
and not for /usr/bin/python3
. I had had /usr/bin/python3.6
configured as an alternative for python
(not python3
), and when I changed this, then I could run do-release-upgrade
as expected.
I wish the error message pointed to python
and not python3
.
Before, with the problem:
$ update-alternatives --display python
python - manual mode
link best version is /usr/bin/python3.6
link currently points to /usr/bin/python2.7
link python is /usr/bin/python
/usr/bin/python2.7 - priority 1
/usr/bin/python3.6 - priority 2
I fixed it this way:
$ sudo update-alternatives --remove-all python
$ sudo ln -sf /usr/bin/python2.7 /usr/bin/python
add a comment |
I just ran into this problem on Pop!_OS 18.04, trying to upgrade to 18.10, and it turns out that the problem lay in the symlink for /usr/bin/python
and not for /usr/bin/python3
. I had had /usr/bin/python3.6
configured as an alternative for python
(not python3
), and when I changed this, then I could run do-release-upgrade
as expected.
I wish the error message pointed to python
and not python3
.
Before, with the problem:
$ update-alternatives --display python
python - manual mode
link best version is /usr/bin/python3.6
link currently points to /usr/bin/python2.7
link python is /usr/bin/python
/usr/bin/python2.7 - priority 1
/usr/bin/python3.6 - priority 2
I fixed it this way:
$ sudo update-alternatives --remove-all python
$ sudo ln -sf /usr/bin/python2.7 /usr/bin/python
I just ran into this problem on Pop!_OS 18.04, trying to upgrade to 18.10, and it turns out that the problem lay in the symlink for /usr/bin/python
and not for /usr/bin/python3
. I had had /usr/bin/python3.6
configured as an alternative for python
(not python3
), and when I changed this, then I could run do-release-upgrade
as expected.
I wish the error message pointed to python
and not python3
.
Before, with the problem:
$ update-alternatives --display python
python - manual mode
link best version is /usr/bin/python3.6
link currently points to /usr/bin/python2.7
link python is /usr/bin/python
/usr/bin/python2.7 - priority 1
/usr/bin/python3.6 - priority 2
I fixed it this way:
$ sudo update-alternatives --remove-all python
$ sudo ln -sf /usr/bin/python2.7 /usr/bin/python
answered Jan 8 at 15:46
J. B. RainsbergerJ. B. Rainsberger
1213
1213
add a comment |
add a comment |
Basically the solution to this problem consists of making /usr/bin/python
point to the right version of Python your Ubuntu release expects (for instance, in 16.04 was Python2.7 and in 18.04 was Python3.6).
If you have several versions of Python installed in your system, you might be using update-alternatives
to manage them. It doesn't matter much your default alternative for Python is the right version your system expects (3.6 in Ubuntu 18.04), it won't work.
The reason why this doesn't work is that, when using update-alternatives
, /usr/bin/python3
points to /etc/alternatives/python3
, and it seems that's not exactly the same as making /usr/bin/python3
point to /usr/bin/python3.6
.
That's why the solution to this problem often consists of stop managing your Python3 versions with update-alternatives
and make /usr/bin/python3
point to the right version of Python3 your system expects.
New contributor
add a comment |
Basically the solution to this problem consists of making /usr/bin/python
point to the right version of Python your Ubuntu release expects (for instance, in 16.04 was Python2.7 and in 18.04 was Python3.6).
If you have several versions of Python installed in your system, you might be using update-alternatives
to manage them. It doesn't matter much your default alternative for Python is the right version your system expects (3.6 in Ubuntu 18.04), it won't work.
The reason why this doesn't work is that, when using update-alternatives
, /usr/bin/python3
points to /etc/alternatives/python3
, and it seems that's not exactly the same as making /usr/bin/python3
point to /usr/bin/python3.6
.
That's why the solution to this problem often consists of stop managing your Python3 versions with update-alternatives
and make /usr/bin/python3
point to the right version of Python3 your system expects.
New contributor
add a comment |
Basically the solution to this problem consists of making /usr/bin/python
point to the right version of Python your Ubuntu release expects (for instance, in 16.04 was Python2.7 and in 18.04 was Python3.6).
If you have several versions of Python installed in your system, you might be using update-alternatives
to manage them. It doesn't matter much your default alternative for Python is the right version your system expects (3.6 in Ubuntu 18.04), it won't work.
The reason why this doesn't work is that, when using update-alternatives
, /usr/bin/python3
points to /etc/alternatives/python3
, and it seems that's not exactly the same as making /usr/bin/python3
point to /usr/bin/python3.6
.
That's why the solution to this problem often consists of stop managing your Python3 versions with update-alternatives
and make /usr/bin/python3
point to the right version of Python3 your system expects.
New contributor
Basically the solution to this problem consists of making /usr/bin/python
point to the right version of Python your Ubuntu release expects (for instance, in 16.04 was Python2.7 and in 18.04 was Python3.6).
If you have several versions of Python installed in your system, you might be using update-alternatives
to manage them. It doesn't matter much your default alternative for Python is the right version your system expects (3.6 in Ubuntu 18.04), it won't work.
The reason why this doesn't work is that, when using update-alternatives
, /usr/bin/python3
points to /etc/alternatives/python3
, and it seems that's not exactly the same as making /usr/bin/python3
point to /usr/bin/python3.6
.
That's why the solution to this problem often consists of stop managing your Python3 versions with update-alternatives
and make /usr/bin/python3
point to the right version of Python3 your system expects.
New contributor
New contributor
answered 13 mins ago
Diego PinoDiego Pino
101
101
New contributor
New contributor
add a comment |
add a comment |
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.
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%2faskubuntu.com%2fquestions%2f1104052%2fyour-python3-install-is-corrupted%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
1
And what about reinstallation (as mentioned in accepted answer)?
– Kulfy
Dec 23 '18 at 18:21