Warren,
"DW" == DeLano, Warren wrote:
DW> import sys
DW> sys.argv = copy.deepcopy(argv)
DW> Directly under "def parse_args(argv):" (line 79) in
DW> PyMOL/modules/pymol/invocation.py.
Will try.
[...]
DW> pymol -c myscript.py -- -pymol -will -ignore -these -arguments
DW> pymol -c myscri
Sounds good to me and besides the syntax is consistent with
a few UNIX apps.
On Thu, 8 Nov 2001, DeLano, Warren wrote:
>
> pymol -c myscript.py -- -pymol -will -ignore -these -arguments
> pymol -c myscript.py -- -your -script -interpret -them -instead
>
> Any objections?
It looks like Andrey wants his script to be able to interpret command
line arguments. Unfortunately, PyMOL doesn't enable this in a
consistent way, since Launching under Windows (embedded Python) is quite
different than unix (non-embedded Python).
With embedded Python, arguments aren't making it
Frank,
"FV" == Frank Vondelft wrote:
FV> I deduce you're referring to windows?
Yes.
FV> I think this is what you get when python gets installed in C:\Program
FV> Files\python or some other location that is not on the (hardcoded?)
FV> search path of pymol, which means it can't find the tcl
Andrey,
I deduce you're referring to windows? I think this is what you get when
python gets installed in C:\Program Files\python or some other location
that is not on the (hardcoded?) search path of pymol, which means it
can't find the tcltk libraries. The solution is to install python on
C:\pyt
Hi!
Is it only me who gets the following:
for i in argv:
print i
[...]
$ pymol -c mov.py
[...]
Hit ESC anytime to toggle between text and graphics.
Command mode. No graphics front end.
Traceback (most recent call last):
File "C:\Program Files\DeLano Scientific\PyMOL/modules\pymol\parse
