lilypond-devel
[Top][All Lists]
Advanced

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

Re: working with Python scripts


From: Werner Arnhold
Subject: Re: working with Python scripts
Date: Tue, 24 Jan 2023 09:55:26 +0100
User-agent: Evolution 3.30.5-1.1

Hi Martin,

a python execution window disappears when the script is finished. So
you simply have to tell the interpreter that it is not finished. Add a
"input()" as the last line in the script. So the interperter has to
wait for some input, a <Return> e.g. before regarding the script as
finished.

Werner

Am Dienstag, den 24.01.2023, 00:07 +0100 schrieb Martín Rincón Botero:
> 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.
> 
> —Martín.
> 




reply via email to

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