-
-
Notifications
You must be signed in to change notification settings - Fork 12.4k
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
SIGABRT with python3 --with-tcl-tk #12808
Comments
My open issue #12068 may be related, as I get a EXC_BAD_ACCESS (SIGSEGV) with python2 --with-tcl-tk trying to open files with IDLE. As with the other issue you mentioned, Apple's Tcl/Tk doesn't have the same behavior. |
Please note that the Apple-provided Tcl/Tk is known to be slow and buggy (https://www.python.org/download/mac/tcltk/) so it would have real value to be able to build Python (both version 2 and 3) with either ActiveState's Tcl/Tk or Homebrew's. |
Same problem for me. Looking for solutions. % python3 -c 'import tkinter; tkinter.Tk()' |
not sure how helpfull but here is the backtrace `(lldb) bt
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Lol it's still an issue. |
@jkl1337 It is?
|
@jkl1337 ah ok I can reproduce this on 10.12 but not 10.11. |
@iMichka sure … but that's a different tcl-tk. |
Having the same issue on mac 10.12.5. Not sure if this helps, but this is where I am after trying to find more info about whats going wrong. Disclosure: I know nothing about tcl/tk and very little about brew. For me, the error is thrown at line 1958 in /usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/tkinter/init.py (might be off a line or two from me messing with it).
called from:
That calling sequence was from:
self.tk is an instance of _tkinter (created around line 2017), which appears to be a class from /usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/lib-dynload/_tkinter.cpython-36m-darwin.so which has dependencies on the tcl/tk libraries:
I was hoping to get more info about what's going wrong beyond the "overflow" posted above which is what appears to me, too. I don't know enough about the systems involved so I'm at a loss to dig up more info. |
According to the Python site (https://www.python.org/download/mac/tcltk/#activetcl-8-5-17-0), Python 3.6.1 should be using Tcl/Tk version 8.5.x, not 8.6. I have noted that the only version available through Homebrew is 8.6.6. ActiveState provides an 8.5 version of ActiveTcl which would presumably work, however I have not had the chance to test it. |
@cemarriott given that the bug doesn't occur on 10.11 that doesn't sound likely to be relevant. |
@cemarriott That page refers to compatibility amongst the various semi-official prebuilt binary versions of python and tcl/tk. And actually that is precisely the reason why this bug is relevant to some of us because it has previously been the one way to get tkinter with tk 8.6 on Mac. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
…ith-x11` option. Without --with-x11 `brew test python` and `brew test python3` fail, and some formulae (eg pymol) break
@cowsandmilk's suggestion to readd (and use) the |
I've closed that PR but an actual fix for these issues would be most welcome. |
…y adding devel build. Also removes semi-function HEAD build
This should be fixed if you
|
Please always follow these steps:
brew update
and retried your prior step?brew doctor
, fixed as many issues as possible and retried your prior step?brew gist-logs <formula>
(where<formula>
is the name of the formula that failed) and included the output link? https://gist.github.com/62075796543a3025e115b278fabb2565To help us debug your issue please explain:
brew install
commands)A similar issue with python2 was opened in #12114, but the user closed it because they reinstalled python against the Apple provided Tcl/Tk, which doesn't resolve the issue.
The text was updated successfully, but these errors were encountered: