unittest is a built-in module; mock is an external library (pre-3.3 betas, anyway). After installing mock via pip install, you import it not by using from unittest.mock import MagicMock but from mock import MagicMock Edit: mock has been included in the unittest module (since Python3.3), and can be imported by import unittest.mock.
If you made a virtual env, then deleted that python installation, you’ll get the same error. Just rm -r your venv folder, then recreate it with a valid python location and do pip install -r requirements.txt and you’ll be all set (assuming you got your requirements.txt right).
You need to explicitly import psycopg2.extras: import psycopg2.extras
You probably don’t have the six Python module installed. You can find it on pypi. To install it: $ easy_install six (if you have pip installed, use pip install six instead)
Apparently, box_utils.py isn’t part of a package. You still can import functions defined in this file, but only if the python script that tries to import these functions lives in the same directory as box_utils.py, see this answer. Nota bene: In my case, I stumbled upon this error with an import statement with one period, … Read more
This fixed the problem by having it as the first two lines of the script: !pip install opencv-python !apt update && apt install -y libsm6 libxext6 !apt-get install -y libxrender-dev
The bug is found in pip 10.0.0. In linux you need to modify file: /usr/bin/pip from: from pip import main if __name__ == ‘__main__’: sys.exit(main()) to this: from pip import __main__ if __name__ == ‘__main__’: sys.exit(__main__._main())
Activate the virtualenv, and then install BeautifulSoup4: $ pip install BeautifulSoup4 When you installed bs4 with easy_install, you installed it system-wide. So your system python can import it, but not your virtualenv python. If you do not need bs4 to be installed in your system python path, uninstall it and keep it in your virtualenv. … Read more
This issue arises due to the ways in which the command line IPython interpreter uses your current path vs. the way a separate process does (be it an IPython notebook, external process, etc). IPython will look for modules to import that are not only found in your sys.path, but also on your current working directory. … Read more
In my case, it is permission problem. The package was somehow installed with root rw permission only, other user just cannot rw to it!