-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
[Bug] Import does not work in V3.2 release for some scripts #873
Comments
Any errors in the browser console? Does it work with pybricksdev? |
No errors in console. Pybricksdev test is scheduled for Friday. |
Apparently errors for this are only enabled in development builds. I get this error in the console:
I guess the parsing library we are using has a problem with async syntax? |
This makes it easier for users to diagnose errors. Issue: pybricks/support#873
The package we were using was only for Python 3.4 and didn't include async/await which broke imports in any script that used async/await. Fixes: pybricks/support#873
This makes it easier for users to diagnose errors. Issue: pybricks/support#873
The package we were using was only for Python 3.4 and didn't include async/await which broke imports in any script that used async/await. Fixes: pybricks/support#873
This makes it easier for users to diagnose errors. Issue: pybricks/support#873
It turns out the parser library we are using in Pybricks Code was developed against Python 3.4, so any newer Python features supported by MicroPython need to be added. |
Describe the bug
Importing does not work in some cases. I found a reproducible case that appears to hinge on
async
appearing somewhere in the code, even if it isn't used.The following reproduces it always in Pybricks Code:
my_module.py
my_main.py
Running the latter gives
The text was updated successfully, but these errors were encountered: