Page 1 of 1

VSCode instead of PyScripter

Published: July 4, 2022 - 4:47 PM
by tuxmania
Hello,

is it possible to configure VSCode to perform package tests as is currently possible with Pyscripter?
Thank you in advance.

Re: VSCode instead of PyScripter

Published: July 5, 2022 - 10:25 PM
by sfonteneau
Hello,

if you specified the editor in the wapt vscode console and you edit a package, then the run configuration should be available.

Re: VSCode instead of PyScripter

Published: July 8, 2022 - 7:03 PM
by tuxmania
Hello @sfontenau,

thank you for your reply.
After making the change, VS Code does open when I edit a package from the WAPT console.
However, I have the contents of setup.py, but I don't see how to test the install() function, for example.
Would you be so kind as to explain how to set up the package testing configuration in VS Code? Despite the information in the WAPT documentation (links below), I can only open setup.py and not the entire project.

https://www.wapt.fr/en/doc-2.2/wapt-cre ... -arguments
https://www.wapt.fr/en/doc-2.2/wapt-cre ... on-windows

Thank you in advance.

Re: VSCode instead of PyScripter

Published: July 11, 2022 - 7:14 PM
by dcardon
When you create an empty template (wapt-get make-template tis-mysoftware), it will create the skeleton with a .vscode folder. The .vscode folder contains the launch.json and settings.json files with the definitions for install, remove, update_package, etc.

You must also install the Python extensions (tis-vscode-python package).

Regards,

Denis