Quote:
Originally Posted by Doitsu
If the developer stop posting .whl files on Github, I'll simply web scrape the fontTools PyPi.org page.
|
Probably easiest.
After a quick glance: they're definitely building a wheel as part of their Travis CI automation (which in turn is automatically creating the Github release), but they must have started cleaning it up after the automated upload to PyPi. *shrug*
The good news is that they look fully automated, now. Commits tagged for Release should automatically trigger both a new Github release and a new version uploaded to PyPi. So there should be very little (if any) lag between the Github and PyPi versions of fontTools from now on (the github release date and the pypi release date of 3.32.0 are indeed one and the same). That should make it easier on you. Good luck!