Skip to content
David Ketcheson edited this page Mar 19, 2015 · 3 revisions

Install all Python to site-packages

Motivation

Python modules are usually installed to a user's site-packages directory, so that they are automatically on the user's path and no manual modification of PYTHONPATH is needed. At present, PyClaw and Riemann follow this convention, installing themselves to site-packages. However, the Python bits of the Fortran codes do not. Besides violating the expectations of users, this can lead to a situation in which the user's PYTHONPATH points to a set of non-compiled files and doesn't work; see https://github.com/clawpack/clawpack/issues/44.

We propose to install all Python modules (including those in GeoClaw, AMRClaw, and clawutil) to site-packages.

Specification

clawpack/setup.py will be modified to put the Python code from GeoClaw, AMRClaw, and clawutil into the symlinked clawpack directory, so that it gets installed to site-packages, and so that pip install clawpack will also install those pieces. @mandli is going to do this.

Backward compatibility

This should not break backward compatibility, since the Python code in question will still live in the same places in the source directory.