Well, I had other plans for that... if it is in the path, you can
directly execute:
python interpreterInfo.py and it should give you all the info
required... (that file is in
org.python.pydev/PySrc/interpreterInfo.py)... I just didn't have the
time to do it automattically right now... (The problem is getting it
if it is not in the path)
Right now, it already works like that, but the user must specify the
interpreter. I didn't find a good place to do that automatically,
although I haven't searched it too much either. You can check the
org.python.pydev.ui.pythonpathconf.InterpreterInfo -- it is the class
that parses those results.
The class InterpreterManager has:
public InterpreterInfo getInterpreterInfo(String executable,
IProgressMonitor monitor)
that is the method that builds those results...
The file (interpreterInfo.py) still needs some fixes, but getting the
interpreter should be the part that works correctly...
Also, it would be nice if you could put the patches as bugs in
sourceforge (http://sourceforge.net/tracker/?group_id=3D85796&atid=3D577329=
),
as it is easier for me to keep track of them... (a bug for each
patch).
Cheers,
Fabio
p.s. I'm forwarding this to the list...
On 7/19/05, the...@op... <the...@op...> wrote:
> > You have to update the plugin.xml in the project, so that
> > the dependencies are satisfied...
|
