From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gammel Holte Subject: Re: Packaging LyX Date: Fri, 22 Dec 2017 23:49:08 +0100 Message-ID: References: <20171222184231.an2qywtr4ilmcqb5@abyayala> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="089e0826a420e5c2770560f59f28" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46579) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eSW7r-0007ZE-NZ for guix-devel@gnu.org; Fri, 22 Dec 2017 17:49:12 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eSW7q-0006Nx-LX for guix-devel@gnu.org; Fri, 22 Dec 2017 17:49:11 -0500 Received: from mail-qt0-x231.google.com ([2607:f8b0:400d:c0d::231]:37519) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eSW7q-0006Nh-GX for guix-devel@gnu.org; Fri, 22 Dec 2017 17:49:10 -0500 Received: by mail-qt0-x231.google.com with SMTP id f2so37941329qtj.4 for ; Fri, 22 Dec 2017 14:49:10 -0800 (PST) In-Reply-To: <20171222184231.an2qywtr4ilmcqb5@abyayala> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org, ng0 --089e0826a420e5c2770560f59f28 Content-Type: text/plain; charset="UTF-8" On Fri, Dec 22, 2017 at 7:42 PM, ng0 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. 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 --089e0826a420e5c2770560f59f28 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Dec 22, 2017 at 7:42 PM, ng0 <ng0@n0.is> wrote:

Thanks for your comm= ents. 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 no= t ready for Python 3 yet. It will be soon, but there are still
tickets o= pen to support it: https:/= /www.lyx.org/trac/ticket/9006

Furthermore, I've t= ested LyX with Python 3 and it breaks.

Any hin= ts 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
=
--089e0826a420e5c2770560f59f28--