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
Using a version of, e.g. "R2018a" is not a standard version number that meets the Pep requirements for python packaging, and as a result causes issues with some programs that assume the standards are being met.
I suggest switching to a semver approach, such as "2018.1.x" for R2018A and "2018.2.x" for R2018B. This allows for proper versioning of bugfix releases as well, similar to the release versions of the major Matlab versions (i.e. R2019a release 8, etc.). Currently, the Poetry dependency manager for Python chokes on matlab.engine versions as a result after installation.
Note: This was after installing from matlabroot/extern/engines/python directly, the pip install method may be different.
The text was updated successfully, but these errors were encountered:
Using a version of, e.g. "R2018a" is not a standard version number that meets the Pep requirements for python packaging, and as a result causes issues with some programs that assume the standards are being met.
I suggest switching to a semver approach, such as "2018.1.x" for R2018A and "2018.2.x" for R2018B. This allows for proper versioning of bugfix releases as well, similar to the release versions of the major Matlab versions (i.e. R2019a release 8, etc.). Currently, the Poetry dependency manager for Python chokes on matlab.engine versions as a result after installation.
Note: This was after installing from matlabroot/extern/engines/python directly, the pip install method may be different.
The text was updated successfully, but these errors were encountered: