Changes between Version 19 and Version 20 of VirtualEnv


Ignore:
Timestamp:
Aug 25, 2010, 1:16:02 PM (16 years ago)
Author:
Darren Weber
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • VirtualEnv

    v19 v20  
    11
    2 == Installing a Python Virtual Environment for Chimera ==
    3 
    4 Get a [http://www.cgl.ucsf.edu/chimera/download.html#daily daily build of Chimera].  In the examples below, it was a linux 64-bit build from 2010-08-05.  To run the installation (accept all the defaults in the prompts):
    5 
    6 {{{
    7 $ cd ~/Downloads/
    8 $ chmod +x chimera-alpha-linux_x86_64.exe
    9 $ sudo chimera-alpha-linux_x86_64.exe
    10 }}}
    11 
    12 This installation used sudo privileges to install into the default path, {{{/opt/UCSF/Chimera64-2010-08-05}}}.  If you don't have sudo priviledges, install to an alternative path where you have write permissions.  I like to have it install symlinks into
    13 {{{
    14 $ ls -al /usr/local/bin/chimera*
    15 lrwxrwxrwx 2 root root 42 2010-08-24 14:45 /usr/local/bin/chimera -> /opt/UCSF/Chimera64-2010-08-05/bin/chimera
    16 lrwxrwxrwx 1 root root 42 2010-08-05 14:53 /usr/local/bin/chimera-2010-08-05 -> /opt/UCSF/Chimera64-2010-08-05/bin/chimera
    17 }}}
    18 
    19 In the following notes, a few environment variables are set to simplify executing the new installation programs.  If your installation path is different, you will need to set the CHIMERA environment variable to your path.
    20 {{{
    21 $ export CHIMERA=/opt/UCSF/Chimera64-2010-08-05
    22 $ export PATH=$PATH:$CHIMERA/bin/
    23 $ export LD_LIBRARY_PATH=$CHIMERA/lib
    24 }}}
    25 
    26 Now get the setuptools package installed into the python system that was specifically built and installed for Chimera.  Note the following has some version specific details that need attention for any current installation.  At the time of writing, this installation used a specific daily-build of Chimera (2010-08-05) and a specific version of setuptools for the version of python that was built for Chimera (python2.7).
    27 
    28 {{{
    29 $ sudo -i
    30 # export CHIMERA=/opt/UCSF/Chimera64-2010-08-05
    31 # export PATH=$PATH:$CHIMERA/bin/
    32 # export LD_LIBRARY_PATH=$CHIMERA/lib
    33 # wget http://pypi.python.org/packages/2.7/s/setuptools/setuptools-0.6c11-py2.7.egg
    34 # sh setuptools-0.6c11-py2.7.egg --prefix=$CHIMERA
    35 }}}
    36 
    37 If you prefer to use distribute instead of setuptools, try the following:
    38 {{{
    39 $ sudo -i
    40 # export CHIMERA=/opt/UCSF/Chimera64-2010-08-05
    41 # export PATH=$PATH:$CHIMERA/bin/
    42 # export LD_LIBRARY_PATH=$CHIMERA/lib
    43 # curl -O http://python-distribute.org/distribute_setup.py
    44 # $CHIMERA/bin/python2.7 distribute_setup.py
    45 ...
    46 Processing distribute-0.6.14-py2.7.egg
    47 creating /opt/UCSF/Chimera64-2010-08-05/lib/python2.7/site-packages/distribute-0.6.14-py2.7.egg
    48 Extracting distribute-0.6.14-py2.7.egg to /opt/UCSF/Chimera64-2010-08-05/lib/python2.7/site-packages
    49 Adding distribute 0.6.14 to easy-install.pth file
    50 Installing easy_install script to /opt/UCSF/Chimera64-2010-08-05/bin
    51 Installing easy_install-2.7 script to /opt/UCSF/Chimera64-2010-08-05/bin
    52 
    53 Installed /opt/UCSF/Chimera64-2010-08-05/lib/python2.7/site-packages/distribute-0.6.14-py2.7.egg
    54 Processing dependencies for distribute==0.6.14
    55 Finished processing dependencies for distribute==0.6.14
    56 After install bootstrap.
    57 Creating /opt/UCSF/Chimera64-2010-08-05/lib/python2.7/site-packages/setuptools-0.6c11-py2.7.egg-info
    58 Creating /opt/UCSF/Chimera64-2010-08-05/lib/python2.7/site-packages/setuptools.pth
     2== Installing Chimera and a Python Virtual Environment for Chimera Development ==
     3
     4This page contains an example of a user installation of Chimera and additional configuration options to create a virtual python environment for development with Chimera.  The Chimera distribution currently ships with a custom build of python2.7 (as of Aug, 2010).  This custom python installation may not be compatible with any other installations of python on the system (including any site-packages in other python installations).  The following examples provide a tidy way to access and add new packages in a virtual environment derived from the Chimera python installation.
     5
     6=== Installing Chimera ===
     7
     8Get a stable release or a [http://www.cgl.ucsf.edu/chimera/download.html#daily daily build of Chimera].  In the examples below, it was a daily build for a linux 64-bit system (dated 2010-08-24).  To run the installation, without superuser privileges:
     9
     10{{{
     11cd ~/Downloads/
     12chmod +x chimera-alpha-linux_x86_64.exe
     13mkdir -p $HOME/src
     14./chimera-alpha-linux_x86_64.exe
     15}}}
     16
     17Here's an example of the interactive prompts and replies:
     18{{{
     19UnZipSFX 5.41 of 16 April 2000, by Info-ZIP (Zip-Bugs@lists.wku.edu).
     20Original path: '/home/dweber/Downloads'
     21  inflating: chimera_install_35bPbx/installer 
     22  inflating: chimera_install_35bPbx/chimera.exe 
     23
     24Enter install location: $HOME/src/Chimera64-2010-08-24
     25Extracting files.  This may take a few minutes.
     26Executing command: './chimera.exe -q -d /home/dweber/src/Chimera64-2010-08-24'
     27UnZipSFX 5.52 of 28 February 2005, by Info-ZIP (http://www.info-zip.org).
     28
     29Install desktop menu and icon? yes
     30
     31To install desktop menu and icon, run:
     32
     33    $HOME/src/Chimera64-2010-08-24/bin/xdg-setup install
     34
     35If run as root, then it installs for all users,
     36otherwise it installs just for the current user.
     37
     38Install symbolic link to chimera for command line use in which directory?
     39    0 -- no link
     40    1 -- /usr/local/sbin
     41    2 -- /usr/local/bin
     42    3 -- /usr/sbin
     43    4 -- /usr/bin
     44    5 -- /sbin
     45    6 -- /bin
     46    7 -- /usr/games
     47[hit Enter for default (0)]:
     48}}}
     49
     50This installation did not use sudo privileges, so the install path was changed from {{{/opt/UCSF/Chimera64-2010-08-05}}} to {{{$HOME/src/Chimera64-2010-08-24}}}.  To install the desktop menu and icons:
     51{{{
     52$HOME/src/Chimera64-2010-08-24/bin/xdg-setup install
     53}}}
     54
     55In addition, I like to setup a few symlinks, like so:
     56{{{
     57cd ~/src
     58ln -s Chimera64-2010-08-24 Chimera64-daily
     59sudo ln -s $HOME/src/Chimera64-daily/bin/chimera /usr/local/bin/chimera
     60}}}
     61
     62Lastly, a few environment variables are set to simplify executing the new installation programs.  If your installation path is different, you will need to set the CHIMERA environment variable to your path.
     63{{{
     64export CHIMERA=$HOME/src/Chimera64-daily
     65export PATH=$PATH:$CHIMERA/bin/
     66export LD_LIBRARY_PATH=$CHIMERA/lib
     67}}}
     68
     69=== Adding python distribution tools to the Chimera installation ===
     70
     71Now get the [http://pypi.python.org/pypi/distribute distribute] or the [http://pypi.python.org/pypi/setuptools setuptools] package installed into the Chimera python installation.  Note the following has some version specific details that need attention for any current installation.  At the time of writing (Aug, 2010), this installation used a specific daily-build of Chimera (2010-08-24) and a specific version of setuptools for the version of python that was built for Chimera (python2.7).
     72
     73Option A: to use [http://pypi.python.org/pypi/distribute distribute], try the following:
     74{{{
     75cd ~/Downloads
     76curl -O http://python-distribute.org/distribute_setup.py
     77$CHIMERA/bin/python2.7 distribute_setup.py
     78}}}
     79
     80Option B: to use [http://pypi.python.org/pypi/setuptools setuptools], try the following:
     81{{{
     82cd ~/Downloads
     83curl -O http://pypi.python.org/packages/2.7/s/setuptools/setuptools-0.6c11-py2.7.egg
     84sh setuptools-0.6c11-py2.7.egg --prefix=$CHIMERA
    5985}}}
    6086
    6187Now it's easy to use these tools for installation of any additional python packages into the Chimera python distribution.
    6288
     89
    6390=== Using virtualenv ===
    6491
    65 Adding additional packages to the Chimera python distribution is now possible and a great way to do this, while preserving the state of the Chimera distribution, is to use [http://pypi.python.org/pypi?%3Aaction=search&term=virtualenv&submit=search virtualenv].  First, add the {{{virtualenv}}} package into the Chimera python installation, like so:
    66 
    67 {{{
    68 $ sudo -i
    69 # export CHIMERA=/opt/UCSF/Chimera64-2010-08-05
    70 # export PATH=$PATH:$CHIMERA/bin/
    71 # export LD_LIBRARY_PATH=$CHIMERA/lib
    72 # $CHIMERA/bin/easy_install-2.7 virtualenv
    73 Searching for virtualenv
    74 Reading http://pypi.python.org/simple/virtualenv/
    75 Reading http://virtualenv.openplans.org
    76 Best match: virtualenv 1.4.9
    77 Downloading http://pypi.python.org/packages/source/v/virtualenv/virtualenv-1.4.9.tar.gz#md5=c49067cab242b5ff8c7b681a5a99533a
    78 Processing virtualenv-1.4.9.tar.gz
    79 Running virtualenv-1.4.9/setup.py -q bdist_egg --dist-dir /tmp/easy_install-eNIuwN/virtualenv-1.4.9/egg-dist-tmp-blYuR8
    80 warning: no previously-included files matching '*.*' found under directory 'docs/_templates'
    81 Adding virtualenv 1.4.9 to easy-install.pth file
    82 Installing virtualenv script to /opt/UCSF/Chimera64-2010-08-05/bin
    83 
    84 Installed /opt/UCSF/Chimera64-2010-08-05/lib/python2.7/site-packages/virtualenv-1.4.9-py2.7.egg
    85 Processing dependencies for virtualenv
    86 Finished processing dependencies for virtualenv
    87 }}}
    88 
    89 
    90 Now that virtualenv is installed in the Chimera python distribution, we can setup any additional custom virtual environments to add python packages into the development environment.  As a regular user, the following will create a Chimera-specific development environment in ~/src/chimera-virtualenv:
    91 
    92 {{{
    93 $ export CHIMERA=/opt/UCSF/Chimera64-2010-08-05
    94 $ export PATH=$PATH:$CHIMERA/bin/
    95 $ export LD_LIBRARY_PATH=$CHIMERA/lib
    96 $ mkdir -p ~/src
    97 $ cd ~/src
    98 $ $CHIMERA/bin/virtualenv chimera-virtualenv
    99 New python executable in chimera-virtualenv/bin/python2.7
    100 Also creating executable in chimera-virtualenv/bin/python
    101 Installing setuptools.................done.
    102 $ ls -al chimera-virtualenv/
    103 total 20
    104 drwxr-xr-x  5 dweber dweber 4096 2010-08-24 14:05 ./
    105 drwxr-xr-x 45 dweber dweber 4096 2010-08-24 14:05 ../
    106 drwxr-xr-x  2 dweber dweber 4096 2010-08-24 14:05 bin/
    107 drwxr-xr-x  2 dweber dweber 4096 2010-08-24 14:05 include/
    108 drwxr-xr-x  3 dweber dweber 4096 2010-08-24 14:05 lib/
     92Adding additional packages to the Chimera python distribution is now possible and a great way to do this, while preserving the state of the Chimera distribution, is to use [http://pypi.python.org/pypi/virtualenv virtualenv].  First, add the {{{virtualenv}}} package into the Chimera python installation, like so:
     93
     94{{{
     95$CHIMERA/bin/easy_install virtualenv
     96$CHIMERA/bin/virtualenv --help
     97}}}
     98
     99Now that {{{virtualenv}}} is installed in the Chimera python distribution, we can setup any additional custom virtual environments to add python packages into our custom development environment.  As a regular user, the following will create a Chimera-specific development environment in ~/src/chimera-virtualenv:
     100
     101{{{
     102mkdir -p ~/src
     103cd ~/src
     104$CHIMERA/bin/virtualenv --distribute $HOME/src/chimera-virtualenv
     105ls -al $HOME/src/chimera-virtualenv/
    109106}}}
    110107
    … …  
    112109
    113110{{{
     111source ~/src/chimera-virtualenv/bin/activate
     112deactivate
     113}}}
     114
     115=== !VirtualEnv Python Development for Chimera ===
     116
     117Now you can start the Chimera build of python and import the chimera module.  First activate the {{{virtualenv}}} and confirm that it's using the right python.
     118
     119{{{
     120source ~/src/chimera-virtualenv/bin/activate
     121python
     122}}}
     123
     124In my case, the terminal session looked like this:
     125
     126{{{
    114127$ source ~/src/chimera-virtualenv/bin/activate
    115 (chimera-virtualenv)$ deactivate
    116 $
    117 }}}
    118 
    119 Now start the Chimera build of python and import the chimera module, like this:
    120 
    121 {{{
    122 $ source ~/src/chimera-virtualenv/bin/activate
     128(chimera-virtualenv)$ which python
     129/home/dweber/src/chimera-virtualenv/bin/python
    123130(chimera-virtualenv)$ python
    124 Python 2.7 (r27:82500, Aug  5 2010, 14:15:36)
    125 [GCC 4.4.3] on linux2
     131Python 2.7 (r27:82500, Aug 23 2010, 21:16:26)
     132[GCC 4.2.3] on linux2
    126133Type "help", "copyright", "credits" or "license" for more information.
    127134>>> import sys
    128135>>> import os
    129136>>> os.getenv('CHIMERA')
    130 '/opt/UCSF/Chimera64-2010-08-05'
     137'/home/dweber/src/Chimera64-daily'
    131138>>> sys.path.append(os.path.join(os.getenv('CHIMERA'), 'share'))
    132139>>> sys.path.append(os.path.join(os.getenv('CHIMERA'), 'lib'))
    133140>>> import chimera
    134141>>> chimera.version.version
    135 'alpha version 1.5 (build 31152) 2010-08-05 19:55:24 GMT'
     142'alpha version 1.5 (build 31253) 2010-08-24 01:28:28 GMT'
    136143>>> for s in sys.path: print s
    137144...
    138145
    139 /home/dweber/src/chimera-virtualenv/lib/python2.7/site-packages/distribute-0.6.14-py2.7.egg
     146/home/dweber/src/chimera-virtualenv/lib/python2.7/site-packages/distribute-0.6.10-py2.7.egg
    140147/home/dweber/src/chimera-virtualenv/lib/python2.7/site-packages/pip-0.7.2-py2.7.egg
    141148/home/dweber/src/chimera-virtualenv/lib/python27.zip
    … …  
    145152/home/dweber/src/chimera-virtualenv/lib/python2.7/lib-old
    146153/home/dweber/src/chimera-virtualenv/lib/python2.7/lib-dynload
    147 /opt/UCSF/Chimera64-2010-08-05/lib/python2.7
    148 /opt/UCSF/Chimera64-2010-08-05/lib/python2.7/plat-linux2
    149 /opt/UCSF/Chimera64-2010-08-05/lib/python2.7/lib-tk
     154/home/dweber/src/Chimera64-daily/lib/python2.7
     155/home/dweber/src/Chimera64-daily/lib/python2.7/plat-linux2
     156/home/dweber/src/Chimera64-daily/lib/python2.7/lib-tk
    150157/home/dweber/src/chimera-virtualenv/lib/python2.7/site-packages
    151 /opt/UCSF/Chimera64-2010-08-05/lib/python2.7/site-packages/distribute-0.6.14-py2.7.egg
    152 /opt/UCSF/Chimera64-2010-08-05/lib/python2.7/site-packages/virtualenv-1.4.9-py2.7.egg
    153 /opt/UCSF/Chimera64-2010-08-05/lib/python2.7/site-packages
    154 /opt/UCSF/Chimera64-2010-08-05/lib/python2.7/site-packages/PIL
    155 /opt/UCSF/Chimera64-2010-08-05/lib/python2.7/site-packages/setuptools-0.6c11-py2.7.egg-info
    156 /opt/UCSF/Chimera64-2010-08-05/share
    157 /opt/UCSF/Chimera64-2010-08-05/lib
    158 >>>
     158/home/dweber/src/Chimera64-daily/lib/python2.7/site-packages/distribute-0.6.14-py2.7.egg
     159/home/dweber/src/Chimera64-daily/lib/python2.7/site-packages/virtualenv-1.4.9-py2.7.egg
     160/home/dweber/src/Chimera64-daily/lib/python2.7/site-packages
     161/home/dweber/src/Chimera64-daily/lib/python2.7/site-packages/PIL
     162/home/dweber/src/Chimera64-daily/lib/python2.7/site-packages/setuptools-0.6c11-py2.7.egg-info
     163/home/dweber/src/Chimera64-daily/share
     164/home/dweber/src/Chimera64-daily/lib
     165>>>
     166(chimera-virtualenv)$ deactivate
     167$
    159168}}}
    160169
    … …  
    163172{{{
    164173$ source ~/src/chimera-virtualenv/bin/activate
    165 (chimera-virtualenv)$ pip help
     174(chimera-virtualenv)$ pip --help
    166175Usage: pip COMMAND [OPTIONS]
    167176
    … …  
    203212=== Developing Chimera with spyder (a python IDE) ===
    204213
    205 Now for something adventurous, installing the [http://packages.python.org/spyder/ spyder].  First, we need to install some dependencies, sip and [http://www.riverbankcomputing.co.uk/software/pyqt/intro PyQt].  (In the example below, sip and !PyQt are installed with sudo privileges only because Chimera was installed with those privileges.  If you install Chimera without sudo privileges, try to run {{{make install}}} commands instead of {{{sudo make install}}}.)
    206 
    207 This example is based on an Ubuntu linux system that had packages installed for Qt4, PyQt4, and QScintilla2, which are [http://packages.python.org/spyder/installation.html#dependencies dependencies for spyder].  Your system may need these installed, along with their development libraries and headers.  Although those packages were installed on the system, they were not directly accessible to the Chimera python build.  In my case, a solution was to download and build !PyQt4 within the Chimera virtual environment.
    208 {{{
    209 $ source ~/src/chimera-virtualenv/bin/activate
    210 (chimera-virtualenv)$ cd ~/Downloads
    211 (chimera-virtualenv)$ wget http://www.riverbankcomputing.co.uk/static/Downloads/sip4/sip-4.10.5.tar.gz
    212 (chimera-virtualenv)$ tar zxvf sip-4.10.5.tar.gz
    213 (chimera-virtualenv)$ cd sip-4.10.5
    214 (chimera-virtualenv)$ python configure.py
    215 (chimera-virtualenv)$ make
    216 (chimera-virtualenv)$ sudo make install
    217 (chimera-virtualenv)$ cd ..
    218 (chimera-virtualenv)$ wget http://www.riverbankcomputing.co.uk/static/Downloads/PyQt4/PyQt-x11-gpl-4.7.4.tar.gz
    219 (chimera-virtualenv)$ tar zxvf PyQt-x11-gpl-4.7.4.tar.gz
    220 (chimera-virtualenv)$ cd PyQt-x11-gpl-4.7.4
    221 (chimera-virtualenv)$ python configure.py --no-designer-plugin --qmake=/usr/bin/qmake-qt4
    222 (chimera-virtualenv)$ make
    223 (chimera-virtualenv)$ sudo make install
    224 (chimera-virtualenv)$ wget http://212.219.56.133/sites/www.ibiblio.org/gentoo/distfiles/QScintilla-gpl-2.4.3.tar.gz
    225 (chimera-virtualenv)$ tar zxvf QScintilla-gpl-2.4.3.tar.gz
    226 (chimera-virtualenv)$ cd QScintilla-gpl-2.4.3
    227 (chimera-virtualenv)$ cd Python
    228 (chimera-virtualenv)$ python configure.py
    229 (chimera-virtualenv)$ make
    230 (chimera-virtualenv)$ sudo make install
    231 }}}
    232 
    233 That should satisfy the [http://packages.python.org/spyder/installation.html#dependencies dependencies for spyder].  Now try to install spyder using pip.
     214[http://www.youtube.com/watch?v=TRU6tQdyYqQ And now for something completely different]!  How about installing the [http://packages.python.org/spyder/ spyder].  First, we need to install some [http://packages.python.org/spyder/installation.html#dependencies spyder dependencies], [http://www.riverbankcomputing.com/software/sip/intro sip] and [http://www.riverbankcomputing.co.uk/software/pyqt/intro PyQt]. 
     215
     216
     217(In the example below, sip and !PyQt are installed with sudo privileges only because Chimera was installed with those privileges.  If you install Chimera without sudo privileges, try to run {{{make install}}} commands instead of {{{sudo make install}}}.)
     218
     219
     220This example is based on an Ubuntu linux system that had packages installed for Qt4, PyQt4, and QScintilla2, which are [http://packages.python.org/spyder/installation.html#dependencies spyder dependencies].  Your system may need these installed, along with their development libraries and headers.  Although those packages were installed on the system, they were not directly accessible to the Chimera python build.  In my case, a solution was to download and build !PyQt4 within the Chimera virtual environment.
     221
     222{{{
     223source ~/src/chimera-virtualenv/bin/activate
     224cd ~/Downloads
     225curl -O http://www.riverbankcomputing.co.uk/static/Downloads/sip4/sip-4.10.5.tar.gz
     226tar zxvf sip-4.10.5.tar.gz
     227cd sip-4.10.5
     228python configure.py
     229make
     230make install
     231deactivate
     232}}}
     233
     234{{{
     235source ~/src/chimera-virtualenv/bin/activate
     236cd ~/Downloads
     237curl -O http://www.riverbankcomputing.co.uk/static/Downloads/PyQt4/PyQt-x11-gpl-4.7.4.tar.gz
     238tar zxvf PyQt-x11-gpl-4.7.4.tar.gz
     239cd PyQt-x11-gpl-4.7.4
     240
     241# configure without installing designer plugin or QScintilla API, as these
     242# should be installed already by a prior installation of Qt4 or PyQt into the
     243# system paths
     244
     245python configure.py --qmake=/usr/bin/qmake-qt4 --no-qsci-api --no-designer-plugin
     246make
     247make install
     248deactivate
     249}}}
     250
     251{{{
     252source ~/src/chimera-virtualenv/bin/activate
     253cd ~/Downloads
     254
     255curl -O http://212.219.56.133/sites/www.ibiblio.org/gentoo/distfiles/QScintilla-gpl-2.4.3.tar.gz
     256tar zxvf QScintilla-gpl-2.4.3.tar.gz
     257cd QScintilla-gpl-2.4.3/Python
     258python configure.py
     259make
     260make install
     261deactivate
     262}}}
     263
     264
     265
     266ADD PYTHON MODULES FOR SPYDER: pylint, numpy, scipy, matplotlib?
     267
     268
     269That should satisfy the [http://packages.python.org/spyder/installation.html#dependencies spyder dependencies].  Now try to install spyder using pip.
     270
    234271{{{
    235272(chimera-virtualenv)$ pip install spyder
    … …  
    239276
    240277{{{
    241 $ source ~/src/chimera-virtualenv/bin/activate
    242 (chimera-virtualenv)$ export CHIMERA=/opt/UCSF/Chimera64-2010-08-05
    243 (chimera-virtualenv)$ export TCL_LIBRARY="$CHIMERA/lib/tcl8.6"
    244 (chimera-virtualenv)$ export TCLLIBPATH="{$CHIMERA/lib}"
    245 (chimera-virtualenv)$ unset TK_LIBRARY
    246 (chimera-virtualenv)$ unset TIX_LIBRARY
    247 (chimera-virtualenv)$ export LD_PRELOAD=libotf.so
    248 (chimera-virtualenv)$ export PATH=$PATH:$CHIMERA/bin
    249 (chimera-virtualenv)$ unset PYTHONHOME
    250 (chimera-virtualenv)$ unset PYTHONPATH
    251 (chimera-virtualenv)$ spyder
    252 }}}
     278source ~/src/chimera-virtualenv/bin/activate
     279export CHIMERA=/opt/UCSF/Chimera64-2010-08-05
     280export TCL_LIBRARY="$CHIMERA/lib/tcl8.6"
     281export TCLLIBPATH="{$CHIMERA/lib}"
     282unset TK_LIBRARY
     283unset TIX_LIBRARY
     284export LD_PRELOAD=libotf.so
     285export PATH=$PATH:$CHIMERA/bin
     286unset PYTHONHOME
     287unset PYTHONPATH
     288spyder
     289}}}
     290
    253291
    254292If that fails (as it did for me), try using sudo privileges (this worked for me):