Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Improve installation instructions

See original GitHub issue

I tried to follow the instructions at https://github.com/googlefonts/fontbakery#mac-os-x and found that

fontforge brew script no longer has a --HEAD option
fontbakery’s pypi package is very old and needs to be updated
when I installed with pip install . then I got no executables in my PATH, so I wasn’t able to run anythign

Would be great to fix this before 0.3.3

Issue Analytics

State:
Created 6 years ago
Comments:30 (29 by maintainers)

Top GitHub Comments

1reaction

anthrotypecommented, Mar 6, 2018

2.7.5 is ancient. Do it a favour, leave the system python alone, just brew install python2 to get a recent python2.7 with all the latest bug fixes and security patches, pip preinstalled and up to date, and proceed from there with the setup.

0reactions

anthrotypecommented, Mar 6, 2018

I was running Maverick when I did all the commands reported above. Then I noticed I was running an old mac os release, so I installed the upgrade to High Sierra. Even after upgrading I still got the same versions of python 2.7.5

That’s very weird. I don’t have my mac here with me, but I’m pretty sure /usr/bin/python --version returns “2.7.10”, not “2.7.5”. Something may have gone wrong with your upgrade from Mavericks (10.9) to High Sierra (10.13).

I googled around and I found several places that confirm High Sierra ships with 2.7.10, not 2.7.5. Here’s one link: https://forums.developer.apple.com/thread/78891