lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lilypond-book.py broken?


From: Colin Campbell
Subject: Re: lilypond-book.py broken?
Date: Sat, 12 Jun 2010 14:01:24 -0600
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100423 Thunderbird/3.0.4

On 10-06-12 12:22 PM, Reinhold Kainhofer wrote:
Am Samstag, 12. Juni 2010, um 20:07:06 schrieb Colin Campbell:
Still breaking, Reinhold, at least for me. Here are the last few lines

of the console:
/home/colin/lilypond-git/scripts/build/out/help2man out/lilypond-book
out/lilypond-book.1
langdefs.py: warning: lilypond-doc gettext domain not found.
Traceback (most recent call last):
   File "out/lilypond-book", line 86, in<module>
     import book_base as BookBase
   File "/home/colin/lilypond-git/python/out/book_base.py", line 4, in
<module>
     import book_snippets as BookSnippet
   File "/home/colin/lilypond-git/python/out/book_snippets.py", line
12, in<module>
     warning = ly.warning
AttributeError: 'module' object has no attribute 'warning'
Hmm, that's really strange... lilylib.py contains warning:

def warning (s):
     stderr_write (program_name + ": " + _ ("warning: %s") % s + '\n')

def error (s):
     stderr_write (program_name + ": " + _ ("error: %s") % s + '\n')

progress = stderr_write


Furthermore, on your installation, python seems to be able to access
ly.progress (the line before ly.warning), but fails for ly.warning...

Can you try removing /home/colin/lilypond-git/python/out/*.pyc ? It might be
that python is still using some old byte-compiled *.pyc files rather than
loading the new versions from *.py...

Cheers,
Reinhold

In ~/lilypond-git/python/out all .pyc files were dated today, but I deleted them as suggested
which python shows /usr/lib/python
python -V gives 2.6.5

ran make clean
./autogen.sh
make all

error unchanged
re-ran make all (if it doesn't work, use a bigger hammer!)
make ran to completion, although it seemed to ignore my local.make file, which sets quiet output and -j3: voluminous output to stdio and no forking into jobs.
make doc is still running, and it *does* read local.make

looking good so far, and if I don't follow up to the list, it was successful.

Many thanks, Reinhold, Graham and Jean-Charles!

cheers,
Colin


--
I stay cool and dig all jive, That's the way I stay alive.
My motto, as I live and learn, is "Dig and be dug in return."
   - Langston Hughes




reply via email to

[Prev in Thread] Current Thread [Next in Thread]