Skip to content

Conversation

@balbasty
Copy link
Contributor

A somewhat recent change to the type system (from about ~2 weeks ago) had quite profoundly broken the conversion of objects from matlab to python. The fix is very short and simple (830af61).

It's a bit annoying that this was not detected by our unit tests. I haven't thought too much about which tests should be added to cover this issue yet. The issue is that since the aforementioned change, dictionaries and lists are not treated exactly the same way depending on whether we know that we are converting mpython objects or not.

I've also made tiny stylistic changes to make my linter happy.

@johmedr
Copy link
Collaborator

johmedr commented Mar 24, 2025

Oh, well spotted. Should we add a batch and a SPM.mat and test to load them in our tests?

@johmedr johmedr merged commit 3bd7a55 into main Mar 24, 2025
32 checks passed
@johmedr johmedr deleted the fix-load-matlabbatch branch March 24, 2025 23:44
johmedr added a commit to MPython-Package-Factory/mpython-core that referenced this pull request Mar 24, 2025
johmedr added a commit that referenced this pull request Mar 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants