Infrastructure/software/python - Revision history

Oe: /* Mixing and Matching */

2019-05-11T22:19:21Z

‎Mixing and Matching

2019-05-10T08:36:11Z

‎Automation

2019-05-10T08:35:54Z

‎Challenges and Ideas

2019-01-31T23:31:54Z

‎Packaging Ideas

2019-01-31T23:27:55Z

‎Basic Principles

2019-01-31T23:26:09Z

‎Background

2018-12-10T15:59:22Z

‎Packaging Ideas

2018-12-05T22:29:40Z

‎Challenges and Ideas

2018-12-05T22:28:42Z

‎Random Ideas

2018-11-27T16:18:42Z

‎Random Ideas

@@ Line 76: / Line 76: @@
 <pre>
-module load nlpl-nltk nlpl-gensim nlpl-tensorflow
+module load nlpl-nltk/3.4/3.7 nlpl-gensim/3.7.3/3.7 nlpl-pytorch/1.1.0/3.7
 </pre>

@@ Line 110: / Line 110: @@
 = Automation =
-On Abel, there is [http://svn.nlpl/eu/operation/python emerging support]
+On Abel, there is [http://svn.nlpl.eu/operation/python emerging support]
 for largely automated installation
 of Python modules, in a modular manner that allows support against
@@ Line 148: / Line 148: @@
 done
 </pre>
 = Challenges and Ideas =

@@ Line 107: / Line 107: @@
 | SciKit-Learn || — || 0.20.2 ||
 |}
 = Challenges and Ideas =

@@ Line 93: / Line 93: @@
 {| class="wikitable"
 |-
-! Component !! 201810 !! 201902 !! 201906
+! Component !! 201810 !! 201901 !! 201906
 |-
-| NumPy || 1.14.6 || ||
+| NumPy || 1.14.6 || — ||
 |-
-| SciPy Library || 1.1. 0 || ||
+| SciPy Library || 1.1. 0 || 1.2.0 ||
 |-
-| MatPlotLib || 3.3.0 || ||
+| MatPlotLib || 3.0.0 || 3.0.2 ||
 |-
-| IPython || 7.0.1 || ||
+| IPython || 7.0.1 || 7.2.0 ||
 |-
-| Pandas || 0.23.4 || ||
+| Pandas || 0.23.4 || 0.24.0 ||
 |-
-| SciKit-Learn || || ||
+| SciKit-Learn || — || 0.20.2 ||
 |}

@@ Line 27: / Line 27: @@
 NLPL standardizes on Python 3.x.
-In mid-2018, we use Python version 3.5 as the default starting
+In 2018, we have used Python version 3.5 as the default starting
 point for NLPL-specific installations of add-on modules, on both Abel and Taito.
 The general philosophy is to emphasize (a) ''parallelism'',
 (b) ''modularity'', and (c) ''replicability''.

@@ Line 19: / Line 19: @@
 of which some are near-universally used (e.g.
 [http://www.numpy.org/ NumPy] or
-[https://matplotlib.org/ MatPlotLib].
+[https://matplotlib.org/ MatPlotLib]).
 For these reasons, maintaining a Python environment for NLPL
 that is to some degree standardized and parallel across the

@@ Line 125: / Line 125: @@
 In principle, one could reduce most of the virtual environments
 to just the wheels that they provide, i.e. remove everything else
-from the standard virtual environment creation, including the
+from the standard virtual environment creation, including most
-binaries.
+binaries (that are not module-specific).
 Because wheels are organized in a directory hierarchy relative to
 each Python minor version, this should make it possible to install

@@ Line 110: / Line 110: @@
 from the standard virtual environment creation, including the
 binaries.
-As the wheels are organized in a directory hierarchy relative to
+Because wheels are organized in a directory hierarchy relative to
 each Python minor version, this should make it possible to install
 the code for add-on components (like MatPlotLib, GenSim, or NLTK)
 for multiple Python versions into the same module.
 As the NLPL collection of modules grows, it may well be helpful to
@@ Line 119: / Line 122: @@
 components (in specific versions) that are often used in conjunction
 and are known to be mutually interoperable.