You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, all the @nxlv/python executors (add, update, remove, build and flake8) just run poetry commands without any activation logic and let poetry decide which virtual environment to use.
However, when the workspace uses the shared virtual environment, to run all the commands the developer needs to manually activate the virtual environment.
With that being said, @nxlv/python should identify if a virtual environment is not activated and the workspace is configured to use a shared virtual environment, if yes and no virtual environment is activated, the @nxlv/python should be activated before running the poetry commands.
Changes all the `@nxlv/python` executors to first verify if the shared virtual environment is
available in the workspace, if yes, activate before running the commands, also adds a new
`@nxlv/python:run-commands` executors to wrap the `nx:run-commands` and activate the virtual
environment before running the commands, if you are using `@nxlv/python` version 16> you can use
this following command to migrate all your `nx:run-commands` to `@nxlv/python:run-commands`: `npx nx
migrate @nxlv/python`
re #132
)
* feat(nx-python): automatically activate shared virtual environment
Changes all the `@nxlv/python` executors to first verify if the shared virtual environment is
available in the workspace, if yes, activate before running the commands, also adds a new
`@nxlv/python:run-commands` executors to wrap the `nx:run-commands` and activate the virtual
environment before running the commands, if you are using `@nxlv/python` version 16> you can use
this following command to migrate all your `nx:run-commands` to `@nxlv/python:run-commands`: `npx nx
migrate @nxlv/python`
re #132
Description
Currently, all the
@nxlv/python
executors (add
,update
,remove
,build
andflake8
) just runpoetry
commands without any activation logic and let poetry decide which virtual environment to use.However, when the workspace uses the shared virtual environment, to run all the commands the developer needs to manually activate the virtual environment.
With that being said,
@nxlv/python
should identify if a virtual environment is not activated and the workspace is configured to use a shared virtual environment, if yes and no virtual environment is activated, the@nxlv/python
should be activated before running the poetry commands.Motivation
Result of this discussion: #128
The text was updated successfully, but these errors were encountered: