I have a directory accessible from multiple Linux machines on the same network (the precise terminology for this is a directory on a "mounted network drive", right?), within which I have a python virtual environment, made with python3 -m venv venv.
I've tried checking the python version from a few of the machines using this:
$ . venv/bin/activate
$ python --version
and I get back different versions depending on what machine it is. Some show 3.8.5, some 3.8.10. I believe I've figured out that this is because the "interpreter" in the venv is really a link to the interpreter in /usr/bin, which is machine-specific:
$ ls -lah ./venv/bin/ | grep python
lrwxrwxrwx 1 echols14 cs236ta 7 Sep 29 02:08 python -> python3
lrwxrwxrwx 1 echols14 cs236ta 16 Sep 29 02:08 python3 -> /usr/bin/python3
When I take a look at the contents of /usr/bin, it seems like there are more things there relating to python than just the single interpreter file python3.8:
$ ls -lah /usr/bin | grep python
-rwxr-xr-x 1 root root 2.3K Jun 20 2017 dh_python3-ply
lrwxrwxrwx 1 root root 23 Sep 28 16:10 pdb3.8 -> ../lib/python3.8/pdb.py
lrwxrwxrwx 1 root root 31 Mar 13 2020 py3versions -> ../share/python3/py3versions.py
lrwxrwxrwx 1 root root 9 Mar 13 2020 python3 -> python3.8
-rwxr-xr-x 1 root root 5.3M Sep 28 16:10 python3.8
lrwxrwxrwx 1 root root 33 Sep 28 16:10 python3.8-config -> x86_64-linux-gnu-python3.8-config
lrwxrwxrwx 1 root root 16 Mar 13 2020 python3-config -> python3.8-config
-rwxr-xr-x 1 root root 364 Dec 17 2019 python3-qr
-rwxr-xr-x 1 root root 3.2K Sep 28 16:10 x86_64-linux-gnu-python3.8-config
lrwxrwxrwx 1 root root 33 Mar 13 2020 x86_64-linux-gnu-python3-config -> x86_64-linux-gnu-python3.8-config
I'd like the venv to use the same python version regardless of which machine it is used from. Is that possible?
My first thought is to copy the python3.8 file from one machine's /usr/bin and place it in the venv's bin, then adjust the links so that it is the one that gets used when the venv is activated. Would I need to copy other python-related files from /usr/bin for it to function? Is this method safe, or should it be avoided for some reason?
If that method is not a good idea, what other way could I get the shared venv to always use the same version of python, regardless of the machine?
NOTE: I don't have root/sudo permissions on all machines in question, but I do have root/sudo permissions on one of the machines.
Found it. When creating the virtual environment, use the --copies option:
--copies Try to use copies rather than symlinks, even when
symlinks are the default for the platform
documentation
Which looks like this:
python3 -m venv --copies venv
And results in this:
$ ls -lah venv/bin/ | grep python
-rwxr-xr-x 1 echols14 cs236ta 5.3M Oct 7 18:26 python
-rwxr-xr-x 1 echols14 cs236ta 5.3M Oct 7 18:26 python3
i have installed python 3 ..
when i do :
ls -ltr /usr/bin | grep python (in buildah it will be $mount_container/usr/bin)
0 lrwxrwxrwx. 1 root root 25 Jan 7 10:12 python3 -> /etc/alternatives/python3
0 lrwxrwxrwx. 1 root root 31 Jun 22 2019 python3.6 -> /usr/libexec/platform-python3.6
0 lrwxrwxrwx. 1 root root 32 Jun 22 2019 python3.6m -> /usr/libexec/platform-python3.6m
0 lrwxrwxrwx. 1 root root 24 Jan 7 10:12 unversioned-python -> /etc/alternatives/python
but when i do
$/usr/bin/python3
it is saying "no such file or directory".
Note that i am running this inside a continer (using buildah , trying to build a docker which has python3)
if i do $mount_continer/usr/bin/python3 it says "no such file or directory"
Try:
cd / (goes into root directory)
and then type
/usr/bin/python3
Now you must see the python interpreter.
Explanation - Python is generally found in the location /usr/bin/
/usr/bin/python3 will simply invoke the python3 found inside /usr/bin but since you run the command from outside the root directory,the first directory i.e /usr is not found. /home and /usr are inside the root directory, and you are running the command from /home directory. Hope it helps.
Note:For Ubuntu 16.04
I have python2.7 and python3.6 in my Ubuntu, both installed from apt-get.
I found python2.7 is only 3.4M, but python3.6 approximates 12M, why so big difference?
The following is the command:
bash-4.3$ ls -lh `which python2.7`
-rwxr-xr-x 1 root root 3.4M Nov 13 03:46 /usr/bin/python2.7
bash-4.3$ ls -lh `which python3.6`
-rwxr-xr-x 2 root root 18K May 5 2018 /usr/local/bin/python3.6
Seems python3.6 executable uses dynamic linking, so I used pamp to find that .so file :
00007fdf14242000 2668 r-x-- 0000000000000000 008:00001 libpython3.6m.so.1.0
00007fdf144dd000 2044 ----- 000000000029b000 008:00001 libpython3.6m.so.1.0
00007fdf146dc000 12 r---- 000000000029a000 008:00001 libpython3.6m.so.1.0
00007fdf146df000 408 rw--- 000000000029d000 008:00001 libpython3.6m.so.1.0
It's libpython3.6m.so.1.0, then I checked its file size:
bash-4.3$ ls -lh /usr/local/lib/libpython3.6m.so.1.0
-r-xr-xr-x 1 root root 12M May 5 2018 /usr/local/lib/libpython3.6m.so.1.0
12M, why so large?
And I'm also confused that libpython3.6m.so.1.0 only occupies (2668k+2044k=)4.7M in virtual address space, where has the other 7.3M gone?
Thank you.
PS: I also used pmap to check the address space of python2.7, no dynamic library of python found, so I think python2.7 is statically linked.
Trying to get jenkins to work with anaconda python. I'm using the shiningpanda plugin and python plugin.
Whenever I try to set the python installation to point to my python 2.7 executable, /home/lminer/anaconda/bin/python2.7, I get the message that it is neither a directory nor an executable. Is there some 2.7 compatibility problem?
Edit:
Here's my python info
# which python
/home/lminer/anaconda/bin/python2
# ls -l /home/lminer/anaconda/bin/python*
lrwxrwxrwx 1 root root 7 Oct 9 17:02 /home/lminer/anaconda/bin/python -> python2
lrwxrwxrwx 1 root root 9 Oct 9 17:02 /home/lminer/anaconda/bin/python2 -> python2.7
-rwxr-xr-x 1 root root 10038 Oct 9 17:02 /home/lminer/anaconda/bin/python2.7
-rwxr-xr-x 1 root root 1600 Oct 9 17:02 /home/lminer/anaconda/bin/python-argcomplete-check-easy-install-script
-rwxr-xr-x 1 root root 1678 Oct 9 17:02 /home/lminer/anaconda/bin/python-config
Not sure how to give evidence on the error. I go to Jenkins > configuration > Python > Python Installations. Under Home or executable I put /home/lminer/anaconda/bin/python2.7, /home/lminer/anaconda/bin/python, /home/lminer/anaconda/bin/. And each time a message in red below the box reads: Neither a directory nor an executable
I don't get this issue if I instead point to /usr/bin/python2.6
Turns out I hadn't set permissions correctly. The directory is recognized once I let everyone execute from it. If there's a better way to do this, perhaps by moving python to a different location, let me know.
I have installed Python 3.2 in my Mac. After I run /Applications/Python 3.2/Update Shell Profile.command, it's confusing that when I type Python -V in Terminal it says that Python 2.6.1.
How can I change the default Python version?
[updated for 2021]
(Regardless if you are on Mac, Linux, or Windows:)
If you are confused about how to start the latest version of python, on most platforms it is the case that python3 leaves your python2 installation intact (due to the above compatibility reasons); thus you can start python3 with the python3 command.
Historically...
The naming convention is that generally, most scripts will call python2 or python3 explicitly. This happened due to a need for backwards compatibility.
Even though technically python doesn't even guarantee backwards compatibility between minor versions, Python3 really breaks backwards compatibility. At the time, programs invoking 'python' were expecting python2 (which was the main version at the time). Extremely old systems may have programs and scripts which expect python=python2, and changing this would break those programs and scripts.
At the time this answer was written, OP should not have changed this due to maintaining compatibility for old scripts.
Circa year 2021...
Nowadays, many years after the python2->python3 transition, most software explicitly refers to python2 or python3 (at least on Linux). For example, they might call #!/usr/bin/env python2 or #!/usr/bin/env python3. This has for example (python-is-python3-package) freed up the python command to be settable to a user default, but it really depends on the operating system.
The prescription for how distributions should handle the python command was written up in 2011 as PEP 394 -- The "python" Command on Unix-Like Systems. It was last updated in June 2019.
Basically if you are writing a library, you should specify the version of python (2 or 3, or finer-grained under specific circumstances) you can use. Otherwise as an end user, you should feel free to rename this for your own personal use (though your OS or distribution may not make that easy).
Shell alias:
You could, however, make a custom alias in your shell. The way you do so depends on the shell, but perhaps you could do alias py=python3, and put it in your shell startup file. This will only work on your local computer (as it should), and is somewhat unnecessary compared to just typing it out (unless you invoke the command constantly).
Confused users should not try to create aliases or virtual environments or similar that make python execute python3; this is poor form.This is acceptable nowadays, but PEP 394 suggests encouraging users to use a virtualenv instead.
Different 3.* versions, or 2.* versions:
In the extremely unlikely case that if someone comes to this question with two python3 versions e.g. 3.1 vs 3.2, and you are confused that you have somehow installed two versions of python, this is possibly because you have done manual and/or manual installations. You can use your OS's standard package/program install/uninstall/management facilities to help track things down, and perhaps (unless you are doing dev work that surprisingly is impacted by the few backwards-incompatible changes between minor versions) delete the old version (or do make uninstall if you did a manual installation). If you require two versions, then reconfigure your $PATH variable so the 'default' version you want is in front; or if you are using most Linux distros, the command you are looking for is sudo update-alternatives. Make sure any programs you run which need access to the older versions may be properly invoked by their calling environment or shell (by setting up the var PATH in that environment).
A bit about $PATH
sidenote: To elaborate a bit on PATH: the usual ways that programs are selected is via the PATH (echo $PATH on Linux and Mac) environment variable. You can always run a program with the full path e.g. /usr/bin/🔳 some args, or cd /usr/bin then ./🔳 some args (replace blank with the 'echo' program I mentioned above for example), but otherwise typing 🔳 some args has no meaning without PATH env variable which declares the directories we implicitly may search-then-execute files from (if /usr/bin was not in PATH, then it would say 🔳: command not found). The first matching command in the first directory is the one which is executed (the which command on Linux and Mac will tell you which sub-path this is). Usually it is (e.g. on Linux, but similar on Mac) something like /usr/bin/python which is a symlink to other symlinks to the final version somewhere, e.g.:
% echo $PATH
/usr/sbin:/usr/local/bin:/usr/sbin:usr/local/bin:/usr/bin:/bin
% which python
/usr/bin/python
% which python2
/usr/bin/python2
% ls -l /usr/bin/python
lrwxrwxrwx 1 root root 7 Mar 4 2019 /usr/bin/python -> python2*
% ls -l /usr/bin/python2
lrwxrwxrwx 1 root root 9 Mar 4 2019 /usr/bin/python2 -> python2.7*
% ls -l /usr/bin/python2.7
-rwxr-xr-x 1 root root 3689352 Oct 10 2019 /usr/bin/python2.7*
% which python3
/usr/bin/python3
% ls -l /usr/bin/python3
lrwxrwxrwx 1 root root 9 Mar 26 2019 /usr/bin/python3 -> python3.7*
% ls -l /usr/bin/python3.7
-rwxr-xr-x 2 root root 4877888 Apr 2 2019 /usr/bin/python3.7*
% ls -l /usr/bin/python*
lrwxrwxrwx 1 root root 7 Mar 4 2019 /usr/bin/python -> python2*
lrwxrwxrwx 1 root root 9 Mar 4 2019 /usr/bin/python2 -> python2.7*
-rwxr-xr-x 1 root root 3689352 Oct 10 2019 /usr/bin/python2.7*
lrwxrwxrwx 1 root root 9 Mar 26 2019 /usr/bin/python3 -> python3.7*
-rwxr-xr-x 2 root root 4877888 Apr 2 2019 /usr/bin/python3.7*
lrwxrwxrwx 1 root root 33 Apr 2 2019 /usr/bin/python3.7-config -> x86_64-linux-gnu-python3.7-config*
-rwxr-xr-x 2 root root 4877888 Apr 2 2019 /usr/bin/python3.7m*
lrwxrwxrwx 1 root root 34 Apr 2 2019 /usr/bin/python3.7m-config -> x86_64-linux-gnu-python3.7m-config*
lrwxrwxrwx 1 root root 16 Mar 26 2019 /usr/bin/python3-config -> python3.7-config*
lrwxrwxrwx 1 root root 10 Mar 26 2019 /usr/bin/python3m -> python3.7m*
lrwxrwxrwx 1 root root 17 Mar 26 2019 /usr/bin/python3m-config -> python3.7m-config*
sidenote2: (In the rarer case a python program invokes a sub-program with the subprocess module, to specify which program to run, one can modify the paths of subprocesses with sys.path from the sys module or the PYTHONPATH environment variable set on the parent, or specifying the full path... but since the path is inherited by child processes this is not remotely likely an issue.)
Check the location of python 3
$ which python3
/usr/local/bin/python3
Write alias in bash_profile
vi ~/.bash_profile
alias python='/usr/local/bin/python3'
Reload bash_profile
source ~/.bash_profile
Confirm python command
$ python --version
Python 3.6.5
On Mac OS X using the python.org installer as you apparently have, you need to invoke Python 3 with python3, not python. That is currently reserved for Python 2 versions. You could also use python3.2 to specifically invoke that version.
$ which python
/usr/bin/python
$ which python3
/Library/Frameworks/Python.framework/Versions/3.2/bin/python3
$ cd /Library/Frameworks/Python.framework/Versions/3.2/bin/
$ ls -l
total 384
lrwxr-xr-x 1 root admin 8 Apr 28 15:51 2to3# -> 2to3-3.2
-rwxrwxr-x 1 root admin 140 Feb 20 11:14 2to3-3.2*
lrwxr-xr-x 1 root admin 7 Apr 28 15:51 idle3# -> idle3.2
-rwxrwxr-x 1 root admin 138 Feb 20 11:14 idle3.2*
lrwxr-xr-x 1 root admin 8 Apr 28 15:51 pydoc3# -> pydoc3.2
-rwxrwxr-x 1 root admin 123 Feb 20 11:14 pydoc3.2*
-rwxrwxr-x 2 root admin 25624 Feb 20 11:14 python3*
lrwxr-xr-x 1 root admin 12 Apr 28 15:51 python3-32# -> python3.2-32
lrwxr-xr-x 1 root admin 16 Apr 28 15:51 python3-config# -> python3.2-config
-rwxrwxr-x 2 root admin 25624 Feb 20 11:14 python3.2*
-rwxrwxr-x 1 root admin 13964 Feb 20 11:14 python3.2-32*
lrwxr-xr-x 1 root admin 17 Apr 28 15:51 python3.2-config# -> python3.2m-config
-rwxrwxr-x 1 root admin 25784 Feb 20 11:14 python3.2m*
-rwxrwxr-x 1 root admin 1865 Feb 20 11:14 python3.2m-config*
lrwxr-xr-x 1 root admin 10 Apr 28 15:51 pythonw3# -> pythonw3.2
lrwxr-xr-x 1 root admin 13 Apr 28 15:51 pythonw3-32# -> pythonw3.2-32
-rwxrwxr-x 1 root admin 25624 Feb 20 11:14 pythonw3.2*
-rwxrwxr-x 1 root admin 13964 Feb 20 11:14 pythonw3.2-32*
If you also installed a Python 2 from python.org, it would have a similar framework bin directory with no overlapping file names (except for 2to3).
$ open /Applications/Python\ 2.7/Update\ Shell\ Profile.command
$ sh -l
$ echo $PATH
/Library/Frameworks/Python.framework/Versions/2.7/bin:/Library/Frameworks/Python.framework/Versions/3.2/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin
$ which python3
/Library/Frameworks/Python.framework/Versions/3.2/bin/python3
$ which python
/Library/Frameworks/Python.framework/Versions/2.7/bin/python
$ cd /Library/Frameworks/Python.framework/Versions/2.7/bin
$ ls -l
total 288
-rwxrwxr-x 1 root admin 150 Jul 3 2010 2to3*
lrwxr-x--- 1 root admin 7 Nov 8 23:14 idle# -> idle2.7
-rwxrwxr-x 1 root admin 138 Jul 3 2010 idle2.7*
lrwxr-x--- 1 root admin 8 Nov 8 23:14 pydoc# -> pydoc2.7
-rwxrwxr-x 1 root admin 123 Jul 3 2010 pydoc2.7*
lrwxr-x--- 1 root admin 9 Nov 8 23:14 python# -> python2.7
lrwxr-x--- 1 root admin 16 Nov 8 23:14 python-config# -> python2.7-config
-rwxrwxr-x 1 root admin 33764 Jul 3 2010 python2.7*
-rwxrwxr-x 1 root admin 1663 Jul 3 2010 python2.7-config*
lrwxr-x--- 1 root admin 10 Nov 8 23:14 pythonw# -> pythonw2.7
-rwxrwxr-x 1 root admin 33764 Jul 3 2010 pythonw2.7*
lrwxr-x--- 1 root admin 11 Nov 8 23:14 smtpd.py# -> smtpd2.7.py
-rwxrwxr-x 1 root admin 18272 Jul 3 2010 smtpd2.7.py*
Old question, but alternatively:
virtualenv --python=python3.5 .venv
source .venv/bin/activate
Update 11 May 2022 Wed EST PM 06:36
Thanks #Aditya Deshpande! Great suggestion!
I've just fixed my answer.
After taking ~/.bashrc or ~/.zshrc effect, there is no need to
quit and restart the terminal.
Do right thing, do thing right!
--->Zero Open your terminal,
--Firstly input python -V, It likely shows:
Python 2.7.10
-Secondly input python3 -V, It likely shows:
Python 3.7.2
--Thirdly input where python or which python, It likely shows:
/usr/bin/python
---Fourthly input where python3 or which python3, It likely shows:
/usr/local/bin/python3
--Fifthly add the following line at the bottom of your PATH environment variable file in ~/.profile file or ~/.bash_profile under Bash or ~/.zshrc under zsh.
alias python='/usr/local/bin/python3'
OR
alias python=python3
-Sixthly input source ~/.bash_profile under Bash or source ~/.zshrc under zsh.
--Seventhly then checkout the version of Python
input python -V, It likely shows:
Python 3.7.2
I had done successfully try it.
Others, the ~/.bash_profile under zsh is not that ~/.bash_profile.
The PATH environment variable under zsh instead ~/.profile (or ~/.bash_file) via ~/.zshrc.
Help you guys!
Change the "default" Python by putting it ahead of the system Python on your path, for instance:
export PATH=/usr/local/bin:$PATH
Set Python 3.5 with higher priority
sudo update-alternatives --install /usr/bin/python python /usr/bin/python2.7 1
sudo update-alternatives --install /usr/bin/python python /usr/bin/python3.5 2
Check the result
sudo update-alternatives --config python
python -V
Check the execution path of python3 where it has libraries
$ which python3
/usr/local/bin/python3 some OS might have /usr/bin/python3
open bash_profile file and add an alias
vi ~/.bash_profile
alias python='/usr/local/bin/python3' or alias python='/usr/bin/python3'
Reload bash_profile to take effect of modifications
source ~/.bash_profile
Run python command and check whether it's getting loading with python3
$ python --version
Python 3.6.5
According to a quick google search, this update only applies to the current shell you have open. It can probably be fixed by typing python3, as mac and linux are similar enough for things like this to coincide. Link to the result of google search.
Also, as ninjagecko stated, most programs have not been updated to 3.x yet, so having the default python as 3.x would break many python scripts used in applications.
I am using OS X 10.7.5 and Python 3.4.2. If you type python3 and what you want to run it will run it using python 3. For example
pyhton3 test001.py. That ran a test program I made called test001. I hope this helps.
you can change temporarily or switch between different versions using following commands:
set path=C:\Users\Shaina\AppData\Local\Programs\Python\Python35-32;%PATH%
python --version
Navigate to:
My Computer -> Properties -> Advanced -> Environment Variables -> System Variables
Suppose you had already having python 2.7 added in path variable and you want to change default path to python 3.x
then add path of python3.5.x folder before python2.7 path.
open cmd: type "python --version"
python version will be changed to python 3.5.x
sudo mv /usr/bin/python /usr/bin/python2
sudo ln -s $(which python3) /usr/bin/python
This will break scripts, but is exactly the way to change python. You should also rewrite the scripts to not assume python is 2.x. This will work regardless of the place where you call system or exec.
In short: change the path in Environment Variables!
For Windows:
Advanced System Settings > Advance (tab). On bottom you'll find 'Environment Variables'
Double-click on the Path. You'll see path to one of the python installations, change that to path of your desired version.
In my case, on my Mac OSX, with Python 2.7.18 installed via mac ports, I was able to set the python version to 2.7 with:
$ sudo port select --set python python27
So:
$ python -V
Python 2.7.18
It should be noted that recent versions of Homebrew/MacOS will require a different entry for the PATH as the location where Homebrew installs Python has changed. Add this like to your .zshrc:
export PATH="/opt/homebrew/opt/python/libexec/bin:$PATH"
This will ensure that the appropriate unversioned python link installed by Homebrew appears before that of version 2.x and will protect you from being impacted by any version updates to python as brew will update the unversioned links whenever it updates the version.
Starting with macOS Catalina the default shell is zsh. Therefore, all those ~/.bash_profile changes are not going to change the default when you open a new terminal since the new terminal is a zsh shell and not a bash shell.
You can confirm your terminal is a zsh shell by typing echo $SHELL and you should see a response of: zsh.
What should you do? You should use a solution that works for zsh shell and bash shell. Therefore, do the following:
enter: vi ~/.bash_profile
enter: alias python='python3'
close and save your bash_profile. Enter: :wq
Now open/create your zsh profile. Enter: vi ~/.zshrc
source your bash inside your zshrc. Enter: source ~/.bash_profile
Now python will be aliased to python3 in your zsh shells (and in bash if you switch the default) automatically.
Test:
python --version
Python 3.8.9
In order to change the python version context switching without exporting environment variable. Please use the below video link to see:
https://youtu.be/jTN4MHNhJZs
After installing the newer version of python to your computer...
When you want to run a python program (e.g. 'program.py') from the terminal (using the latest version of python on your system); instead of running 'python program.py' run 'python3 program.py'
Similarly, if you want to use python in the terminal (using the latest version of python on your system) run 'python3' instead of 'python'
As a test try to run 'python3 --v' in the terminal...