Re: check_translation crashes
Am Freitag, den 13.03.2020, 19:50 +0100 schrieb Francisco Vila: > El 8/3/20 a las 18:33, Jonas Hahnfeld escribió: > > Am Sonntag, den 08.03.2020, 18:29 +0100 schrieb Jean-Charles > > Malahieude: > > > Le 08/03/2020 à 18:16, Jonas Hahnfeld a écrit : > > > > Am Samstag, den 07.03.2020, 11:27 +0100 schrieb Jean-Charles > > > > Malahieude: > > > > > Hi all, > > > > > > > > > > As I'm done with the French translations for 2.20, I'd like to now > > > > > take > > > > > care of 2.21 but… my workflow is now broken and I'm not able to > > > > > diagnose > > > > > what's wrong. The only change in the body of check_translation.py > > > > > since > > > > > 2009 has been introduced with issue 5646. A "python --version" gives > > > > > 3.7.6. > > > > > > > > Yes, that's fallout from the switch to Python 3 please apply the one > > > > -liner from > > > > https://sourceforge.net/p/testlilyissues/issues/5838/ > > > > > > > > . If > > > > that also works on your system, I'll likely super-fast-track this. > > > > > > > > > > YES! works like a charm! 187 Ko like the one Franciso sent me privately > > > yesterday night. > > > > > > It might be useful in other places as well, I don't know. > > > > What do you mean? I hope I got most other scripts covered. Please let > > me know if I missed other as well. > > > > Jonas > > > > Now it crashes for me. > > $ python --version > Python 2.7.16 > > $ python3 --version > Python 3.7.3 > > Now the script sees $(PYTHON) as python2 > > [...] > > But if I force python3 here, it works. > > How to make python3 the default for all lilypond build? `configure' from master requires python3. Are you sure that you regenerated it and are not running with something from stable/2.20? Jonas signature.asc Description: This is a digitally signed message part
Re: check_translation crashes
El 8/3/20 a las 18:33, Jonas Hahnfeld escribió: Am Sonntag, den 08.03.2020, 18:29 +0100 schrieb Jean-Charles Malahieude: Le 08/03/2020 à 18:16, Jonas Hahnfeld a écrit : Am Samstag, den 07.03.2020, 11:27 +0100 schrieb Jean-Charles Malahieude: Hi all, As I'm done with the French translations for 2.20, I'd like to now take care of 2.21 but… my workflow is now broken and I'm not able to diagnose what's wrong. The only change in the body of check_translation.py since 2009 has been introduced with issue 5646. A "python --version" gives 3.7.6. Yes, that's fallout from the switch to Python 3 please apply the one -liner from https://sourceforge.net/p/testlilyissues/issues/5838/ . If that also works on your system, I'll likely super-fast-track this. YES! works like a charm! 187 Ko like the one Franciso sent me privately yesterday night. It might be useful in other places as well, I don't know. What do you mean? I hope I got most other scripts covered. Please let me know if I missed other as well. Jonas Now it crashes for me. $ python --version Python 2.7.16 $ python3 --version Python 3.7.3 Now the script sees $(PYTHON) as python2 Traceback (most recent call last): File "/home/fravd/source/lilypond/scripts/auxiliar/check_translation.py", line 168, in main () File "/home/fravd/source/lilypond/scripts/auxiliar/check_translation.py", line 165, in main do_file (i, list(langdefs.LANGDICT.keys ())) File "/home/fravd/source/lilypond/scripts/auxiliar/check_translation.py", line 96, in do_file sys.stdout.write (diff_string) UnicodeEncodeError: 'ascii' codec can't encode character u'\xe0' in position 1941: ordinal not in range(128) make: *** [GNUmakefile:393: check-translation] Error 1 But if I force python3 here, it works. How to make python3 the default for all lilypond build? -- Francisco Vila, Ph.D. - Badajoz (Spain) paconet.org , lilypond.es
Re: check_translation crashes
On 08/03/2020 18:22, Jonas Hahnfeld wrote: Am Sonntag, den 08.03.2020, 19:05 +0100 schrieb Jean-Charles Malahieude: Le 08/03/2020 à 18:33, Jonas Hahnfeld a écrit : Am Sonntag, den 08.03.2020, 18:29 +0100 schrieb Jean-Charles Malahieude: It might be useful in other places as well, I don't know. What do you mean? I hope I got most other scripts covered. Please let me know if I missed other as well. It's just that I now see some python files with a line "# -*- coding: utf-8 -*-" and some other without. But I don't know the implications. It's only for editors (emacs, vim), not relevant during execution. So I've pushed the one-liner to staging and it should appear in master soon. Not sure how it gets to the translation branch though... Jonas I've started a patchy merge now. Assuming all goes well it should be pushed in the next 20 mins. James
Re: check_translation crashes
Am Sonntag, den 08.03.2020, 19:05 +0100 schrieb Jean-Charles Malahieude: > Le 08/03/2020 à 18:33, Jonas Hahnfeld a écrit : > > Am Sonntag, den 08.03.2020, 18:29 +0100 schrieb Jean-Charles > > Malahieude: > > > It might be useful in other places as well, I don't know. > > > > What do you mean? I hope I got most other scripts covered. Please let > > me know if I missed other as well. > > > > It's just that I now see some python files with a line "# -*- coding: > utf-8 -*-" and some other without. But I don't know the implications. It's only for editors (emacs, vim), not relevant during execution. So I've pushed the one-liner to staging and it should appear in master soon. Not sure how it gets to the translation branch though... Jonas signature.asc Description: This is a digitally signed message part
Re: check_translation crashes
Le 08/03/2020 à 18:33, Jonas Hahnfeld a écrit : Am Sonntag, den 08.03.2020, 18:29 +0100 schrieb Jean-Charles Malahieude: It might be useful in other places as well, I don't know. What do you mean? I hope I got most other scripts covered. Please let me know if I missed other as well. It's just that I now see some python files with a line "# -*- coding: utf-8 -*-" and some other without. But I don't know the implications. Cheers, -- Jean-Charles
Re: check_translation crashes
Am Sonntag, den 08.03.2020, 18:29 +0100 schrieb Jean-Charles Malahieude: > Le 08/03/2020 à 18:16, Jonas Hahnfeld a écrit : > > Am Samstag, den 07.03.2020, 11:27 +0100 schrieb Jean-Charles > > Malahieude: > > > Hi all, > > > > > > As I'm done with the French translations for 2.20, I'd like to now take > > > care of 2.21 but… my workflow is now broken and I'm not able to diagnose > > > what's wrong. The only change in the body of check_translation.py since > > > 2009 has been introduced with issue 5646. A "python --version" gives > > > 3.7.6. > > > > Yes, that's fallout from the switch to Python 3 please apply the one > > -liner from > > https://sourceforge.net/p/testlilyissues/issues/5838/ > > . If > > that also works on your system, I'll likely super-fast-track this. > > > > YES! works like a charm! 187 Ko like the one Franciso sent me privately > yesterday night. > > It might be useful in other places as well, I don't know. What do you mean? I hope I got most other scripts covered. Please let me know if I missed other as well. Jonas signature.asc Description: This is a digitally signed message part
Re: check_translation crashes
Le 08/03/2020 à 18:16, Jonas Hahnfeld a écrit : Am Samstag, den 07.03.2020, 11:27 +0100 schrieb Jean-Charles Malahieude: Hi all, As I'm done with the French translations for 2.20, I'd like to now take care of 2.21 but… my workflow is now broken and I'm not able to diagnose what's wrong. The only change in the body of check_translation.py since 2009 has been introduced with issue 5646. A "python --version" gives 3.7.6. Yes, that's fallout from the switch to Python 3 please apply the one -liner from https://sourceforge.net/p/testlilyissues/issues/5838/. If that also works on your system, I'll likely super-fast-track this. YES! works like a charm! 187 Ko like the one Franciso sent me privately yesterday night. It might be useful in other places as well, I don't know. Thanks, -- Jean-Charles
Re: check_translation crashes
Am Samstag, den 07.03.2020, 11:27 +0100 schrieb Jean-Charles Malahieude: > Hi all, > > As I'm done with the French translations for 2.20, I'd like to now take > care of 2.21 but… my workflow is now broken and I'm not able to diagnose > what's wrong. The only change in the body of check_translation.py since > 2009 has been introduced with issue 5646. A "python --version" gives 3.7.6. Yes, that's fallout from the switch to Python 3 please apply the one -liner from https://sourceforge.net/p/testlilyissues/issues/5838/. If that also works on your system, I'll likely super-fast-track this. Jonas signature.asc Description: This is a digitally signed message part
check_translation crashes
Hi all, As I'm done with the French translations for 2.20, I'd like to now take care of 2.21 but… my workflow is now broken and I'm not able to diagnose what's wrong. The only change in the body of check_translation.py since 2009 has been introduced with issue 5646. A "python --version" gives 3.7.6. Here is the output on the transalation-staging branch (reflecting stable/2.20): -*- mode: compilation; default-directory: "~/GIT/Doc-Stable/Documentation/" -*- Compilation started at Sat Mar 7 10:48:28 make ISOLANG=fr NO_COLOR=1 check-translation > ../../chktrans langdefs.py: warning: lilypond-doc gettext domain not found. Compilation finished at Sat Mar 7 10:48:30 And on translation (reflecting master): -*- mode: compilation; default-directory: "~/GIT/Traduc/Documentation" -*- Compilation started at Sat Mar 7 10:14:19 make ISOLANG=fr NO_COLOR=1 check-translation > ../../chktrans Traceback (most recent call last): File "/home/jcharles/GIT/Traduc/scripts/auxiliar/check_translation.py", line 168, in main () File "/home/jcharles/GIT/Traduc/scripts/auxiliar/check_translation.py", line 165, in main do_file (i, list(langdefs.LANGDICT.keys ())) File "/home/jcharles/GIT/Traduc/scripts/auxiliar/check_translation.py", line 96, in do_file sys.stdout.write (diff_string) TypeError: write() argument must be str, not bytes make: *** [GNUmakefile:393: check-translation] Error 1 Compilation exited abnormally with code 2 at Sat Mar 7 10:14:19 Any help in resolving this will be really mostly appreciated. Cheers, -- Jean-Charles
