title: Why are pip packages not installed to $PATH to by default?
body: <p>Typically when using <code>rubygems</code> in the <code>ruby</code> ecosystem or <code>npm</code>/<code>yarn</code> in the JavaScript ecosystem packages are installed somewhere on the <code>$PATH</code> or at least you are instructed to add the package install location to your path <code>$PATH</code>.</p>
  
  <p>It seems like with <code>pip</code> in the <code>python</code> ecosystem there is never an emphasis on this. Instead, you are encouraged to run modules via <code>python -m &lt;name&gt;</code>, etc.</p>
  
  <p>Seems a bit odd to me, was this just a design decision? Is it good practice to put <code>site-packages</code> or whatever location <code>pip</code> is using into <code>$PATH</code>? Sometimes a binary is added to <code>/usr/local/bin</code> (and sometimes with a different name than the package itself e.g <code>django-admin</code> instead of <code>django</code> with <code>pip install Django</code> whereas the binary is usually the same as the package name in <code>ruby</code>/JavaScript ecosystems), for example, I see, but is that all of the time?</p>