CODEWITHSUNDEEP
pythonwindowssocketsexepyinstaller
Searene
Searene

Reputation: 27614

Imported module not found in PyInstaller

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?

Upvotes: 25

Views: 109417

Answers (13)

bt3
bt3

Reputation: 188

I was using a conda environment, and in my case the module scipy.io couldn't be found when running my pyinstaller executable. In my code I had import scipy. Changing this to from scipy import io fixed the issue.

Upvotes: 0

Moein Hasani
Moein Hasani

Reputation: 91

I found out that if you make the setup.py for your code and run python setup.py install and then python setup.py build the pyinstaller will be able to find your packages. you can use the find_packages function from setuptools in your setup.py file so it automatically includes everything.

Upvotes: 0

Shmack
Shmack

Reputation: 2341

Another "In my case" post.

pypdfium2 (an import in my file that I want to convert to an .exe) has a .dll that it calls called pdfium. pyinstaller doesn't import that .dll when you go to build the .exe by default.

Fix:

I think you can do the option --collect-all pypdfium2 ,but at least for me --add-data "C:\Program Files\Python39\Lib\site-packages\pypdfium2\pdfium.dll";. (The "." at the end is intentional and needed!) got the job done.

Upvotes: 3

Diedre
Diedre

Reputation: 565

In my case I was trying to import a folder that I created, and ended up here. I solved that problem by removing __init__.py from the main folder, keeping the __init__.py in the subfolders that I was importing.

Upvotes: 11

Nathnael M.
Nathnael M.

Reputation: 61

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

Upvotes: 5

Sami Ullah
Sami Ullah

Reputation: 89

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

Upvotes: 5

Jeyakeethan Geethan
Jeyakeethan Geethan

Reputation: 79

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.

Upvotes: 0

xinthose
xinthose

Reputation: 3848

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.

Upvotes: 7

user1277936
user1277936

Reputation:

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!

Upvotes: 1

Korben Dallas
Korben Dallas

Reputation: 1

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!

Upvotes: 0

marius_cornescu
marius_cornescu

Reputation: 76

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.

Upvotes: 2

danodonovan
danodonovan

Reputation: 20373

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>)

Upvotes: 4

karantan
karantan

Reputation: 1015

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

Upvotes: 39

Related Questions