Gammel Holte transcribed 2.0K bytes:
> On Fri, Dec 22, 2017 at 7:42 PM, ng0 <ng0@n0.is> wrote:
> 
> Thanks for your comments. I will address those before I circulate a patch.
> 
> > Is this python-2 only? If not, could you explain why you picked 2 and not
> 3
> > (2 is on its way out in 20 months).
> 
> LyX is sadly not ready for Python 3 yet. It will be soon, but there are
> still
> tickets open to support it: https://www.lyx.org/trac/ticket/9006
> 
> Furthermore, I've tested LyX with Python 3 and it breaks.

Okay, no problem.

> Any hints on how to wrap the LyX package output so that it binds to the
> Python input, instead of looking for it at runtime, like the Nix package
> does?
> 
> https://github.com/NixOS/nixpkgs/blob/86da6d441f7a248b02d545ac1b2c90ef27f42d0b/pkgs/applications/misc/lyx/default.nix

It depends. I have no time to look at the code (to see where python
is required, how much of it (modules etc)), but we have multiple
options, including:

1. Wrap the program. One of many examples:
   https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/gnuzilla.scm#n759
2. patch calls of 'python' to the gnu-store python executable. I can see this
   failing if python modules are required to be present and not just python.
3. Search for 'wrap' in the source checkout of Guix. You will find commits like
   0498d24866c4955faee95a4fc19ff6817e5483d2 
  (https://git.savannah.gnu.org/cgit/guix.git/commit/gnu/packages?id=0498d24866c4955faee95a4fc19ff6817e5483d2)

-- 
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://c.n0.is/ng0_pubkeys/tree/keys
  WWW: https://n0.is