-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Python Mode won't run sketches in 4.0b6 #409
Comments
Created by: benfry Nuts; ok… that's due to detaching sketch name and the name of the first tab. Didn't realize Python Mode was using that method. |
Created by: benfry Added a fix for beta 7; in the meantime you can also just build from the source. |
Created by: Rauschii
Hi, i know it is unusual to ask here but I cannot contact you otherwise. |
Created by: benfry I'd like to get something out as soon as possible (today? this week?) but it's just a matter of when I can get some spare time to make it happen. Beta 5 should also work fine (still on the GitHub releases page) in case that's an option for you. |
Created by: tabreturn https://github.com/processing/processing4/releases/tag/processing-1280-4.0b5 |
Created by: Rauschii Thank you both!!! @benfry and @tabreturn |
Created by: benfry Beta 7, which has the fixes, has been up for 3 weeks: https://github.com/processing/processing4/releases If there are problems with beta 7, I've not seen any reports yet. |
Created by: github-actions[bot] This issue has been automatically locked. To avoid confusion with reports that have already been resolved, closed issues are automatically locked 30 days after the last comment. Please open a new issue for related bugs. |
Created by: tabreturn
Description
Python Mode worked in 4.0b5, but won't run sketches in 4.0b6
Expected Behavior
Python Mode Sketches won't run. Instead I get this error in the console (truncated here) --
Steps to Reproduce
Your Environment
Possible Causes / Solutions
Note sure of the cause. For now, Processing Python Mode users could use 4.0b5 or 3.5.4
The text was updated successfully, but these errors were encountered: