I've archived this because there is a solution...
https://github.com/BradenM/micropy-cli/
This is all based on the good work by @Josver's MicroPython Stubber
This assumes you're using PyMakr Extentsion for VSCode.
- Save any data off your board. We're going to overwrite files.
- If your board does not connect. Edit the address in the pymakr.conf to match the IP, COM, or Serial connection you normally use in development.
- Upload this repo to your PyCom Board.
- In the REPL
import createstubs
. This will generate the files needed into a '/stubs/BOARD_VERSION folder. - When this completes Download the files from your board back into your repo.
Your new STUBS will now be in the /stubs folder.
In each of your Project Workspaces where you're writing code for you Pycom boards, you need to create a .vscode/settings.json file which has at least these settings.
{
"python.linting.enabled": true,
"python.linting.pylintEnabled": true,
"python.autoComplete.extraPaths": [
"./lib/",
"/YOUR_PATH_TO_REPO_FILES/pycom_stubs/stubs/GPy_v1_11",
"YOUR NEW STUBS GO HERE",
],
"python.autoComplete.typeshedPaths": [
"/YOUR_PATH_TO_REPO_FILES/pycom_stubs/stubs/GPy_v1_11",
"YOUR NEW STUBS GO HERE",
],
"python.analysis.typeshedPaths": [
"/YOUR_PATH_TO_REPO_FILES/pycom_stubs/stubs/GPy_v1_11",
"YOUR NEW STUBS GO HERE",
]
}
- Generate your stubs and download them into your branch.
- Update the README.MD so it includes your newly generated stubs in each section. Just like the GPy_v1_11 version.
- Submit a PR! :-)