From fkawasak@po.twin.ne.jp Thu Dec 10 17:11:13 2009 From: fkawasak@po.twin.ne.jp (KAWASAKI) Date: Fri, 11 Dec 2009 02:11:13 +0900 Subject: [Pythonmac-SIG] newbie's Q Message-ID: hello,all I am a newbie to mac python. when I double click a module in whatever folder the interpreter says to me it can't find the module. for example. Double click $PYTHON:Lib:binhex.py --->PythonInterpreter:: can't open file 'binhex.py:' I can import the binhex.py from the interpreter command line. I suspect it is not a problem of path settings.( indeed $PYTHON:Lib: is in the path) I thought I had no trouble when I was using ver 1.4 Please tell me what's wrong. Thank you in advance. From kw at codebykevin.com Tue Dec 1 02:46:44 2009 From: kw at codebykevin.com (Kevin Walzer) Date: Mon, 30 Nov 2009 20:46:44 -0500 Subject: [Pythonmac-SIG] py2app and pygame results in application that may not launch In-Reply-To: References: Message-ID: <4B147584.2050808@codebykevin.com> On 11/30/09 3:21 PM, Russell E. Owen wrote: > > The solution was to upgrade to the latest py2app and associated software. > Russell, Is this a 32-bit or 64-bit application? I've tried a few times to update to the latest py2app and macholib, but they barf on my four-way universal 64-bit/32-bit app (using Tk-Cocoa). I don't think Ronald Ousorren has had time to look at this yet and I don't know py2app/macholib well enough to attempt a patch, so I've resorted to using bundlebuilder to ship my apps in the meantime. --Kevin -- Kevin Walzer Code by Kevin http://www.codebykevin.com From ronaldoussoren at mac.com Tue Dec 1 09:57:35 2009 From: ronaldoussoren at mac.com (Ronald Oussoren) Date: Tue, 01 Dec 2009 09:57:35 +0100 Subject: [Pythonmac-SIG] py-appscript 0.20.3, 0.21.0 and impending 1.0.0 release (addendum) In-Reply-To: <94749.1259438426@parc.com> References: <94749.1259438426@parc.com> Message-ID: <27AAC26A-2DE3-4F9D-A8EA-B70C5F2E7687@mac.com> On 28 Nov, 2009, at 21:00, Bill Janssen wrote: > has wrote: > >> The bouncing Dock icon is gone when using appscript 0.21.0 on a version of Python that was built against 10.5 or 10.6 SDKs. (Yay!) > > Yay! Now I can can my private copy of Python with the LSUIElement flag set... > >> Perhaps it's time python.org started distributing framework builds for 10.5 and later? > > Seems like a good thought. I don't mind linking to the 10.5, or even 10.6, SDK instead of the 10.4 one, but only if the resulting binary runs on 10.4 as well. This won't happen until 2.7 is released (and likewise for 3.2 in the py3k branch). Ronald -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3567 bytes Desc: not available URL: From downgeoff2 at hotmail.com Thu Dec 3 21:30:29 2009 From: downgeoff2 at hotmail.com (downie -) Date: Thu, 3 Dec 2009 15:30:29 -0500 Subject: [Pythonmac-SIG] OSX3 install problem Message-ID: Hi List, I'm trying to install Python on OSX10.3.9 , downloaded python-2.6.4_macosx10.3.dmg, but unfortunately the install process ends with 'There have been errors in the install process. Please try again.' Console.log entry is not much more informative: "2009-12-03 20:11:22 +0000 Not a JPEG file: starts with 0x89 0x50 2009-12-03 20:14:11.844 Installer[387] Exception raised during posting of notification. Ignored. exception: Some files for PythonFramework-2.6 may not have been written correctly. (code 1)" Any ideas on where to look for better diagnostics? Thanks, GD PS I's also like to install the IPy module, but I can't compile from source - impossible? _________________________________________________________________ Windows 7: Unclutter your desktop. Learn more. http://www.microsoft.com/windows/windows-7/videos-tours.aspx?h=7sec&slideid=1&media=aero-shake-7second&listid=1&stop=1&ocid=PID24727::T:WLMTAGL:ON:WL:en-US:WWL_WIN_7secdemo:122009 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Barker at noaa.gov Thu Dec 3 22:23:23 2009 From: Chris.Barker at noaa.gov (Christopher Barker) Date: Thu, 03 Dec 2009 13:23:23 -0800 Subject: [Pythonmac-SIG] OSX3 install problem In-Reply-To: References: Message-ID: <4B182C4B.7020506@noaa.gov> downie - wrote: > I'm trying to install Python on OSX10.3.9 , downloaded > python-2.6.4_macosx10.3.dmg, but unfortunately the install process ends > with 'There have been errors in the install process. Please try again.' While it should support 10.3.9, I think there has been very little testing, and I know that some packages modules (like wxPython) don't work right on pre-10.4 systems. If you can get away with running Python 2.5, you may have better luck. Sorry that I have no clue about that error. -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker at noaa.gov From nad at acm.org Thu Dec 3 22:42:07 2009 From: nad at acm.org (Ned Deily) Date: Thu, 03 Dec 2009 13:42:07 -0800 Subject: [Pythonmac-SIG] OSX3 install problem References: Message-ID: In article , downie - wrote: > I'm trying to install Python on OSX10.3.9 , downloaded > python-2.6.4_macosx10.3.dmg, but unfortunately the install process ends with > 'There have been errors in the install process. Please try again.' > Console.log entry is not much more informative: > "2009-12-03 20:11:22 +0000 > Not a JPEG file: starts with 0x89 0x50 > 2009-12-03 20:14:11.844 Installer[387] Exception raised during posting of > notification. Ignored. exception: Some files for PythonFramework-2.6 may > not have been written correctly. (code 1)" > > Any ideas on where to look for better diagnostics? Interesting. The installer is seldom (if ever) tested on 10.3.9 these days although the hope is that it should work. I forget if the OS X Installer app has this option in 10.3 but, at least on later versions of OS X, the Installer menu bar has a Window -> Installer Log option and at the bottom of the Installer Log window there is an selector for "Show Everything". Could you see if there is anything more there, perhaps the specific file name? -- Ned Deily, nad at acm.org From downgeoff2 at hotmail.com Thu Dec 3 22:49:50 2009 From: downgeoff2 at hotmail.com (downie -) Date: Thu, 3 Dec 2009 16:49:50 -0500 Subject: [Pythonmac-SIG] OSX3 install problem In-Reply-To: References: , Message-ID: > To: pythonmac-sig at python.org > From: nad at acm.org > Date: Thu, 3 Dec 2009 13:42:07 -0800 > Subject: Re: [Pythonmac-SIG] OSX3 install problem > > In article , > downie - wrote: > > I'm trying to install Python on OSX10.3.9 , downloaded > > python-2.6.4_macosx10.3.dmg, but unfortunately the install process ends with > > 'There have been errors in the install process. Please try again.' > > Console.log entry is not much more informative: > > "2009-12-03 20:11:22 +0000 > > Not a JPEG file: starts with 0x89 0x50 > > 2009-12-03 20:14:11.844 Installer[387] Exception raised during posting of > > notification. Ignored. exception: Some files for PythonFramework-2.6 may > > not have been written correctly. (code 1)" > > > > Any ideas on where to look for better diagnostics? > > Interesting. The installer is seldom (if ever) tested on 10.3.9 these > days although the hope is that it should work. I forget if the OS X > Installer app has this option in 10.3 but, at least on later versions of > OS X, the Installer menu bar has a Window -> Installer Log option and at > the bottom of the Installer Log window there is an selector for "Show > Everything". Could you see if there is anything more there, perhaps the > specific file name? > > -- > Ned Deily, > nad at acm.org 2.5.4 installs ok - I'll try 2.6.4 again. GD _________________________________________________________________ Chat with Messenger straight from your Hotmail inbox. http://www.microsoft.com/windows/windowslive/hotmail_bl1/hotmail_bl1.aspx?ocid=PID23879::T:WLMTAGL:ON:WL:en-ww:WM_IMHM_4:092009 -------------- next part -------------- An HTML attachment was scrubbed... URL: From hengist.podd at virgin.net Thu Dec 3 23:43:28 2009 From: hengist.podd at virgin.net (has) Date: Thu, 3 Dec 2009 22:43:28 +0000 Subject: [Pythonmac-SIG] [ann] py-appscript 0.21.0 Message-ID: Hi all, Announcing a new release of Python appscript, an easy-to-use Apple event bridge for the popular Python scripting language. http://appscript.sourceforge.net/py-appscript.html What's new in py-appscript 0.21.0: - A built-in workaround for Mac OS X 10.6's return ID bug prevents occasional unexpected timeout errors (this won't prevent the OS from periodically dropping other processes' Apple events on the floor, but appscript-based scripts should now be immune) - You can now launch and manipulate multiple instances of an application side-by-side - Python.app icons no longer appear in the Dock when using appscript on Python frameworks built for 10.5+ - Several bug fixes in 64-bit and Python 3.0 support. A new version of the ASDictionary documentation tool has also been released. ASDictionary 0.12.0 addresses occasional launch problems, and is a recommended update. Except for any bug-fix updates that might be required, this will be the final release of py-appscript before it hits the big one-zero, so please give it a thorough workout and report any issues as soon as possible. If no further problems are found, appscript 1.0.0 will be released in the next month or so. Enjoy! has p.s. Ruby and ObjC users can also check out the latest rb-appscript and objc-appscript trunks in appscript's Subversion repository for return ID workarounds and other improvements. -- Control AppleScriptable applications from Python, Ruby and ObjC: http://appscript.sourceforge.net From xiao at xiao-yu.com Thu Dec 3 04:41:30 2009 From: xiao at xiao-yu.com (Xiao Yu) Date: Wed, 2 Dec 2009 22:41:30 -0500 Subject: [Pythonmac-SIG] Can't build PIL on Snow Leopard Message-ID: <341B5CCC-723C-40FF-A4A3-F828964F26BA@xiao-yu.com> Hi, I apologize for not having caught onto the nuance of differences between the Apple system Python, python.org's Python and MacPort's Python yet. I have installed python.org's Python 2.6.4. I however have trouble building PIL on it. lipo: can't open input file: /var/tmp//ccmUAK0V.out (No such file or directory) error: Setup script exited with error: command 'gcc-4.0' failed with exit status 1 I am being told by the folks at comp.lang.python that the problem is because of missing libraries. Could someone please instruct me how to proceed? I couldn't google the proper procedures. My ultimate goal is to get my PyQt-PIL application working again. Regards, Xiao From Chris.Barker at noaa.gov Fri Dec 4 01:52:25 2009 From: Chris.Barker at noaa.gov (Christopher Barker) Date: Thu, 03 Dec 2009 16:52:25 -0800 Subject: [Pythonmac-SIG] Can't build PIL on Snow Leopard In-Reply-To: <341B5CCC-723C-40FF-A4A3-F828964F26BA@xiao-yu.com> References: <341B5CCC-723C-40FF-A4A3-F828964F26BA@xiao-yu.com> Message-ID: <4B185D49.302@noaa.gov> First: Does anyone have a PIL binary for Python2.6.4? That would be the easiest way to get it? I built one for Frederik last spring, but I don't know what happened to it, nor do I remember whether it was for py2.5 or py2.6 It's not too hard to do -- at least with 10.5 machine -- I have a 10.4.11 PP now, and macports does not build Universal right at this point :-( Xiao Yu wrote: > I apologize for not having caught onto the nuance of differences between the Apple system Python, python.org's Python and MacPort's Python yet. > > I have installed python.org's Python 2.6.4. I however have trouble building PIL on it. > > lipo: can't open input file: /var/tmp//ccmUAK0V.out (No such file or directory) > error: Setup script exited with error: command 'gcc-4.0' failed with exit status 1 > > I am being told by the folks at comp.lang.python that the problem is because of missing libraries. Could someone please instruct me how to proceed? I couldn't google the proper procedures. My ultimate goal is to get my PyQt-PIL application working again. That is likely. If you look at the error messages that came before, you may find more details, but PIL does depend in a couple other libs that Apple does not provide. You will find a list of these libs in the PIL docs, and probably discussion about Mac-specific issue in the archives of this list and assorted Wikis -- do some goggling. I think you need libjpeg and libfreetype, though freetype may now come with OS-X 10.6 The easiest way to get them is to use macports (or maybe fink). If you just need it to work for you, then it's pretty easy. Use macports to build libjpeg, and make sure the PIL build can find it, and away you go. If you want to re-distribute, then you'll want to build the libd Universal, which macports shoudl be able to do with: port install libjpeg _universal or something like that. Then you want make sure that PIL finds only the static libs -- I think macports builds both, so you may need to go delete the *.dylib versions so that they won't be found -- a kludge, but gcc really tries hard to use dynamic libs. Sorry I don't have time to do more right now! -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker at noaa.gov From listmail at gearyweb.com Fri Dec 4 03:45:56 2009 From: listmail at gearyweb.com (michael geary) Date: Thu, 3 Dec 2009 19:45:56 -0700 Subject: [Pythonmac-SIG] Can't build PIL on Snow Leopard In-Reply-To: <4B185D49.302@noaa.gov> References: <341B5CCC-723C-40FF-A4A3-F828964F26BA@xiao-yu.com> <4B185D49.302@noaa.gov> Message-ID: i have a PIL binary for python2.6.1 on Snow Leopard. I use the Apple-native python, and i haven't run the module through any tests to verify it's soundness, but just doing "import Image" in python works just fine... let me know if anyone would like it, or would like to discuss. I can always be found on #utahpython on IRC under the name mgeary. best, michael geary On Dec 3, 2009, at 5:52 PM, Christopher Barker wrote: > First: > > Does anyone have a PIL binary for Python2.6.4? That would be the easiest way to get it? > > I built one for Frederik last spring, but I don't know what happened to it, nor do I remember whether it was for py2.5 or py2.6 > > It's not too hard to do -- at least with 10.5 machine -- I have a 10.4.11 PP now, and macports does not build Universal right at this point :-( > > Xiao Yu wrote: >> I apologize for not having caught onto the nuance of differences between the Apple system Python, python.org's Python and MacPort's Python yet. I have installed python.org's Python 2.6.4. I however have trouble building PIL on it. >> lipo: can't open input file: /var/tmp//ccmUAK0V.out (No such file or directory) >> error: Setup script exited with error: command 'gcc-4.0' failed with exit status 1 >> I am being told by the folks at comp.lang.python that the problem is because of missing libraries. Could someone please instruct me how to proceed? I couldn't google the proper procedures. My ultimate goal is to get my PyQt-PIL application working again. > > That is likely. If you look at the error messages that came before, you may find more details, but PIL does depend in a couple other libs that Apple does not provide. > > You will find a list of these libs in the PIL docs, and probably discussion about Mac-specific issue in the archives of this list and assorted Wikis -- do some goggling. I think you need libjpeg and libfreetype, though freetype may now come with OS-X 10.6 > > The easiest way to get them is to use macports (or maybe fink). > > If you just need it to work for you, then it's pretty easy. Use macports to build libjpeg, and make sure the PIL build can find it, and away you go. > > If you want to re-distribute, then you'll want to build the libd Universal, which macports shoudl be able to do with: > > port install libjpeg _universal > > or something like that. Then you want make sure that PIL finds only the static libs -- I think macports builds both, so you may need to go delete the *.dylib versions so that they won't be found -- a kludge, but gcc really tries hard to use dynamic libs. > > Sorry I don't have time to do more right now! > > -Chris > > > > > -- > Christopher Barker, Ph.D. > Oceanographer > > Emergency Response Division > NOAA/NOS/OR&R (206) 526-6959 voice > 7600 Sand Point Way NE (206) 526-6329 fax > Seattle, WA 98115 (206) 526-6317 main reception > > Chris.Barker at noaa.gov > _______________________________________________ > Pythonmac-SIG maillist - Pythonmac-SIG at python.org > http://mail.python.org/mailman/listinfo/pythonmac-sig From downgeoff2 at hotmail.com Fri Dec 4 12:52:07 2009 From: downgeoff2 at hotmail.com (downie -) Date: Fri, 4 Dec 2009 06:52:07 -0500 Subject: [Pythonmac-SIG] OSX3 install problem In-Reply-To: References: , Message-ID: > To: pythonmac-sig at python.org > From: nad at acm.org > Date: Thu, 3 Dec 2009 13:42:07 -0800 > Subject: Re: [Pythonmac-SIG] OSX3 install problem > > In article , > downie - wrote: > > I'm trying to install Python on OSX10.3.9 , downloaded > > python-2.6.4_macosx10.3.dmg, but unfortunately the install process ends with > > 'There have been errors in the install process. Please try again.' > > Console.log entry is not much more informative: > > "2009-12-03 20:11:22 +0000 > > Not a JPEG file: starts with 0x89 0x50 > > 2009-12-03 20:14:11.844 Installer[387] Exception raised during posting of > > notification. Ignored. exception: Some files for PythonFramework-2.6 may > > not have been written correctly. (code 1)" > > > > Any ideas on where to look for better diagnostics? > > Interesting. The installer is seldom (if ever) tested on 10.3.9 these > days although the hope is that it should work. I forget if the OS X > Installer app has this option in 10.3 but, at least on later versions of > OS X, the Installer menu bar has a Window -> Installer Log option and at > the bottom of the Installer Log window there is an selector for "Show > Everything". Could you see if there is anything more there, perhaps the > specific file name? > > -- > Ned Deily, > nad at acm.org > It's actually under 'File/Show Log'. Log attached. Thanks, GD _________________________________________________________________ Windows Live Hotmail is faster and more secure than ever. http://www.microsoft.com/windows/windowslive/hotmail_bl1/hotmail_bl1.aspx?ocid=PID23879::T:WLMTAGL:ON:WL:en-ww:WM_IMHM_1:092009 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: 2.6.log.txt URL: From Chris.Barker at noaa.gov Fri Dec 4 18:26:57 2009 From: Chris.Barker at noaa.gov (Christopher Barker) Date: Fri, 04 Dec 2009 09:26:57 -0800 Subject: [Pythonmac-SIG] Can't build PIL on Snow Leopard In-Reply-To: References: <341B5CCC-723C-40FF-A4A3-F828964F26BA@xiao-yu.com> <4B185D49.302@noaa.gov> Message-ID: <4B194661.1090109@noaa.gov> michael geary wrote: > i have a PIL binary for python2.6.1 on Snow Leopard. I use the Apple-native python, What did you use for the dependencies? Though I don't know if the Apple-native python is universal anyway (though does it support both 32 and 64 bit?) The key thing is if the dependencies are statically linked -- if not, then no one can use it that doesn't have the same dynamic libs installed. you could run bist_mpkg on it, and send it to the OP and see what happens! -CHB -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker at noaa.gov From rowen at uw.edu Sat Dec 5 00:04:18 2009 From: rowen at uw.edu (Russell E. Owen) Date: Fri, 04 Dec 2009 15:04:18 -0800 Subject: [Pythonmac-SIG] py2app and pygame results in application that may not launch References: <4B147584.2050808@codebykevin.com> Message-ID: In article <4B147584.2050808 at codebykevin.com>, Kevin Walzer wrote: > On 11/30/09 3:21 PM, Russell E. Owen wrote: > > > > > The solution was to upgrade to the latest py2app and associated software. > > > > Russell, > > Is this a 32-bit or 64-bit application? I've tried a few times to update > to the latest py2app and macholib, but they barf on my four-way > universal 64-bit/32-bit app (using Tk-Cocoa). I don't think Ronald > Ousorren has had time to look at this yet and I don't know > py2app/macholib well enough to attempt a patch, so I've resorted to > using bundlebuilder to ship my apps in the meantime. > > --Kevin I'm pretty sure I'm using the python.org version of Python 2.5.2 that I was using with Leopard. I'm trying to keep backward compatible so I can build apps for folks on 10.5 and 10.4. So 32-bit only. Regards, -- Russell From nad at acm.org Sat Dec 5 02:41:24 2009 From: nad at acm.org (Ned Deily) Date: Fri, 04 Dec 2009 17:41:24 -0800 Subject: [Pythonmac-SIG] OSX3 install problem References: Message-ID: In article , downie - wrote: >[nad wrote]: > > In article , > > downie - wrote: > > > I'm trying to install Python on OSX10.3.9 , downloaded > > > python-2.6.4_macosx10.3.dmg, but unfortunately the install process ends > > > with > > > 'There have been errors in the install process. Please try again.' > > > Console.log entry is not much more informative: > > > "2009-12-03 20:11:22 +0000 > > > Not a JPEG file: starts with 0x89 0x50 > > > 2009-12-03 20:14:11.844 Installer[387] Exception raised during posting of > > > notification. Ignored. exception: Some files for PythonFramework-2.6 > > > may > > > not have been written correctly. (code 1)" > > > > > > Any ideas on where to look for better diagnostics? > > Interesting. The installer is seldom (if ever) tested on 10.3.9 these > > days although the hope is that it should work. I forget if the OS X > > Installer app has this option in 10.3 but, at least on later versions of > > OS X, the Installer menu bar has a Window -> Installer Log option and at > > the bottom of the Installer Log window there is an selector for "Show > > Everything". Could you see if there is anything more there, perhaps the > > specific file name? [...] > Dec 4 11:43:43 : Extracting files from Python Framework > Dec 4 11:43:43 : Running task: > /System/Library/PrivateFrameworks/Installation.framework/Resources/pax > Dec 4 11:44:24 : ERROR:Could not write file. - pax: WARNING! These patterns > were not matched: - > Dec 4 11:44:24 : > ./Versions/2.6/Resources/Python.app/Contents/Resources/English.lproj/Documenta > tion/ide/hello_world.gif > Dec 4 11:44:24 : > ./Versions/2.6/Resources/Python.app/Contents/Resources/English.lproj/Documenta > tion/ide/loading_ide.gif Ugh! This is an odd one! Since I'm too lazy to create a 10.3 system to test this, I'm only guessing at what's happening on 10.3 but it seems very likely that the reason the patterns weren't matched is that those two files from the installer package pax archive are attempting to be installed under bogus file names. If I mount the installer dmg file on 10.4.11 and use pax directly on the Archive file: $ cd "/Volumes/Python 2.6.4/Python.mpkg/Contents/Packages/" $ cd PythonFramework-2.6.pkg/Contents/ $ pax -zf Archive.pax.gz | grep '/ide' [...] ./Versions/2.6/Resources/Python.app/Contents/Resources/English.lproj/Docu mentation/ide/entering_in_new_window.gif ./Versions/2.6/Resources/Python.app/Contents/Resources/English.lproj/Docu mentation/ide/hello_world.gif0000664 0000000 0000120 00000036501 11271640421 0034576 0 ./Versions/2.6/Resources/Python.app/Contents/Resources/English.lproj/Docu mentation/ide/IDE.gif ./Versions/2.6/Resources/Python.app/Contents/Resources/English.lproj/Docu mentation/ide/index.html ./Versions/2.6/Resources/Python.app/Contents/Resources/English.lproj/Docu mentation/ide/loading_ide.gif0000664 0000000 0000120 00000142643 11271640421 0034527 0 [...] Note the two rather peculiar file names. On 10.5 or 10.6, the same commands with the same installer dmg produce the expected normal file names and on 10.5 and 10.6 the files are installed with those normal file names. Now on 10.4, those two files *are* installed with the bogus file names *but*, apparently unlike under 10.3, the 10.4 installer doesn't complain about the two files listed in the BOM not being found so the installation completes normally. What's doubly annoying about this is that those particular files are ancient, vestigial documentation files that should not even be part of the installer image anyway. See http://bugs.python.org/issue5648 for the details. Unfortunately, the fix to remove them was not applied to the 2.6 maintenance tree so those files remain in 2.6.x OS installers (they are gone in 3.1.1 and in the upcoming 2.7 release). So, since 10.3 isn't tested and since it doesn't cause any warning in 10.4 and since the two corrupted file names aren't used anyway, this problem has gone undetected. That said, the presence of those vestigial files should not be causing a problem and it is worrisome that any file names are being corrupted. Further investigation shows that it is only those two files in the entire Python frameworks directory that are affected. The actual contents of the files are OK, BTW. The issue of the two corrupted file names isn't limited to that one installer disk image, either: I see the same behavior with a 2.6.4rc2 installer that I built myself in a manner nearly identical to the official 2.6.4 one that Ronald built. Both were built on 10.5. Ah, but I also have a 2.6.4rc2 installer from the same source snapshot but built on 10.4 rather than 10.5 and - surprise! - the 10.4-built pax archive shows the correct file names. Thus, I conclude the probable root cause here is a some change in the 10.5 version of pax or possibly gzip. All of that is interesting and should be pinned down further so it doesn't happen again. I've opened a python bug tracker issue for it: http://bugs.python.org/issue7437 but that doesn't help you with getting 2.6.4 running on 10.3. You noted that 2.5.4 installs OK. If you're OK with just 2.5.4, then great. I can't think of a particularly easy way to workaround the 2.6.4 problem without going in and messing with the installer image itself. For testing purposes, I could whip up a 10.4-built image for you but that's not a long-term solution. Thanks for flagging this and for sending the extra logging info. -- Ned Deily, nad at acm.org From news at xiao-yu.com Sun Dec 6 08:04:08 2009 From: news at xiao-yu.com (Xiao Yu) Date: Sun, 6 Dec 2009 02:04:08 -0500 Subject: [Pythonmac-SIG] Can't build PIL on Snow Leopard Message-ID: There is no problem at all when I use Apple Python with pretty much everything. Except when I have to distribute it with py2app. A separate Python is essential for me. I could use MacPort or Fink but that would put me a few versions behind the latest release. I'd really like to just use Python from python.org and add all the libraries I need but I can't seem to compile any libraries for this Python. They all end with a similar error. I'm not sure what I'm missing. It gives the same error when I try to egg this too. Regards, Xiao > i have a PIL binary for python2.6.1 on Snow Leopard. I use the Apple-native python, and i haven't run the module through any tests to verify it's soundness, but just doing "import Image" in python works just fine... > > let me know if anyone would like it, or would like to discuss. I can always be found on #utahpython on IRC under the name mgeary. > > best, > > michael geary > > > On Dec 3, 2009, at 5:52 PM, Christopher Barker wrote: > > > First: > > > > Does anyone have a PIL binary for Python2.6.4? That would be the easiest way to get it? > > > > I built one for Frederik last spring, but I don't know what happened to it, nor do I remember whether it was for py2.5 or py2.6 > > > > It's not too hard to do -- at least with 10.5 machine -- I have a 10.4.11 PP now, and macports does not build Universal right at this point :-( > > > > Xiao Yu wrote: > >> I apologize for not having caught onto the nuance of differences between the Apple system Python, python.org's Python and MacPort's Python yet. I have installed python.org's Python 2.6.4. I however have trouble building PIL on it. > >> lipo: can't open input file: /var/tmp//ccmUAK0V.out (No such file or directory) > >> error: Setup script exited with error: command 'gcc-4.0' failed with exit status 1 > >> I am being told by the folks at comp.lang.python that the problem is because of missing libraries. Could someone please instruct me how to proceed? I couldn't google the proper procedures. My ultimate goal is to get my PyQt-PIL application working again. > > > > That is likely. If you look at the error messages that came before, you may find more details, but PIL does depend in a couple other libs that Apple does not provide. > > > > You will find a list of these libs in the PIL docs, and probably discussion about Mac-specific issue in the archives of this list and assorted Wikis -- do some goggling. I think you need libjpeg and libfreetype, though freetype may now come with OS-X 10.6 > > > > The easiest way to get them is to use macports (or maybe fink). > > > > If you just need it to work for you, then it's pretty easy. Use macports to build libjpeg, and make sure the PIL build can find it, and away you go. > > > > If you want to re-distribute, then you'll want to build the libd Universal, which macports shoudl be able to do with: > > > > port install libjpeg _universal > > > > or something like that. Then you want make sure that PIL finds only the static libs -- I think macports builds both, so you may need to go delete the *.dylib versions so that they won't be found -- a kludge, but gcc really tries hard to use dynamic libs. > > > > Sorry I don't have time to do more right now! > > > > -Chris > > > > > > > > > > -- > > Christopher Barker, Ph.D. > > Oceanographer > > > > Emergency Response Division > > NOAA/NOS/OR&R (206) 526-6959 voice > > 7600 Sand Point Way NE (206) 526-6329 fax > > Seattle, WA 98115 (206) 526-6317 main reception > > > > Chris.Barker at noaa.gov > > _______________________________________________ > > Pythonmac-SIG maillist - Pythonmac-SIG at python.org > > http://mail.python.org/mailman/listinfo/pythonmac-sig > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nad at acm.org Mon Dec 7 09:50:19 2009 From: nad at acm.org (Ned Deily) Date: Mon, 07 Dec 2009 00:50:19 -0800 Subject: [Pythonmac-SIG] Can't build PIL on Snow Leopard References: Message-ID: In article , Xiao Yu wrote: > There is no problem at all when I use Apple Python with pretty much > everything. Except when I have to distribute it with py2app. A separate > Python is essential for me. I could use MacPort or Fink but that would put me > a few versions behind the latest release. I'd really like to just use Python > from python.org and add all the libraries I need but I can't seem to compile > any libraries for this Python. They all end with a similar error. I'm not > sure what I'm missing. It gives the same error when I try to egg this too. For what it's worth, the MacPorts pythons seem to be keeping right up-to-date with the latest releases. $ sudo port selfupdate $ sudo port install py26-pil py26-py2app-devel should get you a working PIL 1.1.6, py2app 0.4.4, and python 2.6.4, all rooted in /opt/local/, e.g. /opt/local/bin/python2.6. -- Ned Deily, nad at acm.org From erik at letterror.com Mon Dec 7 10:54:59 2009 From: erik at letterror.com (Erik van Blokland) Date: Mon, 7 Dec 2009 10:54:59 +0100 Subject: [Pythonmac-SIG] Installing Python 2.6.4 alongside stock python 2.6.1 on SnowLeopard Message-ID: <9A61427D-09ED-4DD1-9474-6E1A14F9EF03@letterror.com> Hi, sorry to bother, but I've run into a spot of trouble in an area I'm not familiar with. (Ronald, this is a follow up of the post I sent yesterday, I'm sorry for the moving target. I'm stuck.) I installed python 2.6.4 on Snow Leopard 10.6.2. I used the prepackaged .dmg installer from python.org. The new 2.6.4: [eBook:pyobjc/trunk/launch] erik% python Python 2.6.4 (r264:75821M, Oct 27 2009, 19:48:32) The stock python 2.6.1 is also still there: [eBook:pyobjc/trunk/launch] erik% /usr/bin/python Python 2.6.1 (r261:67515, Jul 7 2009, 23:51:51) With casual testing the new 2.6.4 seems to work well. But when installing other libraries I get very peculiar crashes. Installing Twisted and Pyobjc (both from source, not easy_install) end in a similar way with lipo complaining and references to a 10.4 sdk: /Developer/SDKs/MacOSX10.4u.sdk. The /Developer/SDKs dir contains a 10.6 sdk. But I am not familiar with what happens or should happen in this place. I posted a question about this on the twistd list earlier, but now I see the same thing happen with trying to install pyobjc, I suspect something in my installation has gone wrong. My next step seems to be to reinstall Snow Leopard. Any pointers are welcome. Could it be related to 32 / 64 bit issues? Regards, Erik Tail of the pyobjc install log: building 'launch._launch' extension gcc-4.0 -arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk -fno-strict-aliasing -fno-common -dynamic -DNDEBUG -g -O3 -I/Library/Frameworks/Python.framework/Versions/2.6/include/python2.6 -c Modules/_launch.c -o build/temp.macosx-10.3-fat-2.6/Modules/_launch.o In file included from /Library/Frameworks/Python.framework/Versions/2.6/include/python2.6/unicodeobject.h:4, from /Library/Frameworks/Python.framework/Versions/2.6/include/python2.6/Python.h:85, from Modules/_launch.c:1: /Developer/SDKs/MacOSX10.4u.sdk/usr/include/stdarg.h:4:25: error: stdarg.h: No such file or directory In file included from /Library/Frameworks/Python.framework/Versions/2.6/include/python2.6/unicodeobject.h:4, from /Library/Frameworks/Python.framework/Versions/2.6/include/python2.6/Python.h:85, from Modules/_launch.c:1: /Developer/SDKs/MacOSX10.4u.sdk/usr/include/stdarg.h:4:25: error: stdarg.h: No such file or directory lipo: can't figure out the architecture type of: /var/tmp//ccNyhKCK.out error: command 'gcc-4.0' failed with exit status 1 [eBook:pyobjc/trunk/launch] erik% From downgeoff2 at hotmail.com Mon Dec 7 19:01:42 2009 From: downgeoff2 at hotmail.com (downie -) Date: Mon, 7 Dec 2009 13:01:42 -0500 Subject: [Pythonmac-SIG] OSX3 install problem In-Reply-To: References: , , , Message-ID: > To: pythonmac-sig at python.org > From: nad at acm.org > Date: Fri, 4 Dec 2009 17:41:24 -0800 > Subject: Re: [Pythonmac-SIG] OSX3 install problem > [snip] > All of that is interesting and should be pinned down further so it > doesn't happen again. I've opened a python bug tracker issue for it: > http://bugs.python.org/issue7437 but that doesn't help you with getting > 2.6.4 running on 10.3. You noted that 2.5.4 installs OK. If you're OK > with just 2.5.4, then great. I can't think of a particularly easy way > to workaround the 2.6.4 problem without going in and messing with the > installer image itself. For testing purposes, I could whip up a > 10.4-built image for you but that's not a long-term solution. Yes, the Python script I wanted to run works fine under 2.5.4 . I registered with the bugtracker but couldn't work out how to add myself to the notification list - I'll be leaving this mailing list shortly. > > Thanks for flagging this and for sending the extra logging info. Hey, I'm just a bug-magnet. Thanks for the help. GD _________________________________________________________________ Windows 7: Unclutter your desktop. Learn more. http://www.microsoft.com/windows/windows-7/videos-tours.aspx?h=7sec&slideid=1&media=aero-shake-7second&listid=1&stop=1&ocid=PID24727::T:WLMTAGL:ON:WL:en-US:WWL_WIN_7secdemo:122009 -------------- next part -------------- An HTML attachment was scrubbed... URL: From nad at acm.org Mon Dec 7 19:55:54 2009 From: nad at acm.org (Ned Deily) Date: Mon, 07 Dec 2009 10:55:54 -0800 Subject: [Pythonmac-SIG] Installing Python 2.6.4 alongside stock python 2.6.1 on SnowLeopard References: <9A61427D-09ED-4DD1-9474-6E1A14F9EF03@letterror.com> Message-ID: In article <9A61427D-09ED-4DD1-9474-6E1A14F9EF03 at letterror.com>, Erik van Blokland wrote: > Hi, > > sorry to bother, but I've run into a spot of trouble in an area I'm not > familiar with. > (Ronald, this is a follow up of the post I sent yesterday, I'm sorry for the > moving target. I'm stuck.) > > I installed python 2.6.4 on Snow Leopard 10.6.2. I used the prepackaged .dmg > installer from python.org. > > The new 2.6.4: > [eBook:pyobjc/trunk/launch] erik% python > Python 2.6.4 (r264:75821M, Oct 27 2009, 19:48:32) > > The stock python 2.6.1 is also still there: > [eBook:pyobjc/trunk/launch] erik% /usr/bin/python > Python 2.6.1 (r261:67515, Jul 7 2009, 23:51:51) > > With casual testing the new 2.6.4 seems to work well. But when installing > other libraries I get very peculiar crashes. Installing Twisted and Pyobjc > (both from source, not easy_install) end in a similar way with lipo > complaining and references to a 10.4 sdk: /Developer/SDKs/MacOSX10.4u.sdk. > The /Developer/SDKs dir contains a 10.6 sdk. But I am not familiar with what > happens or should happen in this place. > I posted a question about this on the twistd list earlier, but now I see the > same thing happen with trying to install pyobjc, I suspect something in my > installation has gone wrong. My next step seems to be to reinstall Snow > Leopard. Any pointers are welcome. You need to install the optional 10.4u SDK. It is included in the Xcode installer (on the Snow Leopard DVD) but, by default, is not selected for installation. -- Ned Deily, nad at acm.org From nad at acm.org Mon Dec 7 19:57:14 2009 From: nad at acm.org (Ned Deily) Date: Mon, 07 Dec 2009 10:57:14 -0800 Subject: [Pythonmac-SIG] OSX3 install problem References: Message-ID: In article , downie - wrote: > Yes, the Python script I wanted to run works fine under 2.5.4 . > I registered with the bugtracker but couldn't work out how to add myself to > the notification list - I'll be leaving this mailing list shortly. Edit the nosy field of the bug to add your registered name. -- Ned Deily, nad at acm.org From Chris.Barker at noaa.gov Mon Dec 7 20:21:28 2009 From: Chris.Barker at noaa.gov (Christopher Barker) Date: Mon, 07 Dec 2009 11:21:28 -0800 Subject: [Pythonmac-SIG] Can't build PIL on Snow Leopard In-Reply-To: References: Message-ID: <4B1D55B8.3010403@noaa.gov> Xiao Yu wrote: > There is no problem at all when I use Apple Python with pretty much > everything. Except when I have to distribute it with py2app. A separate > Python is essential for me. I could use MacPort or Fink ... > I need but I can't seem to compile any libraries for this Python. They > all end with a similar error. what else have you tried to compile other than PIL? Anyway, to compile PIL, you need its dependencies -- you can use macports or fink to build *jsut the dependencies*, and still use the Apple or python.org python. > I'm not sure what I'm missing. It gives > the same error when I try to egg this too. If the egg is a source egg, then it will try to build, so it's almost exactly the same as downloading and building by hand. -CHB -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker at noaa.gov From erik at letterror.com Mon Dec 7 21:03:36 2009 From: erik at letterror.com (Erik van Blokland) Date: Mon, 7 Dec 2009 21:03:36 +0100 Subject: [Pythonmac-SIG] Installing Python 2.6.4 alongside stock python 2.6.1 on SnowLeopard In-Reply-To: References: <9A61427D-09ED-4DD1-9474-6E1A14F9EF03@letterror.com> Message-ID: <04BA0D84-7CDA-4D54-A433-444FF29CC286@letterror.com> On 7 dec 2009, at 19:55, Ned Deily wrote: >> Leopard. Any pointers are welcome. > > You need to install the optional 10.4u SDK. It is included in the Xcode > installer (on the Snow Leopard DVD) but, by default, is not selected for > installation. Ai caramba! I had indeed not installed it from the SL installer. (There was a 10.4u SDK folder present, I guess not the right one). That did the trick, pyobjc and twisted installed without a hitch. What a relief :) Many many thanks! Erik From xiao at xiao-yu.com Sun Dec 6 11:00:14 2009 From: xiao at xiao-yu.com (Xiao Yu) Date: Sun, 6 Dec 2009 05:00:14 -0500 Subject: [Pythonmac-SIG] py2app/PyQt/64-bit/Mach-O Message-ID: Hi, I think this problem might have been previously discussed but I'm not too sure what the solution is. I'm attempting to build my PyQt4 application. I'm receiving an error here: File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/py2app/build_app.py", line 589, in _run self.run_normal() File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/py2app/build_app.py", line 660, in run_normal self.create_binaries(py_files, pkgdirs, extensions, loader_files) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/py2app/build_app.py", line 768, in create_binaries mm.mm.run_file(runtime) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/macholib/MachOGraph.py", line 66, in run_file m = self.createNode(MachO, pathname) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/macholib/MachOStandalone.py", line 23, in createNode res = super(FilteredMachOGraph, self).createNode(cls, name) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/altgraph/ObjectGraph.py", line 148, in createNode m = cls(name, *args, **kw) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/macholib/MachO.py", line 63, in __init__ self.load(file(filename, 'rb')) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/macholib/MachO.py", line 78, in load self.load_header(fh, 0, size) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/macholib/MachO.py", line 108, in load_header hdr = MachOHeader(self, fh, offset, size, magic, hdr, endian) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/macholib/MachO.py", line 148, in __init__ self.load(fh) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/macholib/MachO.py", line 161, in load header = self.mach_header.from_fileobj(fh, **kw) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/macholib/ptypes.py", line 44, in from_fileobj return cls.from_str(f.read(cls._size_), **kw) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/macholib/ptypes.py", line 48, in from_str return cls.from_tuple(struct.unpack(endian + cls._format_, s), **kw) error: unpack requires a string argument of length 32 > /opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/macholib/ptypes.py(48)from_str() -> return cls.from_tuple(struct.unpack(endian + cls._format_, s), **kw) Any solutions? I have qt4-mac 4.5.3 python26 @2.6.4_0+darwin py26-sip @4.9.3_0 py26-pyqt4 @4.6.2_0 py26-py2app-devel @0.4.4_0 py26-macholib @1.2.1_2 Regards, Xiao From kw at codebykevin.com Tue Dec 8 02:53:59 2009 From: kw at codebykevin.com (Kevin Walzer) Date: Mon, 07 Dec 2009 20:53:59 -0500 Subject: [Pythonmac-SIG] py2app/PyQt/64-bit/Mach-O In-Reply-To: References: Message-ID: <4B1DB1B7.3080507@codebykevin.com> On 12/6/09 5:00 AM, Xiao Yu wrote: > Hi, > > I think this problem might have been previously discussed but I'm not too sure what the solution is. > I'm attempting to build my PyQt4 application. > error: unpack requires a string argument of length 32 >> /opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/macholib/ptypes.py(48)from_str() > -> return cls.from_tuple(struct.unpack(endian + cls._format_, s), **kw) > > It's a problem with macholib (part of py2app). I've run into something similar trying to build a 64-bit Tkinter application, and I've seen other problems on the list with PyObjC. I don't know enough about macholib to offer a patch, and no one else has had time to delve into it. If you run across a solution, some of us would be glad to hear it! -- Kevin Walzer Code by Kevin http://www.codebykevin.com From kw at codebykevin.com Tue Dec 8 04:19:37 2009 From: kw at codebykevin.com (Kevin Walzer) Date: Mon, 07 Dec 2009 22:19:37 -0500 Subject: [Pythonmac-SIG] py2app/PyQt/64-bit/Mach-O In-Reply-To: <65fadfc30912071913o33210161n24bde05ead131f03@mail.gmail.com> References: <4B1DB1B7.3080507@codebykevin.com> <65fadfc30912071913o33210161n24bde05ead131f03@mail.gmail.com> Message-ID: <4B1DC5C9.7070606@codebykevin.com> On 12/7/09 10:13 PM, Nehemiah Dacres wrote: > the solution is to fix the endian bug. you're on intel right? I bet if > you used the new PySide qt python bridge, it wouldn't have this problem. > I bet its talking directly to the c++ runtime ? instead of ? ? It may be an issue with endian-ness, but the same problem has shown up with four-way universal builds of applications using Tkinter (mine) and PyObjC (see http://mail.python.org/pipermail/pythonmac-sig/2008-August/020423.html). It's an issue with macholib and/or py2app, in that they don't seem to be able to handle four-way universal builds. So PySide may not be the answer at all. -- Kevin Walzer Code by Kevin http://www.codebykevin.com From kw at codebykevin.com Wed Dec 9 02:22:41 2009 From: kw at codebykevin.com (Kevin Walzer) Date: Tue, 08 Dec 2009 20:22:41 -0500 Subject: [Pythonmac-SIG] Bundlebuilder and four-way universal binaries: alternative to py2app Message-ID: <4B1EFBE1.1020905@codebykevin.com> Hi all, I wanted to report that I've successfully built a four-way universal binary of one of my Python applications using bundlebuilder in Python 2.6.2. I previously had problems with this because I got errors about argvemulator not being supported (apparently a Carbon function that doesn't exist in 64-bit mode). Here are the steps I've taken: 1. In your setup/makeapplication.py script, don't import argvemulation. 2. When you run the setup script, make sure you call python2.6-all as the Python interpreter--this will hit the 64-bit and 32-bit versions. My call looks like this: python2.6-all makeapplication.py build And that's it. I realize that bundlebuilder is going away in Python 3.x, and I have no idea if it would work if you simply separated out the bundlebuilder.py module and ran it with your own Python 3.x applications. I also understand that bundlebuilder is quirky and a less graceful solution than py2app: you have to do some trial and error to get all the packages bundled in your app. However, until py2app plays nice with four-way universal binaries, bundlebuilder will be a good short- and mid-term solution for me. Just wanted to share, Kevin -- Kevin Walzer Code by Kevin http://www.codebykevin.com From kw at codebykevin.com Wed Dec 9 14:08:33 2009 From: kw at codebykevin.com (Kevin Walzer) Date: Wed, 09 Dec 2009 08:08:33 -0500 Subject: [Pythonmac-SIG] Bundlebuilder--why remove it? Message-ID: <4B1FA151.6020908@codebykevin.com> After spending some time getting bundlebuilder to work with my 64-bit programs, I have begun to wonder: what's the rationale for removing it from Python 3.X? Its Carbon dependencies can be eliminated by simply removing the "import argvemulator" statement, so (as far as I can see) there is no serious technical impediment to leaving it in the Python library. Bundlbuilder doesn't really argvemulation anyway, since hooks for this exist in all the major GUI libraries (Tk, wxPython, and certainly PyObjC). And while bundlebuilder is a less robust tool than py2app, it is nonetheless capable enough: I'm shipping two commercial applications that make use of it. In fact, its simplicity (a single module) make it easier to dig into and patch, something I can't do with py2app. I wouldn't have been able to release my applications without it. What's the best way to keep bundlebuilder available for Python 3.x? Submit a feature request at the bug tracker? Or separate it out, and submit a PyPi project? --Kevin -- Kevin Walzer Code by Kevin http://www.codebykevin.com From Chris.Barker at noaa.gov Wed Dec 9 18:32:53 2009 From: Chris.Barker at noaa.gov (Christopher Barker) Date: Wed, 09 Dec 2009 09:32:53 -0800 Subject: [Pythonmac-SIG] Bundlebuilder--why remove it? In-Reply-To: <4B1FA151.6020908@codebykevin.com> References: <4B1FA151.6020908@codebykevin.com> Message-ID: <4B1FDF45.3040603@noaa.gov> Kevin Walzer wrote: > Bundlbuilder > doesn't really argvemulation anyway, since hooks for this exist in all > the major GUI libraries (Tk, wxPython, and certainly PyObjC). I actually use argv emulation more for non-gui apps -- a way for folks that don't like the command line to do some simple processing with drag-and-drop. However, presumably py2app has the same issue, and if not, whatever py2app does could be ported over. Form my point of view I want something that works and will be supported. With Bob I. no longer active in the PythonMac community, py2app has been languishing, though Jack Jansen isn't around either, so so has BundleBuilder. Ronald has done a great job of fixing the really critical bugs -- but he's doing so much else. So it comes down to: is anyone intending to support either one, and if so -- that person gets to choose which! If it were me, I'd choose one based on what code base is the most robust and maintianble, rather than what happens to work now. What I'd really like to see is a "grand unification" of executable builders: while the actual executable building is platform dependent, detection of what modules need to be included, etc, is not, and neither is the API for specifying what you need. There has been some progress in that vein: bbfreeze uses modulgraph from the py2aap project. It also support Windows and Linux, and Mac a little bit -- the author recently requested that someone take on the Mac version -- it's not really his thing, but I don't think any one has. PyInstaller has a Mac version in SVN that I haven't tried yet. Are there others? Maybe putting over efforts behind one of these projects would be more fruitful -- we' only need to maintain the mac-specific parts. > And while bundlebuilder is a less robust tool than py2app, In what way? I never quite understood its limitations. > In fact, its simplicity (a single module) make it > easier to dig into and patch, something I can't do with py2app. I agree -- the py2app code is a bit opaque to me too. > I also > understand that bundlebuilder is quirky and a less graceful solution > than py2app: you have to do some trial and error to get all the packages > bundled in your app. Frankly, I have to do the same with py2app anyway, for all but trivial apps. On a related note: I had some thoughts about figuring out what to include. AFAICT, all the systems examine the source for imports to determine what to include. This used to work pretty well, but it seems more and more packages are using more dynamic import methods, and also setuptools fatures that result in: 1) not including packages I need and 2) including all sorts of stuff I don't need -- many, many megabytes! I've been wondering is the opposite approach would work: rather than examining the source, run the app, and examine it to see what got imported. This would, of course, might not include some things conditionally imported, but if you have decent test coverage, you could run it on your test code instead, and get a pretty good list. In practice, it seems there is always some hand-work in significant aps anyway. If you really wanted to be safe, you could do a superset of code analysis and run-time analysis, which as I think about it, is a good idea -- you wouldn't get anything extra that you weren't getting with code analysis anyway. Would it be as simple as dumping sys.modules after running the app? > What's the best way to keep bundlebuilder available for Python 3.x? > Submit a feature request at the bug tracker? Or separate it out, and > submit a PyPi project? Are you proposing to be the maintainer? I'd say submit patches, and see if they are accepted -- if not, then fork it and make a new project. I wish I could find time to work on it more, but I just haven't -- I will probably provide the occasional tiny patch to whichever system I end up continuing to use, but I can't really play a major role. my $0.02 -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker at noaa.gov From ron at arts-betel.org Wed Dec 9 21:55:49 2009 From: ron at arts-betel.org (Ron Arts) Date: Wed, 09 Dec 2009 21:55:49 +0100 Subject: [Pythonmac-SIG] Newbie question: py2app does only include main .py file, not the rest. Message-ID: <4B200ED5.8080100@arts-betel.org> Hi, I am porting an app that was initially written for Windows and Linux to OSX. For Linux an .rpm is created, for Windows I used a py2exe setup.py script. I adapted that script for OSX, and it seems to do a lot of work, generates an App Bundle, but in the Contents/Resources directory only the main .py file is created, not all other .py files from the application. If I copy those in manually I get: ImportError: No module named pkg_resources. Now I'm at a loss how to continue. What should I do next? Thanks, Ron From ronaldoussoren at mac.com Wed Dec 9 22:17:37 2009 From: ronaldoussoren at mac.com (Ronald Oussoren) Date: Wed, 09 Dec 2009 22:17:37 +0100 Subject: [Pythonmac-SIG] Bundlebuilder--why remove it? In-Reply-To: <4B1FA151.6020908@codebykevin.com> References: <4B1FA151.6020908@codebykevin.com> Message-ID: On 9 Dec, 2009, at 14:08, Kevin Walzer wrote: > After spending some time getting bundlebuilder to work with my 64-bit programs, I have begun to wonder: what's the rationale for removing it from Python 3.X? > > Its Carbon dependencies can be eliminated by simply removing the "import argvemulator" statement, so (as far as I can see) there is no serious technical impediment to leaving it in the Python library. Bundlbuilder doesn't really argvemulation anyway, since hooks for this exist in all the major GUI libraries (Tk, wxPython, and certainly PyObjC). > > And while bundlebuilder is a less robust tool than py2app, it is nonetheless capable enough: I'm shipping two commercial applications that make use of it. In fact, its simplicity (a single module) make it easier to dig into and patch, something I can't do with py2app. I wouldn't have been able to release my applications without it. Py2app's code isn't that bad, although it does seem to be more complex than needed. Refactoring is hard though due to a complete lack of automated tests. > > What's the best way to keep bundlebuilder available for Python 3.x? Submit a feature request at the bug tracker? Or separate it out, and submit a PyPi project? Separating it out would be better. I'm not interested in re-adding bundlebuilder. What really should be done is restart py2app development, starting with automated tests and improved egg support. I'd love to work on that but basicly don't have time for that at the moment. Ronald -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3567 bytes Desc: not available URL: From Chris.Barker at noaa.gov Wed Dec 9 23:50:08 2009 From: Chris.Barker at noaa.gov (Christopher Barker) Date: Wed, 09 Dec 2009 14:50:08 -0800 Subject: [Pythonmac-SIG] Newbie question: py2app does only include main .py file, not the rest. In-Reply-To: <4B200ED5.8080100@arts-betel.org> References: <4B200ED5.8080100@arts-betel.org> Message-ID: <4B2029A0.8090709@noaa.gov> Ron, Search this list and you'll a number of good discussions of py2app, but a few hints: 1) use the latest version: easy_install py2app==dev (at least I think that's the syntax) > generates an App Bundle, but in the Contents/Resources directory > only the main .py file is created, not all other .py files > from the application. There should be a "lib" dir in Resources that has most of the python code in it -- look in theree. Also, most of the python modules get put in a single zip archive, which you can unzip to see what's there. > If I copy those in manually I get: If you put them directly in Resources, I'm not sure they'll be found, anyway. > ImportError: No module named pkg_resources. That's a setuptools module -- eggs and setuptools are not supported well by py2app, though I can usually get it to work. Make sure none of your eggs are zipped -- that can be a problem. > Now I'm at a loss how to continue. What should I do next? Back up a step, and use py2app to build a simple app first. If that works, try adding stuff in bit my bit. If that's too hard to do, then you can built your entire app, run it, and then each time you get an error, you can add the missing package manually to the setup.py script. It's a bit slow going, but you'l get there. You can also look in the app bundle, and unzip the site-packages.zip to see what is there, and what's missing. adding a "print sys.path" can be helpful too -- stdout goes to the Console app, so you can see it. HTH, -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker at noaa.gov From kw at codebykevin.com Thu Dec 10 00:03:55 2009 From: kw at codebykevin.com (Kevin Walzer) Date: Wed, 09 Dec 2009 18:03:55 -0500 Subject: [Pythonmac-SIG] Bundlebuilder--why remove it? In-Reply-To: <4B1FDF45.3040603@noaa.gov> References: <4B1FA151.6020908@codebykevin.com> <4B1FDF45.3040603@noaa.gov> Message-ID: <4B202CDB.7010405@codebykevin.com> On 12/9/09 12:32 PM, Christopher Barker wrote: > Kevin Walzer wrote: >> Bundlbuilder doesn't really argvemulation anyway, since hooks for this >> exist in all the major GUI libraries (Tk, wxPython, and certainly >> PyObjC). > > I actually use argv emulation more for non-gui apps -- a way for folks > that don't like the command line to do some simple processing with > drag-and-drop. > > However, presumably py2app has the same issue, and if not, whatever > py2app does could be ported over. Hmm, OK, not sure how py2app does this. > > Form my point of view I want something that works and will be supported. > With Bob I. no longer active in the PythonMac community, py2app has been > languishing, though Jack Jansen isn't around either, so so has > BundleBuilder. Ronald has done a great job of fixing the really critical > bugs -- but he's doing so much else. Agreed. No criticism of Ronald; he is extremely busy and I am grateful for all he does. > > So it comes down to: is anyone intending to support either one, and if > so -- that person gets to choose which! If it were me, I'd choose one > based on what code base is the most robust and maintianble, rather than > what happens to work now. As I said, I've done some hacking on bundlebuilder, simply because I can more or less grok what's going on with it. > > What I'd really like to see is a "grand unification" of executable > builders: while the actual executable building is platform dependent, > detection of what modules need to be included, etc, is not, and neither > is the API for specifying what you need. > > There has been some progress in that vein: bbfreeze uses modulgraph from > the py2aap project. It also support Windows and Linux, and Mac a little > bit -- the author recently requested that someone take on the Mac > version -- it's not really his thing, but I don't think any one has. > > PyInstaller has a Mac version in SVN that I haven't tried yet. > > Are there others? Not that I know of. Pyinstaller looks interesting, but it's not there yet. > > Maybe putting over efforts behind one of these projects would be more > fruitful -- we' only need to maintain the mac-specific parts. Perhaps, but I'm not the person to do that...my time, like everyone else's, is also limited. > >> And while bundlebuilder is a less robust tool than py2app, > > In what way? I never quite understood its limitations. It doesn't seem to be quite as good at finding all the modules to include. I've found that I have had to manually specify some packages to bundle. Its debugging messages even say that it may not find everything, and that it may be a "false alarm." py2app, also, is a more general packaging tool--you can create pkg installers with it, and you can't with bundlebuilder. > >> What's the best way to keep bundlebuilder available for Python 3.x? >> Submit a feature request at the bug tracker? Or separate it out, and >> submit a PyPi project? > > Are you proposing to be the maintainer? I'd say submit patches, and see > if they are accepted -- if not, then fork it and make a new project. I might just fork bundlebuilder, once I move to Python 3.x, which won't be for some time. I need to make sure all the libraries I use or am planning to use are supported. In the shorter term, I'm going to move my app packaging to bundlebuilder, if for no other reason than it works for me now. The current issues with py2app and 64-bit support would be showstoppers for me, Ronald's time is too scarce for him to look at this right now, and I don't know enough to offer a fix. So I have to go with the solution that works. --Kevin -- Kevin Walzer Code by Kevin http://www.codebykevin.com From kw at codebykevin.com Thu Dec 10 00:05:13 2009 From: kw at codebykevin.com (Kevin Walzer) Date: Wed, 09 Dec 2009 18:05:13 -0500 Subject: [Pythonmac-SIG] Bundlebuilder--why remove it? In-Reply-To: References: <4B1FA151.6020908@codebykevin.com> Message-ID: <4B202D29.1070404@codebykevin.com> On 12/9/09 4:17 PM, Ronald Oussoren wrote: >> What's the best way to keep bundlebuilder available for Python 3.x? Submit a feature request at the bug tracker? Or separate it out, and submit a PyPi project? > > Separating it out would be better. I'm not interested in re-adding bundlebuilder. Understood. I'll probably fork it once I move to 3.x. --Kevin -- Kevin Walzer Code by Kevin http://www.codebykevin.com From Chris.Barker at noaa.gov Thu Dec 10 00:26:04 2009 From: Chris.Barker at noaa.gov (Christopher Barker) Date: Wed, 09 Dec 2009 15:26:04 -0800 Subject: [Pythonmac-SIG] Bundlebuilder--why remove it? In-Reply-To: References: <4B1FA151.6020908@codebykevin.com> Message-ID: <4B20320C.4070408@noaa.gov> Ronald Oussoren wrote: > What really should be done is restart py2app development, Unless PyInstaller is looking good -- there may be an advantage to a code base with more people working on it. Mac folks would still need to do the Mac-specific stuff, but not the rest of it. bbFreeze isn't bad, either, but needs more work -- I don't think it ever could produce an App bundle. > starting with automated tests What did you have in mind here? I can't quite image what unit-tests to write, but maybe a suite of test cases fro various packages that could as least be auto run on various platforms. There is a start to this in the samples dir -- so maybe we "just" need a test runner. > and improved egg support. by the way, I think bbFreeze has extended modulegraph -- partly for better egg support. and I suppose quad architecture support -- Kevin, isn't that your show-stopper? -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker at noaa.gov From charles.hartman at conncoll.edu Thu Dec 10 01:26:09 2009 From: charles.hartman at conncoll.edu (Charles Hartman) Date: Wed, 9 Dec 2009 19:26:09 -0500 Subject: [Pythonmac-SIG] Bundlebuilder--why remove it? In-Reply-To: References: <4B1FA151.6020908@codebykevin.com> Message-ID: I just want to add a vote (plea, whimper) from somebody who writes Python programs, doesn't feel particularly comfortable with Terminal or bash, and wants to be able to make distributable apps for Mac. And keep making them as Python and associated libs get updated. I may be wrong, but I think there are a whole lot of people like me, and in some sense we're an important part of the Python and Mac user base. From this point of view, hardly anything in the P. & M. development world is more important than a reliable and easy-to-use version of py2app. By the same token, interested as we are in all senses, we're pretty thoroughly unqualified to help with the development or even maintenance of the bundling code. Charles Hartman On Dec 9, 2009, at 4:17 PM, Ronald Oussoren wrote: > > On 9 Dec, 2009, at 14:08, Kevin Walzer wrote: > >> After spending some time getting bundlebuilder to work with my 64- >> bit programs, I have begun to wonder: what's the rationale for >> removing it from Python 3.X? >> >> Its Carbon dependencies can be eliminated by simply removing the >> "import argvemulator" statement, so (as far as I can see) there is >> no serious technical impediment to leaving it in the Python >> library. Bundlbuilder doesn't really argvemulation anyway, since >> hooks for this exist in all the major GUI libraries (Tk, wxPython, >> and certainly PyObjC). >> >> And while bundlebuilder is a less robust tool than py2app, it is >> nonetheless capable enough: I'm shipping two commercial >> applications that make use of it. In fact, its simplicity (a single >> module) make it easier to dig into and patch, something I can't do >> with py2app. I wouldn't have been able to release my applications >> without it. > > Py2app's code isn't that bad, although it does seem to be more > complex than needed. Refactoring is hard though due to a complete > lack of automated tests. > >> >> What's the best way to keep bundlebuilder available for Python 3.x? >> Submit a feature request at the bug tracker? Or separate it out, >> and submit a PyPi project? > > Separating it out would be better. I'm not interested in re-adding > bundlebuilder. > > What really should be done is restart py2app development, starting > with automated tests and improved egg support. I'd love to work on > that but basicly don't have time for that at the moment. > > Ronald_______________________________________________ > Pythonmac-SIG maillist - Pythonmac-SIG at python.org > http://mail.python.org/mailman/listinfo/pythonmac-sig From ronaldoussoren at mac.com Thu Dec 10 08:02:30 2009 From: ronaldoussoren at mac.com (Ronald Oussoren) Date: Thu, 10 Dec 2009 08:02:30 +0100 Subject: [Pythonmac-SIG] Bundlebuilder--why remove it? In-Reply-To: <4B20320C.4070408@noaa.gov> References: <4B1FA151.6020908@codebykevin.com> <4B20320C.4070408@noaa.gov> Message-ID: On 10 Dec, 2009, at 0:26, Christopher Barker wrote: > Ronald Oussoren wrote: > >> What really should be done is restart py2app development, > > Unless PyInstaller is looking good -- there may be an advantage to a code base with more people working on it. Mac folks would still need to do the Mac-specific stuff, but not the rest of it. bbFreeze isn't bad, either, but needs more work -- I don't think it ever could produce an App bundle. PyInstaller is GPL licensed and I am therefore not interested. > >> starting with automated tests > > What did you have in mind here? I can't quite image what unit-tests to write, but maybe a suite of test cases fro various packages that could as least be auto run on various platforms. There probably should be unittests at some point, but I'm more interested in functional/acceptence test style tests where every testcase builds an application bundle (or plugin bundle) and verifies that the result is correct. The verification step should idealy run the application to check that it works instead of only checking if files are present in the bundle. > > There is a start to this in the samples dir -- so maybe we "just" need a test runner. > > > and improved egg support. > > by the way, I think bbFreeze has extended modulegraph -- partly for better egg support. > > and I suppose quad architecture support -- Kevin, isn't that your show-stopper? Quad architecture is pretty low on my list, I have the files from Kevin to reproduce the issue but little time to work on py2app. Ronald -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3567 bytes Desc: not available URL: From kw at codebykevin.com Thu Dec 10 15:46:28 2009 From: kw at codebykevin.com (Kevin Walzer) Date: Thu, 10 Dec 2009 09:46:28 -0500 Subject: [Pythonmac-SIG] Bundlebuilder--why remove it? In-Reply-To: References: <4B1FA151.6020908@codebykevin.com> <4B20320C.4070408@noaa.gov> Message-ID: <4B2109C4.2040809@codebykevin.com> On 12/10/09 2:02 AM, Ronald Oussoren wrote: >> and I suppose quad architecture support -- Kevin, isn't that your show-stopper? > > Quad architecture is pretty low on my list, I have the files from Kevin to reproduce the issue but little time to work on py2app. Indeed, quad architecture is my biggest concern. Given the constraints on Ronald's time, which I understand, I've found bundlebuilder to be the best solution for my apps. I've done a bit more digging into the other alternatives. bbfreeze seems to be an an alpha state at the moment--as Chris said, it appears the developer of that tool is looking for a Mac developer to help and hasn't found that yet. pyinstaller seems to be farther along, it can actually produce Mac bundles, but it doesn't yet (AFAIK) produce universal binaries. It also seems to have some weird bugs with window focus and launching new instances of Python with a generic icon--at least, this has been reported on their mailing list WRT wxPython apps. So it doesn't seem ready for prime time yet either. Kevin -- Kevin Walzer Code by Kevin http://www.codebykevin.com From Chris.Barker at noaa.gov Fri Dec 11 18:50:11 2009 From: Chris.Barker at noaa.gov (Christopher Barker) Date: Fri, 11 Dec 2009 09:50:11 -0800 Subject: [Pythonmac-SIG] Bundlebuilder--why remove it? In-Reply-To: References: <4B1FA151.6020908@codebykevin.com> <4B20320C.4070408@noaa.gov> Message-ID: <4B228653.8070801@noaa.gov> Ronald Oussoren wrote: >>> What really should be done is restart py2app development, >> Unless PyInstaller is looking good -- there may be an advantage to a code base with more people working on it. Mac folks would still need to do the Mac-specific stuff, but not the rest of it. bbFreeze isn't bad, either, but needs more work -- I don't think it ever could produce an App bundle. > > PyInstaller is GPL licensed and I am therefore not interested. May I ask why? I understand for libraries, but PyInstaller is a stand alone -- you'd use it, rather than including it with something you produce. It could therefore be used for applications released under any license (though we can't freely borrow code -- darn). Unless in includes GPL's code in our bundle, which would be problem. However, from their FAQ: """ * If I use PyInstaller for my commercial Python application, will I have to distribute my source code as well? Absolutely not. You can ship the executables created with PyInstaller with whatever license you want. """ which looks reasonable to me. It still may not be a great technical solution, though. >>> starting with automated tests > There probably should be unittests at some point, but I'm more > interested in functional/acceptence test style tests where every > testcase builds an application bundle (or plugin bundle) and verifies > that the result is correct. The verification step should idealy run > the application to check that it works instead of only checking if > files are present in the bundle. Checking if it really works is tough -- but yes, it should at least test that it starts up without error. I think we could get a long way by having each test app produce a little output or something when run -- then at least that could be easily tested. I'll try to get a start on this. I have a couple test apps already that I've written just for this purpose - I just need to but a test framework around them. > Quad architecture is pretty low on my list, I wonder about this -- PPC macs are getting pretty old in the tooth -- when was the last one sold? I now that I'm getting pretty sick of supporting it -- macports is hardly getting tested on it, etc. I'm doing it now, as we're running a bunch of PPC macs here, but as soon as we can get permission(another ugly story), we'll all be getting new Intel macs, and I'll be able to dump PPC support for our in-house stuff. At which point I'll have a hard time finding any energy for working on PPC (plus I won't have one to test on). So maybe looking to the future -- PPC is dead. Also, my bundles are getting really, really huge as it is -- I'm not sure i want to go there with a quad build! > I have the files from Kevin to reproduce the issue but little time to work on py2app. Any idea how big a deal it is? If BundleBuilder supports it, then it's got to be possible! Kevin Walzer wrote: > I've done a bit more digging into the other alternatives. bbfreeze seems > to be an an alpha state at the moment-- For Mac or everything? certainly alpha for Mac. > pyinstaller seems to be farther along, it can actually > produce Mac bundles, but it doesn't yet (AFAIK) produce universal > binaries. I wonder why not -- it should use whatever python it's run with. Maybe I'll try to check it out -- though see above -- without the possibility of Ronald's help, I'm be afraid to even start! > It also seems to have some weird bugs with window focus and > launching new instances of Python with a generic icon--at least, this > has been reported on their mailing list WRT wxPython apps. So it doesn't > seem ready for prime time yet either. I wonder who's working on the Mac stuff -- I don't think I've seen anyone on this list talk about it -- are you here? -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker at noaa.gov From Chris.Barker at noaa.gov Fri Dec 11 19:01:23 2009 From: Chris.Barker at noaa.gov (Christopher Barker) Date: Fri, 11 Dec 2009 10:01:23 -0800 Subject: [Pythonmac-SIG] Bundlebuilder--why remove it? In-Reply-To: References: <4B1FA151.6020908@codebykevin.com> Message-ID: <4B2288F3.2050108@noaa.gov> Charles Hartman wrote: > I may be wrong, > but I think there are a whole lot of people like me, and in some sense > we're an important part of the Python and Mac user base. Maybe. I've been watching the community for a long time now, and I've observed two things: 1) there are a LOT more people running Python on the Mac than there were a few years ago. 2) There is less interest/involvement with mac-specific issues. This is a bit of a paradox, but I think these explain it: a) With OS-X, the Mac is far more like a *nix box for development purposes -- there just isn't as much need for mac-specific stuff. Even more so with macports and fink. b) With the greater use comes greater support -- more packages are being pre-built for the mac by their maintainers, rather than by the python-mac community (unfortunately, not always is a robust way!) c) People are doing more and more web development -- and in that case, the Mac really is just like any other unix box. All these lead to less involvement in things like Py2app, and bdist_mpkg. It's open-source, it's only going to get done if someone that needs it rolls up his/her sleeves and does it -- which may mean learning more about the nitty gritty details of OS-X. My suggestion to Charles, and Kevin, (and me!) is to try to find some time to dig into py2app -- I think once you grok the code structure, you can probably find the source of the errors, and then, if you can't figure out a solution, Ronald or Ned (or??) might be able to help out, without them having to do all the work -- i.e. use the experts only for the part where their expertise is critical. Oh, and writing some tests may be a good start! -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker at noaa.gov From msanvitale at real.com Fri Dec 11 22:57:32 2009 From: msanvitale at real.com (Mark Sanvitale) Date: Fri, 11 Dec 2009 13:57:32 -0800 Subject: [Pythonmac-SIG] deconstruct a py-appscript reference Message-ID: <442FBF34-6E38-4F53-B4EE-AC0E05C82001@real.com> I am new to both python and to appscript (I took up both at the same time). I am curious about what I think is an internal detail of the appscript module and its classes. Given my newbie status, I apologize in advance if my terminology for appscript things strays from the standard. I have a reference returned by calling get() on some other reference (e.g. asking an iphoto album for its child list). The reference I get back is fully resolved to a unique item (i.e. of the form app(u'/Applications/iPhoto.app').albums.ID(4294967326) and not involving a by-name lookup or query). Now, I can use the returned reference to get() its properties, however, if the property I am after is "id" then it would be wasteful (i.e. extra IPC) to perform a get() for the id property because I can see it is a component of the reference I already have. Thus, my question is how can I get the id directly out of such a reference? Presumably, via some means more elegant than parsing a string version of the reference. (So far, I have gotten as far as poking around myRef.AS_appdata and myRef.AS_aemreference but have not yet found the magic word.) Thanks. Mark Sanvitale From njriley at illinois.edu Fri Dec 11 23:29:55 2009 From: njriley at illinois.edu (Nicholas Riley) Date: Fri, 11 Dec 2009 16:29:55 -0600 Subject: [Pythonmac-SIG] deconstruct a py-appscript reference In-Reply-To: <442FBF34-6E38-4F53-B4EE-AC0E05C82001@real.com> References: <442FBF34-6E38-4F53-B4EE-AC0E05C82001@real.com> Message-ID: <20091211222955.GA11530@illinois.edu> On Fri, Dec 11, 2009 at 01:57:32PM -0800, Mark Sanvitale wrote: > Thus, my question is how can I get the id directly out of such a > reference? Presumably, via some means more elegant than parsing a > string version of the reference. (So far, I have gotten as far as > poking around myRef.AS_appdata and myRef.AS_aemreference but have > not yet found the magic word.) myRef.AS_aemreference._key should do it. I don't see another way to access this information. AEM/appscript uses inheritance pretty extensively, so you may find it useful to look at the hierarchy. For example: In [54]: type(s.AS_aemreference).mro() Out[54]: [, , , , , ] -- Nicholas Riley From kw at codebykevin.com Sat Dec 12 00:38:40 2009 From: kw at codebykevin.com (Kevin Walzer) Date: Fri, 11 Dec 2009 18:38:40 -0500 Subject: [Pythonmac-SIG] Bundlebuilder--why remove it? In-Reply-To: <4B228653.8070801@noaa.gov> References: <4B1FA151.6020908@codebykevin.com> <4B20320C.4070408@noaa.gov> <4B228653.8070801@noaa.gov> Message-ID: <4B22D800.7090703@codebykevin.com> On 12/11/09 12:50 PM, Christopher Barker wrote: > > Also, my bundles are getting really, really huge as it is -- I'm not > sure i want to go there with a quad build! > >> I have the files from Kevin to reproduce the issue but little time to >> work on py2app. > > Any idea how big a deal it is? If BundleBuilder supports it, then it's > got to be possible! Bundlebuilder basically wraps up/copies the relevant scripts, modules and frameworks into an app directory. To get it to work with 64-bit, you just need to make sure you're running the 64-bit Python interpreter and have removed incompatible bits (i.e. argvemulator). py2app does a lot more, including running install_name_tool on every binary in the app bundle. It's here that py2app barfs--it either says "too big to relocate header" or "struct needs string length of 8, 16, 32" (it varies). It's here that the complexity of py2app's internals gets beyond me. I've tried a few things to get it to work, but with no progress. -- Kevin Walzer Code by Kevin http://www.codebykevin.com From kw at codebykevin.com Sat Dec 12 00:41:21 2009 From: kw at codebykevin.com (Kevin Walzer) Date: Fri, 11 Dec 2009 18:41:21 -0500 Subject: [Pythonmac-SIG] Bundlebuilder--why remove it? In-Reply-To: <4B2288F3.2050108@noaa.gov> References: <4B1FA151.6020908@codebykevin.com> <4B2288F3.2050108@noaa.gov> Message-ID: <4B22D8A1.6060700@codebykevin.com> On 12/11/09 1:01 PM, Christopher Barker wrote: > > My suggestion to Charles, and Kevin, (and me!) is to try to find some > time to dig into py2app -- I think once you grok the code structure, you > can probably find the source of the errors, and then, if you can't > figure out a solution, Ronald or Ned (or??) might be able to help out, > without them having to do all the work -- i.e. use the experts only for > the part where their expertise is critical. I wasn't the first one to report the 64-bit bug for py2app on the list--a similar bug was reported over a year ago, with no resolution. I've also tried to fix the problem myself, but have made no progress. At this point I've lost interest in improving py2app and am content to stick with the dumber, blunter, but simpler instrument of bundlebuilder. -- Kevin Walzer Code by Kevin http://www.codebykevin.com From hengist.podd at virgin.net Sat Dec 12 19:57:08 2009 From: hengist.podd at virgin.net (has) Date: Sat, 12 Dec 2009 18:57:08 +0000 Subject: [Pythonmac-SIG] deconstruct a py-appscript reference In-Reply-To: References: Message-ID: Mark Sanvitale wrote: > I am new to both python and to appscript (I took up both at the same time). I am curious about what I think is an internal detail of the appscript module and its classes. Given my newbie status, I apologize in advance if my terminology for appscript things strays from the standard. > > I have a reference returned by calling get() on some other reference (e.g. asking an iphoto album for its child list). The reference I get back is fully resolved to a unique item (i.e. of the form app(u'/Applications/iPhoto.app').albums.ID(4294967326) and not involving a by-name lookup or query). Now, I can use the returned reference to get() its properties, however, if the property I am after is "id" then it would be wasteful (i.e. extra IPC) to perform a get() for the id property because I can see it is a component of the reference I already have. > > Thus, my question is how can I get the id directly out of such a reference? Presumably, via some means more elegant than parsing a string version of the reference. (So far, I have gotten as far as poking around myRef.AS_appdata and myRef.AS_aemreference but have not yet found the magic word.) If deep appscript juju is your thing, the aem package's Query subclasses provide a visitor method, AEM_resolve, for walking the entire reference. (The appscript.referencerenderer module uses it.) However, unless you're sending many thousands of events then asking the application for the object's id is unlikely to be a performance bottleneck. Personally I'd just ask the application, and maybe run a Python profiler if I think I'm still not getting my money's worth. If you are sending many thousands of events, there are probably other optimisation techniques you should be using anyway. Despite superficial appearances, Apple event IPC is a combination of RPC+queries; trying to apply object-oriented idioms to appscript code when dealing with large data sets is a common cause of poor performance. See chapter 13 of the appscript manual for more information, and post back here if you need more advice. HTH has -- Control AppleScriptable applications from Python, Ruby and ObjC: http://appscript.sourceforge.net From hengist.podd at virgin.net Sat Dec 12 20:00:22 2009 From: hengist.podd at virgin.net (has) Date: Sat, 12 Dec 2009 19:00:22 +0000 Subject: [Pythonmac-SIG] [ann] py-appscript 0.21.1 Message-ID: Hi all, Just posted a bug-fix release to PyPI that corrects a problem when unpacking Boolean values on Python 3.x. (The 1.0 release date is pushed back accordingly.) Please go beat harder on it. :) has -- Control AppleScriptable applications from Python, Ruby and ObjC: http://appscript.sourceforge.net From hengist.podd at virgin.net Sat Dec 12 20:33:25 2009 From: hengist.podd at virgin.net (has) Date: Sat, 12 Dec 2009 19:33:25 +0000 Subject: [Pythonmac-SIG] Bundlebuilder--why remove it? In-Reply-To: References: Message-ID: <248BD26D-2DA0-4276-9942-7E574D14CA23@virgin.net> Christopher Barker wrote: > It's open-source, it's only going to get done if someone that needs it rolls up his/her sleeves and does it -- which may mean learning more about the nitty gritty details of OS-X. Yep. If you want something done right, sometimes you just gotta step up and do it yourself. It's that or large cash bribes to get someone else to do it; take your pick. > My suggestion to Charles, and Kevin, (and me!) is to try to find some time to dig into py2app -- I think once you grok the code structure, you can probably find the source of the errors, and then, if you can't figure out a solution, Ronald or Ned (or??) might be able to help out, without them having to do all the work -- i.e. use the experts only for the part where their expertise is critical. I'd go further, and suggest pulling py2app to pieces. Creating an executable stub is a separate task to bundling project files is a separate task to locating and bundling third-party module dependencies is a separate task to bundling a Python framework (full or stripped). Some of these parts have more intrinsic value than others (e.g. identifying module dependencies), particularly as they can be used cross-platform and so will be easier to muster maintainers. Rather than revive the moribund bundlebuilder, put the time you'd spend on that into bringing the Xcode-Python templates up to scratch. The executable stub is a piece of crap that imports the first Python framework it finds, as opposed to the version you built with; fixing this should not be too difficult if you know some C/ObjC (dynamically binding framework functions is not that hard - I've done it myself - and you can borrow the code from py2app). Once you've got Xcode building Python-based .app bundles that don't suck, you can look at providing dependency bundling as an extra build phase. Personally, I like py2app and I'm not a huge fan of Xcode for Python development, but the first rule of sustainable OSS development has to be: when you have limited time, knowledge and manpower at your disposal, invest it on functionality that can't be leveraged from elsewhere. Xcode is not ideal, but it's good enough. In addition, Xcode's privileged position in OS X development makes it the first stopping point for newcomers to Python+PyObjC development, so targeting it will help market Python for Mac application development and strengthen the community as a whole. HTH has p.s. Re. the original subject line, kicking bundlebuilder and the rest of the decaying/decayed Mac-specific libraries out of Python's stdlib was completely the right decision for Python's overall health. -- Control AppleScriptable applications from Python, Ruby and ObjC: http://appscript.sourceforge.net From kw at codebykevin.com Sat Dec 12 23:26:32 2009 From: kw at codebykevin.com (Kevin Walzer) Date: Sat, 12 Dec 2009 17:26:32 -0500 Subject: [Pythonmac-SIG] Bundlebuilder--why remove it? In-Reply-To: <248BD26D-2DA0-4276-9942-7E574D14CA23@virgin.net> References: <248BD26D-2DA0-4276-9942-7E574D14CA23@virgin.net> Message-ID: <4B241898.1030101@codebykevin.com> On 12/12/09 2:33 PM, has wrote: > Christopher Barker wrote: > >> It's open-source, it's only going to get done if someone that needs it rolls up his/her sleeves and does it -- which may mean learning more about the nitty gritty details of OS-X. > > Yep. If you want something done right, sometimes you just gotta step up and do it yourself. It's that or large cash bribes to get someone else to do it; take your pick. Exactly what I'm doing--with bundlebuilder. > > > Rather than revive the moribund bundlebuilder, put the time you'd spend on that into bringing the Xcode-Python templates up to scratch. The executable stub is a piece of crap that imports the first Python framework it finds, as opposed to the version you built with; fixing this should not be too difficult if you know some C/ObjC (dynamically binding framework functions is not that hard - I've done it myself - and you can borrow the code from py2app). Once you've got Xcode building Python-based .app bundles that don't suck, you can look at providing dependency bundling as an extra build phase. > > Personally, I like py2app and I'm not a huge fan of Xcode for Python development, but the first rule of sustainable OSS development has to be: when you have limited time, knowledge and manpower at your disposal, invest it on functionality that can't be leveraged from elsewhere. Xcode is not ideal, but it's good enough. In addition, Xcode's privileged position in OS X development makes it the first stopping point for newcomers to Python+PyObjC development, so targeting it will help market Python for Mac application development and strengthen the community as a whole. > A fine project to take on if a) you use Xcode and b) you're doing PyObjC development. I am doing neither, so this doesn't interest me. > p.s. Re. the original subject line, kicking bundlebuilder and the rest of the decaying/decayed Mac-specific libraries out of Python's stdlib was completely the right decision for Python's overall health. > We disagree about bundlebuilder, but Apple's decision to deprecate Carbon made removing those bits from the standard library the only sane decision. None of that stuff works with a 64-bit build of 2.6, that's for sure. --Kevin -- Kevin Walzer Code by Kevin http://www.codebykevin.com From MLMLists at Comcast.net Sun Dec 13 06:21:43 2009 From: MLMLists at Comcast.net (Mitchell L Model) Date: Sun, 13 Dec 2009 00:21:43 -0500 Subject: [Pythonmac-SIG] 32-bit build of Python 3.1 on 64-bit machine running Snow Leopard? In-Reply-To: References: Message-ID: Is it possible to create 32-bit build of Python 3.1 on 64-bit machine running Snow Leopard? Using the 3.1 subversion sources I have tried a variety of configure settings, but all produce 64-bit builds. The following does create a 32-bit only build for 2.6: configure --enable-framework --with-universal-archs=32-bit --enable-universalsdk=/ One reason I am asking is because I am curious about how the 3.1.1 binary installer, which is 32-bit only, was created -- was it just done on a 32-bit machine? I have other reasons to ask that are related to attempts to many experiments I've performed on several different machines in 10.5 and 10.6 building 3.1 and PyQt and running 3.1 inside of IDEs. From nad at acm.org Sun Dec 13 11:39:15 2009 From: nad at acm.org (Ned Deily) Date: Sun, 13 Dec 2009 02:39:15 -0800 Subject: [Pythonmac-SIG] 32-bit build of Python 3.1 on 64-bit machine running Snow Leopard? References: Message-ID: In article , Mitchell L Model wrote: > Is it possible to create 32-bit build of Python 3.1 on 64-bit machine running > Snow Leopard? Using the 3.1 subversion sources I have tried a variety of > configure settings, but all produce 64-bit builds. The following does create > a 32-bit only build for 2.6: > configure --enable-framework --with-universal-archs=32-bit > --enable-universalsdk=/ > > One reason I am asking is because I am curious about how the 3.1.1 binary > installer, which is 32-bit only, was created -- was it just done on a 32-bit > machine? I have other reasons to ask that are related to attempts to many > experiments I've performed on several different machines in 10.5 and 10.6 > building 3.1 and PyQt and running 3.1 inside of IDEs. The 3.1.1 and recent 2.6.x installers were created on 10.5 systems. There are some fixes pending for both 2.x and 3.x to correctly build installers on 10.6. -- Ned Deily, nad at acm.org From amorris at mistermorris.com Sun Dec 13 16:45:13 2009 From: amorris at mistermorris.com (Adam Morris) Date: Sun, 13 Dec 2009 22:45:13 +0700 Subject: [Pythonmac-SIG] coercing to text Message-ID: <9b202abc0912130745u53d4fe79vfd9ca0a2aa8390f0@mail.gmail.com> Hi all, Quick question from someone getting used to appscript with python. How do I coerce into a text? reference.get(resulttype=k.text) But that doesn't seem to do what I want it to do. In Applescript I actually get the string, but in appscript I still get a reference. Thanks for your help! -Adam -------------- next part -------------- An HTML attachment was scrubbed... URL: From nad at acm.org Sun Dec 13 20:56:19 2009 From: nad at acm.org (Ned Deily) Date: Sun, 13 Dec 2009 11:56:19 -0800 Subject: [Pythonmac-SIG] coercing to text References: <9b202abc0912130745u53d4fe79vfd9ca0a2aa8390f0@mail.gmail.com> Message-ID: In article <9b202abc0912130745u53d4fe79vfd9ca0a2aa8390f0 at mail.gmail.com>, Adam Morris wrote: > Quick question from someone getting used to appscript with python. > > How do I coerce into a text? > > reference.get(resulttype=k.text) > > But that doesn't seem to do what I want it to do. In Applescript I actually > get the string, but in appscript I still get a reference. Are you sure you are formulating the correct reference? Normally there is no need to coerce the type. You might want to try has's ASTranslate tool: http://appscript.sourceforge.net/tools.html -- Ned Deily, nad at acm.org From amorris at mistermorris.com Mon Dec 14 12:18:13 2009 From: amorris at mistermorris.com (Adam Morris) Date: Mon, 14 Dec 2009 18:18:13 +0700 Subject: [Pythonmac-SIG] coercing to text Message-ID: <9b202abc0912140318n22443edbja061b7e6c7ccebc7@mail.gmail.com> In Applescript, I would write the following: tell app "Pages" to tell front document to get its selection -- text from character x to character y tell app "Pages" to tell front document to get its selection as text -- "whatever is selected" > Are you sure you are formulating the correct reference? Normally there > is no need to coerce the type. You might want to try has's ASTranslate > tool: http://appscript.sourceforge.net/tools.html > > -- > Ned Deily, > nad at acm.org > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hengist.podd at virgin.net Mon Dec 14 14:37:12 2009 From: hengist.podd at virgin.net (hengist.podd e-mail) Date: Mon, 14 Dec 2009 13:37:12 +0000 Subject: [Pythonmac-SIG] coercing to text Message-ID: Adam Morris wrote: > In Applescript, I would write the following: > > tell app "Pages" to tell front document to get its selection -- text from > character x to character y > tell app "Pages" to tell front document to get its selection as text -- > "whatever is selected" At a guess, the 'text' type isn't recognised outside of AppleScript 2.0 and you need to specify the 'Unicode text' type instead. So try k.Unicode_text in place of k.text and see if that works. (Annoyingly, applications seem to ignore unrecognised 'as' parameters rather than reporting them as errors, otherwise you'd know for sure if that was the problem.) If you run your above AppleScript in ASTranslate as Ned suggests, it will display each Apple event that AppleScript sends in appscript syntax. Very handy when you already know how to do it AppleScript and need some clues on how to write your appscript commands correctly. HTH has From aditya at wefoundland.com Tue Dec 15 06:17:33 2009 From: aditya at wefoundland.com (aditya bhargava) Date: Mon, 14 Dec 2009 23:17:33 -0600 Subject: [Pythonmac-SIG] Problems with py2app and qt Message-ID: <4d91314c0912142117q794089ct492b3289e0d9f119@mail.gmail.com> Hi python users, I'm getting some strange results running py2app on my machine. It works fine with most scripts, but any time I use it with a script that uses PyQt, the built application immediately quits and gives me an "unexpectedly quit" message. It's not the code, because I tried py2app with a couple of the example scripts that come with PyQt and got the same result. Any thoughts? I'm on mac OS X 10.4 running Python 2.5. My copy of py2app is very recent, I just got the latest one yesterday. Thanks for your help! Aditya -------------- next part -------------- An HTML attachment was scrubbed... URL: From nad at acm.org Tue Dec 15 07:19:40 2009 From: nad at acm.org (Ned Deily) Date: Mon, 14 Dec 2009 22:19:40 -0800 Subject: [Pythonmac-SIG] coercing to text References: Message-ID: Adam Morris wrote: >In Applescript, I would write the following: > tell app "Pages" to tell front document to get its selection -- text from > character x to character y >>> app('Pages').documents[1].selection.get() or just >>> app('Pages').documents[1].selection() app(u"/Applications/iWork '09/Pages.app").documents.ID(13779112).body_text.text[app.documents.ID(13 779112).body_text.characters[95]:app.documents.ID(13779112).body_text.cha racters[1681]] >tell app "Pages" to tell front document to get its selection as text -- > "whatever is selected" >>> app('Pages').documents[1].selection()() u'Lorem ipsum dolor sit amet, [...]' (Tested with Pages '09 and appscript 0.21) -- Ned Deily, nad at acm.org From amorris at mistermorris.com Tue Dec 15 12:49:08 2009 From: amorris at mistermorris.com (Adam Morris) Date: Tue, 15 Dec 2009 18:49:08 +0700 Subject: [Pythonmac-SIG] coercing to text (Adam Morris) Message-ID: <9b202abc0912150349k6e6194dne77646efa1c44dc4@mail.gmail.com> ASTranslate tells me that tell application "Pages" to tell front document to get selection as text should be app(u'Pages').documents[1].selection.get(resulttype=k.unicode_text) but that doesn't return what I want (a reference? ... hardly useful!). Yet: app('Pages').documents[1].selection()() returns what I want. The unicode text. I don't get what that 'extra' set of parens is doing. What implicit function is being called? Can't imagine it's get(). I'm obviously missing something here, but no idea what! ASTranslate seems to be missing it too. Thanks for your help! -Adam -------------- next part -------------- An HTML attachment was scrubbed... URL: From howes at ll.mit.edu Tue Dec 15 17:03:17 2009 From: howes at ll.mit.edu (Brad Howes) Date: Tue, 15 Dec 2009 11:03:17 -0500 Subject: [Pythonmac-SIG] Problems with py2app and qt In-Reply-To: <4d91314c0912142117q794089ct492b3289e0d9f119@mail.gmail.com> References: <4d91314c0912142117q794089ct492b3289e0d9f119@mail.gmail.com> Message-ID: <3C3F519A-6DFC-4010-BA4C-C3528A00F2E0@ll.mit.edu> On Dec 15, 2009, at 12:17 AM, aditya bhargava wrote: > I'm getting some strange results running py2app on my machine. It works fine with most scripts, but any time I use it with a script that uses PyQt, the built application immediately quits and gives me an "unexpectedly quit" message. It's not the code, because I tried py2app with a couple of the example scripts that come with PyQt and got the same result. Any thoughts? Usually, I see the problem documented in the Console app. Is there something there about missing stuff or incompatible architectures? Brad -- Brad Howes Group 42 MIT Lincoln Laboratory ? 244 Wood St. ? Lexington, MA 02173 Phone: 781.981.5292 ? Fax: 781.981.3495 ? Secretary: 781.981.7420 From bluemangroupie at gmail.com Tue Dec 15 18:30:23 2009 From: bluemangroupie at gmail.com (aditya bhargava) Date: Tue, 15 Dec 2009 11:30:23 -0600 Subject: [Pythonmac-SIG] Problems with py2app and qt In-Reply-To: <3C3F519A-6DFC-4010-BA4C-C3528A00F2E0@ll.mit.edu> References: <4d91314c0912142117q794089ct492b3289e0d9f119@mail.gmail.com> <3C3F519A-6DFC-4010-BA4C-C3528A00F2E0@ll.mit.edu> Message-ID: <4d91314c0912150930v3572b907j6b6d70c50faa3099@mail.gmail.com> It's a memory issue with Qt I think. The other interesting thing is, this problem doesn't occur if I build the app in alias mode with the -A flag...but of course that's not too useful if I want to distribute applications. Here's the issue I get: Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000 Thread 0 Crashed: 0 QtGui 0x167c792d QWidget::isActiveWindow() const + 141 1 QtGui 0x16c6fd2e QAccessibleWidget::state(int) const + 222 2 QtGui 0x16c6fd73 QAccessibleWidgetEx::state(int) const + 35 3 libqtaccessiblewidgets.dylib 0x16197b9d QAccessibleLineEdit::state(int) const + 33 4 QtGui 0x028f2178 QAccessible::cleanup() + 14728 5 QtGui 0x028f7016 QAccessible::cleanup() + 34854 6 QtGui 0x028f750d QAccessible::updateAccessibility(QObject*, int, QAccessible::Event) + 621 7 QtGui 0x02954e7a QWidgetPrivate::show_helper() + 330 8 QtGui 0x02955553 QWidget::setVisible(bool) + 1267 9 QtGui.so 0x02234aa5 sipQLineEdit::setVisible(bool) + 101 10 QtGui 0x02954cd8 QWidgetPrivate::showChildren(bool) + 328 11 QtGui 0x02954d8c QWidgetPrivate::show_helper() + 92 12 QtGui 0x02955553 QWidget::setVisible(bool) + 1267 13 QtGui.so 0x02417f11 sipQWidget::setVisible(bool) + 101 14 QtGui 0x02954cd8 QWidgetPrivate::showChildren(bool) + 328 15 QtGui 0x02954d8c QWidgetPrivate::show_helper() + 92 16 QtGui 0x02955553 QWidget::setVisible(bool) + 1267 17 QtGui.so 0x02417f11 sipQWidget::setVisible(bool) + 101 18 QtGui.so 0x02420150 sipQWidget::sipProtectVirt_languageChange(bool) + 25936 19 org.python.python 0x00499c5d PyEval_EvalFrameEx + 19936 20 org.python.python 0x0049b8ad PyEval_EvalCodeEx + 1819 21 org.python.python 0x0049ba61 PyEval_EvalCode + 87 22 org.python.python 0x004bf1d0 PyRun_FileExFlags + 260 23 org.python.python 0x0048fe3d PyAST_FromNode + 7784 24 org.python.python 0x00499c5d PyEval_EvalFrameEx + 19936 25 org.python.python 0x0049b8ad PyEval_EvalCodeEx + 1819 26 org.python.python 0x00498f2e PyEval_EvalFrameEx + 16561 27 org.python.python 0x0049b8ad PyEval_EvalCodeEx + 1819 28 org.python.python 0x0049ba61 PyEval_EvalCode + 87 29 org.python.python 0x004bf1d0 PyRun_FileExFlags + 260 30 org.python.python 0x004bf56a PyRun_SimpleFileExFlags + 640 31 org.python.python 0x004bf70d PyRun_SimpleFile + 40 32 ...cified.softwareRequirements 0x00007b9f start + 23863 33 ...cified.softwareRequirements 0x00008091 main + 297 34 ...cified.softwareRequirements 0x00001f63 start + 251 35 ...cified.softwareRequirements 0x00001e91 start + 41 Thread 0 crashed with X86 Thread State (32-bit): eax: 0x00000000 ebx: 0x028f2007 ecx: 0x16784105 edx: 0x00000000 edi: 0x003bc630 esi: 0x003ab8a0 ebp: 0xbfffdce8 esp: 0xbfffdcc0 ss: 0x0000001f efl: 0x00010246 eip: 0x167c792d cs: 0x00000017 ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037 -------------- next part -------------- An HTML attachment was scrubbed... URL: From emanuelesantos at gmail.com Tue Dec 15 19:45:37 2009 From: emanuelesantos at gmail.com (Emanuele Santos) Date: Tue, 15 Dec 2009 11:45:37 -0700 Subject: [Pythonmac-SIG] Problems with py2app and qt In-Reply-To: <4d91314c0912150930v3572b907j6b6d70c50faa3099@mail.gmail.com> References: <4d91314c0912142117q794089ct492b3289e0d9f119@mail.gmail.com> <3C3F519A-6DFC-4010-BA4C-C3528A00F2E0@ll.mit.edu> <4d91314c0912150930v3572b907j6b6d70c50faa3099@mail.gmail.com> Message-ID: Maybe your app is loading the wrong libs? Try running from the terminal and printing the libs that are being loaded: $ cd /path/to/your/bundle.app/Contents/MacOS $ DYLD_PRINT_LIBRARIES=1 ./your_app Check if all the Qt and PyQt libraries loaded are in your bundle. -- Emanuele. On Dec 15, 2009, at 10:30 AM, aditya bhargava wrote: > It's a memory issue with Qt I think. The other interesting thing is, > this problem doesn't occur if I build the app in alias mode with the > -A flag...but of course that's not too useful if I want to > distribute applications. > > Here's the issue I get: > > > Exception: EXC_BAD_ACCESS (0x0001) > Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000 > > Thread 0 Crashed: > 0 QtGui 0x167c792d > QWidget::isActiveWindow() const + 141 > 1 QtGui 0x16c6fd2e > QAccessibleWidget::state(int) const + 222 > 2 QtGui 0x16c6fd73 > QAccessibleWidgetEx::state(int) const + 35 > 3 libqtaccessiblewidgets.dylib 0x16197b9d > QAccessibleLineEdit::state(int) const + 33 > 4 QtGui 0x028f2178 > QAccessible::cleanup() + 14728 > 5 QtGui 0x028f7016 > QAccessible::cleanup() + 34854 > 6 QtGui 0x028f750d > QAccessible::updateAccessibility(QObject*, int, QAccessible::Event) > + 621 > 7 QtGui 0x02954e7a > QWidgetPrivate::show_helper() + 330 > 8 QtGui 0x02955553 > QWidget::setVisible(bool) + 1267 > 9 QtGui.so 0x02234aa5 > sipQLineEdit::setVisible(bool) + 101 > 10 QtGui 0x02954cd8 > QWidgetPrivate::showChildren(bool) + 328 > 11 QtGui 0x02954d8c > QWidgetPrivate::show_helper() + 92 > 12 QtGui 0x02955553 > QWidget::setVisible(bool) + 1267 > 13 QtGui.so 0x02417f11 > sipQWidget::setVisible(bool) + 101 > 14 QtGui 0x02954cd8 > QWidgetPrivate::showChildren(bool) + 328 > 15 QtGui 0x02954d8c > QWidgetPrivate::show_helper() + 92 > 16 QtGui 0x02955553 > QWidget::setVisible(bool) + 1267 > 17 QtGui.so 0x02417f11 > sipQWidget::setVisible(bool) + 101 > 18 QtGui.so 0x02420150 > sipQWidget::sipProtectVirt_languageChange(bool) + 25936 > 19 org.python.python 0x00499c5d PyEval_EvalFrameEx > + 19936 > 20 org.python.python 0x0049b8ad PyEval_EvalCodeEx > + 1819 > 21 org.python.python 0x0049ba61 PyEval_EvalCode + 87 > 22 org.python.python 0x004bf1d0 PyRun_FileExFlags > + 260 > 23 org.python.python 0x0048fe3d PyAST_FromNode + > 7784 > 24 org.python.python 0x00499c5d PyEval_EvalFrameEx > + 19936 > 25 org.python.python 0x0049b8ad PyEval_EvalCodeEx > + 1819 > 26 org.python.python 0x00498f2e PyEval_EvalFrameEx > + 16561 > 27 org.python.python 0x0049b8ad PyEval_EvalCodeEx > + 1819 > 28 org.python.python 0x0049ba61 PyEval_EvalCode + 87 > 29 org.python.python 0x004bf1d0 PyRun_FileExFlags > + 260 > 30 org.python.python 0x004bf56a > PyRun_SimpleFileExFlags + 640 > 31 org.python.python 0x004bf70d PyRun_SimpleFile + > 40 > 32 ...cified.softwareRequirements 0x00007b9f start + 23863 > 33 ...cified.softwareRequirements 0x00008091 main + 297 > 34 ...cified.softwareRequirements 0x00001f63 start + 251 > 35 ...cified.softwareRequirements 0x00001e91 start + 41 > > Thread 0 crashed with X86 Thread State (32-bit): > eax: 0x00000000 ebx: 0x028f2007 ecx: 0x16784105 edx: 0x00000000 > edi: 0x003bc630 esi: 0x003ab8a0 ebp: 0xbfffdce8 esp: 0xbfffdcc0 > ss: 0x0000001f efl: 0x00010246 eip: 0x167c792d cs: 0x00000017 > ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037 > _______________________________________________ > Pythonmac-SIG maillist - Pythonmac-SIG at python.org > http://mail.python.org/mailman/listinfo/pythonmac-sig From hengist.podd at virgin.net Tue Dec 15 19:48:12 2009 From: hengist.podd at virgin.net (has) Date: Tue, 15 Dec 2009 18:48:12 +0000 Subject: [Pythonmac-SIG] coercing to text (Adam Morris) In-Reply-To: References: Message-ID: <03535A76-EC68-49CF-8A48-6A6717120580@virgin.net> Adam Morris wrote: > ASTranslate tells me that > tell application "Pages" to tell front document to get selection as text > should be > app(u'Pages').documents[1].selection.get(resulttype=k.unicode_text) > > but that doesn't return what I want (a reference? ... hardly useful!). Yet: > > app('Pages').documents[1].selection()() > > returns what I want. The unicode text. > > I don't get what that 'extra' set of parens is doing. What implicit function > is being called? Can't imagine it's get(). app('Pages').documents[1].selection()() is shorthand for: app('Pages').documents[1].selection.get().get() First command asks for the selection property's value; Pages returns a reference representing a text range. Second command asks for the specified text range, Pages returns the characters in that range as a (Unicode) string. > I'm obviously missing something here, but no idea what! ASTranslate seems to > be missing it too. Thanks for your help! ASTranslate only tells you what events AppleScript sent. In this case, it looks like Pages is completely ignoring the return type argument and always returning a reference (Apple never laid down hard rules about how this feature should work, so different applications do all sorts of different things - though most just ignore it). If the value returned by an application command isn't of the type you specified, AppleScript will make its own attempt to correct this by coercing the value itself - and AS resolves coercing a reference by packing it into a 'get' event and sending it off for the application to evaluate. (You won't see that second event in ASTranslate unless the 'send events to app' option is checked.) Appscript replicates most AppleScript behaviours for sake of application compatibility, but doesn't try to mimic this sort of opaque, non-publicly documented magic (e.g. no implicit gets, no munging of 'count' commands) just because it's tricky to figure out exactly what AS is doing at times, and mimicking it badly is worse than not mimicking it at all. So what you ask appscript for is exactly what you get, and 98% of the time it's what AS would have asked for as well. It's the other 2% of corner cases that are tricky to fathom, but once you understand what's going on it should be straightforward to rephrase your requests appropriately - in this case by sending a second 'get' command yourself. HTH has -- Control AppleScriptable applications from Python, Ruby and ObjC: http://appscript.sourceforge.net From bluemangroupie at gmail.com Tue Dec 15 21:27:10 2009 From: bluemangroupie at gmail.com (aditya bhargava) Date: Tue, 15 Dec 2009 14:27:10 -0600 Subject: [Pythonmac-SIG] Problems with py2app and qt In-Reply-To: References: <4d91314c0912142117q794089ct492b3289e0d9f119@mail.gmail.com> <3C3F519A-6DFC-4010-BA4C-C3528A00F2E0@ll.mit.edu> <4d91314c0912150930v3572b907j6b6d70c50faa3099@mail.gmail.com> Message-ID: <4d91314c0912151227q57e4fe7atd65d3cb76912d6f2@mail.gmail.com> Brilliant...it turned out that the Qt libraries were being loaded *twice* ? once from inside the bundle and once from the libraries on my computer. The hack fix was to create a qt.conf file inside Contents/Resources and give it a bad path...this way only the libraries inside the bundle are being loaded. Putting this inside qt.conf: [Paths] Plugins = bollocks Did the trick :) Thanks Emanuele! On Tue, Dec 15, 2009 at 12:45 PM, Emanuele Santos wrote: > Maybe your app is loading the wrong libs? > Try running from the terminal and printing the libs that are being loaded: > > $ cd /path/to/your/bundle.app/Contents/MacOS > $ DYLD_PRINT_LIBRARIES=1 ./your_app > > Check if all the Qt and PyQt libraries loaded are in your bundle. > > -- Emanuele. > > > On Dec 15, 2009, at 10:30 AM, aditya bhargava wrote: > > It's a memory issue with Qt I think. The other interesting thing is, this >> problem doesn't occur if I build the app in alias mode with the -A >> flag...but of course that's not too useful if I want to distribute >> applications. >> >> Here's the issue I get: >> >> >> Exception: EXC_BAD_ACCESS (0x0001) >> Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000 >> >> Thread 0 Crashed: >> 0 QtGui 0x167c792d >> QWidget::isActiveWindow() const + 141 >> 1 QtGui 0x16c6fd2e >> QAccessibleWidget::state(int) const + 222 >> 2 QtGui 0x16c6fd73 >> QAccessibleWidgetEx::state(int) const + 35 >> 3 libqtaccessiblewidgets.dylib 0x16197b9d >> QAccessibleLineEdit::state(int) const + 33 >> 4 QtGui 0x028f2178 QAccessible::cleanup() + >> 14728 >> 5 QtGui 0x028f7016 QAccessible::cleanup() + >> 34854 >> 6 QtGui 0x028f750d >> QAccessible::updateAccessibility(QObject*, int, QAccessible::Event) + 621 >> 7 QtGui 0x02954e7a >> QWidgetPrivate::show_helper() + 330 >> 8 QtGui 0x02955553 >> QWidget::setVisible(bool) + 1267 >> 9 QtGui.so 0x02234aa5 >> sipQLineEdit::setVisible(bool) + 101 >> 10 QtGui 0x02954cd8 >> QWidgetPrivate::showChildren(bool) + 328 >> 11 QtGui 0x02954d8c >> QWidgetPrivate::show_helper() + 92 >> 12 QtGui 0x02955553 >> QWidget::setVisible(bool) + 1267 >> 13 QtGui.so 0x02417f11 >> sipQWidget::setVisible(bool) + 101 >> 14 QtGui 0x02954cd8 >> QWidgetPrivate::showChildren(bool) + 328 >> 15 QtGui 0x02954d8c >> QWidgetPrivate::show_helper() + 92 >> 16 QtGui 0x02955553 >> QWidget::setVisible(bool) + 1267 >> 17 QtGui.so 0x02417f11 >> sipQWidget::setVisible(bool) + 101 >> 18 QtGui.so 0x02420150 >> sipQWidget::sipProtectVirt_languageChange(bool) + 25936 >> 19 org.python.python 0x00499c5d PyEval_EvalFrameEx + >> 19936 >> 20 org.python.python 0x0049b8ad PyEval_EvalCodeEx + 1819 >> 21 org.python.python 0x0049ba61 PyEval_EvalCode + 87 >> 22 org.python.python 0x004bf1d0 PyRun_FileExFlags + 260 >> 23 org.python.python 0x0048fe3d PyAST_FromNode + 7784 >> 24 org.python.python 0x00499c5d PyEval_EvalFrameEx + >> 19936 >> 25 org.python.python 0x0049b8ad PyEval_EvalCodeEx + 1819 >> 26 org.python.python 0x00498f2e PyEval_EvalFrameEx + >> 16561 >> 27 org.python.python 0x0049b8ad PyEval_EvalCodeEx + 1819 >> 28 org.python.python 0x0049ba61 PyEval_EvalCode + 87 >> 29 org.python.python 0x004bf1d0 PyRun_FileExFlags + 260 >> 30 org.python.python 0x004bf56a PyRun_SimpleFileExFlags >> + 640 >> 31 org.python.python 0x004bf70d PyRun_SimpleFile + 40 >> 32 ...cified.softwareRequirements 0x00007b9f start + 23863 >> 33 ...cified.softwareRequirements 0x00008091 main + 297 >> 34 ...cified.softwareRequirements 0x00001f63 start + 251 >> 35 ...cified.softwareRequirements 0x00001e91 start + 41 >> >> Thread 0 crashed with X86 Thread State (32-bit): >> eax: 0x00000000 ebx: 0x028f2007 ecx: 0x16784105 edx: 0x00000000 >> edi: 0x003bc630 esi: 0x003ab8a0 ebp: 0xbfffdce8 esp: 0xbfffdcc0 >> ss: 0x0000001f efl: 0x00010246 eip: 0x167c792d cs: 0x00000017 >> ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037 >> _______________________________________________ >> Pythonmac-SIG maillist - Pythonmac-SIG at python.org >> http://mail.python.org/mailman/listinfo/pythonmac-sig >> > > _______________________________________________ > Pythonmac-SIG maillist - Pythonmac-SIG at python.org > http://mail.python.org/mailman/listinfo/pythonmac-sig > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jon.christopher at gmail.com Tue Dec 15 22:14:24 2009 From: jon.christopher at gmail.com (Jon Christopher) Date: Tue, 15 Dec 2009 13:14:24 -0800 Subject: [Pythonmac-SIG] timeout of connection? Message-ID: <6b913bc30912151314t779eee92q8cf27bbeab02f37d@mail.gmail.com> I'm the developer of PyeTV (http://code.google.com/p/pyetv/), a Front Row plugin for EyeTV. I'm experiencing some weird behavior that I'd like to ask the experts here about. Essentially all PyeTV does is communicate with EyeTV via appscript and throw up a few menu options in Front Row. When the user activates a menu option for playing a recording, it sends the appropriate appscript command to EyeTV, something like: app("EyeTV").play(id) where "id" is the stored integer id of the recording to play. In general, this works quite well, however, there are certain curcumstances where it seems that EyeTV never gets the message to play the recording. It seems that after Front Row has been idle for quite some time (perhaps 12 hours or more), and I then attempt to play a recording, it doesn't seem like the message is sent to EyeTV, (or perhaps it's just not received; I can't really tell.) If I then restart Front Row (and therefore python) and try again, it works 100% of the time, until it's been idle again for a long time. I haven't been able to observe anything unusual in the logs, and am beginning to grasp at straws for an explanation here. I've stared at my code and poked and prodded it until my eyes have started bleeding, all to no avail. I'm beginning to wonder if the problem might lie in some of the behind-the-scenes implementation details of appscript. Perhaps there's some sort of caching of connections to applications which times at some point. In any case, can any of the appscript gurus think of any reason why the following (pseudo) code should fail: import appscript id=app("EyeTV").recordings.get()[0] app("EyeTV").play(id) # works just fine app("EyeTV").stop() #works just fine go_do_other_stuff_possibly_in_other_threads_for_a_really_long_time() app("EyeTV").play(id) # has no effect Thanks, Jon Again, I've researched this quite a bit, and haven't From howes at ll.mit.edu Wed Dec 16 19:25:52 2009 From: howes at ll.mit.edu (Brad Howes) Date: Wed, 16 Dec 2009 13:25:52 -0500 Subject: [Pythonmac-SIG] timeout of connection? In-Reply-To: <6b913bc30912151314t779eee92q8cf27bbeab02f37d@mail.gmail.com> References: <6b913bc30912151314t779eee92q8cf27bbeab02f37d@mail.gmail.com> Message-ID: <6329DB29-7485-4BD1-AD30-590E957EB8A7@ll.mit.edu> On Dec 15, 2009, at 4:14 PM, Jon Christopher wrote: > It seems that after Front Row has been idle for quite some time > (perhaps 12 hours or more), and I then attempt to > play a recording, it doesn't seem like the message is sent to EyeTV, > (or perhaps it's just not received; I can't really tell.) If I then > restart Front Row (and therefore python) and try again, it works 100% > of the time, until it's been idle again for a long time. I too have encountered this issue for a long-living connecting to an iTunes process. Not sure if it was connected to the notorious wrap-around bug in AppleScript message IDs, but after upgrading my appscript install, it has not materialized in weeks. Brad -- PySLiMP3 - Python + ITunes + SLiMP3 (http://code.google.com/p/pyslimp3) From jon.christopher at gmail.com Wed Dec 16 20:26:57 2009 From: jon.christopher at gmail.com (Jon Christopher) Date: Wed, 16 Dec 2009 11:26:57 -0800 Subject: [Pythonmac-SIG] timeout of connection? In-Reply-To: <6329DB29-7485-4BD1-AD30-590E957EB8A7@ll.mit.edu> References: <6b913bc30912151314t779eee92q8cf27bbeab02f37d@mail.gmail.com> <6329DB29-7485-4BD1-AD30-590E957EB8A7@ll.mit.edu> Message-ID: <6b913bc30912161126v44cf3a2dgc831245851de77cb@mail.gmail.com> Thanks for the reply, Brad. I'm not familiar with the issue you describe. Can you provide a pointer to some related info? How would I test to see if my script is affected? Thanks again, Jon On Wed, Dec 16, 2009 at 10:25 AM, Brad Howes wrote: > On Dec 15, 2009, at 4:14 PM, Jon Christopher wrote: > >> It seems that after Front Row has been idle for quite some time >> (perhaps 12 hours or more), and I then attempt to >> play a recording, it doesn't seem like the message is sent to EyeTV, >> (or perhaps it's just not received; I can't really tell.) ?If I then >> restart Front Row (and therefore python) and try again, it works 100% >> of the time, until it's been idle again for a long time. > > > I too have encountered this issue for a long-living connecting to an iTunes process. Not sure if it was connected to the notorious wrap-around bug in AppleScript message IDs, but after upgrading my appscript install, it has not materialized in weeks. > > Brad > > -- > PySLiMP3 - Python + ITunes + SLiMP3 (http://code.google.com/p/pyslimp3) > > _______________________________________________ > Pythonmac-SIG maillist ?- ?Pythonmac-SIG at python.org > http://mail.python.org/mailman/listinfo/pythonmac-sig > From howes at ll.mit.edu Thu Dec 17 19:26:53 2009 From: howes at ll.mit.edu (Brad Howes) Date: Thu, 17 Dec 2009 13:26:53 -0500 Subject: [Pythonmac-SIG] timeout of connection? In-Reply-To: <6b913bc30912161126v44cf3a2dgc831245851de77cb@mail.gmail.com> References: <6b913bc30912151314t779eee92q8cf27bbeab02f37d@mail.gmail.com> <6329DB29-7485-4BD1-AD30-590E957EB8A7@ll.mit.edu> <6b913bc30912161126v44cf3a2dgc831245851de77cb@mail.gmail.com> Message-ID: <7D0C23D0-10B9-4F1D-9EF8-761E692A3547@ll.mit.edu> On Dec 16, 2009, at 2:26 PM, Jon Christopher wrote: > Thanks for the reply, Brad. > > I'm not familiar with the issue you describe. Can you provide a > pointer to some related info? How would I test to see if my script is > affected? http://db.tidbits.com/article/10643 -- Brad Howes Group 42 MIT Lincoln Laboratory ? 244 Wood St. ? Lexington, MA 02173 Phone: 781.981.5292 ? Fax: 781.981.3495 ? Secretary: 781.981.7420 From jon.christopher at gmail.com Thu Dec 17 20:01:30 2009 From: jon.christopher at gmail.com (Jon Christopher) Date: Thu, 17 Dec 2009 11:01:30 -0800 Subject: [Pythonmac-SIG] timeout of connection? In-Reply-To: <7D0C23D0-10B9-4F1D-9EF8-761E692A3547@ll.mit.edu> References: <6b913bc30912151314t779eee92q8cf27bbeab02f37d@mail.gmail.com> <6329DB29-7485-4BD1-AD30-590E957EB8A7@ll.mit.edu> <6b913bc30912161126v44cf3a2dgc831245851de77cb@mail.gmail.com> <7D0C23D0-10B9-4F1D-9EF8-761E692A3547@ll.mit.edu> Message-ID: <6b913bc30912171101x2d0886a0u2287863127b74000@mail.gmail.com> Thanks again Brad. The link and the related peek into the underlying operation of Apple Events was instructuve. Unfortunately, my particular bug shows up under Leopard too, not just Snow Leopard, so I don't think it's related. So, I'll reiterate my request. Can can any of the appscript gurus think of any reason why the following (pseudo) code should fail: import appscript id=app("EyeTV").recordings.get()[0] app("EyeTV").play(id) # works just fine app("EyeTV").stop() #works just fine go_do_other_stuff_possibly_in_other_threads_for_a_really_long_time() app("EyeTV").play(id) # has no effect Thanks for your time. -Jon On Thu, Dec 17, 2009 at 10:26 AM, Brad Howes wrote: > On Dec 16, 2009, at 2:26 PM, Jon Christopher wrote: > >> Thanks for the reply, Brad. >> >> I'm not familiar with the issue you describe. ?Can you provide a >> pointer to some related info? ?How would I test to see if my script is >> affected? > > http://db.tidbits.com/article/10643 > > -- > Brad Howes > Group 42 > MIT Lincoln Laboratory ? 244 Wood St. ? Lexington, MA 02173 > Phone: 781.981.5292 ? Fax: 781.981.3495 ? Secretary: 781.981.7420 > > > > > From ken.manheimer at gmail.com Thu Dec 17 20:10:57 2009 From: ken.manheimer at gmail.com (ken manheimer) Date: Thu, 17 Dec 2009 14:10:57 -0500 Subject: [Pythonmac-SIG] timeout of connection? In-Reply-To: <7D0C23D0-10B9-4F1D-9EF8-761E692A3547@ll.mit.edu> References: <6b913bc30912151314t779eee92q8cf27bbeab02f37d@mail.gmail.com> <6329DB29-7485-4BD1-AD30-590E957EB8A7@ll.mit.edu> <6b913bc30912161126v44cf3a2dgc831245851de77cb@mail.gmail.com> <7D0C23D0-10B9-4F1D-9EF8-761E692A3547@ll.mit.edu> Message-ID: <2cd46e7f0912171110p2b675161j4552ce13ddee57fa@mail.gmail.com> On Thu, Dec 17, 2009 at 1:26 PM, Brad Howes wrote: > On Dec 16, 2009, at 2:26 PM, Jon Christopher wrote: > > > Thanks for the reply, Brad. > > > > I'm not familiar with the issue you describe. Can you provide a > > pointer to some related info? How would I test to see if my script is > > affected? > > http://db.tidbits.com/article/10643 > and see these threads for the description of the problem in python appscript and the fix: http://old.nabble.com/-ann--appscript-0.20.2-tt26413893.html and http://old.nabble.com/-ann--py-appscript-0.21.0-tt26634638.html note that i experienced the problem in leopard as well as snow leopard. it does seem to be well explained by the return id problem, even though the above article attributes it to only snow leopard. plus, has' fix seems to have completely resolved the problem that i was, until the fix, seeing consistently. has the update failed to settle the problem you're seeing? -- ken http://myriadicity.net > -- > Brad Howes > Group 42 > MIT Lincoln Laboratory ? 244 Wood St. ? Lexington, MA 02173 > Phone: 781.981.5292 ? Fax: 781.981.3495 ? Secretary: 781.981.7420 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jon.christopher at gmail.com Thu Dec 17 20:51:27 2009 From: jon.christopher at gmail.com (Jon Christopher) Date: Thu, 17 Dec 2009 11:51:27 -0800 Subject: [Pythonmac-SIG] timeout of connection? In-Reply-To: <2cd46e7f0912171110p2b675161j4552ce13ddee57fa@mail.gmail.com> References: <6b913bc30912151314t779eee92q8cf27bbeab02f37d@mail.gmail.com> <6329DB29-7485-4BD1-AD30-590E957EB8A7@ll.mit.edu> <6b913bc30912161126v44cf3a2dgc831245851de77cb@mail.gmail.com> <7D0C23D0-10B9-4F1D-9EF8-761E692A3547@ll.mit.edu> <2cd46e7f0912171110p2b675161j4552ce13ddee57fa@mail.gmail.com> Message-ID: <6b913bc30912171151j7c350ab4n6ee45142bde09af4@mail.gmail.com> Thanks, I'll try the fix when I get home. However, I should reiterate that I'm not seeing a timeout (which would cause an exception, right?). It's just that I (eventually) issue an applescript command which seems to go nowhere. As I understand the id-rollover bug: 1) it will cause events which want a reply to eventually timeout. 2) which would trigger a python exception I'm not sure how that would be at play here since: 1) the command I'm sending doesn't (apparently) need a reply 2) I'm not getting exceptions. Did I missunderstand something? On Thu, Dec 17, 2009 at 11:10 AM, ken manheimer wrote: > On Thu, Dec 17, 2009 at 1:26 PM, Brad Howes wrote: >> >> On Dec 16, 2009, at 2:26 PM, Jon Christopher wrote: >> >> > Thanks for the reply, Brad. >> > >> > I'm not familiar with the issue you describe. ?Can you provide a >> > pointer to some related info? ?How would I test to see if my script is >> > affected? >> >> http://db.tidbits.com/article/10643 > > and see these threads for the description of the problem in python appscript > and the fix: > > http://old.nabble.com/-ann--appscript-0.20.2-tt26413893.html > and > http://old.nabble.com/-ann--py-appscript-0.21.0-tt26634638.html > > note that i experienced the problem in leopard as well as snow leopard.? it > does seem to be well explained by the return id problem, even though the > above article attributes it to only snow leopard.? plus, has' fix seems to > have completely resolved the problem that i was, until the fix, seeing > consistently.? has the update failed to settle the problem you're seeing? > -- > ken > http://myriadicity.net > > >> >> -- >> Brad Howes >> Group 42 >> MIT Lincoln Laboratory ? 244 Wood St. ? Lexington, MA 02173 >> Phone: 781.981.5292 ? Fax: 781.981.3495 ? Secretary: 781.981.7420 > > From ken.manheimer at gmail.com Thu Dec 17 21:24:01 2009 From: ken.manheimer at gmail.com (ken manheimer) Date: Thu, 17 Dec 2009 15:24:01 -0500 Subject: [Pythonmac-SIG] timeout of connection? In-Reply-To: <6b913bc30912171151j7c350ab4n6ee45142bde09af4@mail.gmail.com> References: <6b913bc30912151314t779eee92q8cf27bbeab02f37d@mail.gmail.com> <6329DB29-7485-4BD1-AD30-590E957EB8A7@ll.mit.edu> <6b913bc30912161126v44cf3a2dgc831245851de77cb@mail.gmail.com> <7D0C23D0-10B9-4F1D-9EF8-761E692A3547@ll.mit.edu> <2cd46e7f0912171110p2b675161j4552ce13ddee57fa@mail.gmail.com> <6b913bc30912171151j7c350ab4n6ee45142bde09af4@mail.gmail.com> Message-ID: <2cd46e7f0912171224k2915fdb3rc2f8408d819dfaca@mail.gmail.com> On Thu, Dec 17, 2009 at 2:51 PM, Jon Christopher wrote: > Thanks, I'll try the fix when I get home. However, I should reiterate > that I'm not seeing a timeout (which would cause an exception, > right?). It's just that I (eventually) issue an applescript command > which seems to go nowhere. > > As I understand the id-rollover bug: > > 1) it will cause events which want a reply to eventually timeout. > 2) which would trigger a python exception > > I'm not sure how that would be at play here since: > > 1) the command I'm sending doesn't (apparently) need a reply > 2) I'm not getting exceptions. > > Did I missunderstand something? > i don't think you're misunderstanding anything, but the two sets of circumstances are not mutually exclusive. i don't know what the system you're dealing with is doing with the command you're sending, in particular (1) whether it's internally issuing a command that does need a reply, in the course of its handling - that seems likely - and (2) whether it's "protecting" against runtime disruption by swallowing any exceptions encountered. perhaps you know all the systems involved well enough to be sure this isn't happening. though it's often bad practice to swallow errors without any signs, (2) is not unusual or unwarranted in executive style programs, though they should issue some kind of warning, like in a log, that can be missed, and too often nothing is issued at all. that doesn't mean the problem is happening and being covered up, just that it might be, and a little bit of "experimental computer science" is probably worth the effort. -- ken http://myriadicity.net > On Thu, Dec 17, 2009 at 11:10 AM, ken manheimer > wrote: > > On Thu, Dec 17, 2009 at 1:26 PM, Brad Howes wrote: > >> > >> On Dec 16, 2009, at 2:26 PM, Jon Christopher wrote: > >> > >> > Thanks for the reply, Brad. > >> > > >> > I'm not familiar with the issue you describe. Can you provide a > >> > pointer to some related info? How would I test to see if my script is > >> > affected? > >> > >> http://db.tidbits.com/article/10643 > > > > and see these threads for the description of the problem in python > appscript > > and the fix: > > > > http://old.nabble.com/-ann--appscript-0.20.2-tt26413893.html > > and > > http://old.nabble.com/-ann--py-appscript-0.21.0-tt26634638.html > > > > note that i experienced the problem in leopard as well as snow leopard. > it > > does seem to be well explained by the return id problem, even though the > > above article attributes it to only snow leopard. plus, has' fix seems > to > > have completely resolved the problem that i was, until the fix, seeing > > consistently. has the update failed to settle the problem you're seeing? > > -- > > ken > > http://myriadicity.net > > > > > >> > >> -- > >> Brad Howes > >> Group 42 > >> MIT Lincoln Laboratory ? 244 Wood St. ? Lexington, MA 02173 > >> Phone: 781.981.5292 ? Fax: 781.981.3495 ? Secretary: 781.981.7420 > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hengist.podd at virgin.net Thu Dec 17 22:09:53 2009 From: hengist.podd at virgin.net (has) Date: Thu, 17 Dec 2009 21:09:53 +0000 Subject: [Pythonmac-SIG] timeout of connection? In-Reply-To: References: Message-ID: Jon Christopher wrote: > So, I'll reiterate my request. Can can any of the appscript gurus > think of any reason why > the following (pseudo) code should fail: > > > import appscript > id=app("EyeTV").recordings.get()[0] > app("EyeTV").play(id) # works just fine > app("EyeTV").stop() #works just fine > > go_do_other_stuff_possibly_in_other_threads_for_a_really_long_time() > > app("EyeTV").play(id) # has no effect Is the EyeTV process running throughout, or does it quit and restart? Are you sure all commands are being executed? What do the references produced by the following look like: print app("EyeTV").recordings.get() Have you tried enabling AEDebug and observing the events being sent? has -- Control AppleScriptable applications from Python, Ruby and ObjC: http://appscript.sourceforge.net From jon.christopher at gmail.com Thu Dec 17 22:40:57 2009 From: jon.christopher at gmail.com (Jon Christopher) Date: Thu, 17 Dec 2009 13:40:57 -0800 Subject: [Pythonmac-SIG] timeout of connection? In-Reply-To: References: Message-ID: <6b913bc30912171340l25b70fcby9b7f48fb0025a09a@mail.gmail.com> @ken: Oh, I'm all for "experimental computer science", I'll try the new version when I get home. @has: > Is the EyeTV process running throughout, or does it quit and restart? Running throughout. > Are you sure all commands are being executed? Reasonably, but I'll have to check again. > What do the references produced by the following look like: > > ? ? ? ?print app("EyeTV").recordings.get() IIRC, it's a list of recording objects (defined in the EyeTV dictionary) which can then be passed back to EyeTV: recs=app("EyeTV").recordings.get() rec=recs[0] app("EyeTV").play(rec) # play the recording or inspected for properties: rec.title.get() # return the title of the recording Now that I think about it, my app caches those recording objects for quite some time. Is there a possibility that they could expire or become invalidated over time? > Have you tried enabling AEDebug and observing the events being sent? Interesting idea. Any suggestions on how to do so? My application is a plug-in for Front Row, and there's something weird about the way FR is started: there's a separate launcher app for the actual .app in /System/Library/Core Services/Front Row.app; I'm not sure if launching FR from the command line actually works, which makes setting the AEDebug environment variable problematic. Finally, since my actual app is a plugin, and this problem only occurs after FR and the machine have been idle for a long time, it's really difficult to debug/reproduce, as the testing cycle currently is "make a code change, wait 18-24h with the computer idle to see if the intermittent problem reoccurs." Not fun. Finally, restarting *Front Row* clears up the problem. If anyone has any bright ideas about how to speed up this turn-around time, I'd be delighted to hear them. Thanks again, Jon From hengist.podd at virgin.net Fri Dec 18 12:45:34 2009 From: hengist.podd at virgin.net (has) Date: Fri, 18 Dec 2009 11:45:34 +0000 Subject: [Pythonmac-SIG] timeout of connection? In-Reply-To: References: Message-ID: Jon Christopher wrote: >> Are you sure all commands are being executed? > > Reasonably, but I'll have to check again. Always helps to be sure. Been there, done that. >> What do the references produced by the following look like: >> >> print app("EyeTV").recordings.get() > > > IIRC, it's a list of recording objects (defined in the EyeTV dictionary) > which can then be passed back to EyeTV: > [...] > Now that I think about it, my app caches those recording objects for > quite some time. Is there a possibility that they could expire or become > invalidated over time? Bear in mind that Apple event IPC uses queries, not pointers, to identify remote objects. (It's roughly analogous to sending XPath queries over XML-RPC.) The reason I ask to see an actual result is because some types of queries are more 'reliable' than others. Only the by-id reference form gives anything like a guarantee of locating the same object every time you use it in a command. >> Have you tried enabling AEDebug and observing the events being sent? > > Interesting idea. Any suggestions on how to do so? My application > is a plug-in for Front Row, > and there's something weird about the way FR is started: there's a > separate launcher app > for the actual .app in /System/Library/Core Services/Front Row.app; > I'm not sure if launching FR > from the command line actually works, which makes setting the AEDebug > environment variable > problematic. Try setting it on EyeTV. http://developer.apple.com/mac/library/technotes/tn2004/tn2124.html#SECAE has -- Control AppleScriptable applications from Python, Ruby and ObjC: http://appscript.sourceforge.net From robince at gmail.com Fri Dec 18 16:51:58 2009 From: robince at gmail.com (Robin) Date: Fri, 18 Dec 2009 15:51:58 +0000 Subject: [Pythonmac-SIG] python-config ldflags problem on mac Message-ID: <2d5132a50912180751r126a8f2avf53f7a3fcf092a96@mail.gmail.com> Hi, I have a problem with using python-config --ldflags on a Mac. Using my python.org install: robin-mbp:github robince$ which python-config /Library/Frameworks/Python.framework/Versions/2.5/bin/python-config robin-mbp:github robince$ python-config --ldflags -L/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/config -ldl -lpython2.5 But if I build a C file with python embedded, the above linker flags result it in it embedding the system python. Obviously the -lpython2.5 is picking up the system one in preference to the one on the -L path. So far the only way I've got it to build against the one I want is with LDFLAGS=-F/ -framework Python (as well as -undefined dynamic_lookup -bundle, but I don't think that's relevant to the problem) However, I am looking for a way to determine this for users to install. Shouldn't python-config return the right thing? Is there something simple to add to LDFLAGS to allow -lpython2.5 to choose the right one so I can continue to use python-config (ie only search the path specified with -L) - this would allow the python-config output to work correctly for both the system python or user installed python. Or is there another way to determine (in an external build tool like make) the correct linker flags for the python in a users path (ie -F/ -framework Python). Any advice appreciated, Cheers Robin From ronaldoussoren at mac.com Fri Dec 18 17:18:32 2009 From: ronaldoussoren at mac.com (Ronald Oussoren) Date: Fri, 18 Dec 2009 17:18:32 +0100 Subject: [Pythonmac-SIG] python-config ldflags problem on mac In-Reply-To: <2d5132a50912180751r126a8f2avf53f7a3fcf092a96@mail.gmail.com> References: <2d5132a50912180751r126a8f2avf53f7a3fcf092a96@mail.gmail.com> Message-ID: <42742742491188333019482271588417382868-Webmail@me.com> On Friday, December 18, 2009, at 04:51PM, "Robin" wrote: >Hi, > >I have a problem with using python-config --ldflags on a Mac. Could you please file a bug on bugs.python.org to ensure that I don't forget to apply a fix for this? > >Using my python.org install: >robin-mbp:github robince$ which python-config >/Library/Frameworks/Python.framework/Versions/2.5/bin/python-config >robin-mbp:github robince$ python-config --ldflags >-L/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/config >-ldl -lpython2.5 The easiest workaround is to open a terminal window and execute the following commands: cd /Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/config ln -s libpython2.5.a libpython2.5.dylib This will ensure that the OSX linker knows that libpython is a shared library and links to this library. By default the OSX linker searches for a .dylib on the entire linker path and only then looks for .a files. BTW. python-config doesn't link using '-framework Python' on purpose: it is impossible to select the framework version that way (e.g. link to python 2.5 when you have 2.5, 2.6 and 3.1 installed) Ronald From lists at lumen.nu Sat Dec 19 02:20:29 2009 From: lists at lumen.nu (Joost Rekveld) Date: Sat, 19 Dec 2009 02:20:29 +0100 Subject: [Pythonmac-SIG] [newbie] install PyObjc under EPD Python ? Message-ID: Hi, i'm very new to this list, relatively new to Python, and don't manage to install PyObjc under the Enthought Python on Snow Leopard (distribution 5.1.1, which includes a Python 2.5.4). - easy_install installs things in their desired places, but chokes on PyObjc-core - macports starts installing all kinds of stuff where I don't want it (and quits when it doesn't find its own Python2.5 version). and everybody writes PyObjc is already installed on Snow Leopard, but I don't know what path to add to my Pythonpath for it to be found ? Would it be that simple ? and online I don't seem to find people having the same problem, so I must be missing something very obvious. any help very much appreciated ! kind regards, Joost. ------------------------------------------- Joost Rekveld ----------- http://www.lumen.nu/rekveld ------------------------------------------- "In theory, there is no difference between theory and practice. In practice, there is." (Jan L. A. van de Snepscheut) ------------------------------------------- From nad at acm.org Sat Dec 19 04:38:50 2009 From: nad at acm.org (Ned Deily) Date: Fri, 18 Dec 2009 19:38:50 -0800 Subject: [Pythonmac-SIG] [newbie] install PyObjc under EPD Python ? References: Message-ID: In article , Joost Rekveld wrote: > and everybody writes PyObjc is already installed on Snow Leopard, but I don't > know what path to add to my Pythonpath for it to be found ? Would it be that > simple ? You don't need to add anything if you use one of the Apple-supplied Pythons in Snow Leopard: $ /usr/bin/python2.6 Python 2.6.1 (r261:67515, Jul 7 2009, 23:51:51) [GCC 4.2.1 (Apple Inc. build 5646)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import objc >>> ^D $ /usr/bin/python2.5 Python 2.5.4 (r254:67916, Jul 7 2009, 23:51:24) [GCC 4.2.1 (Apple Inc. build 5646)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import objc >>> ^D -- Ned Deily, nad at acm.org From lists at lumen.nu Sat Dec 19 10:44:17 2009 From: lists at lumen.nu (Joost Rekveld) Date: Sat, 19 Dec 2009 10:44:17 +0100 Subject: [Pythonmac-SIG] [newbie] install PyObjc under EPD Python ? In-Reply-To: References: Message-ID: <438D4269-AE6A-42A7-B104-0FED6CE77EB5@lumen.nu> Hi Ned, thanks for your reply. Yes, I read that you don't have to do anything for the apple-supplied Pythons, but what if I want to keep using my EPD Python ? If not, i'll have to install everything else in order to be able to use PyObjc. If it is the only way, I'd consider it, but I'd find it strange ? how can I install PyObjc for a non-apple-supplied Python ? easy_install actually seems to work up to a point; it installs about twenty packages but then I get: > > Running pyobjc-core-2.2/setup.py -q bdist_egg --dist-dir /tmp/easy_install-mXb8PO/pyobjc-core-2.2/egg-dist-tmp-xJGYdv > warning: no directories found matching 'Scripts' > warning: no directories found matching 'setup-lib' > warning: no directories found matching 'source-deps' > warning: no previously-included files matching '.DS_Store' found anywhere in distribution > warning: no previously-included files matching '*.pyc' found anywhere in distribution > warning: no previously-included files matching '*.so' found anywhere in distribution > libffi-src/x86/x86-ffi_darwin.c:39: warning: no previous prototype for ?ffi_prep_args? > libffi-src/x86/x86-ffi_darwin.c:178: warning: function declaration isn?t a prototype > libffi-src/x86/x86-ffi_darwin.c:186: warning: function declaration isn?t a prototype > Modules/objc/objc-class.m: In function ?PyObjCClass_New?: > Modules/objc/objc-class.m:1416: warning: implicit declaration of function ?PyType_Modified? > Modules/objc/objc-class.m:1416: warning: nested extern declaration of ?PyType_Modified? > Modules/objc/OC_PythonObject.m: In function ?-[OC_PythonObject replacementObjectForKeyedArchiver:]?: > Modules/objc/OC_PythonObject.m:1370: warning: conflicting types for ?-(NSObject *)replacementObjectForKeyedArchiver:(NSKeyedArchiver *)archiver? this goes on and on with similar messages, until: > > Modules/objc/parsexml.m:1715: warning: implicit declaration of function ?xmlFreeDoc? > Modules/objc/parsexml.m:1715: warning: nested extern declaration of ?xmlFreeDoc? > error: Setup script exited with error: command 'gcc' failed with exit status 1 why doesn't this work ? My feeling is that I need a few clever symlinks to somewhere else, but I have no idea what precisely.. any ideas ? cheers, Joost. On 19 Dec, 2009, at 4:38 AM, Ned Deily wrote: > In article , > Joost Rekveld wrote: >> and everybody writes PyObjc is already installed on Snow Leopard, but I don't >> know what path to add to my Pythonpath for it to be found ? Would it be that >> simple ? > > You don't need to add anything if you use one of the Apple-supplied > Pythons in Snow Leopard: > > $ /usr/bin/python2.6 > Python 2.6.1 (r261:67515, Jul 7 2009, 23:51:51) > [GCC 4.2.1 (Apple Inc. build 5646)] on darwin > Type "help", "copyright", "credits" or "license" for more information. >>>> import objc >>>> ^D > $ /usr/bin/python2.5 > Python 2.5.4 (r254:67916, Jul 7 2009, 23:51:24) > [GCC 4.2.1 (Apple Inc. build 5646)] on darwin > Type "help", "copyright", "credits" or "license" for more information. >>>> import objc >>>> ^D > > -- On 19 Dec, 2009, at 2:20 AM, Joost Rekveld wrote: > Hi, > > i'm very new to this list, relatively new to Python, and don't manage to install PyObjc under the Enthought Python on Snow Leopard (distribution 5.1.1, which includes a Python 2.5.4). > > - easy_install installs things in their desired places, but chokes on PyObjc-core > - macports starts installing all kinds of stuff where I don't want it (and quits when it doesn't find its own Python2.5 version). > > and everybody writes PyObjc is already installed on Snow Leopard, but I don't know what path to add to my Pythonpath for it to be found ? Would it be that simple ? > > and online I don't seem to find people having the same problem, so I must be missing something very obvious. > any help very much appreciated ! > > kind regards, > > Joost. ------------------------------------------- Joost Rekveld ----------- http://www.lumen.nu/rekveld ------------------------------------------- "A is better off if B is better off.? (Heinz von Foerster) ------------------------------------------- From nad at acm.org Sat Dec 19 11:50:14 2009 From: nad at acm.org (Ned Deily) Date: Sat, 19 Dec 2009 02:50:14 -0800 Subject: [Pythonmac-SIG] [newbie] install PyObjc under EPD Python ? References: <438D4269-AE6A-42A7-B104-0FED6CE77EB5@lumen.nu> Message-ID: In article <438D4269-AE6A-42A7-B104-0FED6CE77EB5 at lumen.nu>, Joost Rekveld wrote: > thanks for your reply. Yes, I read that you don't have to do anything for the > apple-supplied Pythons, but what if I want to keep using my EPD Python ? > If not, i'll have to install everything else in order to be able to use > PyObjc. If it is the only way, I'd consider it, but I'd find it strange ? > > how can I install PyObjc for a non-apple-supplied Python ? Sorry, I have no experience with the the Enthought distribution. You might ask over on the EPD-Users mailing list. Depending on how that Python 2.5.4 was built and whether it has been patched to support building extensions on 10.6, you may need to use a different version of gcc (typically, export CC=/usr/bin/gcc-4.0) and/or add -arch i386 flags. Python 2.5 is rather old and only receives critical security bug fixes these days from the Python development team. PyObjC is also available as a MacPorts port if you care to use a complete MacPorts solution: sudo port install py25-pyobjc-cocoa or sudo port install py26-pyobjc-cocoa. -- Ned Deily, nad at acm.org From lists at lumen.nu Sat Dec 19 12:22:58 2009 From: lists at lumen.nu (Joost Rekveld) Date: Sat, 19 Dec 2009 12:22:58 +0100 Subject: [Pythonmac-SIG] [newbie] install PyObjc under EPD Python ? In-Reply-To: References: <438D4269-AE6A-42A7-B104-0FED6CE77EB5@lumen.nu> Message-ID: Hi Ned, thanks for the reply. The problem with MacPorts is that it installs everything around its own Python25, which is again in a different place and I don't know how to persuade it to install PyObjc where I want it. Independently I found this page: and when I add this to my PythonPath: /System/Library/Frameworks/Python.framework/Versions/2.5/Extras/lib/python/PyObjC /System/Library/Frameworks/Python.framework/Versions/2.5/Extras/lib/python/py2app it all seems to work: at least it seems now that I can import objc, AppKit, QTKit tonight i'll be able to see whether it really works. This workaround seems a bit dodgy to me, but it works ? If anybody has a better suggestion, i'd be very curious.. ciao, Joost. On 19 Dec, 2009, at 11:50 AM, Ned Deily wrote: > In article <438D4269-AE6A-42A7-B104-0FED6CE77EB5 at lumen.nu>, > Joost Rekveld wrote: >> thanks for your reply. Yes, I read that you don't have to do anything for the >> apple-supplied Pythons, but what if I want to keep using my EPD Python ? >> If not, i'll have to install everything else in order to be able to use >> PyObjc. If it is the only way, I'd consider it, but I'd find it strange ? >> >> how can I install PyObjc for a non-apple-supplied Python ? > > Sorry, I have no experience with the the Enthought distribution. You > might ask over on the EPD-Users mailing list. Depending on how that > Python 2.5.4 was built and whether it has been patched to support > building extensions on 10.6, you may need to use a different version of > gcc (typically, export CC=/usr/bin/gcc-4.0) and/or add -arch i386 flags. > Python 2.5 is rather old and only receives critical security bug fixes > these days from the Python development team. > > PyObjC is also available as a MacPorts port if you care to use a > complete MacPorts solution: > sudo port install py25-pyobjc-cocoa > or sudo port install py26-pyobjc-cocoa. > > -- > Ned Deily, > nad at acm.org > > _______________________________________________ > Pythonmac-SIG maillist - Pythonmac-SIG at python.org > http://mail.python.org/mailman/listinfo/pythonmac-sig ------------------------------------------- Joost Rekveld ----------- http://www.lumen.nu/rekveld ------------------------------------------- ?This alone I ask you, O reader, that when you peruse the account of these marvels that you do not set up for yourself as a standard human intellectual pride, but rather the great size and vastness of earth and sky; and, comparing with that Infinity these slender shadows in which miserably and anxiously we are enveloped, you will easily know that I have related nothing which is beyond belief.? (Girolamo Cardano) ------------------------------------------- From nad at acm.org Sun Dec 20 05:28:35 2009 From: nad at acm.org (Ned Deily) Date: Sat, 19 Dec 2009 20:28:35 -0800 Subject: [Pythonmac-SIG] [newbie] install PyObjc under EPD Python ? References: <438D4269-AE6A-42A7-B104-0FED6CE77EB5@lumen.nu> Message-ID: In article , Joost Rekveld wrote: > The problem with MacPorts is that it installs everything around its own > Python25, which is again in a different place and I don't know how to > persuade it to install PyObjc where I want it. You don't. A Python package, particularly one that contains C extensions, should only be used with the Python instance which it was built with and installed into. There can be major differences in the build options between Python instances even at the same release level. So if you install a MacPorts PyObjC, you use the MacPorts python, too. > Independently I found this page: > > > > and when I add this to my PythonPath: > > /System/Library/Frameworks/Python.framework/Versions/2.5/Extras/lib/python/PyO > bjC > /System/Library/Frameworks/Python.framework/Versions/2.5/Extras/lib/python/py2 > app > > it all seems to work: at least it seems now that I can import objc, AppKit, > QTKit > tonight i'll be able to see whether it really works. > > This workaround seems a bit dodgy to me, but it works ? It's bad practice to follow. In the absence of compatibility guarantees, the only safe approach is to install any missing modules you need into each Python instance where you need them. And, while it is fine to install additional packages to the Apple-supplied pythons (these additional site packages are placed in /Library/Python), one should never try to remove or delete the Apple-supplied files (in /usr/bin and /System/Library). They are part of OS X and managed by Apple. -- Ned Deily, nad at acm.org From lists at lumen.nu Sun Dec 20 12:34:51 2009 From: lists at lumen.nu (Joost Rekveld) Date: Sun, 20 Dec 2009 12:34:51 +0100 Subject: [Pythonmac-SIG] [newbie] install PyObjc under EPD Python ? In-Reply-To: References: <438D4269-AE6A-42A7-B104-0FED6CE77EB5@lumen.nu> Message-ID: <045FA67C-03BC-421A-AFBE-4AFDC9383EC4@lumen.nu> yes, I see, so my first question remains: how can I install PyObjc into a non-Apple, non-MacPort Python instance ? thanks, Joost. On 20 Dec, 2009, at 5:28 AM, Ned Deily wrote: >> This workaround seems a bit dodgy to me, but it works ? > > It's bad practice to follow. In the absence of compatibility > guarantees, the only safe approach is to install any missing modules you > need into each Python instance where you need them. And, while it is ------------------------------------------- Joost Rekveld ----------- http://www.lumen.nu/rekveld ------------------------------------------- "There are no passengers on spaceship earth. We are all crew.? (Marshall McLuhan) ------------------------------------------- From nad at acm.org Sun Dec 20 22:45:29 2009 From: nad at acm.org (Ned Deily) Date: Sun, 20 Dec 2009 13:45:29 -0800 Subject: [Pythonmac-SIG] [newbie] install PyObjc under EPD Python ? References: <438D4269-AE6A-42A7-B104-0FED6CE77EB5@lumen.nu> <045FA67C-03BC-421A-AFBE-4AFDC9383EC4@lumen.nu> Message-ID: In article <045FA67C-03BC-421A-AFBE-4AFDC9383EC4 at lumen.nu>, Joost Rekveld wrote: > yes, I see, so my first question remains: > > how can I install PyObjc into a non-Apple, non-MacPort Python instance ? And the answers I've given you still stand. It depends on what version of Python and what distribution you are talking about. For the current python.org 2.6 installer for OS X, python 2.6.4, you just need to install setuptools/easy_install (http://pypi.python.org/pypi/setuptools) for that python and then use it to install pyobjc. At the moment, Python 2.6.4 is the only python.org python that has been fully tested with and is known to work on 10.6 (Snow Leopard). For EPD Pythons, you should ask on an Enthought forum of people who are familiar with Enthought's OS X distribution. Chances are, though, that their python2.5 does not allow you to correctly build packages with C extension modules (such as those in PyObjC) on 10.6. There were fixes needed for 2.6 to do that and those will not be backported to python.org's 2.5 which is no longer maintained except for critical security patches and was last released before 10.6 was released. Perhaps Enthought has done the backporting and testing. There is also a mailing list for questions about PyObjC itself: http://dir.gmane.org/gmane.comp.python.pyobjc.devel -- Ned Deily, nad at acm.org From lists at lumen.nu Mon Dec 21 11:43:18 2009 From: lists at lumen.nu (Joost Rekveld) Date: Mon, 21 Dec 2009 11:43:18 +0100 Subject: [Pythonmac-SIG] [newbie] install PyObjc under EPD Python ? In-Reply-To: References: <438D4269-AE6A-42A7-B104-0FED6CE77EB5@lumen.nu> <045FA67C-03BC-421A-AFBE-4AFDC9383EC4@lumen.nu> Message-ID: <2BBC9E4C-0D1A-42BE-B059-ADF9BC6C5E28@lumen.nu> Hi Ned, thanks for the replies and for explaining the Snow Leopard/Python issues. That might be the reason why my effort to install PyObjc with easy_install (see first post) failed ? I'll try to find an Enthought list in order to ask there or I'll consider switching to another Python distro, hoping that installing the other packages I use will be straightforward. ciao, Joost. On 20 Dec, 2009, at 10:45 PM, Ned Deily wrote: > In article <045FA67C-03BC-421A-AFBE-4AFDC9383EC4 at lumen.nu>, > Joost Rekveld wrote: > >> yes, I see, so my first question remains: >> >> how can I install PyObjc into a non-Apple, non-MacPort Python instance ? > > And the answers I've given you still stand. It depends on what version > of Python and what distribution you are talking about. > > For the current python.org 2.6 installer for OS X, python 2.6.4, you > just need to install setuptools/easy_install > (http://pypi.python.org/pypi/setuptools) for that python and then use it > to install pyobjc. At the moment, Python 2.6.4 is the only python.org > python that has been fully tested with and is known to work on 10.6 > (Snow Leopard). > > For EPD Pythons, you should ask on an Enthought forum of people who are > familiar with Enthought's OS X distribution. Chances are, though, that > their python2.5 does not allow you to correctly build packages with C > extension modules (such as those in PyObjC) on 10.6. There were fixes > needed for 2.6 to do that and those will not be backported to > python.org's 2.5 which is no longer maintained except for critical > security patches and was last released before 10.6 was released. > Perhaps Enthought has done the backporting and testing. > > There is also a mailing list for questions about PyObjC itself: > > http://dir.gmane.org/gmane.comp.python.pyobjc.devel > > -- > Ned Deily, > nad at acm.org > > _______________________________________________ > Pythonmac-SIG maillist - Pythonmac-SIG at python.org > http://mail.python.org/mailman/listinfo/pythonmac-sig From Chris.Barker at noaa.gov Mon Dec 21 18:34:44 2009 From: Chris.Barker at noaa.gov (Christopher Barker) Date: Mon, 21 Dec 2009 09:34:44 -0800 Subject: [Pythonmac-SIG] [newbie] install PyObjc under EPD Python ? In-Reply-To: References: <438D4269-AE6A-42A7-B104-0FED6CE77EB5@lumen.nu> <045FA67C-03BC-421A-AFBE-4AFDC9383EC4@lumen.nu> Message-ID: <4B2FB1B4.500@noaa.gov> Ned Deily wrote: > Chances are, though, that > their python2.5 does not allow you to correctly build packages with C > extension modules (such as those in PyObjC) on 10.6. whooa! This appears to mean that python2.6 (or 3.1, I guess) is the only fully supported option for 10.6 and above? That's good to know -- hopefully we'll be going to 10.6 soon, and have not yet ported some critical stuff to 2.6. Have I got that right? -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker at noaa.gov From Chris.Barker at noaa.gov Mon Dec 21 18:39:15 2009 From: Chris.Barker at noaa.gov (Christopher Barker) Date: Mon, 21 Dec 2009 09:39:15 -0800 Subject: [Pythonmac-SIG] [newbie] install PyObjc under EPD Python ? In-Reply-To: <2BBC9E4C-0D1A-42BE-B059-ADF9BC6C5E28@lumen.nu> References: <438D4269-AE6A-42A7-B104-0FED6CE77EB5@lumen.nu> <045FA67C-03BC-421A-AFBE-4AFDC9383EC4@lumen.nu> <2BBC9E4C-0D1A-42BE-B059-ADF9BC6C5E28@lumen.nu> Message-ID: <4B2FB2C3.3080405@noaa.gov> Joost Rekveld wrote: > thanks for the replies and for explaining the Snow Leopard/Python issues. > That might be the reason why my effort to install PyObjc with easy_install (see first post) failed ? > I'll try to find an Enthought list in order to ask there or I'll consider switching to another Python distro, > hoping that installing the other packages I use will be straightforward. Well, many packages are still available with binaries for 2.5. Maybe you can get someone (even Enthought) to build PyObj for EPD on a 10.5 machine. I wonder when Enthought is going to go to 2.6 for EPD? -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker at noaa.gov From robert.kern at gmail.com Mon Dec 21 18:42:19 2009 From: robert.kern at gmail.com (Robert Kern) Date: Mon, 21 Dec 2009 11:42:19 -0600 Subject: [Pythonmac-SIG] [newbie] install PyObjc under EPD Python ? In-Reply-To: <4B2FB2C3.3080405@noaa.gov> References: <438D4269-AE6A-42A7-B104-0FED6CE77EB5@lumen.nu> <045FA67C-03BC-421A-AFBE-4AFDC9383EC4@lumen.nu> <2BBC9E4C-0D1A-42BE-B059-ADF9BC6C5E28@lumen.nu> <4B2FB2C3.3080405@noaa.gov> Message-ID: On 2009-12-21 11:39 AM, Christopher Barker wrote: > I wonder when Enthought is going to go to 2.6 for EPD? The betas are out now and are available to subscribers. I'm not sure exactly when the final release will be out (and freely available for the academic license), but soon. -- 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 From geoff.dutton at noaa.gov Mon Dec 21 23:52:25 2009 From: geoff.dutton at noaa.gov (Geoff Dutton) Date: Mon, 21 Dec 2009 15:52:25 -0700 Subject: [Pythonmac-SIG] Apple event time out with appscript Message-ID: <7a9810630912211452x776ca2edn5172250ebf72239a@mail.gmail.com> Hi I am using appscript to automate data processing through "Igor Pro". However, I keep running into an Apple event time out problem when running a process in Igor. I realize the timeout duration on some programs can be set, but I can't seem to set it through Igor's Do_Script command. I have pasted my code here: http://python.pastebin.com/m5e45943e The time out occurs in the Igor_ProcessMol def. How do I lengthen the time out duration? I have tried setting it via self.igor.activate(timeout=1200) but that doesn't work. It seems like self.igor.Do_Script() should have a way to set the time out. Any suggestions or work around greatly appreciated. Geoff -- NOAA Earth System Research Laboratory Global Monitoring Division 325 Broadway, R/GMD1 Boulder, CO 80305 -------------- next part -------------- An HTML attachment was scrubbed... URL: From nad at acm.org Tue Dec 22 05:25:29 2009 From: nad at acm.org (Ned Deily) Date: Mon, 21 Dec 2009 20:25:29 -0800 Subject: [Pythonmac-SIG] [newbie] install PyObjc under EPD Python ? References: <438D4269-AE6A-42A7-B104-0FED6CE77EB5@lumen.nu> <045FA67C-03BC-421A-AFBE-4AFDC9383EC4@lumen.nu> <4B2FB1B4.500@noaa.gov> Message-ID: In article <4B2FB1B4.500 at noaa.gov>, Christopher Barker wrote: > Ned Deily wrote: > > Chances are, though, that > > their python2.5 does not allow you to correctly build packages with C > > extension modules (such as those in PyObjC) on 10.6. > whooa! > > This appears to mean that python2.6 (or 3.1, I guess) is the only fully > supported option for 10.6 and above? > > That's good to know -- hopefully we'll be going to 10.6 soon, and have > not yet ported some critical stuff to 2.6. > > Have I got that right? There was stuff that needed to be done to make multi-architecture multiple-OS-level builds work correctly on 10.6. I'm thinking of things like forcing compilation with gcc-4.0 and using the 10.4u SDK for building extension modules. It certainly is possible to get 2.5.4 working for 10.6 - Apple has done it. But if there were recent patches, they wouldn't have been accepted into the python.org svn tree for 2.5. If you had to start from scratch for 2.5.4 on 10.6, I would guess the safest approach would be to limit yourself to a single-architecture build. The 2.5.4 from the python.org OS X installer should probably work OK on 10.6 since it is 32-bit only, except for the extension building issues. OTOH, 2.5.x is no longer supported on *any* platform by the Python Dev team, other than for critical security patches. And there are all those fixes that have gone into 2.6.x. -- Ned Deily, nad at acm.org From ronaldoussoren at mac.com Tue Dec 22 09:51:46 2009 From: ronaldoussoren at mac.com (Ronald Oussoren) Date: Tue, 22 Dec 2009 09:51:46 +0100 Subject: [Pythonmac-SIG] [newbie] install PyObjc under EPD Python ? In-Reply-To: <4B2FB1B4.500@noaa.gov> References: <438D4269-AE6A-42A7-B104-0FED6CE77EB5@lumen.nu> <045FA67C-03BC-421A-AFBE-4AFDC9383EC4@lumen.nu> <4B2FB1B4.500@noaa.gov> Message-ID: <0A70C27E-FE22-486A-B990-3F7F36F5F800@mac.com> On 21 Dec, 2009, at 18:34, Christopher Barker wrote: > Ned Deily wrote: >> Chances are, though, that their python2.5 does not allow you to correctly build packages with C extension modules (such as those in PyObjC) on 10.6. > > whooa! > > This appears to mean that python2.6 (or 3.1, I guess) is the only fully supported option for 10.6 and above? 2.6.4 contains a number of patches that make it possible to build extensions for the python.org binary installer on 10.6, those patches have been forward ported to the 3.1 tree, but there hasn't been a release of 3.1.x that includes those fixes. 2.7 and 3.2 will obviously also work when those are released. Python 2.5 was released long before OSX 10.6 was released and there won't be any further maintainance releases, that's why the SL fixes haven't been backported to 2.5. Ronald -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3567 bytes Desc: not available URL: From cbrewster at gmail.com Tue Dec 22 20:12:48 2009 From: cbrewster at gmail.com (Christopher Brewster) Date: Tue, 22 Dec 2009 20:12:48 +0100 Subject: [Pythonmac-SIG] total confusion with multiple pythons and pip Message-ID: <6B2B1490-2AD2-4303-BB18-E3F1A16CBE5A@gmail.com> (My apologies if all this is obvious) I appear to have 4 different installations of Python on my reformatted Snow Leopard installation. I have been trying to install pil and matplotlib and going round in circles. Versions of Python: 1. came with SL I assume it is here: /usr/bin/python $ /usr/bin/python Python 2.6.1 (r261:67515, Jul 7 2009, 23:51:51) [GCC 4.2.1 (Apple Inc. build 5646)] on darwin 2. From Python.org I assume it is the one here: /usr/local/bin/python $ /usr/local/bin/python Python 2.6.4 (r264:75821M, Oct 27 2009, 19:48:32) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin 3. From Macports I know it is the one here: /opt/local/bin/python $ /opt/local/bin/python Python 2.6.4 (r264:75706, Dec 21 2009, 20:23:10) [GCC 4.2.1 (Apple Inc. build 5646) (dot 1)] on darwin 4. I do not know where this came from: /Library/Frameworks/Python.framework/Versions/2.6/bin/python $ /Library/Frameworks/Python.framework/Versions/2.6/bin/python Python 2.6.4 (r264:75821M, Oct 27 2009, 19:48:32) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin Clearly when I install something with macports, it is accessible only if I run the macports version of python. However, I have installed 'pip' and this seems to be installing packages so that they only work with the original python (in /usr/bin/python). So I get the following: Christopher-Brewsters-MacBook-Pro-15:~ kiffer$ python Python 2.6.4 (r264:75821M, Oct 27 2009, 19:48:32) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import matplotlib Traceback (most recent call last): File "", line 1, in ImportError: No module named matplotlib >>> Christopher-Brewsters-MacBook-Pro-15:~ kiffer$ /usr/bin/python Python 2.6.1 (r261:67515, Jul 7 2009, 23:51:51) [GCC 4.2.1 (Apple Inc. build 5646)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import matplotlib /Library/Python/2.6/site-packages/matplotlib/__init__.py:62: DeprecationWarning: the md5 module is deprecated; use hashlib instead import md5, os, re, shutil, sys, warnings /Library/Python/2.6/site-packages/pytz/tzinfo.py:5: DeprecationWarning: the sets module is deprecated from sets import Set >>> Christopher-Brewsters-MacBook-Pro-15:~ kiffer$ /opt/local/bin/python Python 2.6.4 (r264:75706, Dec 21 2009, 20:23:10) [GCC 4.2.1 (Apple Inc. build 5646) (dot 1)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import matplotlib >>> Question: How do I get 'pip' to install correctly so as to be accessible with the current default python which appears to be the one installed from python.org? If I want to use the Macport python, how do I set this to be the default, or do I always have to call it via opt/local/bin/python? Thanks, Christopher From hengist.podd at virgin.net Tue Dec 22 23:22:22 2009 From: hengist.podd at virgin.net (has) Date: Tue, 22 Dec 2009 22:22:22 +0000 Subject: [Pythonmac-SIG] Apple event time out with appscript In-Reply-To: References: Message-ID: <03674686-BCAA-461F-91AF-AED5598FCD9D@virgin.net> Geoff Dutton wrote: > I am using appscript to automate data processing through "Igor Pro". However, I keep running into an Apple event time out problem when running a process in Igor. I realize the timeout duration on some programs can be set, but I can't seem to set it through Igor's Do_Script command. I have pasted my code here: http://python.pastebin.com/m5e45943e > > The time out occurs in the Igor_ProcessMol def. How do I lengthen the time out duration? I have tried setting it via self.igor.activate(timeout=1200) but that doesn't work. It seems like self.igor.Do_Script() should have a way to set the time out. 1. Make sure you're using appscript 0.21.1 (contains a workaround for a periodic Apple event timeout bug in 10.6). 2. Add a 'timeout' attribute to each command that needs a non-standard timeout, e.g. igor.Do_Script("some command", timeout=1200) HTH has -- Control AppleScriptable applications from Python, Ruby and ObjC: http://appscript.sourceforge.net From geoff.dutton at noaa.gov Wed Dec 23 01:01:39 2009 From: geoff.dutton at noaa.gov (Geoff Dutton) Date: Tue, 22 Dec 2009 17:01:39 -0700 Subject: [Pythonmac-SIG] Apple event time out with appscript In-Reply-To: <03674686-BCAA-461F-91AF-AED5598FCD9D@virgin.net> References: <03674686-BCAA-461F-91AF-AED5598FCD9D@virgin.net> Message-ID: <7a9810630912221601q6870aa55o3fce5a5bc23249b6@mail.gmail.com> On Tue, Dec 22, 2009 at 3:22 PM, has wrote: > Geoff Dutton wrote: > > > I am using appscript to automate data processing through "Igor Pro". > However, I keep running into an Apple event time out problem when running a > process in Igor. I realize the timeout duration on some programs can be > set, but I can't seem to set it through Igor's Do_Script command. I have > pasted my code here: http://python.pastebin.com/m5e45943e > > > > The time out occurs in the Igor_ProcessMol def. How do I lengthen the > time out duration? I have tried setting it via > self.igor.activate(timeout=1200) but that doesn't work. It seems like > self.igor.Do_Script() should have a way to set the time out. > > 1. Make sure you're using appscript 0.21.1 (contains a workaround for a > periodic Apple event timeout bug in 10.6). > > 2. Add a 'timeout' attribute to each command that needs a non-standard > timeout, e.g. igor.Do_Script("some command", timeout=1200) > > HTH > > has > -- > Control AppleScriptable applications from Python, Ruby and ObjC: > http://appscript.sourceforge.net > > _______________________________________________ > Pythonmac-SIG maillist - Pythonmac-SIG at python.org > http://mail.python.org/mailman/listinfo/pythonmac-sig > Thanks has! I was using the current version of appscript, however, I tried using the timeout parameter BEFORE the igor.Do_Script command. I realize, now, that timeout is an optional parameter and has to follow the Do_Script command. Thanks, Geoff -- NOAA Earth System Research Laboratory Global Monitoring Division 325 Broadway, R/GMD1 Boulder, CO 80305 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Barker at noaa.gov Wed Dec 23 20:02:09 2009 From: Chris.Barker at noaa.gov (Christopher Barker) Date: Wed, 23 Dec 2009 11:02:09 -0800 Subject: [Pythonmac-SIG] total confusion with multiple pythons and pip In-Reply-To: <6B2B1490-2AD2-4303-BB18-E3F1A16CBE5A@gmail.com> References: <6B2B1490-2AD2-4303-BB18-E3F1A16CBE5A@gmail.com> Message-ID: <4B326931.7030906@noaa.gov> Christopher Brewster wrote: > I appear to have 4 different installations of Python on my reformatted Snow Leopard installation. actually, 3 -- see below. > Versions of Python: > 1. came with SL > I assume it is here: > /usr/bin/python yup -- but see below > 2. From Python.org > I assume it is the one here: > /usr/local/bin/python yup, but same note. > 3. From Macports > I know it is the one here: > /opt/local/bin/python yup. > 4. I do not know where this came from: > /Library/Frameworks/Python.framework/Versions/2.6/bin/python That is the actual installation location for the python.org python. /usr/local/bin/python is a link to it. In fact, Apple's python lives in /System//Library/Frameworks/Python.framework > Clearly when I install something with macports, it is accessible only if I run the macports version of python. correct. > However, I have installed 'pip' and this seems to be installing > packages so that they only work with the original python (in > /usr/bin/python). I haven't used pip, but the key is to run it with the python you want to use, which may mean making sure you install it into the python you want to use. > Question: How do I get 'pip' to install correctly so as to be > accessible with the current default python which appears to be the one > installed from python.org? from the pip docs: "pip does not have to be installed to use it, you can run python path/to/pip.py and it will work" so that should do it. If you want to be extra careful, use /usr/local/bin/python > If I want to use the Macport python, how do I set this to be the > default, or do I always have to call it via opt/local/bin/python? That is determined by your PATH setting. Mine is set in ~/.bash_profile. It could be in a couple of other places (sigh). macports put this line in mine: export PATH=/opt/local/bin:/opt/local/sbin:$PATH That puts the macports stuff in front of everything else in your system, so it will be found first. (unless there is another PATH setting after that). type: $ echo $PATH to see what you've got now. you can also do: $ which python to see what python (or any other command) it's finding. HTH, -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker at noaa.gov From maparent at acm.org Sun Dec 27 20:25:42 2009 From: maparent at acm.org (Marc-Antoine Parent) Date: Sun, 27 Dec 2009 14:25:42 -0500 Subject: [Pythonmac-SIG] py2app/PyQt/64-bit/Mach-O In-Reply-To: <4B1DC5C9.7070606@codebykevin.com> References: <4B1DB1B7.3080507@codebykevin.com> <65fadfc30912071913o33210161n24bde05ead131f03@mail.gmail.com> <4B1DC5C9.7070606@codebykevin.com> Message-ID: I also ran into this recently. I was trying to wrap a PyQt application on Snow Leopard, and I wanted a 64-bit application as a result. The first issue you ran into involves macholib, and is easy enough to correct; here is the patch file. -------------- next part -------------- A non-text attachment was scrubbed... Name: macholib.diff Type: application/octet-stream Size: 11678 bytes Desc: not available URL: -------------- next part -------------- Also, py2app builds a 32-bit bootstrap executable in dist/ApplicationName.app/Contents/MacOS/ApplicationName ; so it will still start in 32 bits. To correct that, the py2app templates have to be rebuilt. Code patch below, and then do the following: cd {sowewhere}/py2app/py2app/apptemplate rm prebuilt/main python setup.py build cd ../bundletemplate rm prebuilt/main python setup.py build Note that the patch involves bumping the minimum system version from 10.3 to 10.4; Ideally this should be parametrized. Another issue that requires more thought, that Kevin also identified, is the argvemulation not working in 64 bits. My patch just hides the failure at this point, something better has to be done. -------------- next part -------------- A non-text attachment was scrubbed... Name: py2app.diff Type: application/octet-stream Size: 3431 bytes Desc: not available URL: -------------- next part -------------- Another issue, finally: If you're wrapping Qt4, the sip recipe omits the Qt plugins. I adjust it by hand, with the following operations (in bash): cat > dist/ApplicationName.app/Contents/Resources/qt.conf < References: <4B1DB1B7.3080507@codebykevin.com> <65fadfc30912071913o33210161n24bde05ead131f03@mail.gmail.com> <4B1DC5C9.7070606@codebykevin.com> Message-ID: <4B38284F.4000203@codebykevin.com> On 12/27/09 2:25 PM, Marc-Antoine Parent wrote: > I also ran into this recently. > I was trying to wrap a PyQt application on Snow Leopard, and I wanted a 64-bit application as a result. > > The first issue you ran into involves macholib, and is easy enough to correct; here is the patch file. > > Also, py2app builds a 32-bit bootstrap executable in dist/ApplicationName.app/Contents/MacOS/ApplicationName ; so it will still start in 32 bits. To correct that, the py2app templates have to be rebuilt. Code patch below, and then do the following: > > cd {sowewhere}/py2app/py2app/apptemplate > rm prebuilt/main > python setup.py build > cd ../bundletemplate > rm prebuilt/main > python setup.py build > > Note that the patch involves bumping the minimum system version from 10.3 to 10.4; Ideally this should be parametrized. Another issue that requires more thought, that Kevin also identified, is the argvemulation not working in 64 bits. My patch just hides the failure at this point, something better has to be done. > Marc-Antoine, Thank you for these patches. I'm sorry to report that even after applying these patches and re-installing py2app and macholib, my four-way Tkinter application won't build with py2app. I get this error in py2app: File "build/bdist.macosx-10.5-universal/egg/macholib/MachO.py", line 295, in synchronize_size raise ValueError("New Mach-O header is too large to relocate") ValueError: New Mach-O header is too large to relocate > /Users/kevin/Desktop/phynchronicity/build/bdist.macosx-10.5-universal/egg/macholib/MachO.py(295)synchronize_size() -> raise ValueError("New Mach-O header is too large to relocate") I've seen this before, and am not sure how to fix it. --Kevin -- Kevin Walzer Code by Kevin http://www.codebykevin.com From maparent at acm.org Mon Dec 28 06:05:30 2009 From: maparent at acm.org (Marc-Antoine Parent) Date: Mon, 28 Dec 2009 00:05:30 -0500 Subject: [Pythonmac-SIG] py2app/PyQt/64-bit/Mach-O In-Reply-To: <4B38284F.4000203@codebykevin.com> References: <4B1DB1B7.3080507@codebykevin.com> <65fadfc30912071913o33210161n24bde05ead131f03@mail.gmail.com> <4B1DC5C9.7070606@codebykevin.com> <4B38284F.4000203@codebykevin.com> Message-ID: > I get this error in py2app: > > File "build/bdist.macosx-10.5-universal/egg/macholib/MachO.py", line 295, in synchronize_size > raise ValueError("New Mach-O header is too large to relocate") > ValueError: New Mach-O header is too large to relocate > > /Users/kevin/Desktop/phynchronicity/build/bdist.macosx-10.5-universal/egg/macholib/MachO.py(295)synchronize_size() > -> raise ValueError("New Mach-O header is too large to relocate") > > I've seen this before, and am not sure how to fix it. Hmmm.... so have I, and I was stumped too, I'm afraid. It depends on the size of headers in a particular library. I do not know of a way to resize them after the fact. Anyone else? If it's a library whose build you control, you could try to give it a large -headerpad value at link (look in man ld), that's at least worth a try. Do you know which library it is? Is it open-sourced? I may give it a shot in that case. Marc-Antoine From kw at codebykevin.com Mon Dec 28 06:31:07 2009 From: kw at codebykevin.com (Kevin Walzer) Date: Mon, 28 Dec 2009 00:31:07 -0500 Subject: [Pythonmac-SIG] py2app/PyQt/64-bit/Mach-O In-Reply-To: References: <4B1DB1B7.3080507@codebykevin.com> <65fadfc30912071913o33210161n24bde05ead131f03@mail.gmail.com> <4B1DC5C9.7070606@codebykevin.com> <4B38284F.4000203@codebykevin.com> Message-ID: <4B38429B.90603@codebykevin.com> On 12/28/09 12:05 AM, Marc-Antoine Parent wrote: > > Hmmm.... so have I, and I was stumped too, I'm afraid. It depends on the size of headers in a particular library. > I do not know of a way to resize them after the fact. Anyone else? > If it's a library whose build you control, you could try to give it a large -headerpad value at link (look in man ld), that's at least worth a try. > Do you know which library it is? Is it open-sourced? I may give it a shot in that case. It's just Tkinter--I have a four-way build (32/64 bit for PPC and Intel) of Tcl/Tk. -- Kevin Walzer Code by Kevin http://www.codebykevin.com From maparent at acm.org Mon Dec 28 18:39:37 2009 From: maparent at acm.org (Marc-Antoine Parent) Date: Mon, 28 Dec 2009 12:39:37 -0500 Subject: [Pythonmac-SIG] py2app/PyQt/64-bit/Mach-O In-Reply-To: <4B38429B.90603@codebykevin.com> References: <4B1DB1B7.3080507@codebykevin.com> <65fadfc30912071913o33210161n24bde05ead131f03@mail.gmail.com> <4B1DC5C9.7070606@codebykevin.com> <4B38284F.4000203@codebykevin.com> <4B38429B.90603@codebykevin.com> Message-ID: > It's just Tkinter--I have a four-way build (32/64 bit for PPC and Intel) of Tcl/Tk. Hmmm.... I tried adding Tkinter to my "includes". Interestingly, the framework did not get added; apparently because it is a system framework. I then tried adding it explicitly with the "frameworks" option of py2app; still not included. I had an old 32bit build of Tcl/Tk frameworks in /Library, that one got added without issues. I also tried moving the /System/Library/Frameworks/Tcl,Tk to /Library/Frameworks; that also worked without a hitch. Can I ask you where you got your Tcl/Tk? And more to the point, do you really need it, since it's been part of /System since 10.4? That said, I have noticed another anomaly: Sometimes, when I apply py2app twice, I get an error such as this one: /usr/bin/strip: the __LINKEDIT segment does not cover the end of the file (can't be processed) in: /Users/maparent/OpenSource/leo-editor/dist/leo-editor.app/Contents/Frameworks/QtXmlPatterns.framework/Versions/4/QtXmlPatterns (for architecture x86_64) The solution for me is to wipe the "dist" directory and start fresh. ("build" is not an issue.) Would you mind trying that, just in case? Cheers, Marc-Antoine From kw at codebykevin.com Mon Dec 28 23:47:06 2009 From: kw at codebykevin.com (Kevin Walzer) Date: Mon, 28 Dec 2009 17:47:06 -0500 Subject: [Pythonmac-SIG] py2app/PyQt/64-bit/Mach-O In-Reply-To: References: <4B1DB1B7.3080507@codebykevin.com> <65fadfc30912071913o33210161n24bde05ead131f03@mail.gmail.com> <4B1DC5C9.7070606@codebykevin.com> <4B38284F.4000203@codebykevin.com> <4B38429B.90603@codebykevin.com> Message-ID: <4B39356A.3080205@codebykevin.com> On 12/28/09 12:39 PM, Marc-Antoine Parent wrote: >> It's just Tkinter--I have a four-way build (32/64 bit for PPC and Intel) of Tcl/Tk. > > > Hmmm.... I tried adding Tkinter to my "includes". Interestingly, the framework did not get added; apparently because it is a system framework. > I then tried adding it explicitly with the "frameworks" option of py2app; still not included. py2app doesn't add stuff in /System because it can't be redistributed (those are Apple-provided bits). > I had an old 32bit build of Tcl/Tk frameworks in /Library, that one got added without issues. > I also tried moving the /System/Library/Frameworks/Tcl,Tk to /Library/Frameworks; that also worked without a hitch. Yes, that should work. > Can I ask you where you got your Tcl/Tk? > And more to the point, do you really need it, since it's been part of /System since 10.4? I built it myself, and I do need my own build because I want 64-bit. The version in /System is ancient (c. 2005) and doesn't support 64-bit. > sr/bin/strip: the __LINKEDIT segment does not cover the end of the file (can't be processed) in: /Users/maparent/OpenSource/leo-editor/dist/leo-editor.app/Contents/Frameworks/QtXmlPatterns.framework/Versions/4/QtXmlPatterns (for architecture x86_64) > > The solution for me is to wipe the "dist" directory and start fresh. ("build" is not an issue.) > Would you mind trying that, just in case? That didn't work, unfortunately. I've tried the maxheader trick before in the past, and it hasn't worked, but I don't feel like recompiling Tcl/Tk this time. Too much work when bundlebuilder is an easier, functioning solution. In the meantime, you might want to ping Ronald Oussoren with your patches--I'm sure that others will find them useful. --Kevin -- Kevin Walzer Code by Kevin http://www.codebykevin.com From aahz at pythoncraft.com Wed Dec 30 02:24:25 2009 From: aahz at pythoncraft.com (Aahz) Date: Tue, 29 Dec 2009 17:24:25 -0800 Subject: [Pythonmac-SIG] FWD: Python tricks with applescript in OS-X Message-ID: <20091230012425.GA18201@panix.com> ----- Forwarded message from "joanmg at gmail.com" ----- > From: "joanmg at gmail.com" > Newsgroups: comp.lang.python > Subject: Python tricks with applescript in OS-X > Date: Fri, 11 Dec 2009 00:13:03 -0800 (PST) > Organization: http://groups.google.com > > Greetings, > > I've written a short document with some working examples of how to > interface python with other applications in OS-X via applescript (had > to spend some time figuring it out, and thought I might as well write > it down). The examples include asking Google Earth for the latitude > and longitude of the point at the center of its screen, or using the > finder to pop-up a dialog window to get input from the user: > > http://juanreyero.com/article/python/os-x-python.html > > Cheers, > > Juan > http://juanreyero.com > ----- End forwarded message ----- -- Aahz (aahz at pythoncraft.com) <*> http://www.pythoncraft.com/ Weinberg's Second Law: If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization. From erik at letterror.com Wed Dec 30 15:17:49 2009 From: erik at letterror.com (Erik van Blokland) Date: Wed, 30 Dec 2009 15:17:49 +0100 Subject: [Pythonmac-SIG] Snow Leopard, Quartz, python 2.6.4, objc 2.2, twisted 9.0.0, cont'd. Message-ID: Hi, Continuing my project to get draw with a Quartz context in a twisted process. Following Ronald's advise, I can now make a context, draw shapes and paths, render the context to bytes and serve them. Running the python.org 2.6.4, pyobjc 2.2, twisted 9.0.0. Exact version info below. I also need to draw a couple bitmap images, so I want to use more functionality from Quartz. My test works when executed in the terminal. But it crashes hard when called as part of a twisted process. I haven't included "non crashing drawing" in this example. I could make an example that does if that helps. > [eBook:trunk/lettersetter/Quartz LS Debug] erik% python /usr/bin/twistd -y twisted.quartz.test.py --pidfile quartztestpid.txt --logfile quartztest.log > versions: > python version: 2.6.4 (r264:75821M, Oct 27 2009, 19:48:32) > [GCC 4.0.1 (Apple Inc. build 5493)] > pyobjc version: 2.2 > twisted.web version: 9.0.0 > > dry run: > saved test image at /Users/erik/Develop/lettersetter/trunk/lettersetter/Quartz LS Debug/test.png > > booting twisted app > done Then I open a browser at http://127.0.0.1:8081/ kerboom! My test script requires a png file to be nearby. Any help or pointers are kindly appreciated. Many thanks and happy new year! Erik -------------- next part -------------- A non-text attachment was scrubbed... Name: twisted.quartz.test.py Type: text/x-python-script Size: 3921 bytes Desc: not available URL: -------------- next part -------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: sourceimage.png Type: image/png Size: 4009 bytes Desc: not available URL: -------------- next part -------------- Crash report: Process: Python [5743] Path: /Library/Frameworks/Python.framework/Versions/2.6/Resources/Python.app/Contents/MacOS/Python Identifier: Python Version: ??? (???) Code Type: X86 (Native) Parent Process: ??? [1] Date/Time: 2009-12-30 14:53:30.091 +0100 OS Version: Mac OS X 10.6.2 (10C540) Report Version: 6 Interval Since Last Report: 322893 sec Crashes Since Last Report: 7 Per-App Crashes Since Last Report: 3 Anonymous UUID: F9FC4B74-FACA-42B0-B2C6-ED4326DE8CEA Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Crashed Thread: 0 Dispatch queue: com.apple.main-thread Application Specific Information: abort() called USING_FORK_WITHOUT_EXEC_IS_NOT_SUPPORTED_BY_FILE_MANAGER Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 libSystem.B.dylib 0x91387732 __kill + 10 1 libSystem.B.dylib 0x91387724 kill$UNIX2003 + 32 2 libSystem.B.dylib 0x9141a98d raise + 26 3 libSystem.B.dylib 0x91430a44 abort + 93 4 ...ple.CoreServices.CarbonCore 0x9441b2f1 _scserver_SCSessionUniverseDisconnect_rpc + 0 5 ...ple.CoreServices.CarbonCore 0x9432a9d4 _SCSessionUniverseByUIDAcquireAndLock + 74 6 ...ple.CoreServices.CarbonCore 0x9432a935 FSNodeStorageGetAndLockCurrentUniverse + 192 7 ...ple.CoreServices.CarbonCore 0x94338db9 FileIDTreeGetVRefNumForDevice + 29 8 ...ple.CoreServices.CarbonCore 0x94338d32 FSMount::FSMount(unsigned int, FSMountNumberType, short*) + 62 9 ...ple.CoreServices.CarbonCore 0x943371b4 PathGetObjectInfo(char const*, unsigned long, unsigned long, short*, unsigned long*, unsigned long*, char*, unsigned long*, unsigned char*) + 314 10 ...ple.CoreServices.CarbonCore 0x94336fb4 FSPathMakeRefInternal(unsigned char const*, unsigned long, unsigned long, FSRef*, unsigned char*) + 134 11 ...ple.CoreServices.CarbonCore 0x94336f2c FSPathMakeRef + 47 12 com.apple.ImageIO.framework 0x9291bfab CGImageReadCreateWithFile + 278 13 com.apple.ImageIO.framework 0x9291bbe4 CGImageSourceCreateWithURL + 318 14 _objc.so 0x0162d08d ffi_call_SYSV + 29 15 _objc.so 0x0162d441 ffi_call + 97 16 _objc.so 0x01638ad6 func_call + 1238 17 org.python.python 0x0000ed35 PyObject_Call + 85 18 org.python.python 0x000beab7 PyEval_EvalFrameEx + 13623 19 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 20 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 21 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 22 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 23 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 24 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 25 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 26 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 27 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 28 org.python.python 0x000c22dd PyEval_EvalCodeEx + 2109 29 org.python.python 0x0003f746 function_call + 166 30 org.python.python 0x0000ed35 PyObject_Call + 85 31 org.python.python 0x000bdf2c PyEval_EvalFrameEx + 10668 32 org.python.python 0x000c22dd PyEval_EvalCodeEx + 2109 33 org.python.python 0x0003f746 function_call + 166 34 org.python.python 0x0000ed35 PyObject_Call + 85 35 org.python.python 0x000bdf2c PyEval_EvalFrameEx + 10668 36 org.python.python 0x000c22dd PyEval_EvalCodeEx + 2109 37 org.python.python 0x0003f746 function_call + 166 38 org.python.python 0x0000ed35 PyObject_Call + 85 39 org.python.python 0x000bdf2c PyEval_EvalFrameEx + 10668 40 org.python.python 0x000c22dd PyEval_EvalCodeEx + 2109 41 org.python.python 0x0003f746 function_call + 166 42 org.python.python 0x0000ed35 PyObject_Call + 85 43 org.python.python 0x000bdf2c PyEval_EvalFrameEx + 10668 44 org.python.python 0x000c22dd PyEval_EvalCodeEx + 2109 45 org.python.python 0x000c034c PyEval_EvalFrameEx + 19916 46 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 47 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 48 org.python.python 0x000c22dd PyEval_EvalCodeEx + 2109 49 org.python.python 0x000c034c PyEval_EvalFrameEx + 19916 50 org.python.python 0x000c22dd PyEval_EvalCodeEx + 2109 51 org.python.python 0x000c034c PyEval_EvalFrameEx + 19916 52 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 53 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 54 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 55 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 56 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 57 org.python.python 0x000c0ae6 PyEval_EvalFrameEx + 21862 58 org.python.python 0x000c22dd PyEval_EvalCodeEx + 2109 59 org.python.python 0x000c23f7 PyEval_EvalCode + 87 60 org.python.python 0x000e6f08 PyRun_FileExFlags + 168 61 org.python.python 0x000e7df3 PyRun_SimpleFileExFlags + 867 62 org.python.python 0x000f9902 Py_Main + 3122 63 org.python.python 0x00001f82 0x1000 + 3970 64 org.python.python 0x00001ea9 0x1000 + 3753 Thread 0 crashed with X86 Thread State (32-bit): eax: 0x00000000 ebx: 0x914309f3 ecx: 0xbfff8b2c edx: 0x91387732 edi: 0x0e000002 esi: 0xbfff8f50 ebp: 0xbfff8b48 esp: 0xbfff8b2c ss: 0x0000001f efl: 0x00000286 eip: 0x91387732 cs: 0x00000007 ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037 cr2: 0x9141a973 Binary Images: 0x1000 - 0x1ff5 +org.python.python 2.6.4 (2.6.4) <4037E992-5FF7-89F8-C547-77DF78B19D35> /Library/Frameworks/Python.framework/Versions/2.6/Resources/Python.app/Contents/MacOS/Python 0x5000 - 0x130fe3 +org.python.python 2.6.4, (c) 2004-2008 Python Software Foundation. (2.6.4) <74126CA0-A482-4EDB-B195-CE276F49DA9E> /Library/Frameworks/Python.framework/Versions/2.6/Python 0x1f5000 - 0x1f8ffc +strop.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/strop.so 0x400000 - 0x407fff +_socket.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_socket.so 0x410000 - 0x413ff7 +_ssl.so ??? (???) <4CB670AF-33F3-41BD-769C-F28FC27BB467> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_ssl.so 0x419000 - 0x43ffff libssl.0.9.7.dylib ??? (???) <8BF98B2F-0F55-40CA-C082-43C76707BD24> /usr/lib/libssl.0.9.7.dylib 0x44e000 - 0x503fe7 libcrypto.0.9.7.dylib ??? (???) <4917E4F2-817F-5AC4-3FBE-54BC96360448> /usr/lib/libcrypto.0.9.7.dylib 0x549000 - 0x54aff9 +cStringIO.so ??? (???) <4C6A1DF3-FC4E-3E99-EB62-D9F4B455D23C> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/cStringIO.so 0x54f000 - 0x552ff7 +_struct.so ??? (???) <1D6CFA30-A56B-C2F2-42AD-AF363C54B793> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_struct.so 0x559000 - 0x55cfff +operator.so ??? (???) <06B2B012-039B-F139-56A8-AEB0E9B94056> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/operator.so 0x563000 - 0x567ffe +itertools.so ??? (???) <59707961-1A72-58D1-CAFA-C6A533F0FC87> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/itertools.so 0x5b0000 - 0x5b1ff6 +termios.so ??? (???) <1F9365C3-628B-1A61-E5EF-E5EBEBCA9A69> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/termios.so 0x5b6000 - 0x5b7fff +time.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/time.so 0x5bd000 - 0x5c8fff +datetime.so ??? (???) <291E576D-4567-B936-C1C9-420B00BEB902> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/datetime.so 0x5d3000 - 0x5d3ffc +_functools.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_functools.so 0x5d7000 - 0x5daff3 +_collections.so ??? (???) <78B59DC9-8C1C-FD7F-1CA1-AAA38F6F70B3> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_collections.so 0x5e0000 - 0x5f1ffd +zlib.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/zlib.so 0x5f6000 - 0x5f6ff7 +_CFBag.so ??? (???) <96175D4A-09E6-656B-25C4-390B043F119B> /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/CoreFoundation/_CFBag.so 0x5fb000 - 0x5fbff7 +_CFBinaryHeap.so ??? (???) /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/CoreFoundation/_CFBinaryHeap.so 0x600000 - 0x600ff7 +_CFBitVector.so ??? (???) /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/CoreFoundation/_CFBitVector.so 0x605000 - 0x606ff7 +_CFCalendar.so ??? (???) <877EF111-F8DB-FFFF-DDD4-D7210ED5B8DB> /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/CoreFoundation/_CFCalendar.so 0x60b000 - 0x60bff7 +_CFDictionary.so ??? (???) <9224A1C3-0E74-E527-47C1-93C550EC0B24> /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/CoreFoundation/_CFDictionary.so 0x610000 - 0x611ff7 +_CFTree.so ??? (???) /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/CoreFoundation/_CFTree.so 0x7ea000 - 0x7eaffd +gestalt.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/gestalt.so 0x7ee000 - 0x7effff +MacOS.so ??? (???) <52F1C9A5-FFD1-3694-E5B4-985304EE8150> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/MacOS.so 0x7fb000 - 0x7fbff5 +_weakref.so ??? (???) <945566A6-ACAF-BFD8-3474-03996C6F0D82> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_weakref.so 0x10f8000 - 0x10f8ff3 +grp.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/grp.so 0x10fc000 - 0x10fcffa +syslog.so ??? (???) <24CB219D-3A60-E56B-A2D3-A7929ADEBF4A> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/syslog.so 0x159c000 - 0x159fffa +_Res.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_Res.so 0x15a6000 - 0x15adff7 +_File.so ??? (???) <767942A5-6991-C70A-6FD1-EAFC22C0251E> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_File.so 0x15b7000 - 0x15baff7 +_zope_interface_coptimizations.so ??? (???) <91B9328F-A098-DA4D-2C17-2672BAC7CDDC> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/zope.interface-3.5.2-py2.6-macosx-10.3-fat.egg/zope/interface/_zope_interface_coptimizations.so 0x15c0000 - 0x15c5fff +binascii.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/binascii.so 0x15ca000 - 0x15d8fff +cPickle.so ??? (???) <440E0C46-62CF-5C05-15AF-17F94C922F9D> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/cPickle.so 0x15e0000 - 0x15e1ff5 +_hashlib.so ??? (???) <5D7347EB-1AB0-A64D-3D0B-9C05B0BA12B3> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_hashlib.so 0x15e6000 - 0x15e9ffe +_sha256.so ??? (???) <9366ADC0-98C8-0CB3-C6E5-FC08C9975D86> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_sha256.so 0x15ed000 - 0x15faff1 +_sha512.so ??? (???) <63CF6A9E-230E-5EB1-4D1B-3BBE856F9155> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_sha512.so 0x15fe000 - 0x1600fff +math.so ??? (???) <06E35D7B-2246-9698-B12B-CC112597523B> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/math.so 0x1606000 - 0x1607fff +_random.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_random.so 0x160b000 - 0x161dfff +_ctypes.so ??? (???) <7AFEFB64-D558-CCF0-1D6E-AC0CF96656A8> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_ctypes.so 0x162b000 - 0x167ffff +_objc.so ??? (???) <8AFD0141-1B19-AEB0-BA9A-2B5628599E12> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/pyobjc_core-2.2-py2.6-macosx-10.3-fat.egg/objc/_objc.so 0x16ae000 - 0x16b4ff0 +_elementtree.so ??? (???) <808FA3F3-C6BA-E727-0700-E59050CB47D6> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_elementtree.so 0x16ba000 - 0x16beff9 +array.so ??? (???) <225C8EDE-27E3-F800-F3CE-B1C6D912187B> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/array.so 0x16c6000 - 0x16f4fe7 +pyexpat.so ??? (???) <5C299820-CCF7-5AE6-C376-046DA57C87CF> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/pyexpat.so 0x1704000 - 0x170effc +_CF.so ??? (???) <6231E0AA-C554-F01C-0A28-BD73CD78AEC6> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_CF.so 0x171e000 - 0x171fff0 +fcntl.so ??? (???) <21B2B1EE-58CF-E74F-B145-30EF50FB8D64> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/fcntl.so 0x1763000 - 0x1763ff0 +_scproxy.so ??? (???) <660139D7-362C-FCC9-DE8F-F9E396F74FAE> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_scproxy.so 0x17a7000 - 0x17a8ffe +_locale.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_locale.so 0x17ec000 - 0x17eefff +select.so ??? (???) <06E5920F-2F6A-B301-E6AA-A22A9F9F2A9D> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/select.so 0x17f4000 - 0x17f4ff5 +_bisect.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_bisect.so 0x17f8000 - 0x17f9ff9 +_heapq.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_heapq.so 0x2180000 - 0x2180ff7 +_c_urlarg.so ??? (???) <774D974E-8A52-96CD-FD23-363830721DB9> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/Twisted-9.0.0_r27662-py2.6-macosx-10.3-fat.egg/twisted/protocols/_c_urlarg.so 0x21c4000 - 0x21c9ff7 +_callbacks.so ??? (???) /Users/erik/.python-eggs/pyobjc_framework_Quartz-2.2-py2.6-macosx-10.3-fat.egg-tmp/Quartz/CoreGraphics/_callbacks.so 0x21d0000 - 0x21d0ff7 +_doubleindirect.so ??? (???) <4688DBA9-DD8A-D6EB-71E3-A3861F89B35F> /Users/erik/.python-eggs/pyobjc_framework_Quartz-2.2-py2.6-macosx-10.3-fat.egg-tmp/Quartz/CoreGraphics/_doubleindirect.so 0x21d5000 - 0x21d5ff7 +_sortandmap.so ??? (???) /Users/erik/.python-eggs/pyobjc_framework_Quartz-2.2-py2.6-macosx-10.3-fat.egg-tmp/Quartz/CoreGraphics/_sortandmap.so 0x21da000 - 0x21dbff7 +_coregraphics.so ??? (???) <2D7F8680-200B-3BDA-429D-78DC7E7EDD8B> /Users/erik/.python-eggs/pyobjc_framework_Quartz-2.2-py2.6-macosx-10.3-fat.egg-tmp/Quartz/CoreGraphics/_coregraphics.so 0x21e0000 - 0x21e0ff7 +_CVPixelBuffer.so ??? (???) /Users/erik/.python-eggs/pyobjc_framework_Quartz-2.2-py2.6-macosx-10.3-fat.egg-tmp/Quartz/CoreVideo/_CVPixelBuffer.so 0x21e5000 - 0x21e5ff7 +_inlines.so ??? (???) /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/Foundation/_inlines.so 0x226d000 - 0x226dff7 +_inlines.so ??? (???) <0EBA241E-B8FC-4523-D519-C491A5A04BCE> /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/CoreFoundation/_inlines.so 0x22f5000 - 0x22f5ff7 +_CFFileDescriptor.so ??? (???) /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/CoreFoundation/_CFFileDescriptor.so 0x22fa000 - 0x22fbff7 +_CFMachPort.so ??? (???) <01A596D2-7375-0376-DF01-1D67A813C689> /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/CoreFoundation/_CFMachPort.so 0x243c000 - 0x243cff7 +_CFMessagePort.so ??? (???) /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/CoreFoundation/_CFMessagePort.so 0x2441000 - 0x2441ff7 +_CFNumber.so ??? (???) /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/CoreFoundation/_CFNumber.so 0x2446000 - 0x2446ff7 +_CFReadStream.so ??? (???) /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/CoreFoundation/_CFReadStream.so 0x244b000 - 0x244bff7 +_CFRunLoopObserver.so ??? (???) <704F1A23-E46C-7194-99E5-D54C7768CA3B> /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/CoreFoundation/_CFRunLoopObserver.so 0x2450000 - 0x2450ff7 +_CFRunLoopTimer.so ??? (???) <4778E98F-9536-3DF4-A90E-74B260D9544F> /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/CoreFoundation/_CFRunLoopTimer.so 0x2455000 - 0x2455ff7 +_CFWriteStream.so ??? (???) <6BCDF06E-2517-2C7B-A905-24B2F5A8681E> /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/CoreFoundation/_CFWriteStream.so 0x245a000 - 0x245bff7 +_CFRunLoopSource.so ??? (???) /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/CoreFoundation/_CFRunLoopSource.so 0x2460000 - 0x2460ff7 +_CFSet.so ??? (???) /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/CoreFoundation/_CFSet.so 0x2465000 - 0x2466ff7 +_CFSocket.so ??? (???) <12B98622-5E7F-66A5-ADEF-57CAC4E9D3BF> /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/CoreFoundation/_CFSocket.so 0x246b000 - 0x246bff7 +_inlines.so ??? (???) /Users/erik/.python-eggs/pyobjc_framework_Quartz-2.2-py2.6-macosx-10.3-fat.egg-tmp/Quartz/CoreGraphics/_inlines.so 0x33cc000 - 0x33cfff7 +_NSDecimal.so ??? (???) /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/Foundation/_NSDecimal.so 0x33d5000 - 0x33d6ff7 +_nsinvocation.so ??? (???) <859D0D49-C6B0-DC88-233C-6C942CE083C6> /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/Foundation/_nsinvocation.so 0x33db000 - 0x33dbff7 +_typecode.so ??? (???) <8741C58D-7242-6E59-7B62-2E366504F50A> /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/Foundation/_typecode.so 0x33e0000 - 0x33e3ff7 +_nscoder.so ??? (???) /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/Foundation/_nscoder.so 0x33e9000 - 0x33eaff7 +_data.so ??? (???) /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/Foundation/_data.so 0x33ef000 - 0x33efff7 +_netservice.so ??? (???) <0000A88F-C540-6768-A9A3-891F1DFE2F42> /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/Foundation/_netservice.so 0x33f4000 - 0x33f4ff7 +_string.so ??? (???) <98A7A49C-1A84-7146-96CA-0C3A4DB13490> /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/Foundation/_string.so 0x33f9000 - 0x33f9ff7 +_inlines.so ??? (???) <0564B51F-4036-A730-ECC4-33818D71ED48> /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/AppKit/_inlines.so 0x3500000 - 0x3500ff7 +_appmain.so ??? (???) <0909D762-00B9-553B-3A49-7C862F3BF7BA> /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/AppKit/_appmain.so 0x3505000 - 0x3506ff7 +_nsbezierpath.so ??? (???) <8074567D-4F6A-18EB-44AA-572B30FC9587> /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/AppKit/_nsbezierpath.so 0x350b000 - 0x350bff7 +_nsfont.so ??? (???) <382E35EC-5660-0B1A-443B-2964AF0F87C7> /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/AppKit/_nsfont.so 0x3510000 - 0x3510ff7 +_nsquickdrawview.so ??? (???) /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/AppKit/_nsquickdrawview.so 0x3515000 - 0x3515ff7 +_nsview.so ??? (???) <806F07AD-8BA7-2674-93BF-850C2CC2D73D> /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/AppKit/_nsview.so 0x351a000 - 0x351bff7 +_nsbitmap.so ??? (???) <65425BDB-F700-DE18-40F6-E1DBA3ED40F6> /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/AppKit/_nsbitmap.so 0x3520000 - 0x3520ff7 +_nswindow.so ??? (???) <96476BE4-4497-68CA-5421-23CC7D461E9D> /Users/erik/.python-eggs/pyobjc_framework_Cocoa-2.2-py2.6-macosx-10.3-fat.egg-tmp/AppKit/_nswindow.so 0x8fe00000 - 0x8fe4162b dyld 132.1 (???) <211AF0DD-42D9-79C8-BB6A-1F4BEEF4B4AB> /usr/lib/dyld 0x90003000 - 0x9000cff7 com.apple.DiskArbitration 2.3 (2.3) /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration 0x900b4000 - 0x900f7ff7 com.apple.NavigationServices 3.5.3 (181) <28CDD978-030E-7D4A-5334-874A8EBE6C29> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationServices.framework/Versions/A/NavigationServices 0x900f8000 - 0x900f8ff7 com.apple.ApplicationServices 38 (38) <8012B504-3D83-BFBB-DA65-065E061CFE03> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices 0x90138000 - 0x9014cffb com.apple.speech.synthesis.framework 3.10.35 (3.10.35) <57DD5458-4F24-DA7D-0927-C3321A65D743> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis 0x90157000 - 0x902d9fe7 libicucore.A.dylib ??? (???) <2B0182F3-F459-B452-CC34-46FE73ADE348> /usr/lib/libicucore.A.dylib 0x902da000 - 0x902dcff7 libRadiance.dylib ??? (???) <462903E2-2E77-FAE5-4ED6-829AAB1980A4> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib 0x902dd000 - 0x9037afe3 com.apple.LaunchServices 362 (362) <8BE1C1A1-BF71-CE07-F3FB-6057D47AF461> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices 0x9037b000 - 0x90381ff7 com.apple.DisplayServicesFW 2.2 (2.2) <72C790A9-F4D2-DA92-015B-4CAF478FC0C2> /System/Library/PrivateFrameworks/DisplayServices.framework/Versions/A/DisplayServices 0x90382000 - 0x90385ffb com.apple.help 1.3.1 (41) <67F1F424-3983-7A2A-EC21-867BE838E90B> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help 0x90386000 - 0x903caff3 com.apple.coreui 2 (113) /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI 0x903ce000 - 0x903f4fff com.apple.DictionaryServices 1.1.1 (1.1.1) <02709230-9B37-C743-6E27-3FCFD18211F8> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices 0x9049e000 - 0x90551fff libFontParser.dylib ??? (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib 0x90647000 - 0x90a7cff7 libLAPACK.dylib ??? (???) <5E2D2283-57DE-9A49-1DB0-CD027FEFA6C2> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib 0x90a7d000 - 0x90a87fe7 com.apple.audio.SoundManager 3.9.3 (3.9.3) <5F494955-7290-2D91-DA94-44B590191771> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.framework/Versions/A/CarbonSound 0x90ac1000 - 0x90b0afe7 libTIFF.dylib ??? (???) <5864AE5B-EAEB-F8B6-18FB-3D27B7895A4C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib 0x90be8000 - 0x90c79fe7 com.apple.print.framework.PrintCore 6.1 (312.3) <6D4322AF-703C-CC19-77B4-53E6D3BB18D4> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore 0x90c7a000 - 0x90f9dfef com.apple.HIToolbox 1.6.2 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox 0x90fe6000 - 0x91028fe7 libvDSP.dylib ??? (???) <8F8FFFB3-81E3-2969-5688-D5B0979182E6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib 0x91029000 - 0x9103aff7 com.apple.LangAnalysis 1.6.6 (1.6.6) <7A3862F7-3730-8F6E-A5DE-8E2CCEA979EF> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis 0x9103b000 - 0x9106eff7 com.apple.AE 496.1 (496.1) <1AC75AE2-AF94-2458-0B94-C3BB0115BA4B> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE 0x9106f000 - 0x91251fff com.apple.imageKit 2.0.1 (1.0) <3CD99122-4DC8-00CE-4BD7-E3E1E1C71C30> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/ImageKit.framework/Versions/A/ImageKit 0x91252000 - 0x9125fff7 com.apple.NetFS 3.2.1 (3.2.1) <5E61A00B-FA16-9D99-A064-47BDC5BC9A2B> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS 0x91276000 - 0x91325ff3 com.apple.ColorSync 4.6.2 (4.6.2) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync 0x91326000 - 0x914cafeb libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib 0x914cb000 - 0x91595fef com.apple.CoreServices.OSServices 352 (352) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices 0x91596000 - 0x915d3ff7 com.apple.SystemConfiguration 1.10.1 (1.10.1) /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration 0x9164c000 - 0x91658ff7 libkxld.dylib ??? (???) <3D2C5BA3-6A8D-C861-B346-0E19942D9AF1> /usr/lib/system/libkxld.dylib 0x925e8000 - 0x925edff7 com.apple.OpenDirectory 10.6 (10.6) <92582807-E8F3-3DD9-EB42-4195CFB754A1> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory 0x9260e000 - 0x92710fef com.apple.MeshKitIO 1.0 (49.0) /System/Library/PrivateFrameworks/MeshKit.framework/Versions/A/Frameworks/MeshKitIO.framework/Versions/A/MeshKitIO 0x92711000 - 0x927a9fe7 edu.mit.Kerberos 6.5.9 (6.5.9) <73EC847F-FF44-D542-2AD5-97F6C8D48F0B> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos 0x928f8000 - 0x928fefff com.apple.CommonPanels 1.2.4 (91) <2438AF5D-067B-B9FD-1248-2C9987F360BA> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels 0x9290e000 - 0x92acafef com.apple.ImageIO.framework 3.0.1 (3.0.1) <598CF4F9-7542-E1A7-26D2-584933497A2E> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO 0x92adc000 - 0x92b5cfeb com.apple.SearchKit 1.3.0 (1.3.0) <9E18AEA5-F4B4-8BE5-EEA9-818FC4F46FD9> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit 0x92c13000 - 0x92c1dff7 libGL.dylib ??? (???) <76A207FE-889A-CF1B-AF9A-795EEE5A463E> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib 0x92c1e000 - 0x92c55ff7 com.apple.CoreMedia 0.420.18 (420.18) <43747711-B334-B0C7-4971-15FA586DAFBF> /System/Library/PrivateFrameworks/CoreMedia.framework/Versions/A/CoreMedia 0x92c77000 - 0x92d1fffb com.apple.QD 3.33 (???) <196CDBA6-5B87-2767-DD57-082D71B0A5C7> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD 0x92ef8000 - 0x92f2dff7 libGLImage.dylib ??? (???) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib 0x92f2e000 - 0x92f32ff7 IOSurface ??? (???) /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface 0x9308d000 - 0x9308dff7 com.apple.Cocoa 6.6 (???) /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa 0x9308e000 - 0x930aefe7 com.apple.opencl 12 (12) <2DB56F60-577B-6724-5708-7B082F62CC0F> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL 0x930af000 - 0x930afff7 com.apple.Accelerate 1.5 (Accelerate 1.5) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate 0x930b0000 - 0x930f4fe7 com.apple.Metadata 10.6.2 (507.4) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata 0x930f5000 - 0x93105ff7 com.apple.DSObjCWrappers.Framework 10.6 (134) <81A0B409-3906-A98F-CA9B-A49E75007495> /System/Library/PrivateFrameworks/DSObjCWrappers.framework/Versions/A/DSObjCWrappers 0x93106000 - 0x9317fff7 com.apple.PDFKit 2.5 (2.5) <58603BDB-337F-FBE3-EB11-7C31CF261995> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/PDFKit.framework/Versions/A/PDFKit 0x93198000 - 0x93202fe7 libstdc++.6.dylib ??? (???) <411D87F4-B7E1-44EB-F201-F8B4F9227213> /usr/lib/libstdc++.6.dylib 0x93203000 - 0x93238ff7 libcups.2.dylib ??? (???) /usr/lib/libcups.2.dylib 0x93240000 - 0x9324bff7 libCSync.A.dylib ??? (???) <9292E6E3-70C1-1DD7-4213-1044F0FA8381> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib 0x933c1000 - 0x93c9fff7 com.apple.AppKit 6.6.3 (1038.25) <72A9AA47-8DCB-DB07-64F5-F837E98C62D8> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit 0x93ca0000 - 0x93caaffb com.apple.speech.recognition.framework 3.11.1 (3.11.1) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition 0x93cab000 - 0x93cc6ff7 libPng.dylib ??? (???) <3F8682CD-C05B-607D-96E7-767646C77DB8> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib 0x93cf9000 - 0x93cf9ff7 com.apple.CoreServices 44 (44) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices 0x93d05000 - 0x93e12ff7 com.apple.MediaToolbox 0.420.18 (420.18) <31935D52-1F8D-4AB2-CCA5-4CF615CBCE24> /System/Library/PrivateFrameworks/MediaToolbox.framework/Versions/A/MediaToolbox 0x93fa8000 - 0x94000fe7 com.apple.datadetectorscore 2.0 (80.7) /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore 0x94001000 - 0x94070ff7 libvMisc.dylib ??? (???) <59243A8C-2B98-3E71-8032-884D4853E79F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib 0x94071000 - 0x94071ff7 com.apple.Accelerate.vecLib 3.5 (vecLib 3.5) <3E039E14-2A15-56CC-0074-EE59F9FBB913> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib 0x9407d000 - 0x940ceff7 com.apple.HIServices 1.8.0 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices 0x940cf000 - 0x942faff3 com.apple.QuartzComposer 4.1 (156.10) <24293329-50D7-D12F-51B3-57976A4E52B1> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuartzComposer.framework/Versions/A/QuartzComposer 0x94326000 - 0x94645fe7 com.apple.CoreServices.CarbonCore 861.2 (861.2) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore 0x94646000 - 0x94664ff7 com.apple.CoreVideo 1.6.0 (43.1) <1FB01BE0-B013-AE86-A063-481BB547D2F5> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo 0x94697000 - 0x949feff7 com.apple.QuartzCore 1.6.1 (227.8) <8B90AB08-46A4-1C5C-4E71-C6AB652477B9> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore 0x949ff000 - 0x94a01ff7 com.apple.securityhi 4.0 (36638) <962C66FB-5BE9-634E-0810-036CB340C059> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI 0x94a02000 - 0x951e54b7 com.apple.CoreGraphics 1.536.12 (???) <263EB5FC-DEAD-7C5B-C486-EC86C173F952> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics 0x951e6000 - 0x95325fe3 com.apple.QTKit 7.6.3 (1591.3) <18F25C19-F0B8-5907-D6D6-65EC53DF0D3B> /System/Library/Frameworks/QTKit.framework/Versions/A/QTKit 0x95698000 - 0x95b46fe7 com.apple.VideoToolbox 0.420.18 (420.18) /System/Library/PrivateFrameworks/VideoToolbox.framework/Versions/A/VideoToolbox 0x95b47000 - 0x95b47ff7 com.apple.Carbon 150 (152) <608A04AB-F35D-D2EB-6629-16B88FB32074> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon 0x95b48000 - 0x95b9eff7 com.apple.MeshKitRuntime 1.0 (49.0) /System/Library/PrivateFrameworks/MeshKit.framework/Versions/A/Frameworks/MeshKitRuntime.framework/Versions/A/MeshKitRuntime 0x95b9f000 - 0x95becfeb com.apple.DirectoryService.PasswordServerFramework 6.0 (6.0) /System/Library/PrivateFrameworks/PasswordServer.framework/Versions/A/PasswordServer 0x95bed000 - 0x95c09fe3 com.apple.openscripting 1.3.1 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting 0x95c4c000 - 0x95cfaff3 com.apple.ink.framework 1.3.1 (105) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink 0x95daa000 - 0x95de9ff7 com.apple.ImageCaptureCore 1.0 (1.0) /System/Library/Frameworks/ImageCaptureCore.framework/Versions/A/ImageCaptureCore 0x95dea000 - 0x95edcff7 libcrypto.0.9.8.dylib ??? (???) <792B8722-3091-5E9F-E25F-67499CFE0599> /usr/lib/libcrypto.0.9.8.dylib 0x95edd000 - 0x95eddff7 com.apple.vecLib 3.5 (vecLib 3.5) <17BEEF92-DF30-CD52-FD65-0B7B43B93617> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib 0x95ede000 - 0x95ef3fff com.apple.ImageCapture 6.0 (6.0) <3F31833A-38A9-444E-02B7-17619CA6F2A0> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture 0x95ef4000 - 0x95f44ff7 com.apple.framework.familycontrols 2.0 (2.0) /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/FamilyControls 0x95f45000 - 0x95f46ff7 com.apple.audio.units.AudioUnit 1.6.1 (1.6.1) <3A08510C-07F7-1A09-D6ED-1A488203ACCC> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit 0x95f4f000 - 0x96029ff3 com.apple.DesktopServices 1.5.3 (1.5.3) /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv 0x9602a000 - 0x960e3fe7 libsqlite3.dylib ??? (???) <16CEF8E8-8C9A-94CD-EF5D-05477844C005> /usr/lib/libsqlite3.dylib 0x96119000 - 0x96290fef com.apple.CoreFoundation 6.6.1 (550.13) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation 0x96291000 - 0x962f5ffb com.apple.htmlrendering 72 (1.1.4) <4D451A35-FAB6-1288-71F6-F24A4B6E2371> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering.framework/Versions/A/HTMLRendering 0x96460000 - 0x96472ff7 com.apple.MultitouchSupport.framework 204.9 (204.9) /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport 0x96473000 - 0x96550ff7 com.apple.vImage 4.0 (4.0) <64597E4B-F144-DBB3-F428-0EC3D9A1219E> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage 0x96551000 - 0x9684afef com.apple.QuickTime 7.6.3 (1591.3) <803CC5FD-2369-83B5-795D-A8963620EFAC> /System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime 0x9684b000 - 0x968e7fe7 com.apple.ApplicationServices.ATS 4.1 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS 0x968e9000 - 0x96957ff7 com.apple.QuickLookUIFramework 2.1 (327.3) <2F51D9CB-F827-E0AF-F201-5F4244C0D02A> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuickLookUI.framework/Versions/A/QuickLookUI 0x969a4000 - 0x96aa5fe7 libxml2.2.dylib ??? (???) /usr/lib/libxml2.2.dylib 0x96aa6000 - 0x96af6fe7 libGLU.dylib ??? (???) <659ADCA2-10EC-59BD-1B0A-4928A965F1D1> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib 0x96af7000 - 0x96b0fff7 com.apple.CFOpenDirectory 10.6 (10.6) <1537FB4F-C112-5D12-1E5D-3B1002A4038F> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory 0x96b10000 - 0x96b24fe7 libbsm.0.dylib ??? (???) <14CB053A-7C47-96DA-E415-0906BA1B78C9> /usr/lib/libbsm.0.dylib 0x96b25000 - 0x96b25ff7 liblangid.dylib ??? (???) /usr/lib/liblangid.dylib 0x96b26000 - 0x96b27ff7 com.apple.TrustEvaluationAgent 1.1 (1) <6C04C4C5-667E-2EBE-EB96-5B67BD4B2185> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent 0x96b28000 - 0x96b2cff7 libGFXShared.dylib ??? (???) <79F4F60E-0A6D-CE9C-282E-FA85825449E3> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib 0x96b65000 - 0x96b6cfff com.apple.print.framework.Print 6.0 (237) <7A06B15C-B835-096E-7D96-C2FE8F0D21E1> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print 0x96b9e000 - 0x96ba2ff7 libGIF.dylib ??? (???) <83FB0DCC-355F-A930-E570-0BD95086CC59> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib 0x96ba3000 - 0x96fb9ff7 libBLAS.dylib ??? (???) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib 0x970e4000 - 0x9710bff7 com.apple.quartzfilters 1.6.0 (1.6.0) <879A3B93-87A6-88FE-305D-DF1EAED04756> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuartzFilters.framework/Versions/A/QuartzFilters 0x9710c000 - 0x9711cff7 libsasl2.2.dylib ??? (???) /usr/lib/libsasl2.2.dylib 0x97125000 - 0x97133fe7 libz.1.dylib ??? (???) <7B7A02AB-DA99-6180-880E-D28E4F9AA8EB> /usr/lib/libz.1.dylib 0x9719a000 - 0x971d6fff com.apple.CoreMediaIOServices 124.0 (850) <5F9B1AA3-8BB3-4E8C-2A31-F8FD5EC3F28A> /System/Library/PrivateFrameworks/CoreMediaIOServices.framework/Versions/A/CoreMediaIOServices 0x971d7000 - 0x971f9fef com.apple.DirectoryService.Framework 3.6 (621.1) <3ED4949F-9604-C109-6586-5CE5F421182B> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryService 0x971fa000 - 0x9723bff7 libRIP.A.dylib ??? (???) <9F0ECE75-1F03-60E4-E29C-136A27C13F2E> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib 0x9723c000 - 0x972e3fe7 com.apple.CFNetwork 454.5 (454.5) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwork.framework/Versions/A/CFNetwork 0x972e4000 - 0x97308ff7 libJPEG.dylib ??? (???) <649E1974-A527-AC0B-B3F4-B4DC30484070> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib 0x97567000 - 0x975c1fe7 com.apple.CorePDF 1.1 (1.1) <8ED0FB5F-D498-D012-DF09-DE5378D40D52> /System/Library/PrivateFrameworks/CorePDF.framework/Versions/A/CorePDF 0x975c2000 - 0x97832ffb com.apple.Foundation 6.6.1 (751.14) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation 0x97918000 - 0x97988ff3 com.apple.AppleVAFramework 4.7.5 (4.7.5) <464A915D-E670-FA22-7799-454259D42B82> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA 0x97989000 - 0x979b1ff7 libxslt.1.dylib ??? (???) <769EF4B2-C1AD-73D5-AAAD-1564DAEA77AF> /usr/lib/libxslt.1.dylib 0x97bb3000 - 0x97bd3fe7 libresolv.9.dylib ??? (???) /usr/lib/libresolv.9.dylib 0x97bd4000 - 0x97ccaff7 libGLProgrammability.dylib ??? (???) <82D03736-D30C-C013-BBB1-20ED9687D47F> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib 0x97d7b000 - 0x97ea9fe7 com.apple.CoreData 102.1 (250) /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData 0x97eaa000 - 0x97eadfe7 libmathCommon.A.dylib ??? (???) <1622A54F-1A98-2CBE-B6A4-2122981A500E> /usr/lib/system/libmathCommon.A.dylib 0x97f57000 - 0x980f4fef com.apple.JavaScriptCore 6531.21 (6531.21.9) /System/Library/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore 0x981a4000 - 0x98226ffb SecurityFoundation ??? (???) <29C27E0E-B2B3-BF6B-B1F8-5783B8B01535> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation 0x98227000 - 0x98353fe3 com.apple.audio.toolbox.AudioToolbox 1.6.1 (1.6.1) /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox 0x98547000 - 0x987a9ff7 com.apple.security 6.0 (36910) <32B8FA26-CD73-4C45-C15A-EF8406D51FCC> /System/Library/Frameworks/Security.framework/Versions/A/Security 0x987aa000 - 0x98804ff7 com.apple.framework.IOKit 2.0 (???) <1BE07087-27D5-0E62-F06B-007C2BED4073> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit 0x9881e000 - 0x9884eff7 com.apple.MeshKit 1.0 (49.0) <435718C1-ED40-6BCC-F0D8-67FA05CFFF1E> /System/Library/PrivateFrameworks/MeshKit.framework/Versions/A/MeshKit 0x9884f000 - 0x988fcfe7 libobjc.A.dylib ??? (???) /usr/lib/libobjc.A.dylib 0x98916000 - 0x98976fe7 com.apple.CoreText 3.1.0 (???) <79FD1B5C-2F93-4C5D-B07B-4DD9088E67DE> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreText.framework/Versions/A/CoreText 0x98977000 - 0x9897aff7 libCoreVMClient.dylib ??? (???) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib 0x9897b000 - 0x989b9ff7 com.apple.QuickLookFramework 2.1 (327.3) /System/Library/Frameworks/QuickLook.framework/Versions/A/QuickLook 0x991e5000 - 0x994deff3 com.apple.RawCamera.bundle 2.3.0 (505) <1C7CEA30-FFE2-B4DE-98CE-D6518DF1E54B> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera 0x994df000 - 0x99525ff7 libauto.dylib ??? (???) <85670A64-3B67-8162-D441-D8E0BE15CA94> /usr/lib/libauto.dylib 0x99526000 - 0x99533ff7 com.apple.opengl 1.6.5 (1.6.5) <0AE8B897-8A80-2C14-D6FC-DC21AC423234> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL 0x99534000 - 0x995aefef com.apple.audio.CoreAudio 3.2.2 (3.2.2) <1F97B48A-327B-89CC-7C01-3865179716E0> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio 0x995b7000 - 0x995b8ff7 com.apple.MonitorPanelFramework 1.3.0 (1.3.0) <0EC4EEFF-477E-908E-6F21-ED2C973846A4> /System/Library/PrivateFrameworks/MonitorPanel.framework/Versions/A/MonitorPanel 0xffff0000 - 0xffff1fff libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib Model: MacBook5,1, BootROM MB51.007D.B03, 2 processors, Intel Core 2 Duo, 2.4 GHz, 2 GB, SMC 1.32f8 Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB Memory Module: global_name AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.10.91.26) Bluetooth: Version 2.2.4f3, 2 service, 0 devices, 1 incoming serial ports Network Service: AirPort, AirPort, en1 Serial ATA Device: FUJITSU MHZ2250BH FFS G1, 232,89 GB Serial ATA Device: OPTIARC DVD RW AD-5960S USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8507, 0x24400000 USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x06100000 USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8213, 0x06110000 USB Device: Apple Internal Keyboard / Trackpad, 0x05ac (Apple Inc.), 0x0237, 0x04600000 USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0x04500000