That's by design...we can't allow calling of Python from p1m files. -- Warren L. DeLano, Ph.D. Principal Scientist
. DeLano Scientific LLC . 400 Oyster Point Blvd., Suite 213 . South San Francisco, CA 94080 USA . Biz:(650)-872-0942 Tech:(650)-872-0834 . Fax:(650)-872-0273 Cell:(650)-346-1154 . mailto:war...@delsci.com > -----Original Message----- > From: Sebastien Moretti [mailto:sebastien.more...@igs.cnrs-mrs.fr] > Sent: Thursday, August 04, 2005 12:17 AM > To: Warren DeLano; pymol-users > Subject: Re: [PyMOL] comments ? > > > Yes -- this is a bug -- thanks for pointing it out. > > > > Cheers, > > Warren > > > > > > It seems that the 'print "..."' commands is unrecognized in > p1m files too. > > >> > >>>But, '#' doesn't work in p1m file. > >>> Error: unrecognized keyword: #second The # line > >> > >>involves an error > >> > >>>but the script goes on. > >> > >>I think indeed you found a bug with the parsing of p1m files. > >>I have the same behaviour on my Linux computer. > >> > >>Nice choice of colors by the way. > >> > >>Cheers, > >> > >>Zac > > -- > Sébastien Moretti > http://www.igs.cnrs-mrs.fr/ > CNRS - IGS > 31 chemin Joseph Aiguier > 13402 Marseille cedex > > >
