"Phil Holmes" <m...@philholmes.net> writes: > ----- Original Message ----- > From: "David Kastrup" <d...@gnu.org> > To: "Phil Holmes" <m...@philholmes.net> > Cc: "Br. Samuel Springuel" <rpspring...@gmail.com>; <lilypond-user@gnu.org> > Sent: Thursday, April 03, 2014 2:07 PM > Subject: Re: LilyPond-Book on Windows >> >> It's not just that: most Windows users aren't actively participating on >> the lists, either. >> >> I have asked several times on one of the lists what the result of >> >> exit(0) >> >> inside of the Python we deliver with Windows (?) would be. Should not >> be too hard, but no response. It's not clear to me what version of >> Python we actually deliver (and I was apparently pointed to the wrong >> GUB repository for finding that out the hard way by looking at the >> source). > > Sorry - probably busy with other stuff. This may be what you want: > > C:\Program Files (x86)\LilyPondV2.18.0\usr\bin>python > Python 2.4.5 (#1, Oct 6 2013, 18:41:07) > [GCC 4.1.1] on mingw32 > Type "help", "copyright", "credits" or "license" for more information. >>>> exit(0) > Traceback (most recent call last): > File "<stdin>", line 1, in ? > TypeError: 'str' object is not callable >>>>
What I suspected. Like the problem that gets a workaround in LilyPond-book (and I am afraid that the workaround will likely break the TEXINPUTS manipulation and thus does not lead to a working program), this is pretty absurd. Instead of trying to find something nicer, like os.exit or sys.exit or whatever, I think it would make more sense first to move to version 2.6 (which probably means updating to Jan's repository and/or merging it into Graham's) and see how we fare there. It's quite conceivable that blunders like that are fixed in later versions. -- David Kastrup _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
