'No module named tkinter.messagebox' - PyInstaller

[ironfelix717]

I suspect I won't get an answer but i'll try regardless...

Compiling my script (pyinstaller) and running the .exe results in:

No module named tkinter.messagebox

When the interpreter will run the script JUST FINE with 0 errors whatsoever.

The script import statement:

import tkinter.messagebox as tkmb

I say this every time i write python:
It shouldn't be this difficult to actually implement a finished product. If you can't compile your code you've produced nothing!

Thanks for any help/ideas.

[buran]

https://pyinstaller.readthedocs.io/en/st...wrong.html

add --hidden-import so that pyinstaller can find it

If you can't compile your code you've produced nothing!

you would be surprised that many/most of python programs run without being compiled to executable

[ironfelix717]

Hi thanks for your reply..

OK hidden imports seemed to fix that, apparently pyinstaller has 0 intelligence - thus i'm going to have to include every single module as one of these 'hidden imports'. I don't know the syntax and the documentation is overly complex.

My current syntax is: (for one file)

pyinstaller -y -F --hidden-import tkinter.messagebox  "//Mac/Home/Desktop/App/InstallerV2.py

Any ideas how to include multiple modules in this command?

P.S. pyinstaller is disappointing...

[buran]

P.S. pyinstaller is disappointing...

actually it's one of the best and easiest to use. documentation is excellent. never mind...

either add --hiden-import option for each module it can't find or better edit the generated spec file. then use the edited spec file to create the executabale
And the reason it can not find them is in the packages - it's explaiend in the link I provided

[ironfelix717]

Hi, thanks... I am debugging now.

My issue is that modules are in Sys.Path.

PyInstaller can't find them from Sys.Path? Not a good design.

[joe_momma]

instead of:

import tkinter.messagebox as tkmb

I import like so:

from tkinter.messagebox import *

with no issues with pyinstaller, you'll have modify your code, the proper way would name the message box directly without the wildcard.

[ironfelix717]

importing with an asterisk is lousy in my opinion for the fact that you now are
not really aware of what library you're using a method from.
Its not clear what module 'messagebox' is from when you use it in code.

Regardless, PyInstaller should have no issues finding modules.
Everything is in Sys.Path. Its basically that simple.

The next issue i just ran into when attempting to execute the .exe on
a barebones system is that it failed to execute EVEN when it ran fine
on my development system. CMD output says can't find a module. How can
i even rely on this tool?

Programs are meant to be compiled and if its that difficult to compile
an interpreted language like Python then i'll consider forgetting the language
as its mostly useless in actually implementing an actual program.

Forgive my irritable mood. Thanks for the help.

[buran]

importing with an asterisk is lousy in my opinion for the fact that you now are
not really aware of what library you're using a method from.
Its not clear what module 'messagebox' is from when you use it in code.

100% agree. Star imports are bad and should be avoided

You don't provide much information about the modules it cannot find. Are you manipulating sys.path in the code? Try to extend search path by adding --paths
https://pyinstaller.readthedocs.io/en/st...g-the-path

also you can get more verbose messages
https://pyinstaller.readthedocs.io/en/st...g-messages
https://pyinstaller.readthedocs.io/en/st...g-the-path