Re: convert-ly broken in 2.21.x?

[David Kastrup]

Stanton Sanderson <stansand@gmail.com> writes:

>> On Aug 7, 2020, at 3:31 PM, David Kastrup <dak@gnu.org> wrote:
>> 
>> Stanton Sanderson <stansand@gmail.com> writes:
>> 
>>> I have had no response to my previous post, so I will try again.
>>> 
>>> On Mac OS 10.14.6 (Mojave), running LilyPond directly from the application 
>>> and using Update Syntax” from the “Compile” menu, applying it to the 
>>> “Welcome to Lilypond” file after renaming it “test 1.ly”, the following 
>>> error message is produced:
>>> 
>>> ---------
>>> Traceback (most recent call last):
>>>  File 
>>> "/Applications/LilyPond_2.21.4..app/Contents/Resources/bin/convert-ly", 
>>> line 86, in <module>
>>>    import convertrules
>>>  File 
>>> "/Applications/LilyPond_2.21.4..app/Contents/Resources/share/lilypond/current/python/convertrules.py",
>>>  line 26, in <module>
>>>    import lilylib
>>>  File 
>>> "/Applications/LilyPond_2.21.4..app/Contents/Resources/share/lilypond/current/python/lilylib.py",
>>>  line 30, in <module>
>>>    sys.stdin = codecs.getreader('utf8')(sys.stdin.detach())
>>> AttributeError: 'file' object has no attribute ‘detach'
>>> ————
>>> 
>>> I saw the same behavior with 2.21.1 and 2.21.3 when I attempted to update 
>>> older files.
>>> 
>>> What am I missing?
>> 
>> A recent enough version of Python?  Can you figure out what Python
>> version is used by your installation?
>> 
>> -- 
>> David Kastrup
>
> David,
>
> Thanks for responding. The Lilypond 2.21.4 app contains:
>
> Lilypond.app->Contents->Frameworks->Python framework->Versions->2.6
>
> However, the system installed version is later-
>
> MacBook-Air:~ (me)$ python --version
> Python 2.7.16
> MacBook-Air:~ (me)$ which python
> /usr/bin/python
>
> I thought Lilypond.app was “self contained” in the sense of providing
> the necessary binaries.

Well, depends on who creates the app.  LilyPond 2.21.4 will require
using a Python 3 variant if I am not mistaken, so it may be that the
application bundle was not assembled properly.  This is a recent change,
maybe the creators have not caught up?

-- 
David Kastrup