Re: Distributions upgrading to Python 3

[Patrick McCarty]

On Sun, Oct 17, 2010 at 11:19 PM, Mark Polesky <address@hidden> wrote:
> Patrick McCarty wrote:
>> Huh.  I've been following the Arch Linux development list
>> for a while, but it didn't occur to me that they were
>> doing something radically different than the recommended
>> policy.
>>
>> This is the procedure they are following, and I think they
>> are nearly finished with the task:
>>
>> http://wiki.archlinux.org/index.php/DeveloperWiki:Python_Todo_List
>
> Their advice is pretty clear (quoted from above link):
>
> Packages pointing at python binary
> (lilypond appears in this list)
>
> Packages which have "/usr/bin/python" or "/usr/bin/env
> python" in their files and will need to change to python2 if
> not already compatible with python-3.x.  Note that some of
> these are fixed by just building against a python2 binary,
> while others require some sed magic...

Yes, but unfortunately, LilyPond needs special sed treatment, since
many substitutions are made *after* configure time.  I will need to
file a bug report...

Specifically, I am looking for a way to make life easier when building
LilyPond without package management (instead of running a sed script
over all the python scripts every time I need to use them).

A simple change to stepmake/aclocal.m4 would ease the process, but I
think I'll keep this as a local patch for a while...

Thanks,
Patrick