Re: [Pydev-code] Some problems running Unit Tests

[Mark L. <mid...@ve...>]

Stepping through the code it seems that it adds PYTHONPATH entries only 
for the values of the PYTHON_LIB and PYTHON_SITE_PACKAGES properties 
(and the specific package dependencies, such as wxPython, numpy, etc) in 
TestDependent.<os>.properties. It doesn't parse any xxx.pth entries in 
those locations as python does. And it sets the infos on the default 
interpreter only with the directories explicitly set in the properties 
file. Unless I'm missing some other way to specify that, this seems to 
be a bug.

To make it work, I created a symlink in the location pointed to by 
PYTHON_LIB, which links to the mathmodule.so file in 
/usr/lib64/lib-dynload. This directory shows up as a lib entry in the 
python interpreter in PyDev preference page (even without the math.pth 
file pointing to it). But it's not being added to PYTHONPATH by the test 
code. Can the test code be made to use the configured PyDev interpreter 
instead of creating a default one with a limited set of PYTHONPATH 
entries? Or is there some way to make the default interpreter parse the 
xxx.pth files at all the PYTHONPATH locations?

I don't know why on my CentOS system I have this lib-dynload directory 
as a sibling to the python library directory, but python seems to be 
configured to recognize it.

-Mark

On 01/25/2016 02:19 PM, Mark Leone wrote:
> Further on this: adding the line
>
>  pythonpath.add("/usr/lib64/python2.6/lib-dynload/");
>
> to the beginning of AbsrtactShell.Tuple() makes the test succeed. 
> Obviously not the right solution, but it seems to demonstrate that my 
> PYTHONPATH setup is the problem. I don;t know why setting it in the 
> Environment tab of the run config doesn't have any effect.
>