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
... in particular, I don't really think that this package specifically needs a version pin unless this package is doing something incompatible with 3.13 (or likely to be incompatible with 3.14, 3.15, etc.). If this package depends on mpython-core and that package has a version pin, then that's fine, this one will effectively inherit it when users try to install it. But by having version pins in both packages means that both packages need to be updated any time one of them is, which is a bit more painful than just letting mpython-core handle the pinning issues directly (esp. if those are related to MATLAB somehow, better to let mpython-core handle it!).
The reason for limiting the support of this package to Python <3.13 is the dependency to the spm-runtime, which contains the CTF file built through Matlab Compiler SDK and is only compatible until 3.12 (see Matlab documentation).
I agree with you regarding putting the pin in a single place. We are currently working on the installation pipeline, and this restricted compatibility should move to the spm-runtime, which is the only piece of code tied to a particular Python version. For now, our efforts have mainly been on making installation through Pip easy, but we are keen on expanding.
Didn't see an open issue, what's the reason for not supporting 3.13? Looks like
mpython-core
supports it:https://github.com/MPython-Package-Factory/mpython-core/blob/1651f7bd2105da1b2ec0d622bd946aa3142ca692/pyproject.toml#L14
The text was updated successfully, but these errors were encountered: