YAQ about reloading python modules in Matlab after python changes
10 visualizzazioni (ultimi 30 giorni)
Mostra commenti meno recenti
I understand that there have been a number of questions regarding issues with Matlab not reloading python modules after they have been changed. Based off other answers, I have an acceptable solution, but I think I am hitting a bug.
My python:
class myTestClass:
def __init__(self, somestr):
self.loc = 1234
print("Init called")
def __del__(self):
print("Destructor")
def myTestFunc(self):
a = 456
print(f'My Test Func called loc={self.loc} a={a}')
My Matlab:
%clear classes
myMatlabTestClass = py.importlib.import_module('myMatlabTestClass');
py.importlib.reload(myMatlabTestClass);
pyclass = myMatlabTestClass.myTestClass("hello");
pyclass.myTestFunc()
The problem:
The above is sensitive to python code changes if I change the value of self.loc, but changing the value of a in myTestFunc requires the inclusion of clear classes.
I fear that clear classes will be too expensive and may impact other code, depending on where it is called.
I'd like to understand why a and self.loc would be treated differently here and if there is a workaround.
Risposte (1)
SHAQLAIN
il 24 Dic 2023
class myTestClass:
def __init__(self, somestr):
self.loc = 1234
print("Init called")
def __del__(self):
print("Destructor")
def myTestFunc(self):
a = 456
print(f'My Test Func called loc={self.loc} a={a}')
2 Commenti
Walter Roberson
il 24 Dic 2023
Could you point out the difference between this and what was originally posted?
Vedere anche
Categorie
Scopri di più su Call Python from MATLAB in Help Center e File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!