From: "alírio eyng" <alirioeyng@gmail.com>
To: ludo@gnu.org
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: font-gnu-freefont-ttf: Update to 20120503 and build from source.
Date: Mon, 4 Apr 2016 14:19:21 +0000 [thread overview]
Message-ID: <CALkz57EOLodCY+5WDN8-N1pRERF=4nyT0Y1E53VbV_jxmRZKLA@mail.gmail.com> (raw)
In-Reply-To: <87a8la9xgc.fsf@gnu.org>
On 4/3/16, Ludovic Courtès <ludo@gnu.org> wrote:
> alírio eyng <alirioeyng@gmail.com> skribis:
>> On 4/2/16, Eric Bavier <ericbavier@openmailbox.org> wrote:
>>> do we really want
>>> python3 for fontforge if their documentation is introducing users to
>>> python2 syntax and many font packages need python2?
...
> I think we should stay close to what Fontforge developers recommend.
following upstream is good.[1]
i don't think old documentation[2][3] last modified more than five
years ago and created before python3 was released is a recommendation.
[1]"Python 2.x is legacy, Python 3.x is the present and future of the language"
https://wiki.python.org/moin/Python2orPython3
[2]"Created on: 29-Nov-2006"
"Last modified: 30-Nov-2006"
https://github.com/fontforge/fontforge.github.io/blob/master/pythonscripts.html
[3]"Created on: 6-Apr-2007"
"Last modified: 28-Apr-2010"
https://github.com/fontforge/fontforge.github.io/blob/master/python.html
prev parent reply other threads:[~2016-04-04 14:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-26 14:47 [PATCH] gnu: font-gnu-freefont-ttf: Update to 20120503 and build from source alírio eyng
2016-03-28 13:40 ` 宋文武
2016-03-29 3:38 ` alírio eyng
2016-03-31 7:48 ` Ludovic Courtès
2016-03-31 13:18 ` alírio eyng
2016-03-31 21:45 ` Ludovic Courtès
2016-04-02 8:39 ` Eric Bavier
2016-04-02 10:38 ` alírio eyng
2016-04-03 21:47 ` Ludovic Courtès
2016-04-04 14:19 ` alírio eyng [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALkz57EOLodCY+5WDN8-N1pRERF=4nyT0Y1E53VbV_jxmRZKLA@mail.gmail.com' \
--to=alirioeyng@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.