At 10:50 AM -0700 4/30/03, wgsc...@chemistry.ucsc.edu wrote:
Coincidently that was the exact same program that hosed my python
installation too.
I had set up my computer to run the python based AutoDock Tools
interface to the docking program AutoDock. The installer for this
program puts its own copy of python as a subdirectory in the main
application directory and adds some environment variables to the
.cshrc file. Apparently, some variable created here affected other
python based apps. When I commented these out and opened a new xterm
and ran pymol, everything worked normally.
Moreover, my attempts to re-engineer the AutoDock installation ended
in a complete morass. This is a great reason for installation
software to at least allow you the option of using your already
installed system python.
Here's what I told my students. It seemed like a reasonable solution.
_________
It appears that the problem was introduced by the installation of
ADT. The ADT installer puts some lines in your .cshrc file that
prevents pymol from working properly. So here is a solution that
worked for me.
Take out the ADT lines and put them into a separate text file--say
call it "ADTenv.csh". If you open a new xterm, pymol should not work
properly.
If you want to run ADT, open a new xterm and "source ADTenv.csh" (no
quotes). Then run "adt" (no quotes) from this window.
_________
Although I didn't try it, I assume that you can't run pymol from that
xterm once you've run the ADTenv.csh script.
TG
--
_________________
Terry M. Gray, Ph.D., Computer Support Scientist
Chemistry Department, Colorado State University
Fort Collins, Colorado 80523
gr...@lamar.colostate.edu http://www.chm.colostate.edu/~grayt/
phone: 970-491-7003 fax: 970-491-1801
