Dear all,

 

I just managed to install the latest Nest version (3.6) on my Ubuntu (18) machine via conda. I realized, that Nest env activates the PYTHONPATH variable, which is usually unset in conda. The Nest deactivation script (if the env is named nest in: ...env/nest/etc/conda/deactivate.d/) does not unset the PYTHONPATH. Switching from Nest env to another env with the still active PYTHONPATH might lead to problems loading specific python modules. CAn be fixed bei adding unset PYTHONPATH at the end of the deactivation script in this folder.

 

Best,

 

Andreas Schulz