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.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Music Notation
http://www.lilypond-design.com
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
