2. Using different IDEs for developing WAPT packages

2.1. Configuring WAPT to use supported IDEs

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

Note

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

2.1.1. On Windows

Natively supported text editors in WAPT on Windows

Text editor name	Text editor logo
PyScripter
Visual Studio Code
Visual Studio Codium

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.

[global]
...
editor_for_packages = vscode

2.1.2. On Linux / macOS

Natively supported text editors in WAPT on Windows

Text editor name	Text editor logo
Visual Studio Code
Visual Studio Codium
Nano
Vim

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.

[global]
...
editor_for_packages = vim

2.2. Configuring WAPT to use a custom editor

WindowsLinux/ macOS

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

2.2.1. Custom arguments

Arguments for the editor_for_packages option

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 the custom text editor and opens the WAPT package folder.
{wapt_base_dir}	Launches the custom text editor and opens the WAPT install folder.