Hi Fabio,
yes, I have some problems. In fact, the name of python exec seems to be the
ID of an InterpreterInfo. For example, you still use the name of python exec
to obtain an InterpreterInfo from a collection (e.g., on
AbstractInterpreterManager#hasInfoOnIntrepreter and also on
AbstractInterpreterManager#internalCreateInterpreterInfo). As you said, we
have to keep it to remain backwards compatible. Then, instead of a String,
why don't we use an object to properly select the correct ID? Or, if such
object tries to initialize from existent interpreters (using
InterpreterInfo#fromString), and the interpreter still remains on old format
(without the name), such object can initialize the name as its exec name
(just a tip).
Best regards,
--Raul
On Wed, May 27, 2009 at 6:03 PM, Fabio Zadrozny <[email protected]> wrote:
> Hi Raul,
>
> That depends on the place. Internally it can use both to access it
> from many places (to remain backwards compatible). Are you
> experiencing some problem regarding that?
>
> Cheers,
>
> Fabio
>
> On Wed, May 27, 2009 at 12:04 PM, Raul Fernandes Herbster
> <[email protected]> wrote:
> > Hi Fabio,
> >
> > on latest PyDev, the user can now define a name for its interpreter.
> > However, PyDev still uses internally the exec name of the interpreter as
> ID
> > of the InterpreterInfo. Is this an accident or intentional?
> >
> > []'s
> > --Raul
> >
>
------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
pydev-code mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pydev-code
