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
A packages installed with pip install --user -e is then not resolved from python when importing it in a python script. I reported this issue first in jupyterlab/jupyterlab#13867 (comment) but it seems related to the installation process itself.
Expected behavior
I would expect the editable installation from my user directory to have priority on any other
The numexpr project dynamically generates the version file on build with a custom script in seutp.py. pip does not intefere with the code, and you need to discuss with the said project why the mechanism does not work as you expect.
numexpr was a dummy example, the initial problem was coming from a lib I created myself. Using a more robust lib (like numexpr) was a way to avoid the "you made a mistake in your config issue".
Thanks to another thread (microsoft/pylance-release#78) I finally understand the issue: setuptools recently added support for PEP660 which seems unsupported by my environment.
running pip install -e . --config-settings editable_mode=compat as suggested in setuptool documentation solved it.
Description
A packages installed with pip install --user -e is then not resolved from python when importing it in a python script. I reported this issue first in jupyterlab/jupyterlab#13867 (comment) but it seems related to the installation process itself.
Expected behavior
I would expect the editable installation from my user directory to have priority on any other
pip version
22.3.1
Python version
3.8.1
OS
Ubuntu focal
How to Reproduce
from my terminal I run:
In my local folder, I find the following:
Now from a python interface, I execute the following commands:
which give me 2.7.1 which is not version I installed in editable mode.
But from the terminal, it returns the correct version.
Output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: