Werner LEMBERG <w...@gnu.org> writes: >> So far we only have an offer for a hard and incompatible transition >> to Python3-only > > Actually, I dislike this. Similar to you, I don't see a convincing > reason to not write python code that is compatible with both version 2 > and version 3.
Well, #!/usr/bin/guile can mean either Guile-1 and Guile-2 whereas #!/usr/bin/python is more or less guaranteed to mean Python-2 for quite a bit of time, even while there may be only Python-3 available at some point of time. So it does look like we are in for a hard change with regard to distributed LilyPond versions anyway. However, the configure process very well could substitute #!@TARGET_PYTHON@ (most installed scripts) as well as #!@PYTHON@ (the build scripts) with either a Python-2 or a Python-3 hashbang, depending on availability/configuration of either option. So we definitely have a use case for supporting both: then a choice can be made by scripts or user at configure time. -- David Kastrup _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
