From: DeLano, W. <wa...@su...> - 2002-07-09 17:20:52
|
> From: Johan Leckner [mailto:jo...@pa...] >=20 > I'm having problems running PyMol from within another Python program. This is not the recommended way to run PyMOL and may lead to problems. = You can run Python programs within PyMOL as follows: from the command-line: pymol example.py # synchronous, in PyMOL module pymol -r example.py # synchronous in __main__ module pymol -l example.py # asychronous in a new module You can also launch python programs from within PyMOL with the commands: run example.py # synchronous in pymol module run example.py,main # synchronous in __main__ module spawn example.py # asychronous in a new module spawn example.py,global # asychronous in the PyMOL module spawn example.py,main # asychronous in the __main__ module see: help launching help run help spawn > Following the examples in /pymol/examples/devel I have been able to=20 > launch and controll PyMOL. The problem occur when I try to quit PyMol=20 > (version. 0.82) however I do it I end up with a fault terminating my=20 > Python interpreter. >=20 > Under Redhat 7.1/Python 2.1 i get a segmentation fault and under=20 > MacOS 10.1.5/Python 2.2.1 I get a Python bus error. I get the same=20 > result both when quitting from the gui or within python with the=20 > command cmd.quit() >=20 > How can I quit PyMol properly? I know for a fact that the Mac take-down process is currently flawed, = and frequently gives a bus error. Because it only happens after you = quit the program, its a low priority issue... Not sure about Redhat. Warren =20 |