-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pyinstaller fails to execute completely with error of tcl #5040
Comments
I used pyinstaller tactile_engine.spec |
It should't make any difference that your running from a spec because when don't PyInstaller just generates the spec then from that spec anyway. Presumably what is actually happening is PyInstaller thinks your project requires tkinter, it runs @nbrummel Could you:
|
I'm on Mac, |
I placed the |
@nbrummel You mean this error?
If you do then no, hidden imports are for python modules, i.e anything it'd make sense to write after Just as a final check - what happens if you |
Yes I can import tkinter fine. I tried in python and ipython. |
I also tried on python 3.8 as well. same issue |
So you do must have tcl installed somewhere. Could you locate it for us?
We can't guess the cause based on out of context single lines of error messages. You'll need to tell us how/where you got that error and what the whole message said. |
So believe I have figured out the problem. I just installed the Mac osx beta 4 and have found out that apple moved some .dylib . Also, the Xcode has changed and that has turned out to mess up with PyInstaller. Do you have a build for the new osx/Xcode? |
@amifunny and/or @reritom Fancy having a stab at this one? Long story short - the tkinter hook needs to updated to track wherever the tcl dylibs have been moved to. @nbrummel You're going to have to clarify your last comment. What does Xcode have to do with it? Unless you're using a Python shipped inside of Xcode it should be irrelevant. |
I am on the new Mac OSX beta 4. Sorry for the confusion. Apple moved the libs for the new OSX Big Sur. |
The following might not be true for all cases, but when I was surprised to see tkinter and it's runtime dependencies popping up in the dist, I ran a pyinstaller with --log-level TRACE to find this:
And on Linux, after excluding the 'test' module, the following objects were no longer needed:
|
There is no need for this module, and it also results into detection of tkinter and deps, which require libX11 xref: pyinstaller/pyinstaller#5040 (comment)
Hmm, this is a bit different from other macOS Tcl/Tk issues (which we are in process of finally fixing), because it is a recent python (3.8.5) that still uses system Tcl/Tk framework - presumably this is a homebrew version (instead of the python.org build)? At any rate, due to Big Sur hiding system libraries (see #5107), this The |
@rokm No, the output I shared is on Linux, using the conda-forge build of python 3.7 |
The issue from the original report (Tcl error with homebrew python 3.8.5 on Big Sur) should be fixed now that we do not try to collect data from system Tcl/Tk framework anymore (and are thus not affected by Big Sur hiding the system libraries). Of course, if Therefore, I'm closing this issue. The problems stemming from Big Sur hiding the system libraries and the fact that |
When I run from a .spec file it does not work and throws errors. I have checked in a python shell the tk and tcl work with python. Any advice or help would be great. Here is my spec file:
Here is the output:
The text was updated successfully, but these errors were encountered: