Problems with converting python file to mac exec

31 views
Skip to first unread message

pure toxic

unread,
Nov 9, 2020, 2:36:11 PM11/9/20
to PyInstaller
Hello, 

we currently have multiple problems with compiling our script to a working exec.
1. issue is that not all libraries get found, means modulenotfounderror.
We tried to solve the issue with the --hidden-import comment, but it didnt work.
It finds some libraries but not all btw.

So we've decided to comment out all libraries that don't work (as a temporary solution)

2. issue was that our files don't get found (filenotfounderror).

Thanks in advance!

Best Regards,
pure toxic

Subramanian Ramajayam

unread,
Nov 10, 2020, 3:35:00 AM11/10/20
to pyins...@googlegroups.com
Hello, 
I had similar issues sometime back. I repeated "pip install modules. ".some we're missing . I had to reinstall. The problem was I also had one more python version. So uninstalled it. I use only py3. 7-64 now.  I had the serious issue with pyinstaller. The issue was, " Your PC cannot run this app. Consult your Software developer".In cmd line, it was"access denied".it took almost a month for me to get the solution from internet search. I just changed the cmd line to, 
C:\Users\yourname\python -m PyInstaller --name "yourscript.py" "C:\Users\yourname\yourscript.py"
This worked for me although it took a little longer to compile. Exe also is also successful. I don't know whether this works for you or not. 
Good luck! 
Ramajayam

--
You received this message because you are subscribed to the Google Groups "PyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pyinstaller...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pyinstaller/1a79e4bd-4c79-4ceb-84ac-e3b4517edf96n%40googlegroups.com.

ttepperg

unread,
Mar 22, 2021, 3:52:48 AM3/22/21
to PyInstaller
Hi Pure Toxic,

I'm experiencing a similar problem whereby some modules are not found, which correspond
to code contained withn .so libraries *within* the library I'm importing. I can get rid of this one by
one via the -hidden-import flag, but it's becoming frustrating to do so by hand.

I wonder whether you have found a solution to this issue yet?

Cheers

Thor

Reply all
Reply to author
Forward
0 new messages