-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Long Live Heap feature is worth mentioning in Differences from MicroPython #3825
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Somebody please add a Documentation label to this - thanks! |
@kbanks-krobotics Want to make a PR with the addition? |
Insufficient time this evening, but something LIKE: |
@kbanks-krobotics how are you hitting this? Are you adding a native module? |
Yes, I was porting over some features from a customized build of MicroPython (on STM32) to CircuitPython (on ESP32S2). At the end of the project I will try to do a documentation PR with what I've learned (so far the "fancier heap" is the only architectural level difference I have noticed). |
Ok, no problem! Please don't advertise it as CircuitPython until the changes are upstreamed. This only matters when a native module holds onto a pointer usually. The Python references will be updated internally. (We only move at the end of an import before multiple copies can be made.) |
@kbanks-krobotics Are you still able to PR this? I'm doing some documentation things and am happy to PR what you wrote if not! |
Rendered moot by #8281, which removed long-lived allocations. |
The use of both a long and short lifetime heap is different from MicroPython and probably worth mentioning in your docs, for example at
https://circuitpython.readthedocs.io/en/6.0.x/README.html#differences-from-micropython
Things that don't move around in MicroPython between compile-time and execution-time can move around in CircuitPython.
FWIW
The text was updated successfully, but these errors were encountered: