Base classes are missing with Pydev and virtualenv interpreter

Question

Good, therefore, if I create a new virtualenv and then go into this environment, go into the python shell in this environment and run the "import log", for example, it imports absolutely accurately. Then I can run eclipse, create a new interpreter based on / bin / python in my virtualenv, and if I open the python console in eclipse based on this new interpreter, I can run the import log again without any problems. I can create a project using this new interpreter and create a sample file with nothing but

  import logging
 print asdf

I get an "unauthorized import" error with a row import log. This can be solved by adding the interpreter configuration to the lib / pythonX.X directory (in my case /System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6), but I would be impressed that this contradicts intuition for what you would like to do with eclipse and virtualenv.

I know the material in this lib / pythonX.X directory is nothing more than base classes, but if they should always be included, shouldn't they be included at all? Isn't that against the way virtualenv sets up links to these same classes inside its own lib / pythonX.X directory? Is adding the python base directory lib / pythonX.X to the eclipse interpreter the correct way to do this, or is there a problem with this?

Am I confused by all the settings, or is it really confusing, and am I right to ask a question? Thanks to everyone who can help.

Answer 1

I think this is just confusing ... You really need to add the paths of the base interpreter when setting up the virtualenv interpreter in PyDev (i.e., on the command line, when you start this interpreter and execute import sys;print(sys.path) , folders the base interpreter will probably be there, so they should also be in PyDev).