PYTHONPATH can be set as an environment variable in the respective line of the
"Run Script" dialog or the environment line of the project debugger properties
dialog.
Am Sonntag, 16. September 2018, 13:23:14 CEST schrieb Alex Gerhardt-Bourke:
> I don’t see a PYTHONPATH option in either of those two places.
>
>
>
> I will try eric more and get back to you on what I think should be part of
> the virtual environment definition.
>
>
>
> ________________________________
> From: Detlev Offenbach <***@die-offenbachs.de>
> Sent: Sunday, September 16, 2018 4:48:02 PM
> To: ***@riverbankcomputing.com
> Cc: Alex Gerhardt-Bourke; Christos Sevastiadis
> Subject: Re: [Eric] Support network for eric, conda, and internet connection
>
> The working directory entry does what it says. The debugger process does a
> kind of 'cd' into this directory and is started thereafter.
>
> Another possibility should be to set the PYTHONPATH environment variable.
> This could be set in the named dialog as well as permanently in the project
> debugger properties (Project menu -> Debugger submenu).
>
> I am open for suggestions for what stuff should be part of a virtual
> environment definition and how it should be used.
>
> Detlev
>
> Am Sonntag, 16. September 2018, 09:38:14 CEST schrieb Alex Gerhardt-Bourke:
> > I have found that, under the setup I described in my last email, it is
> > necessary to have \AppData\Local\conda\conda\envs\testEric\Library\bin;
> > Included in PATH in order to import numpy successfully.
> >
> > Setting this path as the “working directory” in the “Run Script” prompt
> > seems to solve the issue. What is the “working directory” setting supposed
> > to control, and would I expect other consequences to doing this? Is there
> > a
> > way to tie this working directory to a particular virtual environment?
> >
> > Regards,
> > Alex.
> >
> > ________________________________
> > From: Eric <eric-***@riverbankcomputing.com> on behalf of Alex
> > Gerhardt-Bourke <***@hotmail.com> Sent: Sunday, September 16, 2018
> > 1:14:12 PM
> > To: Christos Sevastiadis; ***@die-offenbachs.de
> > Cc: ***@riverbankcomputing.com
> > Subject: Re: [Eric] Support network for eric, conda, and internet
> > connection
> >
> > Hi All,
> >
> > Thankyou for your responses.
> >
> > Toggling the Dynamic Online Status Determination meant I am now able to
> > retrieve the list of plugins. It did not solve the issue of being able to
> > connect to IRC servers – not a huge issue but would be nice to know what
> > is
> > causing this.
> >
> > With regards to Conda environments – thankyou Christos for your useful
> > contributions. Installing eric6 under its own virtual environment is a
> > great idea as it means I can keep pyqt5 and qscintilla and other packages
> > used by eric in compatible versions with eric. The way you have described
> > setting conda virtual environments works a charm – it seems you can only
> > set an environment as a “global environment” if you have not also set the
> > directory path name. I also do not know what the effect of this is.
> >
> > I have now realized, after testing with other modules, that it is the
> > numpy
> > module in particular that is making life difficult. Here is my setup:
> > Miniconda installed, base environment has no extra modules installed eric6
> > environment has pyqt5, qscintilla installed underneath it. Eric has been
> > installed and is running under this environment testEric environment has
> > numpy installed. Numpy successfully imports when running through the
> > anaconda prompt with the testEric environment activated.
> >
> > Now, if I try to import numpy in a script and run through eric, where I
> > choose testEric as the virtual environment, I get an import error. This is
> > the same import error I get if I manually run the testEric python
> > interpreter and try to import numpy. So I assume conda is doing something
> > else when I run its activation script. I have tried changing the virtual
> > environment configuration in eric, in particular the “global environment”
> > toggle as mentioned before, as well as changing the <default> global
> > environment to both the conda base interpreter, and the eric6 environment
> > interpreter. Clearly none of these settings also change whatever conda is
> > doing.
> >
> > Cristos – do you work with numpy and do you work with numpy in eric?
> > Perhaps this is one of your “working” packages you have installed under
> > the base environment. I assume this issue won’t exist if running through
> > the base environment, but this is clearly not a solution if one wants to
> > work with virtual environments in their intended sense.
> >
> > Thankyou all again for your input,
> > Regards,
> > Alex.
> >
> >
> > From: Christos Sevastiadis<mailto:***@auth.gr>
> > Sent: Saturday, September 15, 2018 10:17 PM
> > Subject: Re: [Eric] Support network for eric, conda, and internet
> > connection
> >
> >
> > On Sat, 15 Sep 2018 at 17:07, Detlev Offenbach
> > <***@die-offenbachs.de<mailto:***@die-offenbachs.de>> wrote:
> >
> > Am Samstag, 15. September 2018, 15:25:05 CEST schrieb Christos
> > Sevastiadis:
> >
> > ..
> >
> > > P.S. to Detlev: It should be convenient if the of the default running
> > > environment was saved in the project. That means there is a default
> > > running
> > > environment for all new projects, but it can be changed and saved on
> > > each
> > > project.
> >
> > Virtual environments can be different on different computers/operating
> > systems. Therefore I am not including this in the project data, because
> > that should be platform/installation neutral. However, one can configure
> > the debugger settings specifically for a project through the Project menu
> > (Project->Debugger). Loading and saving of the project debugger settings
> > can be configured on the Project->Project configuration page.
> >
> > Detlev
> > --
> > Detlev Offenbach
> > ***@die-offenbachs.de<mailto:***@die-offenbachs.de>
> >
> >
> >
> > I didn't notice the Debug options in the project Menu, as I was expecting
> > it somewhere in or close to the Project options in the same menu. Because
> > I started to use Python with the Anaconda distribution, which is popular
> > for scientific applications, from the beginning I was involved with the
> > problems of Conda environments and Eric. One way or another I solved
> > them, with no need the Conda system to be integrated into Eric. I hope
> > Alex will make it either.
> >
> > Christos.
>
> --
> Detlev Offenbach
> ***@die-offenbachs.de
--
Detlev Offenbach
***@die-offenbachs.de