Skip to content
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

Feature Request: Accept alternative .hex runtime #220

Open
PropGit opened this issue Aug 16, 2019 · 1 comment
Open

Feature Request: Accept alternative .hex runtime #220

PropGit opened this issue Aug 16, 2019 · 1 comment

Comments

@PropGit
Copy link

PropGit commented Aug 16, 2019

Request that the Load/Save dialog accept custom .hex runtime (MicroPython interpreter runtime) that it uses for that project in-place of it's built-in runtime. This would be similar to functionality already in the Mu editor and would allow users to enjoy the same benefits.

This thought may be similar to subpostings in Issue #26

Suggestions:

  • the runtime appears in the Project files list (file system list) of the Load/Save dialog.
  • limit to 1 runtime per project (of course); new runtimes replace old runtime
  • .hex file loading properly parses out user .py, modules, and runtime, if provided .hex is an entire project (rather than just a MicroPython runtime).
@yanghao
Copy link

yanghao commented Feb 28, 2021

This makes a lot of things easier, for example, currently the default v2 in python.microbit.org (version 2.1.1) does not yet fix the time_pulse_us() problem, which would be highly beneficial if a different runtime can be selected. (see: microbit-foundation/micropython-microbit-v2#26).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants