lilypond-devel
[Top][All Lists]
Advanced

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

Re: working with Python scripts


From: Jean Abou Samra
Subject: Re: working with Python scripts
Date: Tue, 24 Jan 2023 00:10:57 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.0

On 24/01/2023 00:07, Martín Rincón Botero wrote:
> Dear list,
> 
> I'm trying to debug this issue
> https://gitlab.com/lilypond/lilypond/-/issues/6518 and I'm having
> trouble with what's probably the most basic thing but I can't seem to
> figure it out. I can't convert musicxml files with a self-compiled
> Lilypond other than inside of Frescobaldi. The problem with
> Frescobaldi is that if everything goes well, the window with the
> python output goes away but I would like to see the printed messages
> (that I'm printing from musicexp.py, which I know they're being
> printed from the times where musicxml2ly fails and I can see them in
> the python log, because Frescobaldi doesn't close the MusicXML import
> window in those circumstances). If I run the script from
> build/out/bin/musicxml2ly (in the terminal instead of Frescobaldi) it
> doesn't seem to run the version of musicxml2ly that is in
> lilypond/python or it's running some other copy of musicexp.py.



Maybe try

$ PYTHONPATH=./python:$PYTHONPATH build/out/bin/musicxml2ly ...

("git grep PYTHONPATH" will take you to where this is documented
in the contributor's guide).

Also remember that if you make any changes to the musicxml2ly.py
script, you need to run "make" again to sync build/out/bin/musicxml2ly.

(Yes, this setup is really weird.)

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


reply via email to

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