Page 1 of 1
[RESOLVED] No more VS Code autocompletion when creating a WAPT package
Published: June 18, 2026 - 4:40 PM
by stan
Hello,
I've recently encountered a problem with VS Code when creating my WAPT packages.
When I generate a package template and the folder opens in VS Code, I lose autocompletion. I can't get suggestions for native functions (like print) or setuphelpers.
However, if I open a blank folder, everything works normally.
If anyone can shed some light on this, I'd be very grateful!
Thanks in advance.
Re: No more VS Code autocompletion when creating a WAPT package
Published: June 18, 2026 - 6:03 PM
by dcardon
Hi Stan,
what version of Wapt are you using, etc.?
Could you try deleting/renaming the vscode directory in your AppData folder? That often solves the problem. Personally, I don't use vscode; I'm more of an old-school developer with PyScripter3.
Regards,
Denis
Re: No more VS Code autocompletion when creating a WAPT package
Published: June 19, 2026 - 09:24
by stan
Good morning,
Here is the information:
Code: Select all
WAPT Enterprise version 2.6.1.17813
OS Server : Debian 12
OS de la machine d'administration : Windows 11 25H2.
Yes, I've already done that and nothing changes.
For PyScripter3, it's really the last resort if I can't solve the problem with VSCode
Sincerely,
Stan
[SOLVED] Re: No more VS Code autocompletion when creating a WAPT package
Published: June 23, 2026 - 4:03 PM
by stan
After downgrading VSCode to version
1.116.0, autocompletion works.
This issue is therefore resolved.
Re: [SOLVED] No more VS Code autocompletion when creating a WAPT package
Published: June 24, 2026 - 11:39
by italbot
Hello,
Noted. After installing version 1.125.0 of VS Code, I still have autocompletion. The problem might be with an extension rather than VS Code itself.
Sincerely,
Ingrid
Re: [SOLVED] No more VS Code autocompletion when creating a WAPT package
Published: June 24, 2026 - 11:41
by stan
Hello,
I removed everything, I only added the Python extension, the same for 1.116.0 and 1.125.0. And only 1.116 works with autocompletion.
Re: [SOLVED] No more VS Code autocompletion when creating a WAPT package
Published: June 25, 2026 - 6:01 PM
by dcardon
Hi Stan,
was this related to
viewtopic.php?t=4715 ?
Does it now work correctly with the latest version of VS Code?
Regards,
Denis
Re: [SOLVED] No more VS Code autocompletion when creating a WAPT package
Published: June 25, 2026 - 6:33 PM
by stan
Hello,
I don't think so, I'll try updating VScode tomorrow to see if that changes anything.
Re: [SOLVED] No more VS Code autocompletion when creating a WAPT package
Published: June 26, 2026 - 12:06
by stan
Good morning,
I found the solution. The problem comes from a setting in VS Code, and not from the interpreter or "debugpy".
In the latest versions of VS Code, if GitHub Copilot is enabled, I believe VS Code applies this behavior by default:
JSON
Code: Select all
"editor.quickSuggestions": {
"other": "offWhenInlineCompletions"
}
This setting disables the standard autocomplete list (Pylance) in favor of Copilot's online suggestions. This is why WAPT functions no longer appear.
To resolve this conflict, you need to force the display of suggestions. I propose adding this default configuration to the settings.json file generated by WAPT:
JSON
Code: Select all
"editor.quickSuggestions": {
"other": "on"
}
Here's a short video showing how it works (in the video I use `true` when it should be "on", I think it's already "on" by default, so that's why it worked):
https://youtu.be/I572GGS2ufE