guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] gnu: font-gnu-freefont-ttf: Update to 20120503 and build fro


From: Eric Bavier
Subject: Re: [PATCH] gnu: font-gnu-freefont-ttf: Update to 20120503 and build from source.
Date: Sat, 2 Apr 2016 03:39:45 -0500

On Thu, 31 Mar 2016 13:18:06 +0000
alírio eyng <address@hidden> wrote:

> reiterating for the list
> On 3/31/16, Ludovic Courtès <address@hidden> wrote:
> > I understand cannot support Python 2 and 3 simultaneously, but I think
> > Leo was suggesting changing the ‘fontforge’ package to use Python 2.x
> > instead of 3.x.  WDYT?  
> python 2 has a end of life determined, 2020,
> https://www.python.org/dev/peps/pep-0373/
> so the default should be python 3

It often appears that in trivial scripts it is simply the 'print'
syntax that causes breakage between python2 and 3.  FontForge's
documentation/examples seems to use the python2 print syntax.  Also,
while packaging the fantasque-sans font, I found that it requires
fontforge with python2 (because of print syntax, ugh).

While I support moving things forward for python3, do we really want
python3 for fontforge if their documentation is introducing users to
python2 syntax and many font packages need python2?

Perhaps we leave python3 in the user-installable fontforge, but have a
private python2 variant for building fonts when necessary?  What do
others think?

`~Eric



reply via email to

[Prev in Thread] Current Thread [Next in Thread]