Re: [Pythonmac-SIG] PIL and Snow Leopard
Jerry LeVan wrote: Snow Leopard seems to have severely broken my WxPython Postgresql database browser tool... two or three queries and the app locks up or dies. I have been trying to 'spiff up' its parent, a Tkinter based browser, which still works except that I appear to have lost PIL, Image and Image-Tk some where along the way so I cannot view images stored in the database any more. I'm a little confused about which packages you are having trouble with: TkInter PIL wxPython. Clearly building PIL is an issue for you, but what about the other two? In particular, what wxPython issues are you having? I don't have Snow Leopard, but I'd like to know if there are wxPython issues for the future, and for when I distribute apps for others to run. By the way, if wxPyhon does work OK, it can do a fair bit of image loading/processing, so maybe you don't need PIL for your app. NOTE 2: if you get PIL building, it would be great if you could build a version that statically links the non-standard dependencies, and post it somewhere (preferably give it to Fredrik for him to put up on the PIL site. -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/ORR(206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception chris.bar...@noaa.gov ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] PIL and Snow Leopard
On 2009-10-04 15:19 PM, Christopher Barker wrote: Clearly building PIL is an issue for you, but what about the other two? In particular, what wxPython issues are you having? I don't have Snow Leopard, but I'd like to know if there are wxPython issues for the future, and for when I distribute apps for others to run. OS X's 64-bit subsystem, now standard in Snow Leopard, does not have Carbon for UIs, only Cocoa. wxPython is still built against Carbon. wxCocoa is still in development. 32-bit builds of Python can still work with wxPython on Snow Leopard, though. -- Robert Kern I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth. -- Umberto Eco ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
[Pythonmac-SIG] PIL and Snow Leopard
On Oct 2, 2009, at 7:40 PM, Bill Janssen wrote: Jerry LeVan jerry.le...@eku.edu wrote: Is building PIL on Snow Leopard 'easy' I have the apple python (32/64) installed and the python.org 2.6.2 (32 bit) version installed. Yes, I just build it with /usr/bin/python, and it works fine. Assuming you have Xcode 3.2 installed. Bill Ugh, this is getting messy... I think that I have built libfreetype.dylib and libjpeg.dylib as i386 and x86_64 libs...at least that is what the file command asserts. I then built the PIL package using the system python in 64 bit mode and installed the rascal in the Apple python. All of the libs appear to be multi-architecture ppc, i386 and x86_64 When I run apple python in 64 bit mode I can run the PIL demos... If I restrict apple python to 32 bit mode all of the programs fail with a bus error. * I then tried to build PIL using the 2.6.2 python from python.org. 1) It would not build under gcc-4.2 I had to define CC=gcc-4.0 the build appeared to succeed and I installed the PIL system. 2) All of the demos failed... I noticed that _imagingtk.so was dynamically linked against the ActiveState Tcl/Tk that is installed in /Library/Frameworks/ Tcl.framework [mbp:/Library/Python/2.6/site-packages/PIL]$ otool -L _imagingtk.so _imagingtk.so: /Library/Frameworks/Tcl.framework/Versions/8.5/Tcl (compatibility version 8.5.0, current version 8.5.4) /Library/Frameworks/Tk.framework/Versions/8.5/Tk (compatibility version 8.5.0, current version 8.5.4) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 124.1.1) I suppose that I could hide the ActiveState versions by renaming the Frameworks... But even if I did that, how could I force setup.py to use the apple 8.4 tcl/tk system instead of the 'current' 8.5 system? Any suggestions as to how I can get PIL to work when apple python is in 32 bit mode? Any suggestions as to how I can build PIL using the 2.6.2 version of Python from python.org? This is getting ugly...too many impedance mismatches. Jerry A little more success to report. .. I hid the activestate tcl/tk frameworks in /Library/Frameworks and set CC to gcc-4.0 and rebuilt PIL and otool showed that _imagingtk.so was linked against the apple 8.4 Tcl/Tk system. So I installed the build and tada Imaging appears to be working in python.org version of python (2.6.2). So this leaves only the why does apple python (2.6.1) not work when run in 32 bit mode but does in 64 bit mode question open... Has anyone had success with PIL in this case? Thanks Jerry When I run the Apple Python in 32 bit mode I get a bus error at the same place when I try to display an image using PIL . Here is part of the dump. Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x0028 Crashed Thread: 0 Dispatch queue: com.apple.main-thread Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 com.tcltk.tklibrary 0x13a1850b Tk_GetImageMasterData + 17 1 com.tcltk.tklibrary 0x13a20cab Tk_FindPhoto + 37 2 _imagingtk.so 0x007faacf PyImagingPhotoPut + 95 3 com.tcltk.tcllibrary 0x138d3d64 TclInvokeStringCommand + 101 4 com.tcltk.tcllibrary0x00489977 Tcl_CreateInterp + 4919 5 com.tcltk.tcllibrary0x0048a96c Tcl_EvalObjv + 72 6 _tkinter.so 0x001e449d Tkapp_CallDeallocArgs + 11750 7 org.python.python 0x0008b372 PyEval_EvalFrameEx + 16375 8 org.python.python 0x0008cf64 PyEval_EvalCodeEx + 1720 9 org.python.python 0x0008b591 PyEval_EvalFrameEx + 16918 10 org.python.python 0x0008cf64 PyEval_EvalCodeEx + 1720 11 org.python.python 0x0002ee2c PyClassMethod_New + 1823 12 org.python.python 0xc700 PyObject_Call + 101 13 org.python.python 0x0001c12e PyClass_New + 1603 14 org.python.python 0xc700 PyObject_Call + 101 15 org.python.python 0x0008677a PyEval_CallObjectWithKeywords + 171 16 org.python.python 0x0001ba58 PyInstance_New + 290 17 org.python.python 0xc700 PyObject_Call + 101 18 org.python.python 0x0008c802 PyEval_EvalFrameEx + 21639 19 org.python.python 0x0008cf64 PyEval_EvalCodeEx + 1720 20 org.python.python 0x0002ee2c PyClassMethod_New + 1823 21 org.python.python 0xc700 PyObject_Call + 101 22 org.python.python 0x0001c12e PyClass_New + 1603 23 org.python.python 0xc700 PyObject_Call + 101 24 org.python.python 0x0008677a PyEval_CallObjectWithKeywords + 171 25 org.python.python 0x0001ba58 PyInstance_New + 290 26 org.python.python 0xc700 PyObject_Call + 101
[Pythonmac-SIG] PIL and Snow Leopard
On Oct 2, 2009, at 7:40 PM, Bill Janssen wrote: Jerry LeVan jerry.le...@eku.edu wrote: Is building PIL on Snow Leopard 'easy' I have the apple python (32/64) installed and the python.org 2.6.2 (32 bit) version installed. Yes, I just build it with /usr/bin/python, and it works fine. Assuming you have Xcode 3.2 installed. Bill Ugh, this is getting messy... I think that I have built libfreetype.dylib and libjpeg.dylib as i386 and x86_64 libs...at least that is what the file command asserts. I then built the PIL package using the system python in 64 bit mode and installed the rascal in the Apple python. All of the libs appear to be multi-architecture ppc, i386 and x86_64 When I run apple python in 64 bit mode I can run the PIL demos... If I restrict apple python to 32 bit mode all of the programs fail with a bus error. * I then tried to build PIL using the 2.6.2 python from python.org. 1) It would not build under gcc-4.2 I had to define CC=gcc-4.0 the build appeared to succeed and I installed the PIL system. 2) All of the demos failed... I noticed that _imagingtk.so was dynamically linked against the ActiveState Tcl/Tk that is installed in /Library/Frameworks/ Tcl.framework [mbp:/Library/Python/2.6/site-packages/PIL]$ otool -L _imagingtk.so _imagingtk.so: /Library/Frameworks/Tcl.framework/Versions/8.5/Tcl (compatibility version 8.5.0, current version 8.5.4) /Library/Frameworks/Tk.framework/Versions/8.5/Tk (compatibility version 8.5.0, current version 8.5.4) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 124.1.1) I suppose that I could hide the ActiveState versions by renaming the Frameworks... But even if I did that, how could I force setup.py to use the apple 8.4 tcl/tk system instead of the 'current' 8.5 system? Any suggestions as to how I can get PIL to work when apple python is in 32 bit mode? Any suggestions as to how I can build PIL using the 2.6.2 version of Python from python.org? This is getting ugly...too many impedance mismatches. Jerry A little more success to report. .. I hid the activestate tcl/tk frameworks in /Library/Frameworks and set CC to gcc-4.0 and rebuilt PIL and otool showed that _imagingtk.so was linked against the apple 8.4 Tcl/Tk system. So I installed the build and tada Imaging appears to be working in python.org version of python (2.6.2). So this leaves only the why does apple python (2.6.1) not work when run in 32 bit mode but does in 64 bit mode question open... Has anyone had success with PIL in this case? Thanks Jerry When I run the Apple Python in 32 bit mode I get a bus error at the same place when I try to display an image using PIL . Here is part of the dump. Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x0028 Crashed Thread: 0 Dispatch queue: com.apple.main-thread Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 com.tcltk.tklibrary 0x13a1850b Tk_GetImageMasterData + 17 1 com.tcltk.tklibrary 0x13a20cab Tk_FindPhoto + 37 2 _imagingtk.so 0x007faacf PyImagingPhotoPut + 95 3 com.tcltk.tcllibrary 0x138d3d64 TclInvokeStringCommand + 101 4 com.tcltk.tcllibrary0x00489977 Tcl_CreateInterp + 4919 5 com.tcltk.tcllibrary0x0048a96c Tcl_EvalObjv + 72 6 _tkinter.so 0x001e449d Tkapp_CallDeallocArgs + 11750 7 org.python.python 0x0008b372 PyEval_EvalFrameEx + 16375 8 org.python.python 0x0008cf64 PyEval_EvalCodeEx + 1720 9 org.python.python 0x0008b591 PyEval_EvalFrameEx + 16918 10 org.python.python 0x0008cf64 PyEval_EvalCodeEx + 1720 11 org.python.python 0x0002ee2c PyClassMethod_New + 1823 12 org.python.python 0xc700 PyObject_Call + 101 13 org.python.python 0x0001c12e PyClass_New + 1603 14 org.python.python 0xc700 PyObject_Call + 101 15 org.python.python 0x0008677a PyEval_CallObjectWithKeywords + 171 16 org.python.python 0x0001ba58 PyInstance_New + 290 17 org.python.python 0xc700 PyObject_Call + 101 18 org.python.python 0x0008c802 PyEval_EvalFrameEx + 21639 19 org.python.python 0x0008cf64 PyEval_EvalCodeEx + 1720 20 org.python.python 0x0002ee2c PyClassMethod_New + 1823 21 org.python.python 0xc700 PyObject_Call + 101 22 org.python.python 0x0001c12e PyClass_New + 1603 23 org.python.python 0xc700 PyObject_Call + 101 24 org.python.python 0x0008677a PyEval_CallObjectWithKeywords + 171 25 org.python.python 0x0001ba58 PyInstance_New + 290 26 org.python.python 0xc700 PyObject_Call + 101 27
Re: [Pythonmac-SIG] PIL and Snow Leopard
On Oct 2, 2009, at 7:40 PM, Bill Janssen wrote: Jerry LeVan jerry.le...@eku.edu wrote: Is building PIL on Snow Leopard 'easy' I have the apple python (32/64) installed and the python.org 2.6.2 (32 bit) version installed. Yes, I just build it with /usr/bin/python, and it works fine. Assuming you have Xcode 3.2 installed. Bill Ugh, this is getting messy... I think that I have built libfreetype.dylib and libjpeg.dylib as i386 and x86_64 libs...at least that is what the file command asserts. I then built the PIL package using the system python in 64 bit mode and installed the rascal in the Apple python. All of the libs appear to be multi-architecture ppc, i386 and x86_64 When I run apple python in 64 bit mode I can run the PIL demos... If I restrict apple python to 32 bit mode all of the programs fail with a bus error. * I then tried to build PIL using the 2.6.2 python from python.org. 1) It would not build under gcc-4.2 I had to define CC=gcc-4.0 the build appeared to succeed and I installed the PIL system. 2) All of the demos failed... I noticed that _imagingtk.so was dynamically linked against the ActiveState Tcl/Tk that is installed in /Library/Frameworks/ Tcl.framework [mbp:/Library/Python/2.6/site-packages/PIL]$ otool -L _imagingtk.so _imagingtk.so: /Library/Frameworks/Tcl.framework/Versions/8.5/Tcl (compatibility version 8.5.0, current version 8.5.4) /Library/Frameworks/Tk.framework/Versions/8.5/Tk (compatibility version 8.5.0, current version 8.5.4) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 124.1.1) I suppose that I could hide the ActiveState versions by renaming the Frameworks... But even if I did that, how could I force setup.py to use the apple 8.4 tcl/tk system instead of the 'current' 8.5 system? Any suggestions as to how I can get PIL to work when apple python is in 32 bit mode? Any suggestions as to how I can build PIL using the 2.6.2 version of Python from python.org? This is getting ugly...too many impedance mismatches. Jerry ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
[Pythonmac-SIG] PIL and Snow Leopard
From: Jerry LeVan jerry.le...@eku.edu Date: October 3, 2009 6:32:45 PM EDT To: Bill Janssen jans...@parc.com Cc: pythonmac-sig@python.org pythonmac-sig@python.org Subject: Re: [Pythonmac-SIG] PIL and Snow Leopard On Oct 2, 2009, at 7:40 PM, Bill Janssen wrote: Jerry LeVan jerry.le...@eku.edu wrote: Is building PIL on Snow Leopard 'easy' I have the apple python (32/64) installed and the python.org 2.6.2 (32 bit) version installed. Yes, I just build it with /usr/bin/python, and it works fine. Assuming you have Xcode 3.2 installed. Bill Ugh, this is getting messy... I think that I have built libfreetype.dylib and libjpeg.dylib as i386 and x86_64 libs...at least that is what the file command asserts. I then built the PIL package using the system python in 64 bit mode and installed the rascal in the Apple python. All of the libs appear to be multi-architecture ppc, i386 and x86_64 When I run apple python in 64 bit mode I can run the PIL demos... If I restrict apple python to 32 bit mode all of the programs fail with a bus error. * I then tried to build PIL using the 2.6.2 python from python.org. 1) It would not build under gcc-4.2 I had to define CC=gcc-4.0 the build appeared to succeed and I installed the PIL system. 2) All of the demos failed... I noticed that _imagingtk.so was dynamically linked against the ActiveState Tcl/Tk that is installed in /Library/Frameworks/ Tcl.framework [mbp:/Library/Python/2.6/site-packages/PIL]$ otool -L _imagingtk.so _imagingtk.so: /Library/Frameworks/Tcl.framework/Versions/8.5/Tcl (compatibility version 8.5.0, current version 8.5.4) /Library/Frameworks/Tk.framework/Versions/8.5/Tk (compatibility version 8.5.0, current version 8.5.4) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 124.1.1) I suppose that I could hide the ActiveState versions by renaming the Frameworks... But even if I did that, how could I force setup.py to use the apple 8.4 tcl/tk system instead of the 'current' 8.5 system? Any suggestions as to how I can get PIL to work when apple python is in 32 bit mode? Any suggestions as to how I can build PIL using the 2.6.2 version of Python from python.org? This is getting ugly...too many impedance mismatches. Jerry A little more success to report. .. I hid the activestate tcl/tk frameworks in /Library/Frameworks and set CC to gcc-4.0 and rebuilt PIL and otool showed that _imagingtk.so was linked against the apple 8.4 Tcl/Tk system. So I installed the build and tada Imaging appears to be working in python.org version of python (2.6.2). So this leaves only the why does apple python (2.6.1) not work when run in 32 bit mode but does in 64 bit mode question open... Has anyone had success with PIL in this case? Thanks Jerry___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
[Pythonmac-SIG] PIL and Snow Leopard
Snow Leopard seems to have severely broken my WxPython Postgresql database browser tool... two or three queries and the app locks up or dies. I have been trying to 'spiff up' its parent, a Tkinter based browser, which still works except that I appear to have lost PIL, Image and Image-Tk some where along the way so I cannot view images stored in the database any more. Is building PIL on Snow Leopard 'easy' I have the apple python (32/64) installed and the python.org 2.6.2 (32 bit) version installed. Anyone have any experiences in building PIL in the above environment? Anyone else having a problem with WxPython on Snow Leopard? Thanks for any insights... Jerry ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] PIL and Snow Leopard
In article c6d2f15e-f3e9-4948-89d3-cc36b7525...@eku.edu, Jerry LeVan jerry.le...@eku.edu wrote: Snow Leopard seems to have severely broken my WxPython Postgresql database browser tool... two or three queries and the app locks up or dies. I have been trying to 'spiff up' its parent, a Tkinter based browser, which still works except that I appear to have lost PIL, Image and Image-Tk some where along the way so I cannot view images stored in the database any more. Is building PIL on Snow Leopard 'easy' I have the apple python (32/64) installed and the python.org 2.6.2 (32 bit) version installed. Anyone have any experiences in building PIL in the above environment? Anyone else having a problem with WxPython on Snow Leopard? Thanks for any insights... This may not be related to what you are seeing with lock ups but a number of people have seen problems with IDLE, which also uses Tkinter, that comes with Apple's python 2.6 on Snow Leopard. In 10.6, the Apple python Tkinter is linked with Tk 8.5.7, believed to be the new Cocoa Tk. At the moment, this problem has not been resolved; see http://bugs.python.org/issue6864 . The pythons installed by the python.org OS X installers, including the newly released 2.6.3, don't exhibit this problem because are linked with Tk 8.4, which is still available and updated by Apple in 10.6. Note that the python.org pythons are still 32-bit-only Intel ppc. For what it's worth, the MacPorts py26-pil port builds fine on 10.6 with the MacPorts python26. -- Ned Deily, n...@acm.org ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] PIL and Snow Leopard
Jerry LeVan jerry.le...@eku.edu wrote: Is building PIL on Snow Leopard 'easy' I have the apple python (32/64) installed and the python.org 2.6.2 (32 bit) version installed. Yes, I just build it with /usr/bin/python, and it works fine. Assuming you have Xcode 3.2 installed. Bill ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
