When developing a workbench that needs a Python dependency specified in the workbench manifest it is not possible to install plugins that are not already added to the ALLOWED_PYTHON_PACKAGES.txt file. This makes local development of a plugin that needs to pull a dependency difficult as this check cannot be skipped.
A solution to this issue could be to allow installing python packages not included in the ALLOWED_PYTHON_PACKAGES.txt file when development mode is enabled. Checking the Addon Manager code it looks like adding a check in the AddonManager._update_allowed_packages_list method to skip this check would be enough.
Is there an existing issue for this?
Problem description
When developing a workbench that needs a Python dependency specified in the workbench manifest it is not possible to install plugins that are not already added to the
ALLOWED_PYTHON_PACKAGES.txt
file. This makes local development of a plugin that needs to pull a dependency difficult as this check cannot be skipped.A solution to this issue could be to allow installing python packages not included in the
ALLOWED_PYTHON_PACKAGES.txt
file when development mode is enabled. Checking the Addon Manager code it looks like adding a check in theAddonManager._update_allowed_packages_list
method to skip this check would be enough.Full version info
Subproject(s) affected?
None
Anything else?
No response
Code of Conduct