diff options
| author | Todd Gamblin <tgamblin@llnl.gov> | 2018-08-24 13:52:48 -0700 |
|---|---|---|
| committer | Todd Gamblin <tgamblin@llnl.gov> | 2018-08-24 16:22:37 -0700 |
| commit | 82820efe3753b76e6ed46428af04ddb0880bf5f1 (patch) | |
| tree | a2b51c0b247e654abf12446c04e6187ad6dd8ce1 /lib | |
| parent | a7f3fa01d5e06f2614087d35db51a400ff26c12c (diff) | |
| download | spack-82820efe3753b76e6ed46428af04ddb0880bf5f1.tar.gz spack-82820efe3753b76e6ed46428af04ddb0880bf5f1.tar.bz2 spack-82820efe3753b76e6ed46428af04ddb0880bf5f1.tar.xz spack-82820efe3753b76e6ed46428af04ddb0880bf5f1.zip | |
Remove Python 3.3 from testing.
- Support for Python 3.3 isn't really needed, as nothing uses it as the
default system Python, and nearly everyone will have a newer Python 3
version installed.
Diffstat (limited to 'lib')
| -rw-r--r-- | lib/spack/docs/contribution_guide.rst | 2 | ||||
| -rw-r--r-- | lib/spack/docs/getting_started.rst | 8 |
2 files changed, 5 insertions, 5 deletions
diff --git a/lib/spack/docs/contribution_guide.rst b/lib/spack/docs/contribution_guide.rst index 8123dbd164..542ba38519 100644 --- a/lib/spack/docs/contribution_guide.rst +++ b/lib/spack/docs/contribution_guide.rst @@ -56,7 +56,7 @@ locally to speed up the review process. If you take a look in ``$SPACK_ROOT/.travis.yml``, you'll notice that we test -against Python 2.6, 2.7, and 3.3-3.6 on both macOS and Linux. We currently +against Python 2.6, 2.7, and 3.4-3.7 on both macOS and Linux. We currently perform 3 types of tests: ^^^^^^^^^^ diff --git a/lib/spack/docs/getting_started.rst b/lib/spack/docs/getting_started.rst index 5c26c30d9f..1ea3c1a0e9 100644 --- a/lib/spack/docs/getting_started.rst +++ b/lib/spack/docs/getting_started.rst @@ -11,7 +11,7 @@ Prerequisites Spack has the following minimum requirements, which must be installed before Spack is run: -1. Python 2 (2.6 or 2.7) or 3 (3.3 - 3.6) +1. Python 2 (2.6 or 2.7) or 3 (3.4 - 3.7) 2. A C/C++ compiler 3. The ``git`` and ``curl`` commands. 4. If using the ``gpg`` subcommand, ``gnupg2`` is required. @@ -1218,13 +1218,13 @@ Here's an example of an external configuration for cray modules: This tells Spack that for whatever package that depends on mpi, load the cray-mpich module into the environment. You can then be able to use whatever environment variables, libraries, etc, that are brought into the environment -via module load. +via module load. .. note:: - For Cray-provided packages, it is best to use ``modules:`` instead of ``paths:`` + For Cray-provided packages, it is best to use ``modules:`` instead of ``paths:`` in ``packages.yaml``, because the Cray Programming Environment heavily relies on - modules (e.g., loading the ``cray-mpich`` module adds MPI libraries to the + modules (e.g., loading the ``cray-mpich`` module adds MPI libraries to the compiler wrapper link line). You can set the default compiler that Spack can use for each compiler type. |