Package Manager
Wing Pro's Packages tool, available in the Tools menu, provides integrated Python package management with pip, pipenv, or conda.
Configuration
Wing expects any requirements.txt package configuration file (or Pipfile and Pipfile.lock when using pipenv) to be in the same directory as the Wing project file or the directory configured with Project Home Directory under the Options tab in Project Properties. Using a requirements.txt with pip and conda is optional, but when present Wing can keep the file updated to reflect the packages that have been installed, removed, or updated.
To set up package management, you need to first create a Wing project, configure the Python Executable either from the New Project dialog or the Environment tab in Project Properties, and then save the project to disk.
Regardless of which package manager you plan to use, Wing assumes that pip is already present in your selected Python installation. In the rare cases that it is not, you must install it manually, using getpip.py or other solution.
Once you save your project, Wing tries to auto-detect the package manager. It will select pipenv if Pipfile is present, conda if the selected Python Executable is found to belong to a found Anaconda environment, and pip in other cases.
Setting up pipenv
If you plan to use pipenv but it is not already set up, you can do so from the Options menu in the Packages tool, by first selecting Use pipenv and then Initialize for pipenv. This installs pipenv into the Python you selected with Python Executable in Wing and then initializes the package manager directory to use pipenv, which sets up a virtualenv and the initial pipenv configuration.
Since this creates Pyfile and Pyfile.lock, you will want to make sure that you first save your Wing project in the directory you want to use as your pipenv project directory, or set Project Home Directory under the Options tab in Project Properties.
Setting up conda
Wing can only use conda if your Anaconda base installation can be found. See Package Management with conda for details.
Packages List
Once the package manager is configured, the Packages tool shows the current status and list of installed packages.
The status area at the top of the tool indicates the type of Python installation (whether local or remote, and regular install or virtualenv), the package manager that is in use, and the package configuration file that is being managed.
The packages tree below this is populated with the packages that are currently installed. This list indicates which packages are in use, either by the requirements.txt or Pipfile or by another installed and in-use package. The version of the package currently installed and the users of each package are listed at the end of each line.
Package management operations are available in the right-click context menu on the packages list, and in the Options menu in the top right of the Packages tool. These are described in detail in the next section.
Working with Containers and Clusters
When working with containers or clusters, the Packages tool displays the packages installed on your container and cluster but it does not offer any operations for installing, removing, or updating packages. In this case, the container or cluster configuration must be edited manually and then rebuilt from the Containers tool.
Section Contents
4.1. Package Manager Options
4.2. Package Management with pipenv
4.3. Package Management with conda
4.4. Package Management Security
