How to make a .mpy file for v 1.23 upython?

[krismc]

For the last few months I've been making .mpy files for v1.23 upython by typing

>pipx run  mpy-cross==1.23.0 -v code.py

into the windows command prompt
It's been working OK till today

Fatal error from pip prevented installation. Full pip output in file:
    C:\Users\Admin\pipx\logs\cmd_2024-12-24_16.19.45_pip_errors.log

Some possibly relevant errors from pip install:
    ERROR: Could not find a version that satisfies the requirement mpy-cross==1.23.0 (from versions: none)
    ERROR: No matching distribution found for mpy-cross==1.23.0
Error installing mpy-cross from spec 'mpy-cross==1.23.0'.

I tried

mpy-cross -v code.py

which produces a .mpy file that gives

ValueError: incompatible .mpy file

when I try to run it in v1.23 upython on an esp32. Presumably because it's v1.24?

Anybody know a way to produce v1.23 compatible .mpy files from the windows command prompt?

[bixb922]

See here https://pypi.org/project/mpy-cross/

This version of mpy-cross allows

mpy-cross --compat 1.23 my_app.py

[krismc]

I tried installing this version.

C:\Users\Admin\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\mpy_cross>pip install mpy-cross
Collecting mpy-cross
  Downloading mpy_cross-1.24.1.post2-py2.py3-none-win_amd64.whl.metadata (3.6 kB)
Downloading mpy_cross-1.24.1.post2-py2.py3-none-win_amd64.whl (1.2 MB)
   ---------------------------------------- 1.2/1.2 MB 1.8 MB/s eta 0:00:00
Installing collected packages: mpy-cross
Successfully installed mpy-cross-1.24.1.post2

Sadly, it shows no inclination to actually make .mpy files. Or if it is making them, I can't find where it puts them.

C:\Users\Admin\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\mpy_cross>mpy-cross --compat 1.23 code.py
usage: mpy-cross [<opts>] [-X <implopt>] <input filename>
Options:
--version : show version information
-o : output file for compiled bytecode (defaults to input with .mpy extension)
-s : source filename to embed in the compiled bytecode (defaults to input file)
-v : verbose (trace various operations); can be multiple
-O[N] : apply bytecode optimizations of level N

Target specific options:
-msmall-int-bits=number : set the maximum bits used to encode a small-int
-mno-unicode : don't support unicode in compiled strings
-mcache-lookup-bc : cache map lookups in the bytecode
-march=<arch> : set architecture for native emitter; x86, x64, armv6, armv7m, armv7em, armv7emsp, armv7emdp, xtensa, xtensawin

Implementation specific options:
  emit={bytecode,native,viper} -- set the default code emitter
  heapsize=<n> -- set the heap size for the GC (default 2097152)

C:\Users\Admin\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\mpy_cross>

[bixb922]

I am sorry to cause a confusion. I checked again and what I am using is this:

https://pypi.org/project/mpy-cross-multi/

And the command is:

mpy-cross-multi --micropython 1.23 myprog.py

[krismc]

This generates a .mpy of the right size (~10k) but the files crashes with a memory allocation error when I try to import it on my V1.23 esp32s2.

>>> import testv123
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
MemoryError: memory allocation failed, allocating 1762562304 bytes

In the words of a long dead Australian prime minister, "Life wasn't meant to be easy".

[bixb922]

Do you have @Native or @viper directives? Have you tried mpy-cross with the -march switch? (I donde have a esp32s2 to test)

[krismc]

None of those. I've found

mpy-cross-multi --micropython 1.23 code.py

will generate .MPYs that run on my V1.23 esp32 if code.py is small (20 lines) anything longer & I either get a memory allocation error or the repl just hangs. The longer 200 line code.py converts to a usable .mpy that runs on a V1.24 esp32 if I use regular mpy-cross. Looks like I might have to settle for that. It's just that I did all my testing with v1.23 & now I'm gonna have to do it all again to make sure the code is stable in v1.24

[Josverl]

I have run into problems with mpy-cross v1.24.0 and large source files as well, but do not have a clear repro at this time.

[krismc]

I've got the opposite problem. I can convert a 200+ line program to a v1.24 .mpy with

mpy_cross>mpy-cross -v code.py 

but can't find anything that will produce a viable v1.23 .mpy from the same program. What ever happened to the notion of backwards compatibility?