other:python:starting
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
other:python:starting [2017/03/09 16:23] jypeter Improved the conda section |
other:python:starting [2019/04/24 15:12] jypeter [Where to start] Updated |
||
|---|---|---|---|
| Line 10: | Line 10: | ||
| In order to start working with Python, you need to have a //Python distribution// installed on your local computer or on the remote Linux server(s) you work on. A //distribution// provides a //Python interpreter//, and Python extensions (aka Python //modules// or //packages//). You may have several distributions installed on your computer and you need to know how to initialize them, and which one you are using at a given time (type ''which python'' on Linux to determine where the python executable is located) | In order to start working with Python, you need to have a //Python distribution// installed on your local computer or on the remote Linux server(s) you work on. A //distribution// provides a //Python interpreter//, and Python extensions (aka Python //modules// or //packages//). You may have several distributions installed on your computer and you need to know how to initialize them, and which one you are using at a given time (type ''which python'' on Linux to determine where the python executable is located) | ||
| - | If you are using a Linux computer or a Mac, you should already have a **default python** installed. The following example shows where the python interpreter is installed on the //asterix// LSCE server (if it's in ''/usr/bin'', it's the default python) and which version it is (example below: version //2.6.6// compiled in May 2015) | + | If you are using a Linux computer or a Mac, you should already have a **default python** installed. The following example shows where the python interpreter is installed on the //obelix// LSCE servers (if it's in ''/usr/bin'', it's the default python) and which version it is (example below: version //2.7.5// compiled in April 2019) |
| <code># Which is the current python (e.g. where is it located)? | <code># Which is the current python (e.g. where is it located)? | ||
| Line 18: | Line 18: | ||
| # Where is it coming from ('rpm' works on a RedHat-like Linux machine)? | # Where is it coming from ('rpm' works on a RedHat-like Linux machine)? | ||
| > rpm -qf /usr/bin/python | > rpm -qf /usr/bin/python | ||
| - | python-2.6.6-64.el6.x86_64 | + | python-2.7.5-77.el7_6.x86_64 |
| # You also get some information when you start the interpreter | # You also get some information when you start the interpreter | ||
| > python | > python | ||
| - | Python 2.6.6 (r266:84292, May 22 2015, 08:34:51) | + | Python 2.7.5 (default, Apr 9 2019, 14:30:50) |
| - | [GCC 4.4.7 20120313 (Red Hat 4.4.7-15)] on linux2 | + | [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)] on linux2 |
| Type "help", "copyright", "credits" or "license" for more information. | Type "help", "copyright", "credits" or "license" for more information. | ||
| >>> | >>> | ||
| Line 147: | Line 147: | ||
| ^ Server ^ Line to add to ''.bashrc'' ^ | ^ Server ^ Line to add to ''.bashrc'' ^ | ||
| | **LSCE** | ''source ~jypeter/.conda_jyp.sh''\\ \\ Note:{{ :other:python:conda_jyp.txt |conda_jyp}} content | | | **LSCE** | ''source ~jypeter/.conda_jyp.sh''\\ \\ Note:{{ :other:python:conda_jyp.txt |conda_jyp}} content | | ||
| + | | **ciclad** | ''source ~jypmce/.conda_jyp.sh'' | | ||
| + | |||
| Note: when you add the specified line to your ''bashrc'' file, you will then always get the python supplied by conda, instead of the system's python, when you use ''bash''. If you don't like this permanent behavior, just type ''source ~jyp_login_on_this_server/.conda_jyp.sh'' in the bash shell where you want to use conda+CDAT, rather than adding it to the ''.bashrc'' file... | Note: when you add the specified line to your ''bashrc'' file, you will then always get the python supplied by conda, instead of the system's python, when you use ''bash''. If you don't like this permanent behavior, just type ''source ~jyp_login_on_this_server/.conda_jyp.sh'' in the bash shell where you want to use conda+CDAT, rather than adding it to the ''.bashrc'' file... | ||
| Line 153: | Line 155: | ||
| <WRAP center round tip 60%> | <WRAP center round tip 60%> | ||
| - | When you initialize UV-CDAT, it will be available only the **current** window/shell. In the other windows, you still get whatever your default python is. This should minimize potential side-effects | + | When you initialize UV-CDAT, it will be available only in the **current** window/shell. In the other windows, you still get whatever your default python is. This should minimize potential side-effects |
| </WRAP> | </WRAP> | ||
| Line 163: | Line 165: | ||
| - Use CDAT ! | - Use CDAT ! | ||
| - | ^ Server ^ UV-CDAT version ^ Environment name\\ and activation line ^ | + | ^ UV-CDAT version ^ Server ^ Environment name\\ and activation line ^ Packages\\ (''conda list'') ^ |
| - | | **LSCE** | [[:other:uvcdat:cdat_conda:cdat_2_8_0|2.8.0]] | **cdatm14**\\ ''source activate cdatm14'' | | + | | [[:other:uvcdat:cdat_conda:cdat_2_8_0|2.8.0]] | **LSCE**\\ **ciclad** |**cdatm14** (''source activate cdatm14'') | {{ :other:uvcdat:cdat_conda:conda_list_lsce_cdatm14_170310.txt |cdatm14 installed packages}} | |
| + | | [[:other:uvcdat:cdat_conda:cdat_2_10|2.10]] | **LSCE** |**cdatm15** (''source activate cdatm15'') | {{ :other:uvcdat:cdat_conda:uvcdat-2.10_list_170721.txt |cdatm14 installed packages}} | | ||
| + | | **cdatm** will always point to the latest stable version |||| | ||
| + | | //latest stable version// | **LSCE** |**cdatm** (''source activate cdatm'') | ''conda list'' | | ||
| === Older versions of UV-CDAT === | === Older versions of UV-CDAT === | ||
other/python/starting.txt · Last modified: 2024/05/30 13:41 by jypeter
