Thanks for it. And a couple of suggestions.

[mogplus88]

Hi Lukas,

Thanks so much for bringing micropython into Pycharm. Apart from Thonny it's really the only seriously usable micropython IDE imho. And I've tried a lot of them.

I'm using it to develop (well, experiment really) with ESP32, Pi Pico, and Black Pill (STM324) and it works really well on all of them. One slight wrinkle with the Pico, and a couple of things I'd like to see which I'm sure you are already working on!

With the Pico, I've found that, if the script uses the PIO functionality, the Pycharm editor flags all the PIO statements as errors, but the program runs happily and produces the output I'm expecting. So everything works, I just have to ignore all the red underlines in the PIO function.

One other thing I would like to be able to do is run a script in isolation, like Thonny does. Several times I have introduced a hard loop bug into my code, which, if it's not in main.py, (and using Thonny) just means resetting the device and fixing the bug. But if it's in main, or called by main, as soon as the device is plugged in, the hard loop executes and it's impossible to interrupt. This has happened to me a couple of times while using Pycharm, and I've had to use flash_nuke.uf2 to get my device back.

Cheers, Ian

[lukaskremla]

Hey,

Thanks for the feedback, glad the plugin is working for you!

I've quickly looked over the stub packages that are currently available through the plugin and I did see mentions of PIO in them. Do you have an active stub package in the settings? If so, could you please tell me the name of it? I have some pico boards that I could try this with. If there's something missing from the stubs then I'll look into what can be done about adding it to them.

And regarding the run functionality you described. The plugin already has a feature that allows you to execute .py and .mpy files in REPL, meaning their code runs without the files actually being uploaded to the device and essentially bricking it until you reflash it.

You can access it by right clicking on .py or .mpy files in the project file tree, it's at the bottom of the context menu that pops up. Please let me know if this feature solves your problem.

[mogplus88]

Hi Lukas,
This is the stubs file I'm using for my pico2 is micropython-v1_24_1-rp2-rpi_pico2-stubs, and for my bog standard pico, micropython-v1_24_1-rp2-rpi_pico-stubs. They both do the same thing.
And thanks for the pointer to the "run this file" option. Exactly what I was looking for!! Now if there was just some way to add it to the run function in the top bar...
;-) Ian

[lukaskremla]

That's a good idea, the run in REPL option should be available through run configurations as well. I'll add this in the next major release.

[lukaskremla]

Hello @mogplus88,

This discussion has been open for quite some time now. Your execute in REPL feature suggestions have been implemented, thanks for bringing them up!

You've mentioned some issues with PIO not being recognized even after correctly configuring the stubs. The plugin retrieves the stub packages differently now - directly from pip. Meaning that they should be more accurate.

I'll be closing this discussion, but if you have any other suggestions or if the issue with PIO persists do feel free to start a new one or to open an issue.