General chat, help, discussion and ideas about the Mu code editor. Don't be afraid to ask a question. We're friendly! Please follow the Code of Conduct (https://www.python.org/psf/codeofconduct/)
Oh hey, I can at least confirm that gitter-badger (The Gitter Badger) is working properly now
Hi, I'm going to submit a PR to fix a typo on the Developer Setup page (Addionionally in the Windows Note). Before I do, it lists using Python 3.5 or higher - should I update that to 3.6 as 3.5 reached EOL in 2020?
And sorry for the PRs each with a small fix, I don't know how you prefer them, I just submitted them as I was reading the docs
@jevers76: I appreciate this is somewhat after the event, but we've just noticed that people using the Windows Store version of Python are seeing the same symptom: Mu fails to start but there are no logs. We have a patch for it waiting in the wings. Is it possible that this is your situation?
So I have recently encountered an issue when trying to run code using the RUN button on an ESP32. MU keeps telling me there is a syntax error that doesn't exist. However, it runs fine if I send the code to the REPL through copy and paste or right-clicking a block. Could this be a timing issue or something similar?
There are two imports in the try/except block, sometimes its one or the other.
Hello. I am trying to get mu working on my Mac. I have installed it OK but, the software cannot find my python install which, was installed as part of Anaconda. How do I change the config so that MU uses the actual path to the Python interpreter?. I suspect its just a simple edit of a config file...
@Ambercam So you have two choices, one is to put your code in the path that MU uses (I personally don't like this method). And two is to setup a VE for you project outside of MU and just point MU to the files in that path. MU just becomes your editor of choice.
On a M1 MacBook Air 2021
searched for a while now
You could also raise a feature suggestion for making it easy to change font to something installed on the system.
I noticed one of the recommended editors on the Mu site (https://codewith.mu/en/tutorials/1.1/moving-on) is Atom. It's going to sunset in December 2022: https://github.blog/2022-06-08-sunsetting-atom/, so I wanted to flag that in case it should be removed from the list.
I just submitted a PR to add a tutorial for rp2040 mode. I notice in rp2040 mode the "Files" button is grayed out on a Pico, but if I use ESP Micropython mode, the Files button works. Is it supposed to be unavailable in rp2040 mode and should it be documented?
Nevermind, I realized it's grayed out when the REPL is open, sorry!
Does anyone else have the issue where upon changing the theme, the helper text window in REPL is unreadable?
Using the Night or Contrast theme, when I type "print" into the REPL pane, the text box that pops out with additional information regarding "print" is white on white text which makes it unreadable
@BingusLover19_twitter: Ok, do you have the Feather plugged into the USB drive?
It should show up as a CIRCUITPY drive
Open the code.py file on the CIRCUITPY drive in Mu, I think by pressing Load
Then press the Serial button in Mu, and you can see the code running or enter the REPL. You may have to click it to get focus and then ctrl-c and ctrl-d will re-run your code
pyinputplus*
I left some comments on some documentation related issues, mostly in the website repo. I'm happy to submit some PRs to help with some of those. If anyone has any feedback on wording or phrasing in those issues, please leave a comment.
(I.e. if nobody comments, it's not because we're ignoring you, it's probably because we're snowed under with "real job" things)
@ntoll: I've been around open source long enough to remember. :) No hurry, just thought I'd share. Happy to help.