Better Homebrew fix: Just symlink our bindings into our vendor tree.

Homebrew reserves the right to decide on the fly which copy of the
Python 2.7 interpreter (Apple's or Homebrew's) we should be using.
This is mostly reasonable, but makes it tricky when a Homebrew package
includes both a Python "application" and Python "bindings", because
the bindings may be installed where the script doesn't see them.  So
we symlink the bindings into the application's private library tree,
just as if the bindings were a third-party library our application
needed.  Silly, but it works (this week).

0 files changed, 0 insertions, 0 deletions