The following forum message was posted by fabioz at http://sourceforge.net/projects/pydev/forums/forum/293649/topic/4366170:
Yes, the problem is that virtualenv for Pydev is just another interpreter, so, it makes no distinction on the paths that should be added to the pythonpath (which as you saw has to be done manually -- pydev does present those folders when you add the interpreter, but they come unchecked). And yes, this is a bit strange, but I couldn't find out how to know that a given Python is actually running based on another Python -- this is done through Python itself in https://github.com/aptana/Pydev/blob/master/plugins/org.python.pydev/P ySrc/interpreterInfo.py when determining the 'INS_PATH' and 'OUT_PATH' -- basically the folders from the base install should be marked as 'INS_PATH' in that code -- so, if someone can figure that out, I'll gladly apply the patch to fix that ;-) Cheers, Fabio ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Pydev-users mailing list Pydev-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pydev-users
