Other micropython modules such as asyncio under newer pybricks-micropython 3.x #2025
-
Good morning, I am experimenting running the newer 3.x pybricks on EV3, following information from #1034 by using
This installs version ('ev3', '3.3.0b6', 'v1.20.0 on 2023-06-02')) Also, used information from https://github.com/orgs/pybricks/discussions/1653#discussioncomment-9639103 and downloaded the latest build on Jan 01 2025: ('ev3', '3.6.0b2', 'v1.20.0-25-g9305b73d7 on 2025-01-01') from https://github.com/pybricks/pybricks-micropython/actions/runs/12573263376 (not all builds include the pybricks-micropython for ev3, this one is the most recent I can find, newer builds only have specific supported hub such as spikeprime, not sure the reason) However, I noticed that some of the standard micropython modules, for example, if I have code in the file like:
I will get
Is that part of effort to speed up the boot without all ev3dev, meaning going forward, in the v3.x/4.x of pybricks the usage of modules outside of pybricks will be restricted? Or just a temporary situation? Is there a solution to make those accessible in v3? Thank you for all the great work! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
We are planning to update EV3 for Pybricks V4.0. This will run without Linux, so this is going to be a bit different from the ev3dev-based release that you have tried. Pybricks 2.0 will continue to exist for those who wish to continue using Pybricks with ev3dev. The new version will support async functions and multitasking just like on Pybricks for SPIKE Prime. What other modules would you like to see enabled? |
Beta Was this translation helpful? Give feedback.
For those kind of applications, Pybricks 2.0 with ev3dev will probably remain the best option 🙂