Re: Help wanted for Windows troubleshooting

[Mats Bengtsson]

One aspect that complicates things is that there are four different
lilylib files that Python can consider to import:

.../usr/share/lilypond/current/python/lilylib.py
.../usr/share/lilypond/current/python/lilylib.pyc
.../usr/bin/lilylib.py
.../usr/bin/lilylib.pyc

When experimenting with the 2.8.5-1 package, it seems that convert-ly
(and the other Python scripts) work well as long as at least one of these
four files is present.

With the 2.9.13 package, there is some problem with
.../usr/share/lilypond/current/python/lilylib.py
just as you say, but as soon all the other three files seem to work well,
so if you just remove it from the distribution, I guess everything should
work well. Same goes for convertrules, where everything works well
as soon as you remove the convertrules.py file in .../python/.
Unfortunately I don't have the Windows competence to discover what
the problem is with these files.

  /Mats

Han-Wen Nienhuys wrote:

> Mats Bengtsson schreef:
>
> > Yes, but he used version 2.6.x before!
>
> I could use some help troubleshooting this windows problem.
> It was seemingly introduced in 2.9.6.
>
> What happens over here, is that the files in
>
>    c:/Program Files/LilyPond/usr/share/lilypond/current/python/
>
> are botched in some way. There seems to be a problem with permissions 
> or somesuch, because the following commands seems to fix the problem
>
>    cd c:/Program Files/LilyPond/usr/share/lilypond/current/python/
>    rename lilylib.py botched.py
>    cp botched.py lilylib.py
>
> note that cp should be the cygwin cp command. It's also ok to do
>
>    cat botched.py > lilylib.py
>
> this will change
>
>   File "c:/Program Files/LilyPond/usr/bin/convert-ly.py", line 39, in ?
>     import lilylib as ly
>   SystemError: NULL result without error in PyObject_Call
>
> to
>
>   File "c:/Program Files/LilyPond/usr/bin/convert-ly.py", line 42, in ?
>     from convertrules import *
>   SystemError: NULL result without error in PyObject_Call
>
> (which is the next import statement)
>
> So, it seems that there is some kind of filesystem access attribute 
> that is set in the installer, and copied along with copy (but not with 
> cp).
>
> I couldn't figure out what it was, but I invite people with more 
> knowledge of Windows to analyze this further.

--
=============================================
        Mats Bengtsson
        Signal Processing
        Signals, Sensors and Systems
        Royal Institute of Technology
        SE-100 44  STOCKHOLM
        Sweden
        Phone: (+46) 8 790 8463                         
       Fax:   (+46) 8 790 7260
        Email: address@hidden
        WWW: http://www.s3.kth.se/~mabe
=============================================