Re: [Frescobaldi] convert-ly don't work in 3.0.1 in Windows
Importing MusicXML also does nothing! Is there a log somewhere, nothing is displayed in the log window... // Anders On 2018-09-11 16:24, Urs Liska wrote: Am 11.09.2018 um 02:06 schrieb Urs Liska: Am 10.09.2018 um 19:07 schrieb Urs Liska: Am 10. September 2018 18:29:32 MESZ schrieb Federico Bruni : ... OK, I have put my hands on the code that calls convert-ly (https://github.com/wbsoft/frescobaldi/commit/ab9cda16d96564a86fd2580c05d3ec86c63b7e51) . It turns out that indeed Frescobaldi just invokes 'convert-ly' (with the absolute path, according to the current LilyPond version) without any notion of Python2/Python3. On Linux this is a shell script that explicitly starts the Python bundled with LilyPond, I don't know what exactly happens with this on Windows, but I think it *should* work, since it relies on what is bundled with LilyPond, not the Python3 from Frescobaldi. I think I'd need more information to give a better opinion. Best Urs One question: IIUC this should not only affect convert-ly, but also importing MusicXML, MIDI or ABC. Could someone check that, please? Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Frescobaldi] convert-ly don't work in 3.0.1 in Windows
Il giorno mar 11 set 2018 alle 16:24, Urs Liska ha scritto: One question: IIUC this should not only affect convert-ly, but also importing MusicXML, MIDI or ABC. Could someone check that, please? Yes, just tried to import from MIDI and I got a silent fail. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Frescobaldi] convert-ly don't work in 3.0.1 in Windows
Il giorno lun 10 set 2018 alle 18:29, Federico Bruni ha scritto: The best fix would be make LilyPond convert-ly work on python3 as well... Fixing the single file may be relatively easier. The problem is porting GUB from python2.4 to python2.7. See this PR 5 year old (2013): https://github.com/gperciva/gub/pull/6#issuecomment-24477663 Perhaps Frescobaldi may bundle a py2+py3 version of these scripts? ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Frescobaldi] convert-ly don't work in 3.0.1 in Windows
Il giorno mar 11 set 2018 alle 2:06, Urs Liska ha scritto: This is exactly a spot I'm currently working on (how Frescobaldi handles external jobs). I will have a look into how convert-ly is called too. OK, I have put my hands on the code that calls convert-ly (https://github.com/wbsoft/frescobaldi/commit/ab9cda16d96564a86fd2580c05d3ec86c63b7e51) . It turns out that indeed Frescobaldi just invokes 'convert-ly' (with the absolute path, according to the current LilyPond version) without any notion of Python2/Python3. On Linux this is a shell script that explicitly starts the Python bundled with LilyPond, I don't know what exactly happens with this on Windows, but I think it *should* work, since it relies on what is bundled with LilyPond, not the Python3 from Frescobaldi. No, it cannot work in Windows, because Linux installers provide the lilypond-wrapper.LANGUAGE bash scripts, while there's not such a thing for Windows. It's the problem I'm currently trying to work around to make lilypond-invoke-editor work on Windows. It's a GUB problem, see: https://github.com/gperciva/gub/blob/master/sourcefiles/lilypond-sharhead.sh#L208 $ ls -l /usr/local/bin/convert-ly lrwxrwxrwx 1 root root 38 1 ago 16.06 /usr/local/bin/convert-ly -> /usr/local/bin/lilypond-wrapper.python $ cat /usr/local/bin/lilypond-wrapper.python #!/bin/sh export PYTHONPATH="/usr/local/lilypond/usr/lib/lilypond/current/python:/usr/local/lilypond/usr/share/lilypond/current/python:$PYTHONPATH" export GUILE_LOAD_PATH="/usr/local/lilypond/usr/share/lilypond/current" export LD_LIBRARY_PATH="/usr/local/lilypond/usr/lib:$LD_LIBRARY_PATH" me=`basename $0` exec "/usr/local/lilypond/usr/bin/python" "/usr/local/lilypond/usr/bin/$me" "$@" ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Frescobaldi] convert-ly don't work in 3.0.1 in Windows
Am 11.09.2018 um 02:06 schrieb Urs Liska: Am 10.09.2018 um 19:07 schrieb Urs Liska: Am 10. September 2018 18:29:32 MESZ schrieb Federico Bruni : ... OK, I have put my hands on the code that calls convert-ly (https://github.com/wbsoft/frescobaldi/commit/ab9cda16d96564a86fd2580c05d3ec86c63b7e51) . It turns out that indeed Frescobaldi just invokes 'convert-ly' (with the absolute path, according to the current LilyPond version) without any notion of Python2/Python3. On Linux this is a shell script that explicitly starts the Python bundled with LilyPond, I don't know what exactly happens with this on Windows, but I think it *should* work, since it relies on what is bundled with LilyPond, not the Python3 from Frescobaldi. I think I'd need more information to give a better opinion. Best Urs One question: IIUC this should not only affect convert-ly, but also importing MusicXML, MIDI or ABC. Could someone check that, please? Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Frescobaldi] convert-ly don't work in 3.0.1 in Windows
Am 10.09.2018 um 19:07 schrieb Urs Liska:
Am 10. September 2018 18:29:32 MESZ schrieb Federico Bruni :
Hi Anders
I confirm the problem on Windows 7.
Detailed versions:
Frescobaldi: 3.0.1
Python: 3.5.2
python-ly: 0.9.4
Qt: 5.8.0
PyQt: 5.8.1
sip: 4.19.1
poppler: 0.52.0
python-poppler-qt: 0.24.2
OS: Windows-7-6.1.7601-SP1
I wonder if any Windows user using Frescobaldi 3 can confirm it. That's
why I've added lilypond-user in Cc.
My **guess** is that Frescobaldi is trying to use the bundled python3
to run convert-ly (which is a LilyPond file) and this is going to fail.
It does even on Linux:
$ python3 /usr/bin/convert-ly /home/fede/tmp/lilypond/converting.ly
Traceback (most recent call last):
File "/usr/bin/convert-ly", line 52, in
import lilylib as ly
File "/usr/share/lilypond/2.19.82/python/lilylib.py", line 238
print log[0]
^
SyntaxError: Missing parentheses in call to 'print'. Did you mean
print(log[0])?
The best fix would be make LilyPond convert-ly work on python3 as
well...
Even though Frescobaldi should handle better this kind of errors and at
least print some information instead of being silent.
This is exactly a spot I'm currently working on (how Frescobaldi handles
external jobs). I will have a look into how convert-ly is called too.
OK, I have put my hands on the code that calls convert-ly
(https://github.com/wbsoft/frescobaldi/commit/ab9cda16d96564a86fd2580c05d3ec86c63b7e51)
.
It turns out that indeed Frescobaldi just invokes 'convert-ly' (with the
absolute path, according to the current LilyPond version) without any
notion of Python2/Python3.
On Linux this is a shell script that explicitly starts the Python
bundled with LilyPond,
I don't know what exactly happens with this on Windows, but I think it
*should* work, since it relies on what is bundled with LilyPond, not the
Python3 from Frescobaldi.
I think I'd need more information to give a better opinion.
Best
Urs
Urs
Best
Federico
In the meanwhile, you may install the latest Python 2.7 (put a tick to
add python to PATH) and run convert-ly in PowerShell. See for example:
PS C:\Users\fede\Documents> python.exe 'C:\Program Files
(x86)\LilyPond\usr\bin\convert-ly.py' .\convert-test.ly
convert-ly.py (GNU LilyPond) 2.19.28
convert-ly.py: Processing `.\convert-test.ly'...
Applying conversion: 2.17.0, 2.17.4, 2.17.5, 2.17.6, 2.17.11, 2.17.14,
2.17.15, 2.17.18, 2.17.19, 2.17.20, 2.17.2
.27, 2.17.29, 2.17.97, 2.18.0, 2.19.2, 2.19.7, 2.19.11, 2.19.16,
2.19.22, 2.19.24, 2.19.28
\version "2.19.28"
{
\tuplet 3/2 { c8 d e }
}
Il giorno dom 9 set 2018 alle 9:36, andis.eriks...@gmail.com ha
scritto:
Hello,
I just updated from version 2 to the latest version 3 for Windows
(Frescobaldi.Setup.3.0.0-2.exe)
When I try to use convert-ly nothing happens!
The dialog shows up as usual, with the current version and the new
version, but that's it!
If I run convert.ly in the Lilypond bin directory then it works...
What's wrong?
// Anders
--
Frescobaldi homepage: http://www.frescobaldi.org/
Mailing list: http://groups.google.com/group/frescobaldi
Issue tracker: https://github.com/wbsoft/frescobaldi/issues
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Frescobaldi] convert-ly don't work in 3.0.1 in Windows
Am 10. September 2018 18:29:32 MESZ schrieb Federico Bruni :
>Hi Anders
>
>I confirm the problem on Windows 7.
>Detailed versions:
>
>Frescobaldi: 3.0.1
>Python: 3.5.2
>python-ly: 0.9.4
>Qt: 5.8.0
>PyQt: 5.8.1
>sip: 4.19.1
>poppler: 0.52.0
>python-poppler-qt: 0.24.2
>OS: Windows-7-6.1.7601-SP1
>
>I wonder if any Windows user using Frescobaldi 3 can confirm it. That's
>
>why I've added lilypond-user in Cc.
>
>My **guess** is that Frescobaldi is trying to use the bundled python3
>to run convert-ly (which is a LilyPond file) and this is going to fail.
>
>It does even on Linux:
>
>$ python3 /usr/bin/convert-ly /home/fede/tmp/lilypond/converting.ly
>Traceback (most recent call last):
> File "/usr/bin/convert-ly", line 52, in
>import lilylib as ly
> File "/usr/share/lilypond/2.19.82/python/lilylib.py", line 238
>print log[0]
>^
>SyntaxError: Missing parentheses in call to 'print'. Did you mean
>print(log[0])?
>
>The best fix would be make LilyPond convert-ly work on python3 as
>well...
>Even though Frescobaldi should handle better this kind of errors and at
>
>least print some information instead of being silent.
>
This is exactly a spot I'm currently working on (how Frescobaldi handles
external jobs). I will have a look into how convert-ly is called too.
Urs
>Best
>Federico
>
>In the meanwhile, you may install the latest Python 2.7 (put a tick to
>add python to PATH) and run convert-ly in PowerShell. See for example:
>
>
>PS C:\Users\fede\Documents> python.exe 'C:\Program Files
>(x86)\LilyPond\usr\bin\convert-ly.py' .\convert-test.ly
>convert-ly.py (GNU LilyPond) 2.19.28
>
>convert-ly.py: Processing `.\convert-test.ly'...
>Applying conversion: 2.17.0, 2.17.4, 2.17.5, 2.17.6, 2.17.11, 2.17.14,
>2.17.15, 2.17.18, 2.17.19, 2.17.20, 2.17.2
>.27, 2.17.29, 2.17.97, 2.18.0, 2.19.2, 2.19.7, 2.19.11, 2.19.16,
>2.19.22, 2.19.24, 2.19.28
>
>
>\version "2.19.28"
>
>{
> \tuplet 3/2 { c8 d e }
>
>}
>
>
>
>
>Il giorno dom 9 set 2018 alle 9:36, andis.eriks...@gmail.com ha
>scritto:
>> Hello,
>>
>> I just updated from version 2 to the latest version 3 for Windows
>> (Frescobaldi.Setup.3.0.0-2.exe)
>> When I try to use convert-ly nothing happens!
>>
>> The dialog shows up as usual, with the current version and the new
>> version, but that's it!
>>
>> If I run convert.ly in the Lilypond bin directory then it works...
>>
>>
>>
>> What's wrong?
>>
>> // Anders
>> --
>> Frescobaldi homepage: http://www.frescobaldi.org/
>> Mailing list: http://groups.google.com/group/frescobaldi
>> Issue tracker: https://github.com/wbsoft/frescobaldi/issues
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Frescobaldi] convert-ly don't work in 3.0.1 in Windows
Hi Anders
I confirm the problem on Windows 7.
Detailed versions:
Frescobaldi: 3.0.1
Python: 3.5.2
python-ly: 0.9.4
Qt: 5.8.0
PyQt: 5.8.1
sip: 4.19.1
poppler: 0.52.0
python-poppler-qt: 0.24.2
OS: Windows-7-6.1.7601-SP1
I wonder if any Windows user using Frescobaldi 3 can confirm it. That's
why I've added lilypond-user in Cc.
My **guess** is that Frescobaldi is trying to use the bundled python3
to run convert-ly (which is a LilyPond file) and this is going to fail.
It does even on Linux:
$ python3 /usr/bin/convert-ly /home/fede/tmp/lilypond/converting.ly
Traceback (most recent call last):
File "/usr/bin/convert-ly", line 52, in
import lilylib as ly
File "/usr/share/lilypond/2.19.82/python/lilylib.py", line 238
print log[0]
^
SyntaxError: Missing parentheses in call to 'print'. Did you mean
print(log[0])?
The best fix would be make LilyPond convert-ly work on python3 as
well...
Even though Frescobaldi should handle better this kind of errors and at
least print some information instead of being silent.
Best
Federico
In the meanwhile, you may install the latest Python 2.7 (put a tick to
add python to PATH) and run convert-ly in PowerShell. See for example:
PS C:\Users\fede\Documents> python.exe 'C:\Program Files
(x86)\LilyPond\usr\bin\convert-ly.py' .\convert-test.ly
convert-ly.py (GNU LilyPond) 2.19.28
convert-ly.py: Processing `.\convert-test.ly'...
Applying conversion: 2.17.0, 2.17.4, 2.17.5, 2.17.6, 2.17.11, 2.17.14,
2.17.15, 2.17.18, 2.17.19, 2.17.20, 2.17.2
.27, 2.17.29, 2.17.97, 2.18.0, 2.19.2, 2.19.7, 2.19.11, 2.19.16,
2.19.22, 2.19.24, 2.19.28
\version "2.19.28"
{
\tuplet 3/2 { c8 d e }
}
Il giorno dom 9 set 2018 alle 9:36, andis.eriks...@gmail.com ha scritto:
Hello,
I just updated from version 2 to the latest version 3 for Windows
(Frescobaldi.Setup.3.0.0-2.exe)
When I try to use convert-ly nothing happens!
The dialog shows up as usual, with the current version and the new
version, but that's it!
If I run convert.ly in the Lilypond bin directory then it works...
What's wrong?
// Anders
--
Frescobaldi homepage: http://www.frescobaldi.org/
Mailing list: http://groups.google.com/group/frescobaldi
Issue tracker: https://github.com/wbsoft/frescobaldi/issues
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
