title: Why Should Homebrew be used to Install Python?
body: <p>I have been reading a lot of the tutorials around the web and answers on the site about using <code>Homebrew</code>. When it comes to <code>Python</code> though, the advice leaves me with more questions than answers.</p>
  
  <p>I understand the how, but none of the answers I have seen so far have really explained the why behind using <code>Homebrew</code> to install <code>Python</code> and what the benefits are to installing <code>Python</code> with <code>Homebrew</code> as opposed to using <code>OS-X</code> installers provided by the Python Foundation? </p>
  
  <p>The newest versions of the installers from Python and the current implementation of <code>PIP</code> seem to be working pretty well, so I would really appreciate any input on my question. I have worked with Python for a while but from more of a tactical, one off problem solving perspective and I am brand new to tools like <code>Brew</code> and version control software such as <code>Git</code>. I am trying to get up the learning curve. Finding an answer to why I would choose to go with a <code>Homebrew</code> install over just heading over to python.org and downloading from them and then using pip to install packages might help me to understand the benefits of a tool like <code>Homebrew</code>.</p>
  
  <p>So I guess, what does <code>Homebrew</code> give me that going through the installation put in place by TPF does not? </p>
  
  <p>Are there advantages/disadvantages to where <code>Homebrew</code> installs <code>Python</code> and Python packages over  the <code>/Library/Frameworks/</code> and the <code>site-packages</code> folder within that framework?</p>
  
  <p>Though this last question is too broad and likely out of scope, if anyone would also address or provide a link to a good answer on what the benefits are of using <code>Homebrew</code> in general, I'd appreciate it?</p>
  
  <p>Thank you, </p>