<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Judy,<div class=""><br class=""></div><div class="">There are several ways to get around having to execute “<font face="Menlo" class="">source activate pyn_test</font>” every time you wish to use PyNIO. In my opinion, the best solution that still provides the benefits of using conda (namely, being able to switch environments) would be to simply append “<font face="Menlo" class="">source activate pyn_test</font>” to your ~/.bashrc file.</div><div class=""><br class=""></div><div class="">Alternatively, you could explicitly add the pyn_test environment’s bin directory to your path, for example:</div><div class=""><font face="Menlo" class="">export PATH=$HOME/miniconda2/envs/pyn_test/bin:$PATH</font></div><div class=""><br class=""></div><div class="">I haven’t used this method before, but I’d be concerned about conda not working correctly without the “$HOME/miniconda2/bin” directory also being included in your path (AFTER the environment directory).</div><div class=""><br class=""></div><div class="">Finally, you could theoretically install PyNIO into the “root” conda environment (which does not require “activation”) using the command:</div><div class=""><font face="Menlo" class="">conda install -n root -c conda-forge pynio</font></div><div class=""><br class=""></div><div class="">The issue with this option is that if you try to install multiple packages from different channels into the root environment, you can run into version conflicts between packages. As such, unless you’re feeling adventurous I would recommend avoiding this solution and try one of the first two.</div><div class=""><br class=""></div><div class="">I hope this helps!</div><div class="">Kevin</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On May 12, 2017, at 7:19 PM, Tsai Judy <<a href="mailto:judytsaibuy@gmail.com" class="">judytsaibuy@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">Hi Pyncl-Talk,</div><div class=""><br class=""></div><div class="">I'm a new user of Python but a experienced using of NCL.</div><div class=""><br class=""></div><div class="">I've tried to install Pyngl/PyNio package on a linux cluster and a MacBook following this link: <a href="http://www.pyngl.ucar.edu/Download/" class="">http://www.pyngl.ucar.edu/Download/</a></div><div class=""><br class=""></div><div class="">I think I successfully installed the package and I'm able to use this package.</div><div class="">However, I have to execute "source activate pyn_test" everytime I would like to use this package, instead of just do "import Nio", which would give me error.</div><div class=""><br class=""></div><div class="">Is it normal or do I miss something?</div><div class=""><br class=""></div><div class="">Thank you</div><div class=""><br class=""></div><div class="">Judy</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div></div>
_______________________________________________<br class="">pyngl-talk mailing list<br class="">List instructions, subscriber options, unsubscribe:<br class=""><a href="http://mailman.ucar.edu/mailman/listinfo/pyngl-talk" class="">http://mailman.ucar.edu/mailman/listinfo/pyngl-talk</a><br class=""></div></blockquote></div><br class=""></div></body></html>