Attention : support for WAPT 1.8.2 ended on June the 30th 2022.

There are known vulnerabilities in WAPT dependencies in WAPT 1.8.2 branch. Please upgrade to the latest supported version. CVE listing (non exhaustive) :

* python engine : python 2.7 (CVE-2020-10735, CVE-2015-20107, CVE-2022-0391, CVE-2021-23336, CVE-2021-3177, CVE-2020-27619, CVE-2020-26116, CVE-2019-20907, CVE-2020-8492, etc.)
* cryptography : openssl : CVE-2022-2068, CVE-2022-1292, CVE-2022-0778, CVE-2021-4160, CVE-2021-3712, CVE-2021-23841, CVE-2021-23840, CVE-2021-23839, CVE-2020-1971, CVE-2020-1968, CVE-2019-1551
* python dependencies : cryptography (CVE-2020-36242, CVE-2020-25659), eventlet (CVE-2021-21419), jinja2 (CVE-2020-28493), psutil (CVE-2019-18874), waitress (CVE-2022-31015), lxml (CVE-2021-4381, CVE-2021-28957, CVE-2020-27783, CVE-2018-19787), ujson (CVE-2022-31117, CVE-2022-31116, CVE-2021-45958), python-ldap (CVE-2021-46823)

Using another IDE for WAPT¶

Introduction¶

If you are used to work with another IDE, you can be relieved now as WAPT supports other editors.

Some code editors are natively supported:

PyScripter;
VSCode;
VSCodium;

Other editors can be selected and will be launched when you create a new template for a WAPT package from WAPT Console.

Configuring WAPT to use another IDE¶

Note

Using a supported IDE will launch the WAPT package project with a valid debug configuration.

Using Microsoft Windows¶

To configure another editor for WAPT, you must modify the editor_for_packages attribute in the [global] section of your WAPT console’s %LOCALAPPDATA%\waptconsole\waptconsole.ini configuration file.

Possible values are:

Editor name	editor_for_packages value
PyScripter	None
Microsoft Visual Studio Code	vscode or code
Microsoft Visual Studio Codium	vscodium or codium

Example config in waptconsole.ini:

[global]
...
editor_for_packages=vscode

Using Linux / macOS¶

To configure another editor for WAPT, you must modify the editor_for_packages attribute in the [global] section of your WAPT agent configuration file: /opt/wapt/wapt-get.ini.

By default, if the editor_for_packages attribute is empty, WAPT will try to launch (in that order):

vscodium;
vscode;
nano;
vim;
vi;

Possible values are:

Editor name	editor_for_packages value
Microsoft Visual Studio Code	vscode or code
Microsoft Visual Studio Codium	vscodium or codium
Nano	nano
Vim	vim
Vi	vi

[global]
...
editor_for_packages=vim

Configuring WAPT to use a custom editor¶

Using Microsoft Windows¶

Custom editors can be used, for example Notepad++ or PyCharm.

Custom editors example:

Editor name	editor_for_packages value
Notepad++	`C:\Program Files\Notepad++\notepad++.exe setup_filename`
PyCharm	`C:\Program Files\JetBrains\PyCharm Community Edition 2019.3.2\bin\pycharm64.exe wapt_sources_dir`

[global]
...
editor_for_packages=C:\Program Files\Notepad++\notepad++.exe {setup_filename}

Using Linux/Apple macOS¶

Custom editors can be used, for example PyCharm.

Custom editors example:

Editor name	editor_for_packages value
PyCharm	`/opt/pycharm/bin/pycharm_x64 wapt_sources_dir`

[global]
...
editor_for_packages=/opt/pycharm/bin/pycharm_x64 {wapt_sources_dir}

Custom arguments¶

Arguments can be passed in the editor_for_packages command:

Argument	Description
`{setup_filename}`	Launches custom editor and edit WAPT package setup.py file
`{control_filename}`	Launches custom editor and edit WAPT package control file
`{wapt_sources_dir}`	Launches custom editor and opens WAPT package folder
`{wapt_base_dir}`	Launches custom editor and opens WAPT install folder