[Eric] Configuring Python path in Eric

[michael.rans at nomura.com]

Hi Detlev,

I appreciate all your help.

Regarding fixing this in the Pylint config file,  if it were possible (and I'm not sure if it is), the problem would be one of relative paths for others using the same Pylint configuration. Most of my colleagues are using Eclipse with PyDev and use this file too.

I would like to make a feature suggestion: the ability to set the environment including Python path at various levels. Highest level would be the external environment. This would be overridden by the global Eric environment. This in turn would be overridden by the project level Eric environment. If this were set, then external tools like Pylint, as well as the debugger and unit tests would use this environment when run (or the global if project not set, or external environment if global not set). 

The facility to extend existing environment variables using $PYTHONPATH or %PYTHONPATH% for example (effectively allowing inheritance from the level above) would be required to make this work well.

A further improvement would be a level below project of per script configurations which would override all the others ie. there could be multiple configurations per project. The external tools could be configured by one of these configurations inheriting from the project level environment or maybe Pylint would use the configuration associated with the script being checked. For me this improvement would be less important than the feature listed above, but nice to have.

Cheers,
Mike

-----Original Message-----
From: detlev [mailto:detlev at die-offenbachs.de] 
Sent: 24 June 2010 17:57
To: eric at riverbankcomputing.com
Cc: Rans, Michael (IT/UK)
Subject: Re: [Eric] Configuring Python path in Eric

On Donnerstag, 24. Juni 2010, michael.rans at nomura.com wrote:
> Hi Detlev,
> 
> Thanks very much for your reply.
> 
> The debugger properties worked when debugging which is certainly a step
>  forwards, but the IDE needs to recognise the Python path as well. For
>  example, the unit test menu functionality won't work as there doesn't seem
>  to be a debug unit test option. Also, if I run the Pylint plugin, it flags
>  methods inherited from a parent class as errors because the parent class's
>  module is not on the Python path.

Does PyLint have an option in the config file to do that? If so, you should 
use this option and save the config file in the project somewhere.

> 
> Ideally the Python path (or environment) should be unspecific to the
>  debugger - is this possible?
> 
> Cheers,
> Mike
> 
> 
> -----Original Message-----
> From: detlev [mailto:detlev at die-offenbachs.de]
> Sent: 23 June 2010 18:57
> To: eric at riverbankcomputing.com
> Cc: Rans, Michael (IT/UK)
> Subject: Re: [Eric] Configuring Python path in Eric
> 
> Hi,
> 
> eric actually gives the option to modify the environment or even replace it
>  on a per project or global basis. In your case you should open the
>  debugger properties dialog via the Project->Debugger menu.
> 
> Detlev
> 
> On Mittwoch, 23. Juni 2010, michael.rans at nomura.com wrote:
> > Hi,
> >
> > I have a large project that has various Subversion branches which I need
> > to switch between (production, development and so forth). Consequently,
> > I want to be able to set the Python path per project.
> >
> > For example, if I load the production project, I want the Python path to
> > include the production code, if I load the development project, it
> > should include the development code.
> >
> > The code is heavily dependent on Python modules, so for each project
> > there is a src and a test folder that need to be added to the Python
> > path.
> >
> > I have not been able to find anywhere to set or append to the Python
> > path in Eric.
> >
> > Currently I've had to use the awful hack of having an Eric batch file
> > that sets the path before loading Eric. As a result, I must reload Eric
> > for each project using a different batch file. Yuk!
> >
> > 1. Does Eric have the facility to set or change the Python path?
> > 2. If not, why not?
> > 3. If not, is there a better workaround than the one I have come up
> > with?
> >
> > Cheers,
> > Mike
> >
> >
> >
> > This e-mail (including any attachments) is confidential, may contain
> > proprietary or privileged information and is intended for the named
> > recipient(s) only. Unintended recipients are prohibited from taking
> > action on the basis of information in this e-mail and must delete all
> > copies. Nomura will not accept responsibility or liability for the
> > accuracy or completeness of, or the presence of any virus or disabling
> > code in, this e-mail. If verification is sought please request a hard
> > copy. Any reference to the terms of executed transactions should be
> > treated as preliminary only and subject to formal written confirmation by
> > Nomura. Nomura reserves the right to monitor e-mail communications
> > through its networks (in accordance with applicable laws). No
> > confidentiality or privilege is waived or lost by Nomura by any
> > mistransmission of this e-mail. Any reference to "Nomura" is a reference
> > to any entity in the Nomura Holdings, Inc. group. Please read our
> > Electronic Communications Legal Notice which forms part of this e-mail:
> > http://www.Nomura.com/email_disclaimer.htm
> 


-- 
Detlev Offenbach
detlev at die-offenbachs.de



This e-mail (including any attachments) is confidential, may contain
proprietary or privileged information and is intended for the named
recipient(s) only. Unintended recipients are prohibited from taking action
on the basis of information in this e-mail and must delete all copies.
Nomura will not accept responsibility or liability for the accuracy or
completeness of, or the presence of any virus or disabling code in, this
e-mail. If verification is sought please request a hard copy. Any reference
to the terms of executed transactions should be treated as preliminary only
and subject to formal written confirmation by Nomura. Nomura reserves the
right to monitor e-mail communications through its networks (in accordance
with applicable laws). No confidentiality or privilege is waived or lost by
Nomura by any mistransmission of this e-mail. Any reference to "Nomura" is
a reference to any entity in the Nomura Holdings, Inc. group. Please read
our Electronic Communications Legal Notice which forms part of this e-mail:
http://www.Nomura.com/email_disclaimer.htm