Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bugfixes for Release 0.1.5
([1,2,3], [4,5,6])
to convert to Matlab{[1 2 3] [4 5 6]}
whereas before it would have converted to Matlab[1 2 3; 4 5 6]
. Python[[1,2,3], [4,5,6]]
will still convert to Matlab[1 2 3; 4 5 6]
.m.axis([0,1,0,1])
due to incorrectly givennargout
in Matlab.py / call.m.get_nlhs
algorithm to setnargout
parameters usesast
to better parse cases of nested Matlab calls, likem.eig(m.rand(3))
but this only works if the full command is one one line; and also does not work for the basic interpreter (but should work in Mantid, Jupyter and Spyder). For those cases, the olddis
algorithm is used, updated to work with Python 3.11 but does not handle nested calls.call_python
. Changed mechanism back to using a globaldict
as direct memory address was failing in some nested calls.call_python
now creates its own instance oftype_converter
to avoid a heap memory error when using the Python initialized object from thelibpymcr
instance. Re-addDEEPBIND
library loading for Linux Lapack/BLAS to avoid conflict with Matlab.