Hi Eric,

Well, I've already received feature requests for that, so, if you want to 'get dirty' I can help you doing it (altough I'm not sure myself what would be needed for that).

I believe that the way to go would be being able to set your interpreter in a 'per-project' configuration (that overrides the default).



On 2/5/06, Eric Wittmann <wittmann@snet.net> wrote:

        Hey there - I have an enhancement request that I am happy to help with.
  In short, I would like to be able to have two different Python
interpreters set up in pydev (you can do that now) but have the
PYTHONPATH be set up correctly for Run/Debug targets based on the
interpreter they are configured to use.

        Here is my use case:  I have an application that I help develop that is
written in Python.  Our current version of the app is based on Python
2.3.x and a few 3rd party libs (site-packages).  I am beginning work on
the next version of the app which will be based on Python 2.4 and
updated versions of the various libraries.  I would like to have both
codebases active in PyDev (in a single workspace) so that I can fix bugs
in the old app while also coding up the new app.

        Minimally this amounts to making sure the PYTHONPATH is correct for
Run/Debug targets that may use different interpreters.  In addition, I
suppose there are some interesting intellisense issues that might arise
(since I think pydev indexes the modules found on the 'system'
PYTHONPATH?  which seems to be the default interpreter).  Perhaps
associating an interpreter with a Project would be best.  That way
intellisense could work AND a default interpreter could be selected for
Run/Debugs (such as when you right-click and run as python app).

        For now, I guess my workaround is to have two different workspaces.  :)



This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
Pydev-code mailing list