On Tue, Nov 25, 2008 at 5:50 PM, Fabio Zadrozny <fabiofz@gmail.com> wrote:
Hi Raul,

> Hi,
> I'm working on Maemo Eclipse Integration project
> (http://maemo.org/development/documentation/ide_integration/) which provides
> ESbox (http://esbox.garage.maemo.org) and PluThon
> (http://pluthon.garage.maemo.org) Eclipse plug-ins for developing maemo
> (http://www.maemo.org) applications with C/C++ and Python. For Python
> support, we use PyDev plug-in as base for providing features which help
> Python developers to implement interesting applications for maemo platform.
> So far, we have implemented some important, but not too complex features on
> ESbox/PluThon based on PyDev. Now, we are facing difficulties to provide
> additional functionalities (e.g, suitable PyDev interpreter configurators),
> because PyDev does not offer extension points to extend some
> functionalities, it has some restrictions on classes/methods/attributes and
> other issues.

Sorry, but I didn't exactly understand what you need in this area...
If you want you can change/implement what you need and send as patches
so that we can discuss on those. Also, just so that you know, not in
the next release (which should add support for python 3.0 and 2.6),
but in the other, there are plans to change the interpreter
configuration quite a bit (to have per-project settings and the
ability to specify environment variables for each interpreter).

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?