search

rougier / freetype-py

Python binding for the freetype library
Other
298 stars 88 forks source link

Drop Python 2.7 and 32 bit builds? #109

Closed madig closed 4 years ago

madig commented 5 years ago

Seeing that Python 2.x is nearing its official death, how about we just drop official builds for it? I currently see no need to convert the source to Python-3-only, but dropping 2.7 builds would simplify the build matrix.

We could also drop 32 bit builds entirely, although I think they are only relevant on Windows. Python.org still points people to 32 bit Python I think.

rougier commented 5 years ago

I suspect there are still plenty of systems around still using Python 2.x but it is probably unlikely they use freetype. For 32 bits, I'm not sure I understand your explanation on Python.org and windows.

HinTak commented 5 years ago

Python windows is 32-bit, that's what madig means. (many windows software don't see the need of a slower/buggy 64-bit build...)

madig commented 4 years ago

If we drop 2.7 and make 3.6 the minimum, I can update the bundled FreeType and HarfBuzz, as HarfBuzz only makes xz tarballs for new releases :)

The plan:

  1. Drop 32 bit builds completely for all platforms -- note that people can still take the sdist and make bwheels for themselves.
  2. Drop Python 2 support, make 3.6 the minimum.

I don't plan on making sweeping changes for this, just drop support and use new 3.6 features where it makes sense.

josh-hadley commented 4 years ago

I think it would be great to drop the Python 2.7 anchor and move on. As long as the older releases are kept available for those unfortunate folks who are somehow still unable to move to Python 3, I see no compelling reason for new releases to support Python 2.7, or anything less than Python 3.5 (or, even better, 3.6 as @madig mentions, since 3.5 is already in "security fixes only mode" and will be EOL in September of 2020).

rougier commented 4 years ago

Ok for me then.

madig commented 4 years ago

Done.