Sven Siegmund wrote: >> Uninstall python 3, as it can override library paths. > > But I really need Python 3. It is much more unicode-aware than Python > 2.x. Is there any hope that Lilypond-book will be ported to python 3? > Python 3 has been over a year around, so maybe it's time to adapt the > source code of lilypond-book a bit, isn't it? It would also be a great > opportunity to include an option for alternative TeX-compilers, e.g. > xelatex, not just pdflatex.
You could try uninstalling both Python 3 and Lilypond, and reinstalling them both... Porting something to work with Python 3 is a non-trivial issue. To give you an idea of the range of needs out there, my Linux distro makes available all versions of Python from 2.3 to 2.6 (the most recent 2.x release) as well as 3.0 and 3.1 -- in order to support various packages. Conversely, a Python program that wants to be widely used has to work with a range of different Python releases, since not everyone has the latest Python available. Porting to 3.x while still maintaining 2.x backwards compatibility is a bit of a load to carry when 2.x is still the most widespread Python out there. ... but you know that, if you're a Python dev -- so what's the chance that you could put some work into the port? :-) I'd also love to see xelatex compatibility, but don't have the faintest clue how to start working on that. _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
