Differences between revisions 21 and 62 (spanning 41 versions)
Revision 21 as of 2014-05-12 08:34:56
Size: 4311
Editor: bonaccos
Comment:
Revision 62 as of 2023-03-31 07:28:15
Size: 5484
Editor: stroth
Comment: Add info about relocation/purging pip cache
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
#rev 2020-09-10 bonaccos

<<TableOfContents()>>
Line 3: Line 7:
We provide as many modules as possible that come with the current Debian GNU/Linux stable release. Nevertheless, that might not be enough for your needs since you may want to use the newest version of some module or one that is not part of Debian. We provide some modules that come with the current Debian GNU/Linux stable release, but usually this is because they are dependencies of an installed software. For python we strongly recommend to build own python environments with the desired python versions and modules.
Line 5: Line 9:
Since Python 2.6 there is an easy way to install missing or outdated modules in your home through `easy_install`. Our recommended way to install such environments is trough Conda, alternatively via building an environment via `pyenv` is as well possible. Additional module can then either be installed by conda itself or trough `pip`.
Line 7: Line 11:
== How to use easy_install == == Installing your own python environment with Conda ==
Line 9: Line 13:
 || Command line help: || `easy_install --help` ||
 || Online documentation: || http://packages.python.org/distribute/easy_install.html ||
 || Install a new module: || `easy_install --user MODULENAME` ||
 || Update an existing module: || `easy_install --user -U MODULENAME` ||
For a detailed overview for conda please follow to the [[Programming/Languages/Conda|Conda documentation]].
Line 14: Line 15:
Modules will be installed in your home within `~/.local/`. You do not need to adapt the `PYTHONPATH` environment variable since python will look for modules in this directory automatically. == Installing your own python versions with pyenv ==
Line 16: Line 17:
== Installing other versions of Python == `Pyenv` is a collection of tools that allow users to manage different versions of python. In the simplest case you will need it to simply get an installation of python in your user space. Using that custom python installation, you will then be able to install additional modules in a very comfortable way, since you can install them in the "system path" (which is then somewhere within your home).
Line 18: Line 19:
You can of course install other versions of Python in your home. A very comfortable way of doing that is by using [[https://github.com/yyuu/pyenv|pyenv]]. You will find a howto on that website with detailled instructions how to use it. Documentation on `pyenv` can be found at https://github.com/pyenv/pyenv
Line 20: Line 21:
With pyenv you can also install additional Python modules like the whole scipy stack in the home directory. Here is a small howto for installing python 3.9.1 in your home:
Line 22: Line 23:
== Installation of custom (non easy_install-able) Python modules in the home directory of a user ==

We are sometimes asked for newer version of Python modules. We do no longer build Python modules in SEPP as the requests for modules and their versions is too widespread to keep these modules maintainable.

On this page we will list some bash-snippets that install some often requested modules in a users home.

== numpy ==

{{{#!highlight bash
#!/bin/bash

VERSION_NUMPY=1.7.1
builddir="/scratch/${USER}/build/numpy"

mkdir -p ${builddir}

cd ${builddir}
wget --output-document=numpy-${VERSION_NUMPY}.tar.gz \
    http://sourceforge.net/projects/numpy/files/NumPy/${VERSION_NUMPY}/numpy-${VERSION_NUMPY}.tar.gz/download
tar -xvvzkf numpy-${VERSION_NUMPY}.tar.gz
cd numpy-${VERSION_NUMPY}
python setup.py build --fcompiler=gnu95
python setup.py install --user
 * Install pyenv:
 {{{
curl https://raw.githubusercontent.com/pyenv/pyenv-installer/master/bin/pyenv-installer -o pyenv-installer
}}}
 Check what the script is doing and then execute it:
 {{{
bash ./pyenv-installer
}}}
 You can remove the installer file afterwards.
 * Add the following lines to your `~/.profile` before sourcing ~/.bashrc`:
 {{{
export PYENV_ROOT="$HOME/.pyenv"
export PATH="$PYENV_ROOT/bin:$PATH"
eval "$(pyenv init --path)"
}}}
 * In the `~/.bashrc`:
 {{{
eval "$(pyenv init -)"
}}}
 * If you want to pyenv-virtualenv automatically (in the `~/.bashrc`):
 {{{
eval "$(pyenv virtualenv-init -)"
Line 47: Line 47:
== scipy ==  * You need a new login shell for all settings to take effect (when logged in on a Desktop environment logoff and login again)
Line 49: Line 49:
|| '''Depends on''' ||
|| numpy ||
 * Install some python version, e.g. for python 3.9.1:
 {{{
env PYTHON_CONFIGURE_OPTS="--enable-shared" pyenv install 3.9.1
pyenv rehash}}}
 Note, that settting of `PYTHON_CONFIGURE_OPTS="--enable-shared"` is needed if you need to link against the libpython shared library.
Line 52: Line 55:
{{{#!highlight bash
#!/bin/bash
 * Make sure that this new python version will be used when you run python. You only need to run this command once:
 {{{
pyenv global 3.9.1}}}
Line 55: Line 59:
VERSION_SCIPY=0.13.0b1
builddir="/scratch/${USER}/build/scipy"
 * In order to update {{{pyenv}}} run:
 {{{
pyenv update}}}
Line 58: Line 63:
mkdir -p ${builddir} === Documentation of pyenv ===
 || Website of pyenv || https://github.com/pyenv/pyenv ||
 || Website of pyenv installer || https://github.com/pyenv/pyenv-installer ||
Line 60: Line 67:
cd ${builddir}
wget --output-document=scipy-${VERSION_SCIPY}.tar.gz \
    http://downloads.sourceforge.net/project/scipy/scipy/${VERSION_SCIPY}/scipy-${VERSION_SCIPY}.tar.gz
tar -xvvzkf scipy-${VERSION_SCIPY}.tar.gz
cd scipy-${VERSION_SCIPY}
python setup.py build
python setup.py install --user

== Installation of additional or newer modules with pip ==

Once you installed your custom python with the explanations given above, you are ready to install additional or newer modules the easy way. The usage of `pip` is very easy. The following command installs the module `numpy`.
{{{
pip install numpy
}}}
while the next command would upgrade an existing installation of {{{numpy}}}
{{{
pip install --upgrade numpy
Line 69: Line 79:
== matplotlib == For advanced usage of `pip`, please consult the manuals: https://pip.pypa.io/en/latest/
Line 71: Line 81:
|| '''Depends on''' ||
|| numpy ||
=== pip cache ===
`pip` uses a cache which is by default stored under `~/.cache/pip` or `$XDG_CACHE_HOME/pip` if it is set to a non-default location. This cache tends to fill up quickly and should occasionally be cleared with
{{{#!highlight bash numbers=disable
pip cache purge
}}}
It is advisable to set the cache's location to the local scratch disk to avoid using up quota:
Line 74: Line 88:
{{{#!highlight bash
#!/bin/bash

VERSION_MATPLOTLIB=1.3.0
builddir="/scratch/${USER}/build/matplotlib"

mkdir -p ${builddir}

cd ${builddir}
wget --output-document=matplotlib-${VERSION_MATPLOTLIB}.tar.gz \
    http://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-${VERSION_MATPLOTLIB}/matplotlib-${VERSION_MATPLOTLIB}.tar.gz/download
tar -xvvzkf matplotlib-${VERSION_MATPLOTLIB}.tar.gz
cd matplotlib-${VERSION_MATPLOTLIB}
python setup.py build
python setup.py install --user
 1. Create a directory for the cache: {{{#!highlight bash numbers=disable
mkdir -p /scratch/$USER/pip_cache
}}}
 1. Temporarily set the environment variable to tell `pip` to use a different cache location: {{{#!highlight bash numbers=disable
export PIP_CACHE_DIR=/scratch/$USER/tmp/
}}}
 1. or create a configuration file to store the location permanently: {{{#!highlight bash numbers=disable
mkdir -p ~/.config/pip
cat << EOF > ~/.config/pip/pip.conf
[global]
cache-dir = /scratch/<my username>/pip_cache
EOF
}}} Make sure to replace `<my username>` with your actual username in `pip.conf`
 1. Check if the cache location is correct: {{{#!highlight bash numbers=disable
pip cache info
Line 91: Line 105:
== nose ==
Line 93: Line 106:
|| '''Depends on''' ||
|| numpy ||
|| scipy ||
== Installation of Python modules that are not available in the archives of pip ==
Line 97: Line 108:
{{{#!highlight bash
#!/bin/bash

VERSION_NOSE=1.0.0
builddir="/scratch/${USER}/build/nose"

mkdir -p ${builddir}

cd ${builddir}
wget http://somethingaboutorange.com/mrl/projects/nose/nose-${VERSION_NOSE}.tar.gz
tar -xvvzkf nose-${VERSION_NOSE}.tar.gz
cd nose-${VERSION_NOSE}
python setup.py build
python setup.py install --user
}}}
Here we provide some shell script snippets for installing frequently asked modules which cannot be installed through {{{pip}}}. These scripts just provide an example installation. You might have to adapt some paths in order to make the module work correctly with the version of python you are using (e.g. if you run your custom python provided through `pyenv`).

Python

We provide some modules that come with the current Debian GNU/Linux stable release, but usually this is because they are dependencies of an installed software. For python we strongly recommend to build own python environments with the desired python versions and modules.

Our recommended way to install such environments is trough Conda, alternatively via building an environment via pyenv is as well possible. Additional module can then either be installed by conda itself or trough pip.

Installing your own python environment with Conda

For a detailed overview for conda please follow to the Conda documentation.

Installing your own python versions with pyenv

Pyenv is a collection of tools that allow users to manage different versions of python. In the simplest case you will need it to simply get an installation of python in your user space. Using that custom python installation, you will then be able to install additional modules in a very comfortable way, since you can install them in the "system path" (which is then somewhere within your home).

Documentation on pyenv can be found at https://github.com/pyenv/pyenv

Here is a small howto for installing python 3.9.1 in your home:

  • Install pyenv:
    curl https://raw.githubusercontent.com/pyenv/pyenv-installer/master/bin/pyenv-installer -o pyenv-installer
    Check what the script is doing and then execute it:
    bash ./pyenv-installer
    You can remove the installer file afterwards.
  • Add the following lines to your ~/.profile before sourcing ~/.bashrc`:

    export PYENV_ROOT="$HOME/.pyenv"
    export PATH="$PYENV_ROOT/bin:$PATH"
    eval "$(pyenv init --path)"
  • In the ~/.bashrc:

    eval "$(pyenv init -)"
  • If you want to pyenv-virtualenv automatically (in the ~/.bashrc):

    eval "$(pyenv virtualenv-init -)"
  • You need a new login shell for all settings to take effect (when logged in on a Desktop environment logoff and login again)
  • Install some python version, e.g. for python 3.9.1:
    env PYTHON_CONFIGURE_OPTS="--enable-shared" pyenv install 3.9.1
    pyenv rehash

    Note, that settting of PYTHON_CONFIGURE_OPTS="--enable-shared" is needed if you need to link against the libpython shared library.

  • Make sure that this new python version will be used when you run python. You only need to run this command once:
    pyenv global 3.9.1
  • In order to update pyenv run:

    pyenv update

Documentation of pyenv

Installation of additional or newer modules with pip

Once you installed your custom python with the explanations given above, you are ready to install additional or newer modules the easy way. The usage of pip is very easy. The following command installs the module numpy.

pip install numpy

while the next command would upgrade an existing installation of numpy

pip install --upgrade numpy

For advanced usage of pip, please consult the manuals: https://pip.pypa.io/en/latest/

pip cache

pip uses a cache which is by default stored under ~/.cache/pip or $XDG_CACHE_HOME/pip if it is set to a non-default location. This cache tends to fill up quickly and should occasionally be cleared with

pip cache purge

It is advisable to set the cache's location to the local scratch disk to avoid using up quota:

  1. Create a directory for the cache:

    mkdir -p /scratch/$USER/pip_cache
    
  2. Temporarily set the environment variable to tell pip to use a different cache location:

    export PIP_CACHE_DIR=/scratch/$USER/tmp/
    
  3. or create a configuration file to store the location permanently:

    mkdir -p ~/.config/pip
    cat << EOF > ~/.config/pip/pip.conf
    [global]
    cache-dir = /scratch/<my username>/pip_cache
    EOF
    

    Make sure to replace <my username> with your actual username in pip.conf

  4. Check if the cache location is correct:

    pip cache info
    

Installation of Python modules that are not available in the archives of pip

Here we provide some shell script snippets for installing frequently asked modules which cannot be installed through pip. These scripts just provide an example installation. You might have to adapt some paths in order to make the module work correctly with the version of python you are using (e.g. if you run your custom python provided through pyenv).

nlopt

   1 #!/bin/bash
   2 
   3 # Installation script for nlopt library
   4 
   5 VERSION=2.3
   6 INSTALLDIR=$HOME/.local
   7 BUILDDIR=/scratch/$USER/nlopt
   8 
   9 mkdir -p $BUILDDIR
  10 cd $BUILDDIR
  11 
  12 wget "http://ab-initio.mit.edu/nlopt/nlopt-${VERSION}.tar.gz"
  13 tar -xvvzkf nlopt-${VERSION}.tar.gz
  14 cd nlopt-${VERSION}
  15 
  16 ./configure \
  17         --enable-shared \
  18         --prefix=$INSTALLDIR \
  19         OCT_INSTALL_DIR=$INSTALLDIR/octave/oct \
  20         M_INSTALL_DIR=$INSTALLDIR/octave/m/ \
  21         MEX_INSTALL_DIR=$INSTALLDIR/mex \
  22         GUILE_INSTALL_DIR=$INSTALLDIR/guile
  23 
  24 make
  25 make install


CategoryLXSW

Programming/Languages/Python (last edited 2023-11-06 08:33:58 by stroth)