python environment on matlab

Hello,

I am trying to use python on matlab. To load the python environment I am giving the python executable file to pyenv() command as follows:

pyenv(Version="/Users/raza/anaconda3/bin/python")

% Check if the current MATLAB working directory is in the Python path

if count(py.sys.path, pwd) == 0

insert(py.sys.path, int32(0), pwd);

end

It shows me the ouput with python environment but it doesn't recognize py command and shows error as follows:

ans =

PythonEnvironment with properties:

Version: "3.11"

Executable: "/Users/raza/anaconda3/bin/python"

Library: "/Users/raza/anaconda3/lib/libpython3.11.dylib"

Home: "/Users/raza/anaconda3"

Status: NotLoaded

ExecutionMode: InProcess

Unable to resolve the name 'py.sys.path'.

Could someone please guide me, is it due to the fact that python doesn't get loaded?

System info - macOS (venture 13.6) Apple M2 Pro

Matlab version - R2023b update 7

Answer 1

[Karl]

The error message indicates a failure in the call to sys.path. There are some hints on troubleshooting this type of failure at:

https://mathworks.com/help/matlab/matlab_external/undefined-variable-py-or-function-py-command.html

[Raza]

Thank you, the problem is when I do simply pyenv("python3") it works it gets loaded. However when I use specific python version installed through anaconda it doesn't get loaded, even though I tried different versions with separate conda environments.

[Karl]

In case you haven't done so already, the following could be worth checking:

1. Do your anaconda Python builds match your MATLAB build? For information about this, specific to macOS with Apple Silicon, see: https://mathworks.com/matlabcentral/answers/1977529-how-to-use-python-from-matlab-on-mac-with-apple-silicon
2. Do you have the PYTHONHOME environment variable either unset or set to match the Python version of pyenv? For information about this, see the last paragraph of: https://mathworks.com/help/matlab/matlab_external/install-supported-python-implementation.html
3. Is there anything in your setting for the PATH environment variable that could be creating conflicts?