The current example/ project does not run with mojo v24.4, it simply needs a couple of simple patches because of changes in the String api, (use str() instead) and also where there are SIMD comparisons, which needs all(result == expect) for example. There might also be an issue with defining 'main' within a package is not yet supported which I don't fully understand yet.
However, a better approach for v24.4 is seems like for mojo-pytest to wrap the newmojo test ... functionality as a backend for mojo tests, rather than the previous approach which was calling mojo run ... as the backend.
guidorice
commented
2 months ago
The current example/ project does not run with mojo v24.4, it simply needs a couple of simple patches because of changes in the String api, (use
str()instead) and also where there are SIMD comparisons, which needsall(result == expect)for example. There might also be an issue withdefining 'main' within a package is not yet supportedwhich I don't fully understand yet.However, a better approach for v24.4 is seems like for
mojo-pytestto wrap the newmojo test ...functionality as a backend for mojo tests, rather than the previous approach which was callingmojo run ...as the backend.