You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As it is matlabengine detects matlab installation path in the setup.py at installation time by checking paths in LD_LIBRARY_PATH.
This requires:
LD_LIBRARY_PATH to be defined
The installation process to be held in the same environment as it will used
Why not also using shutil.which to probe for the installation path of matlab rather than only relying on LD_LIBRARY_PATH?
What about moving this probing from setup.py (which goal is to produce the _arch.txt file) to matlab/__init__.py where this information is actually used? This would allow to make wheels and be resilient to changes in the path matlab is installed.
The text was updated successfully, but these errors were encountered:
As it is
matlabengine
detectsmatlab
installation path in thesetup.py
at installation time by checking paths inLD_LIBRARY_PATH
.This requires:
LD_LIBRARY_PATH
to be definedWhy not also using
shutil.which
to probe for the installation path of matlab rather than only relying onLD_LIBRARY_PATH
?What about moving this probing from
setup.py
(which goal is to produce the_arch.txt
file) tomatlab/__init__.py
where this information is actually used? This would allow to make wheels and be resilient to changes in the path matlab is installed.The text was updated successfully, but these errors were encountered: