Difference between revisions of "Python"

From PDP/Grid Wiki
Jump to navigationJump to search
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
Analysis packages usually do not work with the system version of python.  Installing a newer one yourself is possible, but not so easy in many cases and you might run out of disk space.  This wiki describes how to do it using Anaconda which is maintained by the PDP group and accessible from most Nikhef machines, as long as they are running SLC6 (do 'cat /etc/issue' to find out).  stbc-i2,i3,i4 work as well as all the stoomboot batch nodes with the exception of those in the 'legacy' queue.
 
Analysis packages usually do not work with the system version of python.  Installing a newer one yourself is possible, but not so easy in many cases and you might run out of disk space.  This wiki describes how to do it using Anaconda which is maintained by the PDP group and accessible from most Nikhef machines, as long as they are running SLC6 (do 'cat /etc/issue' to find out).  stbc-i2,i3,i4 work as well as all the stoomboot batch nodes with the exception of those in the 'legacy' queue.
 +
 +
'''If you need lots of non-python packages and the ability to compile and link stuff, you are likely better off following the SFT path explained elsewhere on this wiki.'''
  
 
These instructions assume that you use the bash shell.  If you don't use bash, just type "bash" before running any of the commands below.  Csh might be possible but if you're using csh you have bigger problems than getting python working ;-)   
 
These instructions assume that you use the bash shell.  If you don't use bash, just type "bash" before running any of the commands below.  Csh might be possible but if you're using csh you have bigger problems than getting python working ;-)   
Line 7: Line 9:
 
in your bash_profile or profile file:
 
in your bash_profile or profile file:
  
export PATH=/project/datagrid/anaconda/bin:$PATH
+
export PATH=/project/datagrid/anaconda/bin:$PATH
  
 
log out and log back in again so that this path setting is activated.  if you are using the SCREEN program you will need to do the same for SCREEN sessions (or else type the above command by hand into each screen session)
 
log out and log back in again so that this path setting is activated.  if you are using the SCREEN program you will need to do the same for SCREEN sessions (or else type the above command by hand into each screen session)
Line 51: Line 53:
  
 
This project was done in collaboration with Daniela Remenska from the Netherlands eScience Center, in collaboration with Chris Tunnell from the XENON group.
 
This project was done in collaboration with Daniela Remenska from the Netherlands eScience Center, in collaboration with Chris Tunnell from the XENON group.
 
 

Latest revision as of 13:25, 29 November 2017