it helps some times Your assumptions are basically right. The second way may not work in Python 2.7 if there is a module named module in the module search path (sys.path) before the one you actually want to import. That's why Python 3 switched to absolute imports, to make importing safer and more predictable.
from . import module
PyCharm unittest: "Failed to import test module" caused by "loadTestsFromName" in a symlink environm
this will help Probably, at the date of our MSVS2017 installation (esp. if prior to April 2018), there were no official .whl files for Windows pytorch (this has since changed). Also, given the default installation pathway, permissions on Windows (or file lock access) may be a problem (for example, when attempting to install to the "c:\ProgramData" folder). The solution is to 1) ensure all pytorch requisites are installed first (for example, if, during your failed pytorch installation you get a "_____ requires _____ which is not installed, for example cython, then install cython) 2) avoid permission errors by using the --user switch, and 3) install directly from the online repository.
On Windows, running "import tensorflow" generates No module named "_pywrap_tensorflow" error