Re: python: fix installation of .py files when building in separate dir (issue 549810043 by hanw...@gmail.com)

I could probably be happy with the following: diff --git a/make/lilypond-vars.make b/make/lilypond-vars.make index 3f1e992626..3ac59f19a4 100644 --- a/make/lilypond-vars.make +++ b/make/lilypond-vars.make @@ -18,6 +18,8 @@ endif LANGS=$(shell $(PYTHON) $(top-src-dir)/python/langdefs.py) export

Re: python: fix installation of .py files when building in separate dir (issue 549810043 by hanw...@gmail.com)

On 2020/04/06 19:51:11, hanwenn wrote: > suppress __pycache__ The suppression only works for the test. Running a full build still gives me python/__pycache__/ in the source directory because PYTHONPATH points there. https://codereview.appspot.com/549810043/

Re: Install python modules from build directory (issue 575960043 by jonas.hahnf...@gmail.com)

https://codereview.appspot.com/575960043/diff/557650043/make/lilypond-vars.make File make/lilypond-vars.make (right): https://codereview.appspot.com/575960043/diff/557650043/make/lilypond-vars.make#newcode20 make/lilypond-vars.make:20: export

Re: Install python modules from build directory (issue 575960043 by jonas.hahnf...@gmail.com)

https://codereview.appspot.com/575960043/diff/557650043/make/lilypond-vars.make File make/lilypond-vars.make (right): https://codereview.appspot.com/575960043/diff/557650043/make/lilypond-vars.make#newcode20 make/lilypond-vars.make:20: export

Re: GUB failure

I bit the bullet and started the upgrade to 16.04. I check that's OK then consider 18.04 later. Upgrading via the GUI software updater. -- Phil Holmes - Original Message - From: "Thomas Morley" To: "Phil Holmes" Cc: "David Kastrup" ; "Devel" Sent: Monday, April 06, 2020 4:18 PM

Re: GUB failure

Am Mo., 6. Apr. 2020 um 16:52 Uhr schrieb Phil Holmes : > > As predicted, GUB has failed to build on my system. The error message shows > that it's because I have Python 3.4.3 and I need at least 3.5. If anyone > knows how to upgrade my Ubuntu 14 machine to the later Python version, > please

Re: GUB failure

On Mon, Apr 6, 2020 at 11:52 PM Phil Holmes wrote: > If anyone knows how to upgrade my Ubuntu 14 machine to the later Python > version, > please say. You can use the deadsnakes ppa (fkrull/deadsnakes for pre Ubuntu-16.04,

Re: GUB failure

"Phil Holmes" writes: > As predicted, GUB has failed to build on my system. The error message > shows that it's because I have Python 3.4.3 and I need at least 3.5. > If anyone knows how to upgrade my Ubuntu 14 machine to the later > Python version, please say. Otherwise I'll have to upgrade

GUB failure

As predicted, GUB has failed to build on my system. The error message shows that it's because I have Python 3.4.3 and I need at least 3.5. If anyone knows how to upgrade my Ubuntu 14 machine to the later Python version, please say. Otherwise I'll have to upgrade to Ubuntu 16, which I was

Re: Problem with LSR import

> (btw, the html->texinfo conversion doesn’t appear to turn into > @itemize bullet as it ideally ought to.) If time permits I'll continue work on my LSR import script that I've already posted to the list. It uses `pandoc` for the HTML to texinfo conversion, which seems to work quite well.

Re: Fix line comments for new snippets (issue 549820043 by d...@gnu.org)

> I'd rather not have 2.21.0 in a state inconsistent > with its makelsr program. So if I were to push, > I'd need to push the results of a new makelsr run > as well. OK, I misunderstood. https://codereview.appspot.com/549820043/

Re: Fix line comments for new snippets (issue 549820043 by d...@gnu.org)

Reviewers: lemzwerg, Message: On 2020/04/06 12:40:50, lemzwerg wrote: > LGTM, and please push directly. I'd rather not have 2.21.0 in a state inconsistent with its makelsr program. So if I were to push, I'd need to push the results of a new makelsr run as well. Description: Fix line comments

Fix line comments for new snippets (issue 549820043 by d...@gnu.org)

LGTM, and please push directly. https://codereview.appspot.com/549820043/

Re: Problem with LSR import

Valentin Villenave writes: > On 4/5/20, David Kastrup wrote: >> Valentin Villenave writes: >>> It should be available in the next LSR database dump (but there’s at >>> least one file in the Japanese version that depends on it, so the name >>> will need to be updated there as well). >> >>

Re: Problem with LSR import

On 4/5/20, David Kastrup wrote: > Valentin Villenave writes: >> It should be available in the next LSR database dump (but there’s at >> least one file in the Japanese version that depends on it, so the name >> will need to be updated there as well). > > Thanks! David, I hope it’s OK if I push