title: Pyinstaller with pipenv
body: <p>So this is my first time trying to build a python project (using pyinstaller in this case). I use pipenv for managing my packages, but it looks like there may be some fundamental issues between the distribution of python I'm using and pyinstaller.</p>
  
  <p>I installed pyinstaller into my environment with <code>$ pipenv install --dev pyinstaller</code>.</p>
  
  <p>Running <code>$ pipenv run pyinstaller src/game.py</code> then yields:</p>
  
  <pre class="lang-none prettyprint-override"><code>OSError: Python library not found: .Python, libpython3.8m.dylib, libpython3.8.dylib, Python
      This would mean your Python installation doesn't come with proper library files.
      This usually happens by missing development package, or unsuitable build parameters of Python installation.
  
      * On Debian/Ubuntu, you would need to install Python development packages
        * apt-get install python3-dev
        * apt-get install python-dev
      * If you're building Python by yourself, please rebuild your Python with `--enable-shared` (or, `--enable-framework` on Darwin)
  </code></pre>
  
  <p>The issue seems to be that I'm not using a "shared"/"framework" version of python.</p>
  
  <p><a href="https://stackoverflow.com/questions/58548730/how-to-use-pyinstaller-with-pipenv-pyenv">How to use pyinstaller with pipenv / pyenv</a> offers a potential solution, but I'm not understanding why I'd need to move from pipenv to pyenv for this case.</p>
  
  <p>Is there a way to get pipenv to use a shared version of python? Is there a fundamental concept of pipenv that I'm misunderstanding that would make this incompatible with pyinstaller?</p>