@sgillies I asked this in a moment of extreme vexation a few months ago. I think @llimllib actually answered it for me and it made sense in Homebrew-logic (I have since stopped using Homebrew to manage both npm and Python)

@sgillies There has to be a way to have Homebrew point to an existing Python executable path so it doesn't insist on installing its own when it's in the dependency tree of a package you `brew install`.

I use `asdf` myself to manage node, python, ruby and other environments.