Sep-13-2019, 04:12 AM
after python2's EOL, is it "safe" to change the plain "python" command to point to or run python3? anyone know when it was changed from python1 to python2?
Skaperen Wrote:is it "safe" to change the plain "python" command to point to or run python3?It probably depends on your OS. I wouldn't change the "python" command in a Linux OS where the default python is python 2. Instead, upgrade the OS to a version where the python command points to python 3.
(Sep-13-2019, 06:31 AM)Larz60+ Wrote: [ -> ]2.0 beta 26-sept-2000
2.0 release candidate 9-Oct-2000
2.0 final release 16-Oct-2000
(Sep-13-2019, 07:37 AM)Gribouillis Wrote: [ -> ]Skaperen Wrote:is it "safe" to change the plain "python" command to point to or run python3?It probably depends on your OS. I wouldn't change the "python" command in a Linux OS where the default python is python 2. Instead, upgrade the OS to a version where the python command points to python 3.
Skaperen Wrote:if one installs python3 from a source build, does that change the "python" command if it already exists?You could experiment with this in a virtualbox instance.
python
and pip
always point to version choose as global(system wide).snippsat Wrote:Why pyenv?
- pyenv will install Python or other Distribution(Anaconda,PyPy,MicroPython...ect),set it as system wide installation(or run it in a shell seesion).
- No more using python3 or pip3 or
sudo
or--user
when pip install something.
- It's always
python
andpip
to version set as global,andpip install requests
to global version.
- It's safe and will not mess with your OS,can go back to default
pyenv local system
or remove all rm -rf $(pyenv root)