Autocompletion issues when using VSCode Workspaces

[Alain-Godo]

First of all, I have to congratulate you for this beautiful project !!!. I followed every step in the guide, and all works fine...but when the project is created and I try to write my code, Pylance still does not detect the modules. Why?

[BradenM]

Hi @Alain-Godo, thanks for the report.

Will some information before I can provide any help, though.

Would you mind sharing your micropy --version, micropy.json file and ~/.micropy/micropy.log files, please? Thanks.

[BradenM]

Thanks.

Although I have no reason to believe the esp32-micropython-1.15.0 stubs shouldn't work -- I would recommend trying to use a package from the newer micropython-stubs repository:
micropy stubs add micropython-esp32-stubs to add latest version (see micropy stubs search --show-outdated esp32 for older versions you can specify in micropy.json). These stubs are much more up to date and provide richer autocompletion and docstrings.

Since I still haven't gotten around to implementing a simple stubs remove command 😬 -- you can remove the stubs you are currently using by removing the entry from micropy.json and recreating the .micropy folder (rm -rf .micropy && micropy)

Please let me know if this works for you, as it may indicate a bug in how micropy handles the older stub packages if so. Thanks.

[Alain-Godo]

I tried all from the being...and I selected the new two stubs (because I don't know what is the right one ), see the micropy.json...I don't know what is wrong : (... Sorry if my English is not the best....Thanks

[BradenM]

@Alain-Godo Selecting both is correct. 🤔

Would you mind sharing your .vscode/settings.json file?
Also, which version of python are you using here?

[Alain-Godo]

Sure!!
Version of Python: 3.11.2 - 64 bits

.vscode/settings.json:

{
//Loaded Stubs: micropython-esp32-stubs micropython-stdlib-stubs

"python.languageServer": "Pylance",
"python.analysis.autoSearchPath": true,
"python.autoComplete.extraPaths": [".micropy\\micropython_esp32_stubs-1.19.1.post12", ".micropy\\micropython-stdlib-stubs-0.9.0", ".micropy\\TinySorbaTest"],



"python.linting.enabled": true,
"python.linting.pylintEnabled": true

}

[BradenM]

@Alain-Godo Thanks for the info. I've done some digging, and it seems the configurations micropy generates are now outdated as of more recent vscode/pylance versions. I am working on a fix now. See: #474
Thanks for bringing this to my attention.

[BradenM]

@Alain-Godo I believe this should be resolved now as of the v4.2.1 version that I've just released.
Thanks again for bringing this to my attention!
Please let me know if this isn't the case.

[Alain-Godo]

Wait I see something.... Look

[BradenM]

@Alain-Godo The first image can be ignored. It's a reference to an older setting and just there for compatibility with older versions (probably can be removed in near future.).

The second image is interesting and definitely seems problematic.
Can you try opening the project directly as it suggests? I.e, by running code . from the directory of your project?

[Alain-Godo]

It works!!!!!!!!! : ) But what happened??

[BradenM]

Interesting. So the issue looks to be something to do with vscode workspaces (which is for working on multiple projects in the same window). I will have to investigate this, but from your images it looks like pylance just isn't loaded in workspaces and you need to open the project directly (which is what code . did for you) instead. I will have to read into why this is.

[Alain-Godo]

I hope it can be solved, now it's working great!!! It is really a super necessary project that you do, I congratulate you. Thanks for all !!!!

[Alain-Godo]

One last question !!! How can I use the pymakr.conf to upload the code to my device? I read this post, but it's not clear enough: https://lemariva.com/blog/2019/08/micropython-vsc-ide-intellisense

[BradenM]

@Alain-Godo Glad to hear you've got a working setup now.

As for pymakr, it's been quite a while since I have used it, but I do know that micropy currently generates a config for the older v1 version (see: #312).

As mentioned in #312, pymakr seems to be more or less discontinued and in the near future I am working on implementing this functionality in micropy itself.

But for now, I would look through that issue and hopefully, you will find what you need. Thanks.