Matlab system and ! commands point to wrong python version?

I am trying to run python programs using the system function in Matlab. In spite of changing the PythonEnvironment using;

>> pe=pyenv('Version','/opt/anaconda3/bin/python3.8')

pe =

PythonEnvironment with properties:

Version: "3.8"

Executable: "/opt/anaconda3/bin/python3.8"

Library: "/opt/anaconda3/lib/libpython3.8.dylib"

Home: "/opt/anaconda3"

Status: NotLoaded

ExecutionMode: InProcess

When using the ! or system comands, Matlab still utilises the old Python vesion. This is illustrated below...

>> pyenv

ans =

PythonEnvironment with properties:

Version: "3.8"

Executable: "/opt/anaconda3/bin/python3.8"

Library: "/opt/anaconda3/lib/libpython3.8.dylib"

Home: "/opt/anaconda3"

Status: NotLoaded

ExecutionMode: InProcess

>> ! python --version

Python 2.7.16

>> system('python --version')

Python 2.7.16

ans =

0

How can I get these commands to access my python 3.8?

Answer 1

[Walter Roberson]

This is expected. Using ! or system() find the python that is first in your system path, which might not be the same one you have configured MATLAB to use. Using the pyenv() call does not reconfigure your PATH environment variables.

You might need to do something like

!PATH="/opt/anaconda3/bin:$PATH" python -version

I do not know enough about python to know whether you need to configure an environment variable for the library.

[Mark Davidson]

Thank you! This worked very well.

>> myPath='/opt/anaconda3/bin:$PATH'

system(['export PATH=' myPath ' ; ','python --version']);

myPath =

'/opt/anaconda3/bin:$PATH'

Python 3.8.8

Answer 2

[Steven Baird]

This worked for me:

>> system('python --version');

Python 3.12.0