[SOLVED] No module named 'requests'

Questions about WAPT Packaging / Requests and help regarding Wapt packages.
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Locked
stan
Messages: 37
Registration: May 26, 2025 - 10:16 p.m.

June 25, 2026 - 11:13

Good morning,

For at least an hour, I haven't been able to use the WAPT debug functions on VSCode due to an error no module named 'requests' " :
wJ1Tq6j.png
wJ1Tq6j.png (90.71 KB) Viewed 1772 times
I haven't touched anything regarding the Python modules and normally these should be installed automatically.

Thank you in advance for your clarifications :D

Sincerely,

Stan

-

Code: Select all

OS Administration : Windows 11 25H2
OS Server : Debian 12
WAPT Version : 2.6.1.17813
VSCode Version : 1.116.0
Last edited by stan on June 25, 2026 - 2:05 PM, edited 1 time.
stan
Messages: 37
Registration: May 26, 2025 - 10:16 p.m.

June 25, 2026 - 2:05 PM

The problem was resolved in a rather unexpected way.

Simply change the type in launch.json to "debugpy", as apparently the "python" type will become obsolete:
gLYb7Yp.png
gLYb7Yp.png (19.58 KB) Viewed 1771 times
And to restart VS Code.
Sincerely,

Stan

-

Information:

Code: Select all

OS Administration : Windows 11 25H2
OS Server : Debian 12
WAPT Version : 2.6.1.17813
VSCode Version : 1.116.0
User avatar
dcardon
WAPT Expert
Messages: 1978
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

June 25, 2026 - 5:38 PM

Hi Stan,

thanks for the feedback and the link to the documentation. We'll run some internal tests to make sure it doesn't cause any other problems (the wapt Python loader is being rewritten to better control environment variables).

Best regards,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
stan
Messages: 37
Registration: May 26, 2025 - 10:16 p.m.

June 25, 2026 - 6:31 PM

Hello,

No problem with the update, however, I don't think it's related to that after all. :lol:

It's more likely that I didn't have the correct Python interpreter selected in VSCode.

I don't know why, though; the first time, just changing that and reloading VSCode fixed it, I hadn't noticed the interpreter issue yet.
Sincerely,

Stan

-

Information:

Code: Select all

OS Administration : Windows 11 25H2
OS Server : Debian 12
WAPT Version : 2.6.1.17813
VSCode Version : 1.116.0
Locked