Re: [Dltk-dev] developing internal interpreter

[Andrei Sobolev <andrei.sobolev@xxxxxxxxx>]

Hi Rong,

You are right, current interpreter management infrastructure is not very
suited to add internal interpreters.
In near future we planed to move all interpreter management to EMF, and
provide additional kind of interpreters (internal,remote).

To make it work now, you should do following:
1) Add new interpreter type for your language.
2) Implement custom IInterpreterInstallType based class, which could
validate some path as valid (for example for some file in metadata), and
return your interpreter from getInterpreterInstalls() method.
2) Implement IInterpreterInstall with custom runner.

I suppose this will be enough to make it work.

Best regards,
Andrei Sobolev.
>
>  
>
> Hello,
>
>  
>
> I am developing a plugin using DLTK. One part involves creating
> internal (API) interpreter. I am new to DLTK. I am studying and
> developing at the same time. What I feel now is that some of the
> required fields such as path to home installation directory etc for
> Interpreter Install I don't want to use make me doing workaround
> often. Would you please advise if it would get worse down the road?
>
>  
>
> If DLTK interpreter install, interpreter install type may consider
> internal interpreter scenario later, that would be great.
>
>  
>
> Thanks very much!
>