Making Python3 the default
T J <[email protected]> Sat, 1 Jun 2019 11:57:48 +0000
| Newsgroups | gmane.comp.fonts.fontforge.devel |
|---|---|
| Message-ID | <SYAPR01MB304004C13668E836D4448A08C21A0@SYAPR01MB3040.ausprd01.prod.outlook.com> |
--===============6490497827006125898==
Content-Language: en-AU
Content-Type: multipart/alternative;
boundary="_000_SYAPR01MB304004C13668E836D4448A08C21A0SYAPR01MB3040ausp_"
--_000_SYAPR01MB304004C13668E836D4448A08C21A0SYAPR01MB3040ausp_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Hi all,
With support for Python 2 dropping off, in the next release of FontForge, t=
he Windows build will use the Python 3 binding instead of the Python 2 bind=
ing, as it has used in the past.
It is likely that the Mac build will follow suit, but this will be decided =
closer to when the next release is cut.
With that, I=92d propose that the next release will be the last release tha=
t actually supports Python 2 (if only by compiling it yourself). From that =
point on, we should move towards removing Python 2 support altogether.
If you have any questions/comments/concerns on this, let me know.
Thanks,
Jeremy
--_000_SYAPR01MB304004C13668E836D4448A08C21A0SYAPR01MB3040ausp_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/of=
fice/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:"Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang=3D"EN-AU">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi all,</p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">With support for Python 2 dropping off, in the next =
release of FontForge, the Windows build will use the Python 3 binding inste=
ad of the Python 2 binding, as it has used in the past.</p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">It is likely that the Mac build will follow suit, bu=
t this will be decided closer to when the next release is cut.</p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">With that, I=92d propose that the next release will =
be the last release that actually supports Python 2 (if only by compiling i=
t yourself). From that point on, we should move towards removing Python 2 s=
upport altogether.</p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">If you have any questions/comments/concerns on this,=
let me know.</p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">Thanks,</p>
<p class=3D"MsoNormal">Jeremy</p>
</div>
</body>
</html>
--_000_SYAPR01MB304004C13668E836D4448A08C21A0SYAPR01MB3040ausp_--
--===============6490497827006125898==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
--===============6490497827006125898==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
fontforge-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html
--===============6490497827006125898==--