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
However, the packages I am currently working on are not included within the exported venv which I create by calling:
pants export --resolve=python-default
As such, I am currently activating the venv, and then manually installing each of my packages within my monorepo with the pip install -e approach.
Ideally, we could export a standard .venv for use with IDEs and Jupyter that is simple, standard, and includes each of our packages installed via -e with pip.
The text was updated successfully, but these errors were encountered:
I think this might be (partly?) fixed by #18639, for python_distribution targets, via a [export].py_editables_in_resolves option. Could you confirm, @cognifloyd?
Yes. This request is explicitly for "development packages", which is represented in pants via python_distribution BUILD targets. So, yes, #18639 resolves this issue. That feature should be released with pants 2.17 😁
I am trying to use the .venv created by pants as a Jupyter Kernel by running:
And then using that kernel within Jupyter Lab.
However, the packages I am currently working on are not included within the exported venv which I create by calling:
As such, I am currently activating the venv, and then manually installing each of my packages within my monorepo with the
pip install -e
approach.Ideally, we could export a standard .venv for use with IDEs and Jupyter that is simple, standard, and includes each of our packages installed via -e with pip.
The text was updated successfully, but these errors were encountered: