Re: [Pydev-code] Introduction to PyDev list

[Raul F. H. <ra...@em...>]

Hi,

>
> >>
> >> 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).
> >
> > Hum... in fact, this solves problems of auto-complete and code indexing.
> > But, we still have a point: on PyDev, whenever a Python interpreter is
> > selected (using the Python Interpreter dialog, which it is accessible
> > through Window -> Preferences), it runs the script on local environment.
> So
> > I cannot set it as the current Python interpreter.
> >
> >>
> >> 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)
> >
> > This solves auto-complete and code indexing, but I still need to define a
> > local Python interpreter on preferences, which does not correspond with
> the
> > correct one.
>
> How exactly would you run that script from your computer (not
> considering pydev for that... how'd you do it from the command line?)
>

For maemo applications, we need to run commands on Scratchbox, using the
command "/scratchbox/login <command>". In addiction, we can execute this
command also on a remote environment throught ssh  (ssh
user@X.X.X.Xpython2.5 ...)

[]'s
--Raul