Project

General

Profile

Install Appion Packages Shared » History » Revision 10

Revision 9 (Anchi Cheng, 03/04/2011 03:09 PM) → Revision 10/15 (Amber Herold, 04/28/2011 08:59 AM)

<pre> 
 cd /path/to/myami-VERSION/myami /your_download_area 
 cd myami 
 sudo ./pysetup.sh install 
 </pre> 

 That will install each package, and report any failures.    To determine the cause of failure, see the generated log file "pysetup.log".    If necessary, you can enter a specific package directory and run the python setup command manually.    For example, if sinedon failed to install, you can try again like this:  

 <pre> 
 cd sinedon 
 sudo python setup.py install 
 </pre> 

 h3. python-site-package-path: where the installed python packages went: 

 Python installer put the packages you installed into its site-packages directory. This enables all users on the same computer to access them. The easiest way to discover where your installed package is loaded from by python is to load a module from the package using interactive python command lines like this: 

 Start the python command line from shell: 
  <pre>python</pre> 

 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. 
 At the python prompt (python>) type: 
 <pre>import sinedon</pre> 


 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 
 <pre> 
 sinedon.__path__ 
 ['/usr/lib/python2.4/site-packages/sinedon'] 
 </pre> 

 In this case, /usr/lib/python2.4/site-packages/ is your python-site-package-path. If you go to that directory, you will find all the packages you just installed. 

 Save this value as an environment variable for use later, for bash: 
 <pre> 
 export PYTHONSITEPKG='/usr/lib/python2.4/site-packages' 
 </pre> 
 or C shell 
 <pre> 
 setenv PYTHONSITEPKG '/usr/lib/python2.4/site-packages' 
 </pre>