Hi to all, Unfortunately the settings of Virtual Environment and Environment (which should be renamed to Environment Variables, because it is a little bit confusing with so many environments in the same dialog) doesn't affect the running and the debugging of a script.
On the other hand, just selecting the Virtual Environment in Run Script and Debug Script dialog windows everything is going as expected. Running the following script: import sys import numpy as np print(sys.version) print(sys.exec_prefix) print(sys.executable) print(sys.path) t = np.linspace(0, 2*np.pi) w = np.sin(t) print(w) The output to the Shell form is: Python 3.6.6 |Anaconda, Inc.| (default, Jun 28 2018, 11:27:44) [MSC v.1900 64 bit (AMD64)] on Hades, Standard >>> 3.6.6 |Anaconda, Inc.| (default, Jun 28 2018, 11:27:44) [MSC v.1900 64 bit (AMD64)] C:\dev\Miniconda3\envs\scientific C:\dev\Miniconda3\envs\scientific\python.exe ['', 'G:\\My Drive\\Python\\python-projects\\Python37_test_project', 'C:\\dev\\Miniconda3\\envs\\eric6\\Lib\\site-packages\\eric6\\DebugClients\\Python', 'C:\\dev\\Miniconda3\\Lib\\site-packages\\omniORBpy-4.2.2\\lib\\python', 'C:\\dev\\Miniconda3\\Lib\\site-packages\\omniORBpy-4.2.2\\lib\\x86_win32', 'C:\\WINDOWS\\System32', 'C:\\dev\\Miniconda3\\envs\\scientific\\python36.zip', 'C:\\dev\\Miniconda3\\envs\\scientific\\DLLs', 'C:\\dev\\Miniconda3\\envs\\scientific\\lib', 'C:\\dev\\Miniconda3\\envs\\scientific', 'C:\\dev\\Miniconda3\\envs\\scientific\\lib\\site-packages'] [ 0.00000000e+00 1.27877162e-01 2.53654584e-01 3.75267005e-01 4.90717552e-01 5.98110530e-01 6.95682551e-01 7.81831482e-01 8.55142763e-01 9.14412623e-01 9.58667853e-01 9.87181783e-01 9.99486216e-01 9.95379113e-01 9.74927912e-01 9.38468422e-01 8.86599306e-01 8.20172255e-01 7.40277997e-01 6.48228395e-01 5.45534901e-01 4.33883739e-01 3.15108218e-01 1.91158629e-01 6.40702200e-02 -6.40702200e-02 -1.91158629e-01 -3.15108218e-01 -4.33883739e-01 -5.45534901e-01 -6.48228395e-01 -7.40277997e-01 -8.20172255e-01 -8.86599306e-01 -9.38468422e-01 -9.74927912e-01 -9.95379113e-01 -9.99486216e-01 -9.87181783e-01 -9.58667853e-01 -9.14412623e-01 -8.55142763e-01 -7.81831482e-01 -6.95682551e-01 -5.98110530e-01 -4.90717552e-01 -3.75267005e-01 -2.53654584e-01 -1.27877162e-01 -2.44929360e-16] I don't set any Working Directory or Environment (Variables) such as PATH or PYTHONPATH. Of course, Alex, and as Detlev said, for special cases somebody should set the aforementioned environment variables (e.g. set PATH=C:\dev\Miniconda3\) instead of Working Directory. Alex, the Anaconda repository has not full upgraded for Python 3.7 and numpy package for Python 3.7 is not ready yet for installation. I cannot import Anaconda numpy in a Python 3.7 conda Virtual Environment, in Eric and anywhere else. Also, I have been using also Intel Distribution for Python with NumPy successfully in Eric. Finally, I tested a Conda Virtual Environment with Python 3.7 with numpy installed not with conda (Anaconda repository) but with pip (Pypi repository)and everything in Eric was ok. Detlev, I don't know if there is a problem or I don't know how to use the settings in the Debugger Options dialog window, but I expected that every Project should have its Virtual Environment and Python interpreter saved separately. Debugger Options seem to be saved on a Eric IDE level and not on Project level. Also, as I see with my experimentation, the Conda Virtual Environments are probably the same with the virtualenv ones. It should be nice to integrate the conda functionality in Eric, but it is not so important for the moment. conda also offers pip functionality with extra features. I use both of them. Sincerely, Christos Sevastiadis
_______________________________________________ Eric mailing list [email protected] https://www.riverbankcomputing.com/mailman/listinfo/eric
