It does not (or should not) spew out any message, Python compiles it
silently (there does not seem to be a verbose mode that I can see in the
documentation). And if you are using the normal analysis script, you
won't get any *.pyc files, just *.pyo ones (and the latter are what you
want, so it is ok).
On Sat, 17 Feb 2007, Murali Vadivelu wrote:
> Dear Wayne,
> It does not seem to work here! I thought it would spew output like it
> does for the C-code. It did not. I could not find a newly
> compiled .pyc file either, when I checked the ccpnmr directory.
> Many thanks.
> On 14 Feb 2007, at 16:34, Wayne Boucher wrote:
> > Hello,
> > The UpdateAgent has now been updated to automatically compile the
> > Python
> > code for both the incremental and new release updates.
> > (And the way this compilation works, if you are running "python" at
> > the
> > time then it creates *.pyc files, and if you are running "python -
> > O" it
> > creates *.pyo files. This seems like an odd restriction for Mr
> > Python to
> > have made but hopefully will not cause a problem because if you use
> > the
> > analysis script it always runs as "python -O", so consistantly
> > deals with
> > *.pyo files.)
> > Wayne
> > On Wed, 14 Feb 2007, Wayne Boucher wrote:
> >> Sounds like a good idea. There even seems to be a couple of modules,
> >> py_compile and compileall, which allow this to be done from inside
> >> Python
> >> (I'll have to look at the documentation to see about *.pyc and
> >> *.pyo).
> >> What a great language, eh.
> >> Wayne
> >> On Tue, 13 Feb 2007, Murali Vadivelu wrote:
> >>> Dear Wayne,
> >>> Can you please extend this mechanism to byte-compile .py files when
> >>> they are updated? That would make life easier for people with
> >>> system-
> >>> level installation of CcpNmr, e.g., Fink installed CcpNmr.
> >>> Many thanks.
> >>> Best regards,
> >>> Murali.