Then, even without manually deleting anything, I installed the "10.3" 2.7 metapackage and now both work. Using the standard GUI installer on a 64-bit-capable machine running 10.6.4, I first installed the "10.5" 2.7 metapackage and verified that both IDLE.app and /usr/local/bin/idle2.7 fail.
#Idle python for mac os how to
Not sure how to get IDLE working.ĭate: Odd, works for me.
#Idle python for mac os install
Well, tried to install the 10.3 version over my 64-bit installation and that had no effect. Note that in the interim, there is a workaround for Snow Leopard users who want to use IDLE or Tkinter: use the 32-bit-only 2.7 OS X installer ("10.3") instead. I want to do this during the europython sprint days. I'm going to experiment with embedding a minimal version of Tk in the installer, which would both fix this issue and ensure that we use a version of Tk that is better adjusted to OSX (which should remove some other issues) (And also let them know that installing the 64 bit version means that Tkinter / IDLE doesn't work on Snow Leopard.) I don't particularly mind what the fix is - but at the moment users can download and install Python from a installer and then have an (apparently) non functioning IDLE and Tkinter.Īt the very least we should advise users to install the 32bit only binary (which presumably works - I should try it) unless they *need* the 64 bit Python. That would have to be a minimal copy of the Tcl/Tk frameworks, and would definitely require feedback from people that actually use Tkinter. I am however slowly moving towards liking to ship a newer version of Tk with Python. I can't find the specific issue right now, but did file a feature request a while back for a patch that allows us to ship copies of _tkinter linked to Tk 8.4 and Tk 8.5 while having a wrapper that loads the right one. IDLE.app somewhat works because the Makefile makes sure it gets started using a 32-bit version of the interpreter (which is a quick workaround: 'arch -i386 python2.7' starts python in 32-bit mode an Tkinter is available there) I'm -1 on creating a 10.6 specific installer, two installers is confusing enough. Mark nails the issue: there is no 64-bit version of Tk on OSX 10.5. Perhaps this means having to have a separate installer for OS X 10.6.Īuthor: Ronald Oussoren (ronaldoussoren) * The binary links to Tcl 8.4 (which doesn't seem to have a 64-bit version). Mark Dickinson confirms the problem and offers this diagnosis: Library/Frameworks/amework/Versions/2.7/lib/python2.7/lib-dynload/_tkinter.so: no matching architecture in universal wrapperĪs a further oddity, if I run IDLE.app I get an IDLE shell (weird as from the command line Tkinter can't even be imported) - but I also get an error dialog that the subprocess can't be connected to and then IDLE shuts down. ImportError: dlopen(/Library/Frameworks/amework/Versions/2.7/lib/python2.7/lib-dynload/_tkinter.so, 2): no suitable image found. Import _tkinter # If this fails your Python may not be configured for Tk * Python 2.7 PPC/i386/x86-64 Max OS X Installer Disk Imageįile "/Library/Frameworks/amework/Versions/2.7/lib/python2.7/ lib-tk/Tkinter.py", line 39, in I installed the following, on Snow Leopard:
#Idle python for mac os for mac os x
Messages (14)Īfter installing Python 2.7 for Mac OS X from the binary I can't use Tkinter or IDLE. Can't import Tkinter / use IDLE after installing Python 2.7 on Mac OS XĪlex.Rodriguez, Sarth.Calhoun, mark.dickinson, michael.foord, ned.deily, ronaldoussoren, yandapandaĬreated on 21:31 by michael.foord, last changed 14:57 by admin.
0 kommentar(er)
