title: Python3 won't find a module even though it is properly installed
body: <p>I'm using a Python 3.6.7 venv and I have installed the <code>PyBluez</code> bluetooth library, in addition to ALL of its dependencies such as <code>sudo apt install bluetooth libbluetooth-dev python3-bluez</code> . When I run my python script, I'm getting:</p>
  
  <p>`ModuleNotFoundError: No module named 'bluetooth'</p>
  
  <p>The crazy part is that I've just checked my environment's <code>/lib/python3.6/site-packages/</code> directory and there is <strong><em>indeed</em></strong> directories entitled bluetooth and a PyBluez-0.22,egg-info.</p>
  
  <p>even still, when I go into the <code>bluetooth</code> directory, there is <strong><em>indeed</em></strong> a <code>ble.py</code> file, a <code>_bluetooth.cpython.so</code> file (name abbreviated), <strong>and</strong> a bluez.py, all with valid code in them. All dependencies were installed via <code>pip3 install</code> from within the virtual environment and even verified with <code>python3 -m pip install</code> to which python3 claimed they were already installed. Additionally, <code>ls -la</code> shows drwxrwxr-x just like every other dependency in the <code>site-packages</code> folder. What is the problem here?</p>
  
  <p>Note: I've also verified install with <code>pip3 list</code> from inside the venv.</p>
  
  <p>Note2: Visual Studio Code seems to not be able to locate the modules... They are underlined in red and pylint extension says <code>unable to import [modulename]</code>. This is only true for modules installed in the venv. This may just be an error with pylint extension searching the system libs rather than my vent's libs... Not a big deal.</p>