Pydev default interpreter path setting

[Rohan2008]

Hi, I am new to pydev and so this might be a bit naïve question: I installed pydev plugin on my eclipse (3.7). I noticed that every time I create a new workspace, I have to provide the python interpreter path. I tried to find a way to make my /usr/bin/python default so that whenever the user creates a new workspace, he doesn’t have to configure the python interpreter… I came across this:
https://sourceforge.net/projects/pydev/forums/forum/293649/topic/3953077?message=8789799

I have also come across another message “yes, pydev does not support the variables defined in eclipse for now.”
https://sourceforge.net/projects/pydev/forums/forum/293649/topic/3822328
Does this mean that I can’t define an eclipse variable that sets the default python path so that the user doesn’t have to set it everytime he creates a new workspace?
Is this “configure interpreter per workspace” a design decision or am I missing something.
Thanks,

[Fabio Zadrozny]

It's a design decision (i.e.: in eclipse, preferences are stored under the .metadata in your workspace).

The idea is that you shouldn't need to have multiple workspaces for a given interpreter (i.e.: single workspace with multiple projects).

So, if you really feel that is something that should be there, can you elaborate a bit on why you need that (if it's something really needed, maybe PyDev could have a way to export that data so that you can import it somewhere else - would that be enough in this case?).

Cheers,

Fabio

[Rohan2008]

Fabioz, thanks for the reply. I am primarly looking to see if this is a design decision or not. I work for a company that offers a modified version of eclipse. I was tasked to integrate pydev plugin and so I have come across this issue. I was not initially sure if this is a design decision or if my integration needs a fix. Now, that it is clear, I think I will put this in the user documentation. thanks for the quick reply.

[Steve Potter]

I've got the same concern.  I'd rather not have each user have to go through a sequence of setup steps that are the same for each workspace.  If there's no way to set the shared installation of pydev to have a properly configured interpreter, is there a way for the user to initialize each new workspace from a template that is already configured?  That would at least cut it down to one step.