Re: working with Python scripts

[Martín Rincón Botero]

Hi Jean,

thank you for your answer. Just to be sure: in the terminal I go to the
build directory and there I type PYTHONPATH=./python:$PYTHONPATH
build/out/bin/musicxml2ly ?

Am Di., 24. Jan. 2023 um 00:10 Uhr schrieb Jean Abou Samra <
jean@abou-samra.fr>:

> 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.)
>
>

-- 
www.martinrinconbotero.com