Building and installing SciPy
It is strongly recommended that you use either a complete scientific Python distribution or binary packages on your platform if they are available, in particular on Windows and Mac OS X. You should not attempt to build SciPy if you are not familiar with compiling software from sources.
Recommended distributions are:
The rest of this install documentation summarizes how to build Scipy. Note that more extensive (and possibly more up-to-date) build instructions are maintained at https://scipy.github.io/devdocs/building/
SciPy requires the following software installed for your platform:
- Python >= 3.5
- NumPy >= 1.13.3
- For building from source: setuptools
- If you want to build the documentation: Sphinx >= 1.2.1
- If you want to build SciPy master or other unreleased version from source (Cython-generated C sources are included in official releases): Cython >= 0.28.5
There are two ways to build Scipy on Windows:
- Use Intel MKL, and Intel compilers or ifort + MSVC. This is what Anaconda and Enthought Canopy use.
- Use MSVC + gfortran with OpenBLAS. This is how the SciPy Windows wheels are built.
It is recommended to use gcc or clang, both work fine. Gcc is available for free when installing Xcode, the developer toolsuite on Mac OS X. You also need a fortran compiler, which is not included with Xcode: you should use a recent gfortran from an OS X package manager (like Homebrew).
Please do NOT use gfortran from hpc.sourceforge.net, it is known to generate buggy scipy binaries.
You should also use a BLAS/LAPACK library from an OS X package manager. ATLAS, OpenBLAS, and MKL all work.
As of Scipy version 1.2.0, we do not support compiling against the system Accelerate library for BLAS and LAPACK. It does not support a sufficiently recent LAPACK interface.
Most common distributions include all the dependencies. You will need to install a BLAS/LAPACK (all of ATLAS, OpenBLAS, MKL work fine) including development headers, as well as development headers for Python itself. Those are typically packaged as python-dev
For the latest information, see the web site:
Use the command:
git clone https://github.com/scipy/scipy.git cd scipy git clean -xdf python setup.py install --user
cd scipy/doc make html
SciPy-<version>.tar.gz, change to the
directory, and run:
pip install . -v --user
This may take several minutes to half an hour depending on the speed of your computer.
To test SciPy after installation (highly recommended), execute in Python
>>> import scipy >>> scipy.test()
To run the full test suite use
If you are upgrading from an older SciPy release, please test your code for any deprecation warnings before and after upgrading to avoid surprises:
$ python -Wd -c my_code_that_shouldnt_break.py
Please note that you must have version 1.0 or later of the Pytest test framework installed in order to run the tests. More information about Pytest is available on the website.
You can specify which Fortran compiler to use by using the following install command:
python setup.py config_fc --fcompiler=<Vendor> install
To see a valid list of <Vendor> names, run:
python setup.py config_fc --help-fcompiler
IMPORTANT: It is highly recommended that all libraries that scipy uses (e.g. BLAS and ATLAS libraries) are built with the same Fortran compiler. In most cases, if you mix compilers, you will not be able to import Scipy at best, have crashes and random results at worst.
When installing with
python setup.py install or a variation on that, you do
not get proper uninstall behavior for an older already installed Scipy version.
In many cases that's not a problem, but if it turns out to be an issue, you
need to manually uninstall it first (remove from e.g. in
Alternatively, you can use
pip install . --user instead of
setup.py install --user in order to get reliable uninstall behavior.
The downside is that
pip doesn't show you a build log and doesn't support
incremental rebuilds (it copies the whole source tree to a tempdir).
If you experience problems when building/installing/testing SciPy, you can ask help from email@example.com or firstname.lastname@example.org mailing lists. Please include the following information in your message:
NOTE: You can generate some of the following information (items 1-5,7) in one command:
python -c 'from numpy.f2py.diagnose import run; run()'
python -c 'import os, sys; print(os.name, sys.platform)' uname -a OS, its distribution name and version information etc.
Information about C,C++,Fortran compilers/linkers as reported by the compilers when requesting their version information, e.g., the output of
gcc -v g77 --version
python -c 'import sys; print(sys.version)'
python -c 'import numpy; print(numpy.__version__)'
ATLAS version, the locations of atlas and lapack libraries, building information if any. If you have ATLAS version 3.3.6 or newer, then give the output of the last command in
cd scipy/Lib/linalg python setup_atlas_version.py build_ext --inplace --force python -c 'import atlas_version'
The output of the following commands
where INSTALLDIR is, for example, /usr/lib/python3.4/site-packages/.
Feel free to add any other relevant information. For example, the full output (both stdout and stderr) of the SciPy installation command can be very helpful. Since this output can be rather large, ask before sending it into the mailing list (or better yet, to one of the developers, if asked).
In case of failing to import extension modules, the output of
can be useful.