As per this question, the 'run' command uses the wrong interpreter regardless of the configuration settings for the run action, and it appears the only way to fix it is to directly edit the source of pydev itself:
stackoverflow.com/questions/9237508/how-to-configure-pydev-to-use-32-bit-python-interpreter-in-eclipse-on-osx-lion
Even after importing the python2.7-32 interpreter as the ONLY defined one, the output of the 'See resulting command-line for the given parameters' on OSX reads:
/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python
-u /Users/douglasl/projects/python/test/test.py
The PYTHONPATH that will be used is:
...
When the configured path to the interpreter is:
/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7-32
This appears to be because the run command is using the sys.executable value INSTEAD of the value that is configured with the selected interpreter, which is the heart of this bug.
Hi there, this tracker is disabled for now. I've started a funding (http://igg.me/at/liclipse) to keep supporting PyDev and if the funding works, I'll create a tracker where you should post issues like this (so, please buffer this request and add it to the new tracker when the funding goes through).