Re: [fontforge-devel] Making Python3 the default

[T J <jt...@ou...>]

Hi Abraham,

Unfortunately not yet. I have some build system overhaul changes planned, but that is still a way off. With that, I am hoping it will be easier to target compiling against the ‘native’ Python Windows installation, which will allow what you are wishing for.

Thanks,
Jeremy
From: Abraham Lee<mailto:tis...@gm...>
Sent: Sunday, 2 June 2019 6:17 AM
To: FontForge developers' discussions<mailto:fon...@li...>
Subject: Re: [fontforge-devel] Making Python3 the default

Hey, Jeremy!

On Sat, Jun 1, 2019 at 5:58 AM T J <jt...@ou...<mailto:jt...@ou...>> wrote:
With support for Python 2 dropping off, in the next release of FontForge, the Windows build will use the Python 3 binding instead of the Python 2 binding, as it has used in the past.

I was thinking about this lately. Thanks for taking the initiative to make this happen. Will the change allow for a more “native” state? Meaning, will it make it easier to use external packages, installed via pip or otherwise? And being able to use other graphics packages (like tcl, wx, etc.) would be really nice to do.

Thanks for all you do!

Best,
Abraham