-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Bundle command #1992
Copy link
Copy link
Closed
Labels
area/cliRelated to the command lineRelated to the command linearea/plugin-apiRelated to plugins/plugin APIRelated to plugins/plugin APIarea/venvRelated to virtualenv managementRelated to virtualenv managementkind/featureFeature requests/implementationsFeature requests/implementations
Metadata
Metadata
Assignees
Labels
area/cliRelated to the command lineRelated to the command linearea/plugin-apiRelated to plugins/plugin APIRelated to plugins/plugin APIarea/venvRelated to virtualenv managementRelated to virtualenv managementkind/featureFeature requests/implementationsFeature requests/implementations
As suggested in #537, the addition of a
bundlecommand could prove useful.There are two cases that we've seen pop up here: the ability to bundle the project and its dependencies in an arbitrary virtual environment and the ability to download the distributions to a specific directory. The former should be implemented directly into Poetry since generating a complete virtual environment makes sense to deploy a Poetry-managed project and the latter could be implemented in a plugin since it's a less common case.
Implementation
Basically the
bundlecommand will be a top-level command (similar toenv) which will expose various sub commands.Initially, only the
venvsub command will be available:If the virtual environment directory already exists it will be removed and regenerated.
Specifying a Python version to use to generate the virtual environment will also be possible:
Extensibility
The
bundlecommand should be extensible so that new sub commands can be added with the use of plugins. This means that this feature depends on the implementation of the plugin system (which is in progress, see #1237)