opkover.blogg.se

Pycharm professional
Pycharm professional





By default it has site-packages and bunch of other paths there. Now this interpreter uses a bunch of Paths to look for a library. Add your package's path (package that you pip developed) here.ex /home/./repo-nameĮach project refers to an interpreter which you can find in settings->project interpreter.The existing paths of the selected interpreter show up in the Interpreter Paths dialog box. In the toolbar of the Project Interpreters dialog box, click the button icon show paths (last option). The available interpreters show up in the Project Interpreters dialog. click wheel framed (settings gear icon) button.So the new question is, can P圜harm be told to update its caches regarding the used python environment? Obviously the problem was that P圜harm didn't have some cache in sync with reality. After the installation, the package installed by python3 setup.py develop is well recognized by P圜harm. I did it through P圜harm by going to File -> Settings -> Project: -> Project Interpreter, there clicking on the green +, finding the package and pressing the Install Package button. However, I managed to solve it, kind-of.įor some reasons I had to install another package from pypi. This problem is still present in P圜harm 5.0.4.

pycharm professional

When I configure the P圜harm project p to live in its own virtualenv and install it there in development mode, everything works fine. The project/package p has the following structure: p/ Why does this happen? Is it a P圜harm thing or packaging related thing? See NEWS below. I can live with this but it is very annoying.

pycharm professional

However, when I run the script in s, everything is fine, the only problem is the P圜harm IDE complaining about not being able to find the module. In P圜harm in project s, import p statements are errorneous with message No module named p. The problem I have is the following: when I install the project (package) p in venv like this: $ source /path/to/venv/bin/activate Project s is (in P圜harm) configured to use a dedicated virtualenv, let's call it venv. The second one, let's call it s (like script), is just a python script along with two modules. with setup.py, all requirements etc., however it is not uploaded to pypi or any other online repository).

pycharm professional

The first one, let's call it p (like package), is structured as a setuptools package (i.e. I have two pure python projects in P圜harm 3.4.1 Professional Edition.







Pycharm professional