Imported module not found in PyInstaller

Question

I'm working in Windows, using PyInstaller to package a python file. But some error is occuring:

Traceback (most recent call last):
  File "<string>", line 2, in <module>
  File "D:\Useful Apps\pyinstaller-2.0\PyInstaller\loader\iu.py", line 386, in importHook
    mod = _self_doimport(nm, ctx, fqname)
  File "D:\Useful Apps\pyinstaller-2.0\PyInstaller\loader\iu.py", line 480, in doimport
    exec co in mod.__dict__
  File "D:\Useful Apps\pyinstaller-2.0\server\build\pyi.win32\server\out00-PYZ.pyz\SocketServer", line 132, in <module>
  File "D:\Useful Apps\pyinstaller-2.0\PyInstaller\loader\iu.py", line 386, in importHook
    mod = _self_doimport(nm, ctx, fqname)
  File "D:\Useful Apps\pyinstaller-2.0\PyInstaller\loader\iu.py", line 480, in doimport
    exec co in mod.__dict__
  File "D:\Useful Apps\pyinstaller-2.0\server\build\pyi.win32\server\out00-PYZ.pyz\socket", line 47, in <module>
  File "D:\Useful Apps\pyinstaller-2.0\PyInstaller\loader\iu.py", line 409, in importHook
    raise ImportError("No module named %s" % fqname)
ImportError: No module named _socket

I know that _socket is in path C:\Python27\libs\_socket.lib, but how can let the generated EXE find that file?

score 17 · Answer 1 · answered Mar 11 '14 at 11:12

17

If you are using virtualenv you should use the "-p" or "--path='D:...'" option. Like this:

pyinstaller.exe --onefile --paths=D:\env\Lib\site-packages  .\foo.py

What this does is generates foo.spec file with this pathex path

answered Mar 11 '14 at 11:12

karantan

785
7
18

score 3 · Answer 2 · edited Jul 17 '15 at 15:13

3

This sounds like a job for hidden imports (only available in the latest builds).

From the docs

a = Analysis(['myscript.py'], 
             hiddenimports = ['_socket'], 
             <and everything else>)

edited Jul 17 '15 at 15:13

Wooble

84,802
12
102
128

answered Mar 05 '13 at 18:15

danodonovan

18,450
7
68
75

score 3 · Answer 3 · answered May 27 '20 at 15:28

3

In my case, I had to delete all folders and files related to pyinstaller in my directory, i.e. __pycache__, build, dist, and *.spec. I re-ran the build and the exe worked.

answered May 27 '20 at 15:28

xinthose

2,529
2
35
51

score 2 · Answer 4 · edited Jul 17 '15 at 15:14

2

You can add the path to your application spec file.

In the Analysis object you can specify pathex=['C:\Python27\libs\', 'C:\Python27\Lib\site-packages'], and any other path ...

Note that if the path is not found there is no problem ... I have paths from linux as well in there.

edited Jul 17 '15 at 15:14

Wooble

84,802
12
102
128

answered Mar 05 '13 at 15:06

marius_cornescu

51
1
5

score 1 · Answer 5 · answered Jan 04 '21 at 19:52

1

If you are using an virtual environment, then problem is because of environment.

SOLUTION Just activate the environment and run the pyinstaller command. For example, If you are using environment of pipenv then run commands in following order.

pipenv shell # To activate environment

pyintaller --onefile youscript.py # Command to generate executable

answered Jan 04 '21 at 19:52

Sami Ullah

39
1
5

1

You are presuming they are using a virtual environment – Danny Watson Mar 04 '21 at 12:43
3

At least, I am giving a possible solution. – Sami Ullah Mar 20 '21 at 21:42

score 1 · Answer 6 · answered Aug 03 '21 at 14:15

1

just delete the '__pycache__' directory then run your exe file again. It worked out for me

answered Aug 03 '21 at 14:15

Nathnael M.

21
1

score 0 · Answer 7 · answered Oct 21 '15 at 13:52

0

None of the above answers worked for me, but I did get it to work. I was using openpyxl and it required jdcal in the datetime.py module. None of the hidden imports or any of those methods helped, running the exe would still say jdcal not found. The work-around that I used was to just copy the few functions from jdcal directly into the datetime.py in the openpyxl code. Then ran pyinstaller -F program.py

and it worked!

answered Oct 21 '15 at 13:52

Korben Dallas

1
1

1

what a coincidence i am also using openpyxl, can you please clarify your solution more. – Rahul Bagdi Mar 11 '22 at 15:36
this has been so long ago, I don't remember! – Captain Fantastic Mar 20 '22 at 15:48

score 0 · Answer 8 · answered Apr 19 '16 at 20:32

Had similar issues. Here's my fix for PyQt5, cffi, python 3.4.3:

This fixes the 'sip' not found error and the '_cffi_backend' one if that comes up:

# -*- mode: python -*-

block_cipher = None


a = Analysis(['LightShowApp.py'],
             pathex=['c:\\MyProjects\\light-show-editor-36',
             'c:\\Python34\\libs\\', 'c:\\Python34\\Lib\\site-packages'],
             binaries=None,
             datas=None,
             hiddenimports=['sip', 'cffi'],
             hookspath=[],
             runtime_hooks=[],
             excludes=[],
             win_no_prefer_redirects=False,
             win_private_assemblies=False,
             cipher=block_cipher)
pyz = PYZ(a.pure, a.zipped_data,
             cipher=block_cipher)
exe = EXE(pyz,
          a.scripts,
          a.binaries,
          a.zipfiles,
          a.datas,
          name='LightShowApp',
          debug=False,
          strip=False,
          upx=True,
          console=True )

Look at 'pathex' and 'hiddenimports' above. Those are the only changes from default generated. Build exe with:

pyinstaller LightShowApp.spec -F

I ran that outside of venv or pip-win - whateverTF that crap is for!

score 0 · Answer 9 · answered Oct 30 '20 at 18:10

The executor does not know the location of the library, "C:\Python27\Lib\site-packages" etc. Thus, pyinstaller binds the module locations when creating the executable. Therefore, you need to import all the modules, you have used into your program.

Import the "_socket" module in your main file and recompile using pyinstaller.

I would probably work.

Note: But the versions of the modules installed in your system and used in the program must be compatible.

Imported module not found in PyInstaller

9 Answers9

Linked