HPC/Applications/python: Difference between revisions
< HPC | Applications
Jump to navigation
Jump to search
Line 40: | Line 40: | ||
but this means a "mere python module" can clash with other MPI implementations used on Carbon. | but this means a "mere python module" can clash with other MPI implementations used on Carbon. | ||
Avoid loading modules at the same time for both a Python suite | Avoid loading modules at the same time for both an MPI implementation and a Python suite, especially in your dot-files. | ||
Doing so may lead to non-obvious failures with either the bundled parallel Python applications or (worse) unrelated compiled applications on Carbon. | Doing so may lead to non-obvious failures with either the bundled parallel Python applications or (worse) unrelated compiled applications on Carbon. | ||
</div> | </div> |
Revision as of 23:43, January 9, 2018
Python variants
Interpreter-only releases from the Python Software Foundation
- Module nomenclature
python/pyMajor.pyMinor/compilerName-compMajor.compMinor/pyMajor.pyMinor.pyPatch-moduleBuild
- Contains
-
- The Python interpreter only, from the python.org sources.
Python interpreters and packages as bundled with the OS
- Module nomenclature
python-osname/pyMajor.pyMinor/compilerName-compMajor.compMinor/pyMajor.pyMinor.pyPatch
- Contains
-
- The Python interpreter that comes with the operating system, which is required for many system internals and for system-provided add-on packages (installed via rpm or yum).
- Notes
- Such a module normally does not need to be loaded. It is included here for visibility in the module system, and as a base for (usually older) modules which provide Python packages outside of Conda or Pip. Such packages are often tied to the version of the Python interpreter under which they were installed.
Conda-based Python suites
- Module nomenclature
python-distributor/pyMajor.pyMinor/distMajor/distributor_defined_version[…]-moduleBuild
- Contains
-
- Wide-ranging Python-based software suites (as opposed to more narrowly scoped applications or libraries), with the package selection as distributed by the vendor.
The suites typically contain:
- A Python interpreter as a base.
- The conda/pip package management systems.
- A rich set of Python-native packages, extensions, and add-on executables, often including
- Idle – Python Integrated DeveLopment Environment
- iPython and juPyter – Interactive computation system
- Cython – Compiler for a superset of Python and C/C++
- Underlying libraries and supporting binaries, e.g.:
- Tcl – Interpreter for the Tool Command Language
- BLAS/LAPACK – Linear algebra libraries
- MPI – Runtime environment for parallel applications using Message Passing Interface, providing the
mpirun
ormpiexec
commands, plus related binaries and libraries.
Caveat: An MPI Runtime within a Python suite makes parallel computing easily accessible under Python, but this means a "mere python module" can clash with other MPI implementations used on Carbon.
Avoid loading modules at the same time for both an MPI implementation and a Python suite, especially in your dot-files. Doing so may lead to non-obvious failures with either the bundled parallel Python applications or (worse) unrelated compiled applications on Carbon.
Custom Conda environments
- Module nomenclature
python-env-distributor/pyMajor.pyMinor/distMajor/pyVersion[…]-moduleBuild
- A default selection of packages deemed useful for jobs on Carbon.
python-env-distributor-purpose/pyMajor.pyMinor/distMajor/pyVersion[…]-moduleBuild
- Same, with alternative package selections. (TBD)
- Contains
-
- Conda "environments", as derived from a vendor-distributed Conda suite, but with the package selection customized for Carbon.