Re: [Pydev-code] Introduction to PyDev list

[Fabio Z. <fa...@gm...>]

> Good news Fabio :) In fact, what I need is a per-project settings for Python
> interpreter (for example, define the Python interpreter for a project, not
> for the workspace) and also extension points to insert
> PythonInterpreterManagers... this maybe sound strange, but I have the
> following problem:
> Modules, types, etc. of a certain python interpreter are obtained by running
> the script on host PC. But, if I want to obtain information about a certain
> Python interpreter on a sandboxed environment? Or on a remote device? I need
> to run this script on different environments and get the information to be
> used on PyDev (on host PC) code indexing and auto-complete features, for
> example. Currently, we have two Python interpreter managers
> (PythonInterpreterManager and JythonInterpreterManager), which are set on
> PydevPlugin#start(...)
>
> How these changes impacts on current Pydev structure?

Well, the changes are not trivial. I still haven't started checking
all that's needed for the per-project settings, but it should be
available in about 2 releases (so, you don't need to worry much about
that one). As for gathering additional information from an environment
not available (which is actually a thing that came up recently), the
current solution is having a script that'll run in that environment
and have it generate python files (just with the basic structure:
modules, classes, methods and docstrings) and add them as if they were
files in the pythonpath (adding it to a zip file may also be nice if
you're having different versions). Would that suffice for what you
want? (as you'd need to create a script to gather that info someway
anyway, you might as well already make it in a format that pydev
already supports)

Cheers,

Fabio