zhangyiss/spack
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove Python 3.3 from testing.

Browse Source 
- 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.
This commit is contained in:
Todd Gamblin 2018-08-24 13:52:48 -07:00
parent a7f3fa01d5
commit 82820efe37
3 changed files with 5 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.travis.yml
View File

@ -35,10 +35,6 @@ jobs:
os: linux os: linux
language: python language: python
env: TEST_SUITE=unit env: TEST_SUITE=unit
- python: '3.3'
os: linux
language: python
env: TEST_SUITE=unit
- python: '3.4' - python: '3.4'
os: linux os: linux
language: python language: python

2
lib/spack/docs/contribution_guide.rst
View File

@ -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 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: perform 3 types of tests:
^^^^^^^^^^ ^^^^^^^^^^

8
lib/spack/docs/getting_started.rst
View File

@ -11,7 +11,7 @@ Prerequisites
Spack has the following minimum requirements, which must be installed Spack has the following minimum requirements, which must be installed
before Spack is run: 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 2. A C/C++ compiler
3. The ``git`` and ``curl`` commands. 3. The ``git`` and ``curl`` commands.
4. If using the ``gpg`` subcommand, ``gnupg2`` is required. 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 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 cray-mpich module into the environment. You can then be able to use whatever
environment variables, libraries, etc, that are brought into the environment environment variables, libraries, etc, that are brought into the environment
via module load. via module load.
.. note:: .. 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 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). compiler wrapper link line).
You can set the default compiler that Spack can use for each compiler type. You can set the default compiler that Spack can use for each compiler type.