From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?YWzDrXJpbyBleW5n?= Subject: Re: [PATCH] gnu: font-gnu-freefont-ttf: Update to 20120503 and build from source. Date: Sat, 2 Apr 2016 10:38:15 +0000 Message-ID: References: <87k2kmn2jk.fsf@member.fsf.org> <87a8lfdr4q.fsf@gnu.org> <20160402033945.3ed65094@openmailbox.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55898) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1amIwb-0007OW-V9 for guix-devel@gnu.org; Sat, 02 Apr 2016 06:38:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1amIwb-0007qw-1F for guix-devel@gnu.org; Sat, 02 Apr 2016 06:38:17 -0400 Received: from mail-lf0-x242.google.com ([2a00:1450:4010:c07::242]:36092) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1amIwa-0007qs-Ot for guix-devel@gnu.org; Sat, 02 Apr 2016 06:38:16 -0400 Received: by mail-lf0-x242.google.com with SMTP id p81so8571716lfb.3 for ; Sat, 02 Apr 2016 03:38:16 -0700 (PDT) In-Reply-To: <20160402033945.3ed65094@openmailbox.org> 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-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: ericbavier@openmailbox.org Cc: guix-devel@gnu.org On 4/2/16, Eric Bavier wrote: > It often appears that in trivial scripts it is simply the 'print' > syntax that causes breakage between python2 and 3. and you trivially fix it with 2to3 command > while packaging the fantasque-sans font, I found that it requires > fontforge with python2 (because of print syntax, ugh). [1] uses obsolete print statement, i think it isn't needed to build [2] uses print function > do we really want > python3 for fontforge if their documentation is introducing users to > python2 syntax and many font packages need python2? making people downgrade to python2 isn't nice[3] "many font packages need python2" is questionable, freefont should support python3 in next release, i think you can _build_ fantasque-sans with python3 > Perhaps we leave python3 in the user-installable fontforge, but have a > private python2 variant for building fonts when necessary? What do > others think? ok the ideal would be to make a font-build-system so we could use the isMonoMono.py from freefont to validate all mono fonts; and the build system would have the right python, not individual fonts the problem with fantasque-sans is they have python code embedded in bash, so i think 2to3 won't work freefont had nontrivial code 2to3 can't convert [1]https://github.com/belluzj/fantasque-sans/blob/master/fontdiff [2]https://github.com/belluzj/fantasque-sans/blob/master/validate-generate [3]https://github.com/ncraun/smoothscan/issues/3#issuecomment-24867766