Can't see/edit my own External Libraries anymore

Hey Daniil,

Thanks for the link, it seems to be related to my problem, indeed. In my case, I'm installng it with pip from my own GitHub repo, but the end result is the same, I suppose it's also related to the way setuptools work. I do something like:

pip install -r my_required_packages_file

and inside the required packages file I have:

-e git+https://github.com/<my project>#egg=<my project name>

As to my environment, I use the separate virtualenv tool (not the native Python 3 venv).

For the record, in my case things still worked from the command line, so the problem is definitely just within PyCharm, not a general installation problem.

I found a different workaround: if I recreate the PyCharm project adding the PARENT folder as my “Django Project folder”, (e.g.: myvirtualenv/ instead of myvirtualenv/mydjangoproject/), then at least PyCharm stops complaining about my imports, and I can again click on a keyword and land within the library, debug, etc. The only thing that still doesn't work as before is having my libraries listed under “External Libraries”. But since I added the parent folder, I can now see them, browse them, open in PyCharm, etc.

I will try the workaround suggested by Adam Forster, that is, to install my libraries using:

pip install -e <project> --config-settings editable_mode=compat

Maybe that solves my problem too!

Thanks,
Rubens

Sure - I install Python with Homebrew, and https://pypi.org/project/virtualenv/ and https://pypi.org/project/virtualenvwrapper/ with pip, on the “Mac OS” level. Then I create my virtual envirnoments using virtualenv/virtualnvwrapper. As mentioned before, my own libraries I install with pip again (using -e to clone the source code), and THEN I setup PyCharm to work on all that.

That's how I've always done, for years. Recently I had to re-do it again, using the latest version of PyCharm, and what I wrote in my original post started to happen…

Hey Daniil,

Thanks for keeping trying! But still no success.

I removed all data from my previous project (.idea folder, etc.), and opened my Django project again, from within PyCharm. It set everything automatically correctly: Python interpreter, DB connection, etc. I can run the project from the PyCharm runner/debugger, all good.

But, again - my already-downloaded dependencies, which ARE being used by the Django project, appear in PyCharm with the “red snake underline” ("unresolved reference"), and sure enough, I cannot CMD-click on them to open the files in the editor ("cannot find declaration to go to").  So they “work”, but PyCharm doesn't acknowledge them as part of my source files.

Under the “External Libraries” section of PyCharm, my libraries are listed within site-packages as any other dependency, that is, the .dist.info folder. All correct, except… PyCharm cannot find the already-downloaded sources (which are in the virtualenv/src folder as usual).

Did you do any manual configuration in your tests, to make the downloaded source libraries visible/editable? Did PyCharm “automatically find” them in your virtualenv? I didn't get the message you mentioned, about libraries being read-only. It simply looks like PyCharm cannot “figure out” I'm using downloaded libraries…

https://youtrack.jetbrains.com/issue/PY-57566/Support-PEP-660-editable-installs is open since 2022 but nothing happened so far