From: DeLano, W. <wa...@su...> - 2002-02-05 17:38:24
|
Stephen, Glad to see you're interested! O'Reilly was a blast... Right now PyMOL is more of a continuous process rather than a discrete set of release stages. Try building off of the CVS source. In theory, the 'ext' distribution contains all the dependencies you need (including Pmw and Numeric), but most of those are now getting to be quite out of date. Yu're best off assembling all of the necessary dependencies from their respective web sites. Please use Python 2.1 or greater. PyMOL isn't really a well behaved Python module, right now. That will change soon. The problem is that PyMOL needs a bit more coddling than a normal Python module in order to run. You can stick all of PyMOL under /usr/lib/python2.1/site-packages/pymol, but you'll need to adjust PYMOLPATH accordingly in the "pymol.com" script, and you'll want to copy or link that script to someplace useful (such as /usr/local/bin). > Ok, after googling the term Numeric I've come across > Numpy which looks to be Numeric. From what I can tell, it > looks like Numeric (or Numpy) is not distributed with redhat > and thus a seperate installation is necessary. Thus the > numeric rpms on the pymol site. If this were to be done > right, the numeric rpms should be located in the numpy > site, rather than the pymol site. I'm wondering if this > goes for Pwm as well.... - Warren |
From: Stephen A. <ad...@bn...> - 2002-02-05 18:46:22
|
Warren, This is what I'm going to do. I've kludge up the installation on my PC to run pymol. I've been able to download a .pdb file from the PDB and actually display a protien structure. (Really cool!) I'm going to try and rationalize my kludges so that anyone who installs the rpm's just has to type 'pymol' under linux and bingo, their off and running. There are a couple of tricks I can apply to the installation to make it integrate better with redhat linux. Also, I'm going to shy away from pulling the code out of CVS. Since I'm building RPM's, this does suggest some kind of stable release, even tho it's a moving target. So that fact that you went through the trouble of putting a .tar.gz file for .73 must mean that .73 has some significance of some sort. Maybe in the near future I can work on some kind of nightly build option or something which does pull the code right out of CVS. Cheers Steve. DeLano, Warren wrote: > Stephen, > > Glad to see you're interested! O'Reilly was a blast... > > Right now PyMOL is more of a continuous process rather than a discrete > set of release stages. Try building off of the CVS source. > > In theory, the 'ext' distribution contains all the dependencies you need > (including Pmw and Numeric), but most of those are now getting to be > quite out of date. Yu're best off assembling all of the necessary > dependencies from their respective web sites. Please use Python 2.1 or > greater. > > PyMOL isn't really a well behaved Python module, right now. That will > change soon. The problem is that PyMOL needs a bit more coddling than a > normal Python module in order to run. You can stick all of PyMOL under > /usr/lib/python2.1/site-packages/pymol, but you'll need to adjust > PYMOLPATH accordingly in the "pymol.com" script, and you'll want to copy > or link that script to someplace useful (such as /usr/local/bin). > > >>Ok, after googling the term Numeric I've come across >>Numpy which looks to be Numeric. From what I can tell, it >>looks like Numeric (or Numpy) is not distributed with redhat >>and thus a seperate installation is necessary. Thus the >>numeric rpms on the pymol site. If this were to be done >>right, the numeric rpms should be located in the numpy >>site, rather than the pymol site. I'm wondering if this >>goes for Pwm as well.... >> > > - Warren > |
From: Stephen A. <ad...@bn...> - 2002-02-05 19:06:47
|
Warren, in launch_pymol.py there is the following code sys.path.append(os.environ['PYMOL_PATH']+'/modules') It looks to me like your adding $PYMOL_PATH/modules to the path of modules searched by python. Right now, there is no modules directory in the final installation. Should I create one and put all the .so files in there? Right now I define $PYMOL_PATH=/usr/lib/python2.1/site-packages/pymol Where pymol has a bunch of .so files and some directories (no modules directory) with various __init__.py files. But it still starts up fine. Its like the sys.path.append does not seem to do much. What do you suggest? Steve. |