Install Appion Packages » History » Version 9
Neil Voss, 05/12/2010 10:11 AM
| 1 | 1 | Amber Herold | h1. Install Appion Packages |
|---|---|---|---|
| 2 | |||
| 3 | h3. Install the package in _each folder_ with commands like these |
||
| 4 | |||
| 5 | *TODO: move these into a single installer, ask Jim* |
||
| 6 | |||
| 7 | <pre> |
||
| 8 | 9 | Neil Voss | cd /your_download_area/ |
| 9 | |||
| 10 | cd myami/leginon |
||
| 11 | 4 | Neil Voss | sudo python setup.py install |
| 12 | 1 | Amber Herold | |
| 13 | cd ../pyami |
||
| 14 | 4 | Neil Voss | sudo python setup.py install |
| 15 | 8 | Neil Voss | |
| 16 | 5 | Neil Voss | cd ../pyscope |
| 17 | 4 | Neil Voss | sudo python setup.py install |
| 18 | 8 | Neil Voss | |
| 19 | 1 | Amber Herold | cd ../sinedon |
| 20 | 4 | Neil Voss | sudo python setup.py install |
| 21 | 8 | Neil Voss | |
| 22 | cd ../imageviewer |
||
| 23 | sudo python setup.py install |
||
| 24 | |||
| 25 | cd ../appion |
||
| 26 | sudo python setup.py install |
||
| 27 | |||
| 28 | #binary packages |
||
| 29 | |||
| 30 | 4 | Neil Voss | cd ../numextension |
| 31 | 1 | Amber Herold | python setup.py build |
| 32 | 6 | Neil Voss | sudo python setup.py install |
| 33 | 8 | Neil Voss | |
| 34 | 4 | Neil Voss | cd ../libcv |
| 35 | 1 | Amber Herold | python setup.py build |
| 36 | sudo python setup.py install |
||
| 37 | 8 | Neil Voss | |
| 38 | 7 | Neil Voss | cd ../appion/radermacher |
| 39 | 6 | Neil Voss | python setup.py build |
| 40 | 4 | Neil Voss | sudo python setup.py install |
| 41 | 1 | Amber Herold | </pre> |
| 42 | |||
| 43 | h3. python-site-package-path: where the installed python packages went: |
||
| 44 | |||
| 45 | Python installer put the packages you installed to its site-packages directory. This enable all users on the same computer to access them. The easiest way to find where your installed package is called by python is to load a module from the package using interactive python command lines like this: |
||
| 46 | |||
| 47 | * Start python command line from shell |
||
| 48 | <pre>> python</pre> |
||
| 49 | |||
| 50 | * Import a module from the package. Let's try sinedon here. All packages installed through the above setup.py script should go to the same place. |
||
| 51 | <pre>python> import sinedon</pre> |
||
| 52 | |||
| 53 | |||
| 54 | * If the module is loaded successfully, call the module attribute __path__ (two underscrolls before "path" and two underscrolls after) will return the location of the module it is loaded from |
||
| 55 | <pre> |
||
| 56 | python> sinedon.__path__ |
||
| 57 | |||
| 58 | RETURNS, For example, |
||
| 59 | python> <module 'sinedon' from '/usr/lib/python2.5/site-packages/sinedon/__init__.pyc'> |
||
| 60 | </pre> |
||
| 61 | In this case, /usr/lib/python2.5/site-packages/ is your python-site-package-path. If you go to that directory, you will find all the packages you just installed. |
||
| 62 | 2 | Amber Herold | |
| 63 | ______ |
||
| 64 | |||
| 65 | [[Perform system check|< Perform system check]] | [[Configure leginon.cfg|Configure leginon.cfg >]] |
||
| 66 | 3 | Amber Herold | |
| 67 | ______ |