🌐 Mailman 3 January 2010 - Pythonmac-SIG - python.org

Re: [Pythonmac-SIG] Integrating aemreceive into a class--help
by has Jan. 12, 2010

Jan. 12, 2010

Kevin Walzer wrote: > First, I simply import aemreceive into my app class. Next, I wrap its "installeventhandler" function into a class method, cf: > > def installeventhandler (self, > eventcallback, > eventcode, > *parameterdefinitions): > aemreceive.installeventhandler(eventcallback, eventcode, *parameterdefinitions, codecs=aem.Codecs()) > > Next, in my app class's __init__ method, I install the event handler like so: > > self.installeventhandler(self.getDomain, > 'CoKvdman', > ('----', 'self', aemreceive.kae.typeUnicodeText), > ('----', 'domain', aemreceive.kae.typeUnicodeText) > ) You don't pass self to a bound method in Python. Delete the ('----', 'self', ...) tuple. HTH has -- Control AppleScriptable applications from Python, Ruby and ObjC: http://appscript.sourceforge.net

2 2

Integrating aemreceive into a class--help
by Kevin Walzer Jan. 12, 2010

Jan. 12, 2010

I'm having a harder time than expected integrating aemreceive into my application class. While aemreceive's example code is admirably clear and the docs are thorough, they are geared for procedural code, and I keep tripping over scoping issues in trying to integrate the library into a more OO setting. Here's where things stand: First, I simply import aemreceive into my app class. Next, I wrap its "installeventhandler" function into a class method, cf: def installeventhandler (self, eventcallback, eventcode, *parameterdefinitions): aemreceive.installeventhandler(eventcallback, eventcode, *parameterdefinitions, codecs=aem.Codecs()) Next, in my app class's __init__ method, I install the event handler like so: self.installeventhandler(self.getDomain, 'CoKvdman', ('----', 'self', aemreceive.kae.typeUnicodeText), ('----', 'domain', aemreceive.kae.typeUnicodeText) ) This actually builds and runs the application without any complaints about "self" being undefined. However, I still can't actually get data from my Apple Event. As it's currently set up, I get this error from AppleScript: "Required parameter '----' is missing." I'm not clear on what this means. According to the aemreceive docs, I need to provide a tuple for each parameter included. This means two, i.e. "self" and "domain," as outlined above. I don't know what the missing parameter is. This doesn't *look* right to me: "self" prepends the "getDomain" method and actually shouldn't be included in the parameter setup as well, by my logic. However, the application crashes if I change "self.getDomain" to "getDomain" because, of course, "getDomain" is not defined. Any guidance in getting the parameters for the event handlers correctly fleshed out would be much appreciated. In particular, I'm not sure where "self" should go, nor am I even certain if aemreceive.kae.typeUnicodeText is the correct data type for that. I hope I don't sound too frustrated. Apple Events are very complicated, and has's work on making them accessible via this higher-level interface is admirable. Tk-Aqua's built-in "do-script" functionality is easier to use, and is very flexible in the sense that it allows you to execute *any* Tcl code, but aemreceive allows you to provide a real AppleScript interface to Python commands (you don't have to call raw Python code from AppleScript). There's a richer Tcl interface to Apple Events called TclAE, but it's more low-level and complex, and and it's only minimally maintained, so the extensive work needed to make it 64-bit capable has not yet been done. So, thanks again to has for his good work on this! And looking forward to additional advice on the package. Best, Kevin -- Kevin Walzer Code by Kevin http://www.codebykevin.com

1 0

Re: [Pythonmac-SIG] Python app with aemreceive is not scriptable
by has Jan. 11, 2010

Jan. 11, 2010

Kevin Walzer wrote: > It appears that Tcl and Python differ in some respects in code execution. Python doesn't appear to return a value from code that is passed to the "exec" statement. exec evaluates statements, and Python statements don't return values. You'd need to pass global/local dicts to it and exchange values via that. For what you're doing though, eval() might be a more appropriate choice. Though personally I'd be looking to add a proper AE API, even if only procedural, so that users can't just run arbitrary code. But that's your decision, not mine. has -- Control AppleScriptable applications from Python, Ruby and ObjC: http://appscript.sourceforge.net

2 2

Create a new tab with index 1?
by Seiya Jan. 10, 2010

Jan. 10, 2010

I would like to use appscript to realize the following applescript: tell application "Safari" tell window 1 make new tab at beginning end tell end tell that is, I want to make a new tab with index 1. The following code safari = app("Safari").windows[1].make(new=k.tab) will create a tab at the end. I know that I should at some "at=" in the parameter. However, I cannot figure out how to use "k.location_reference". I wonder whether someone can help me out. Thanks.

2 1

font-choice dialog in Snow Leopard
by Charles Hartman Jan. 10, 2010

Jan. 10, 2010

I admit I haven't looked into it in detail yet, and I will, but maybe somebody can simplify the hunt. In an app I last built with py2app under Leopard, a standard dialog to choose a font (using wxPython's wx.GetFontFromUser() ) appears on the screen for a brief flash and then vanishes when I run the executable under Snow Leopard. I could begin by just rebuilding with py2app under Snow Leopard, but I'm nervous, given all the S.L. alarms I've seen here. Charles Hartman

1 0

Re: [Pythonmac-SIG] [Numpy-discussion] 1.4.0 installer fails on OSX 10.6.2
by Christopher Barker Jan. 8, 2010

Jan. 8, 2010

NOTE: cc-d to the pythonmac list from the numpy list -- this is really a Mac issue. It's a discussion of what/how to produce binaries of numpy for OS-X David Cournapeau wrote: > On Wed, Jan 6, 2010 at 9:18 AM, Christopher Barker > <Chris.Barker(a)noaa.gov> wrote: > >> If distutils/setuptools could identify the python version properly, then >> binary eggs and easy-install could be a solution -- but that's a mess, >> too. > > It would not solve the problem, really. Two same versions of python > does not imply compatible python when C extensions are involved. In > current state of affairs, where python does not have a stable ABI, the > only workable solution is to target one specific python So you are saying that binary eggs are simply impossible altogether. Maybe true, I suppose, but... >>> As the 2.6 series is binary compatible, you can build a single >>> installer >>> that will work with both > > I don't think that's true. 2.6.x are compatible with each other iif > they are built with the same compiler options. There are too many > differences between Apple python and the python.org python (dtrace, 64 > bits support, compiler options, etc...) IMHO to make a compatible > installer for both versions worthwhile. Well, it was possible once, and it's been working just fine for wxPython for a good while. Things may have changed with OS-X 10.6, tough I think the wxPython binary still works (32 bit only, of course). > I agree that the lack of 64 bits installer is an issue, but building > numpy on mac os x is not that difficult, and I think people who need > 64 bits often are more knowledgeable. I agree -- but what do you get if you install OS-X 10.6, and then type "python" at the prompt -- is that a 32 bit or 64 bit python? > There are also solutions like > EPD and the likes, which support 64 bits. but not PPC anymore, sigh. There is a key problem here -- folks running OS-X expecting it to be another Unix are fine -- they install the compiler, build their own extensions, probably use some combination of fink and macports, etc. This may well apply to many Scientific programmers, and web developers (though it maybe not). However, there is a different type of Mac user -- the type that has traditionally used Macs. Some of these folks are giving a bit of programming a try, and have heard that python is an easy to learn language -- and, cool, OS-X even comes with it installed! But then they soon enough discover that they need additional packages of some sort --- and numpy is a very, very useful package, and not just for the experienced programmer (think Matlab users, for instance). These folks haven't installed the compiler, don't know 64 from 32 bit, and heaven forbid, have no idea how the heck to compile a dependency with the "./configure && make && make install" dance. Some years ago, the community on the pythonmac list made significant efforts to try to support these folks. Primarily what they need are binary installers. We also more or less declared the python.org python as the official python to support, and even had a repository of pre-built packages (http://pythonmac.org/packages/py25-fat/index.html). It was pretty handy -- you could get python itself and all the major packages there, all working together. That repository is not longer maintained, for a couple reasons: 1) Bob Ippolito is doing other things 2) A lot of package developers are providing binaries themselves 3) It's gotten even messier! But there is still a community out there that it would be nice to support. So the question is: how do we do it? That repository appears to be dead, though it could be revived if there is a bit of interest. But even without it, it would be great if there was some sort of consensus among the pythonmac crowd and the major package developers as to what to provide binaries for. We're really in a mess if you can only get a binary for PIL for the Apple Python, and only get a binary for numpy for the python.org python. Personally, I still think the Apple python is dead-end -- Apple has never supported it properly. And, if you go that route you need a different build for people running 10.4 and 10.5, and 10.6, and ... I'm not sure what the 64 bit story is -- I suspect that David is right -- folks running 64 bits are the ones that know what they are doing, so they have less need for binaries. So maybe for now this is a good goal: python 2.5: python.org build (32 bit PPC and intel) python 2.6: 32 bit python.org 2.6.4 64 bit python.org build? python 2.7: python.org 3-way build, if that happens. or separate 32 and 64 bit builds python 3.1: python.org build (whatever it ends up being) Darn, that's quite a few to support! NOTE: Ned Deily just posted a good summary of what's out there on teh pythonmac list: http://mail.python.org/pipermail/pythonmac-sig/2010-January/022031.html -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(a)noaa.gov

4 6

py2app with python 2.6 on OSX 10.4.9/Xcode 2.5
by Karsten Wolf Jan. 6, 2010

Jan. 6, 2010

Hi, I have an application which I created with python 2.5 and py2app on OSX 10.4.11. All is well. Trying to build it with python 2.6.4 and py2app 0.4.3 ends in pdb. python setup.py -A works. Analyzing the code snippet which causes the exception, one can see it calls a unix tool called 'ibtool' which is not present on my system. Seeing that the same tool is used for .xib files my guess is it belongs to Xcode 3.x. What can I do about it (without going to OSX 10.5 and Xcode 3) -karsten In py2app/converters/nibfile.py: p = subprocess.Popen(['ibtool', '--compile', destination, source]) Stack trace. creating /Users/karstenwo/python/pyobjc/bildimporter-git/build/ bildimporter.app/Contents/Resources/English.lproj Traceback (most recent call last): File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ python2.6/site-packages/py2app-0.4.3-py2.6.egg/py2app/build_app.py", line 589, in _run self.run_normal() File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ python2.6/site-packages/py2app-0.4.3-py2.6.egg/py2app/build_app.py", line 660, in run_normal self.create_binaries(py_files, pkgdirs, extensions, loader_files) File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ python2.6/site-packages/py2app-0.4.3-py2.6.egg/py2app/build_app.py", line 755, in create_binaries target, arcname, pkgexts, copyexts, target.script) File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ python2.6/site-packages/py2app-0.4.3-py2.6.egg/py2app/build_app.py", line 1180, in build_executable copy_resource(src, dest, dry_run=self.dry_run) File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ python2.6/site-packages/py2app-0.4.3-py2.6.egg/py2app/util.py", line 84, in copy_resource converter(source, destination, dry_run=dry_run) File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ python2.6/site-packages/py2app-0.4.3-py2.6.egg/py2app/converters/ nibfile.py", line 27, in convert_nib p = subprocess.Popen(['ibtool', '--compile', destination, source]) File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ python2.6/subprocess.py", line 621, in __init__ errread, errwrite) File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ python2.6/subprocess.py", line 1126, in _execute_child raise child_exception OSError: [Errno 2] No such file or directory > /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/ subprocess.py(1126)_execute_child() -> raise child_exception (Pdb)

1 0

What to build binaries for???
by Christopher Barker Jan. 6, 2010

Jan. 6, 2010

Hi folks, Another poster on the numpy list has been bitten by the "must have the system python" issue with the binary installer, meaning the python.org build. 1) I thought I provided a patch a good while ago to update that message -- did that get lost in the shuffle? 2) we're talking on that list about implementing what Robin Dunn has done for wxPython -- a single installer that puts numpy somewhere, then puts *.pth files in both the Apple and Python.org Pythons, so that a single installer will work with both. But now we have issues as to what to support: 32+64 bit, PPC + intel. wxPython is strictly 32 bit, so it's a bit easier. What is being delivered now? Is there a 64 bit build at Python.org? What has Apple delivered with 10.6 and 10.5? Are we going to need multiple installers, maybe 32 and 64 bit? This was messy enough a couple years ago! What do you folks suggest? -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(a)noaa.gov

3 4

path, xcode, and python
by Adam Morris Jan. 6, 2010

Jan. 6, 2010

Hi all, Just trying to get my system set up for some coding ... decided to reinstall everything (Snow Leopard) from scratch. What a mistake that was. I updated to 10.6.2, installed Xcode and THEN installed python 2.6.4. I think that might have something to do with two problems I'm seeing. The major one is: import Foundation, Appkit doesn't work with import error (copy of path is is below) The other one -- I don't know if this is related -- but when I run in interactive mode I can import appscripts no problemo but when I run it from a script (with FastScripts) it gives me an import error. I've looked around the internet for some help, focusing on how path works (something I'm missing?) but I can't help but think it's because I should have installed XCode after doing the python upgrade. Also because I did exactly that previously. Any insight? -brainysmurf ['', '/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/setuptools-0.6c11-py2.6.egg', '/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/macosx_launch-0.0.0-py2.6-macosx-10.3-fat.egg', '/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/appscript-0.21.1-py2.6-macosx-10.3-fat.egg', '/Library/Frameworks/Python.framework/Versions/2.6/lib/python26.zip', '/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6', '/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/plat-darwin', '/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/plat-mac', '/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/plat-mac/lib-scriptpackages', '/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-tk', '/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-old', '/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload', '/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages']

4 7

Re: [Pythonmac-SIG] Python app with aemreceive is not scriptable
by has Jan. 5, 2010

Jan. 5, 2010

Kevin Walzer wrote: > Now my app responds to Apple Events and doesn't complain about a corrupted dictionary. However, I'm having some additional difficulty. It appears that Apple Events are bypassing the bundled Python and are going straight to the Tk framework instead. Tk/Aqua has pretty good AppleScript support, and implements a "do script" command that will execute Tcl scripts. My application responds to this code: > [...] > This is very weird, and I have no clue how to untangle it. My app won't respond to Apple Events at all without a valid sdef file in the bundle's Resources directory. You only need to install event handlers for an application to respond to Apple events. The sdef is only there to provide human-readable terminology; not having one just means that users have to resort to raw chevron syntax (in AppleScript) or the aem API (in appscript) in order to communicate with it. (Cocoa Scripting-based apps do use the sdef for implementation purposes as well, but as your app doesn't use Cocoa Scripting to provide its Apple event interface it's a non-issue for you.) > However, if the sdef is present, the commands and Apple Events defined there are ignored and are instead handled by the Tcl/Tk interpreter and its sdef instead. To avoid this conflict, I've tried removing the Tk sdef file, and changing the Apple Event class/ID of my Python event to something else, but these have no effect. If I understand you, Tk implements a 'do script' handler that executes arbitrary Tcl scripts (right...no potential security issues there, then) and you are installing your own 'do script' handler as well. If that's the case, make sure your handler gets installed _after_ Tk has auto-installed its version, otherwise Tk will simply replace yours with its own. I'm not familiar with Tk though, so can't tell you at what point you need to do this. Alternatively, give your handler a different name and Apple event code so that it doesn't conflict with Tk's handler in the first place. HTH has -- Control AppleScriptable applications from Python, Ruby and ObjC: http://appscript.sourceforge.net

2 1