title: No module named contextlib? in a virtualenv?
body: <p>I have a virtualenv that is being used on multiple machines, through dropbox. Our dropboxes are all syncing to the same spot, (or at least symlinking so it appears thus) so, the relocation issues should be moot.</p>
  
  <p>On my machine, everything works fine. I can create a virtualenv and it works fine. However, when someone else uses it, python gives <code>No module named contextlib</code></p>
  
  <p>When I create the virtualenv on the other person's computer, it appears to work on mine (I haven't tested exhaustively) </p>
  
  <p>All computers are macs. Mine is running High Sierra, everyone else's is running Mojave, in case that matters.</p>
  
  <p>How do I solve this problem? or at least, what is causing it?</p>
  
  <p>I've seen <a href="https://stackoverflow.com/questions/5520515/python-no-module-named-contextlib">Python: No module named contextlib?</a>, but that seems to be an unrelated issue on embedded hardware.</p>
  
  <p>NOTE: I understand that python thinks I shouldn't be doing this. However, I have a user base who are NOT programmers. They cannot manage their own venvs. They cannot handle complicated docker stuff. They want to type <code>python foo.py</code> and just have it work. In the past, I've gotten this to work with venvs. </p>
  
  <p>If python can't handle this simple situation easily, then that's a problem, in my opinion.</p>
  
  <p>OH, and I know that libraries are different for different OSes, I'm dealing with that more simply, by having a different set of venvs for the windows users. THAT works well, with no problems.</p>