title: Matplotlib Version
body: <p>Having my system prepped with homebrew and using <code>pip install matplotlib</code> after successful installation of numpy and scipy, I'm getting a successful installation. Then, running </p>
  
  <pre><code>$ python
  Python 2.7.6 (default, Jan 30 2014, 20:19:23) 
  [GCC 4.2.1 Compatible Apple LLVM 5.0 (clang-500.2.79)] on darwin
  Type "help", "copyright", "credits" or "license" for more information.
  &gt;&gt;&gt; import matplotlib
  &gt;&gt;&gt; matplotlib.__version__
  '1.1.1'
  </code></pre>
  
  <p>This is a very outdated version and noone of my programs run with it. I used <code>pip uninstall matplotlib</code> and redid it with <code>pip install 'the url for 1.3.1'</code> and it still reads version 1.1.1. Is there a way I can manually delete all python libraries, even python itself, and restart from scratch? Or is this an obvious fix for this?</p>
  
  <p>EDIT: I'm running Mac OS X version 10.9. I just reinstalled python 2.7 with scipy, numpy, and matplotlib through macports. Is there a very basic way to see where, when I <code>import matplotlib</code> from the python environment, it is calling it from? Like <code>which</code> in the terminal? I began using homebrew but switched to macports for more control. Can that be a problem? Do I need to completely remove homebrew?</p>
  
  <p>I did get this message at first:
  <code>Warning: Error parsing file /Applications/MacPorts/Python 2.7/Python Launcher.app/Contents/MacOS/Python Launcher: Error opening or reading file</code> but after running <code>$ sudo port -f deactivate python27</code> followed by <code>sudo port activate python27</code> I no longer have that warning, but I wanted to include this detail for completeness. </p>
  
  <p>EDIT 2: Could some things be installing to <code>opt/local/bin</code> when they need to be installed to <code>usr/local/bin</code>?</p>
  
  <p>EDIT 3: To shed some light on this, <code>print scipy.__version__</code> reads <code>0.11.0</code> which is several outdated, <code>print numpy.__version__</code> reads <code>1.6.2</code> which is also outdated. However I attempt to  install says the installation was successful, which I don't doubt. I suspect it's not linked up together in a correct way. Is there a way delete everything that is connected to python at all and restart? </p>
  
  <p>FINAL EDIT: I think the easiest way to handle this is to run <code>which python</code> and see what options you have to run python. Because I used homebrew and macports at this time (not recommended) I had four options- a macports install, a package install from python.org, a homebrew install, and the standard 2.6 from Apple. Iterate through these and find which one your installer (<code>pip</code> or <code>easy_install</code>) is placing your frameworks and run that python when you need certain dependencies. The best way is use only one package manager and run virtual environments if you need different dependencies, but we're all learning as we go.</p>