Pre-Compiled files using more memory?

Questions and discussion about The WiPy board.
You can buy one at the store.
Target audience: Users with a WiPy.
danielm
Posts: 129
Joined: Mon Oct 05, 2015 12:24 pm

Re: Pre-Compiled files using more memory?

Postby danielm » Thu Oct 06, 2016 6:47 am

This is the best resource I could find:
http://hinch.me.uk/html/reference/constrained.html

Found link in this topic:
viewtopic.php?f=3&t=2396

formatc1702
Posts: 4
Joined: Fri Mar 10, 2017 3:17 pm

Re: Pre-Compiled files using more memory?

Postby formatc1702 » Fri Mar 10, 2017 4:11 pm

Hi,

I realize this thread is older, but it's related to my question so I shall add it here.

Using mpy-cross yields .mpy files that are larger than their respective .py files!

My main.py is so long it can only be imported by commenting out some lines (that are not even called by the code unless specific conditions happen). So I'm guessing it's just too large for the compiler. I tried using mpy-cross, but I ended up with 10KB instead of 9KB! :-(

Am I missing the point? Am I doing something wrong?
Placing my main.py file in the mpy-cross folder and running
./mpy-cross main.py
yields the above result. Any parameters I have to set?

Renaming main.mpy to something.mpy and importing it from the REPL gives me:
ValueError: invalid .mpy file

Interestingly, out of 8 .py files I tried, exactly one of them compiled into a useable .mpy file. :shock:

Platform: ESP8266
MicroPython 1.8.7


Return to “The WiPy”

Who is online

Users browsing this forum: No registered users and 1 guest