🌐 Mailman 3 May 2009 - Pythonmac-SIG - python.org

Re: [Pythonmac-SIG] Python PyGame GTK SQLAlchemy on Leopard
by Christopher Barker May 17, 2009

May 17, 2009

(make sure to reply to the list, for the archives...) Chris Van Bael wrote: > Yes, I absolutely do want to buil binaries that can run on 10.3.9 and 10.4! > This is very important. Then you want the python.org python. > Do you have the paths for the system python and the installation from > python.org? system python is in: /Library/Frameworks/Python.framework/ python.org goes into: /Library/Frameworks/Python.framework/ > My problem with Mac installers is that they just ask a partition in > which to install the software. > But I want to be sure that they install the packages into the correct > python installation. (the one from python.org) If you are using an installer, then it has to be built for the python you want. Most only target one -- wxPython targets both python.org and Apple's (for Python 2.5) if you use easy_install or setup.py, be sure to run them with the python you want to use. -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 11

Why is Framework build of Python needed
by Brian Granger May 14, 2009

May 14, 2009

Hi, I seem to recall that a Framework build of Python is needed if you want to do anything with the native Mac GUI. Is my understanding correct? If so, is this requirement documented somewhere? Thanks! Brian

6 14

Re: [Pythonmac-SIG] Pythonmac-SIG Digest, Vol 73, Issue 7
by Edward Hartley May 8, 2009

May 8, 2009

On 8 May 2009, at 11:00, pythonmac-sig-request(a)python.org wrote: > Send Pythonmac-SIG mailing list submissions to > pythonmac-sig(a)python.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mail.python.org/mailman/listinfo/pythonmac-sig > or, via email, send a message with subject or body 'help' to > pythonmac-sig-request(a)python.org > > You can reach the person managing the list at > pythonmac-sig-owner(a)python.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Pythonmac-SIG digest..." > Today's Topics: > > 1. Re: Using AHRegisterHelpBook (has) > 2. Leaning PyObjC (Kevin Walzer) > 3. Re: Leaning PyObjC (Bill Janssen) > > From: has <hengist.podd(a)virgin.net> > Date: 7 May 2009 19:13:36 BST > To: pythonmac-sig(a)python.org > Subject: Re: [Pythonmac-SIG] Using AHRegisterHelpBook > > > Ronald Oussoren wrote: > >> Another option is PyObjC, it definitly allows you to integrate with >> the native Cocoa help API's. > > > Out of interest, does PyObjC play nicely with wxPython/Tkinter? > You obviously can't mix GUI toolkits but you can use other PyObjC API's with Tkinter and wxPython. However the GIL needs consideration. Also I found some of the older bridging API's defunct when I tried to use them, particularly quicktime. But it has been a while since I looked at this. > A further option, if it hasn't already been suggested, would be to > call AHRegisterHelpBook directly via ctypes. Just because Python's > Mac modules have all been deprecated and removed doesn't mean that > all of the underlying OS X APIs have done the same. Some have (e.g. > QuickTime, QuickDraw, and anything GUI-related are best avoided) but > others are still fully supported. > > Or, if futzing with ctypes is too much hassle, consider grabbing the > source for the Carbon.AH extension and repackage it as part of the > project. This is what I did with Carbon.AE when developing > appscript, for example. > > HTH > > has > -- > Control AppleScriptable applications from Python, Ruby and ObjC: > http://appscript.sourceforge.net > > > > > > From: Kevin Walzer <kw(a)codebykevin.com> > Date: 7 May 2009 22:53:53 BST > To: pythonmac-sig(a)python.org > Subject: [Pythonmac-SIG] Leaning PyObjC > Reply-To: kw(a)codebykevin.com > > > Hi all, > > What's the current "best practice" for learning PyObjC? I've been > developing in Python/Tkinter for quite some time, and I've learned > enough Objective-C/Cocoa to create a small extension that calls into > some Cocoa methods (it's actually a Tcl extension that I can call, > via Tkinter, to change my app's dock icon). I'm planning to work > through some samples in the latest Hillegass book to get familiar > with the full Cocoa toolchain, i.e. Xcode, IB, etc.) > > I'm finding myself a bit lost, however, in how to download, build, > and play with PyObjC itself. Based on what I've gathered from the > PyObjC site, I can do the following: > > 1. Download version 2.0 from SVN or use easy_install 2.2b. > 2. Build as outlined in the instructions. > 3. Follow the "Creating your first PyObjc application" tutorial, > which requires PyObjC 1.3.1. > > I'm especially curious about the tutorial--is it up to date? I've > read a lot about changes between PyObjC 1.x and 2.x, but it's not > clear to me what those changes are. I do know that the differences > between older Cocoa tutorials (pre-Leopard) and new tutorials are > big enough to make it hard to learn from the old ones, owing > especially to big changes in Interface Builder. > > My strong preference is to keep my Python toolchain reasonably close > to what I'm doing already, i.e. doing my development outside of > Xcode and using py2app for bundling, rather than using Xcode. > > Does this sound like a good approach, or am I missing something > glaringly obvious? What do others who are shipping PyObjC apps do? > > --Kevin > > -- > Kevin Walzer > Code by Kevin > http://www.codebykevin.com > > > > > From: Bill Janssen <janssen(a)parc.com> > Date: 7 May 2009 23:24:21 BST > To: kw(a)codebykevin.com > Cc: pythonmac-sig(a)python.org > Subject: Re: [Pythonmac-SIG] Leaning PyObjC > > > Kevin Walzer <kw(a)codebykevin.com> wrote: > >> My strong preference is to keep my Python toolchain reasonably close >> to what I'm doing already, i.e. doing my development outside of Xcode >> and using py2app for bundling, rather than using Xcode. > > I found crossing this bridge a bit tricky, until I embraced Xcode. > Start a Python-Cocoa project with Xcode. Look at the framework it > builds for you. Go on and edit your app delegate, not necessarily > using > Xcode. Hit the "Build and Run" button in Xcode. See what happens. > Repeat. > > After you've successfully built a couple of Python apps this way, > you'll > be better prepared to get into the whole py2app thing. The major > problem there is that the folks who build and maintain it are > overworked, and have little to no time to update documentation. So > there are lots of out-of-date documentation pages and examples, which > will mislead you mightily unless you have some other grounding to fall > back on to see if they make sense. > > Even then, I have to admit I still don't know how to build a > PreferencePane from scratch. I've got one working, but I had to take > the example, and hack it into shape. > > Oh, and read Will Larson's series: > > http://lethain.com/entry/2008/aug/22/an-epic-introduction-to-pyobjc-and-coc… > > all the way through. > > Bill > > >

1 0

Leaning PyObjC
by Kevin Walzer May 7, 2009

May 7, 2009

Hi all, What's the current "best practice" for learning PyObjC? I've been developing in Python/Tkinter for quite some time, and I've learned enough Objective-C/Cocoa to create a small extension that calls into some Cocoa methods (it's actually a Tcl extension that I can call, via Tkinter, to change my app's dock icon). I'm planning to work through some samples in the latest Hillegass book to get familiar with the full Cocoa toolchain, i.e. Xcode, IB, etc.) I'm finding myself a bit lost, however, in how to download, build, and play with PyObjC itself. Based on what I've gathered from the PyObjC site, I can do the following: 1. Download version 2.0 from SVN or use easy_install 2.2b. 2. Build as outlined in the instructions. 3. Follow the "Creating your first PyObjc application" tutorial, which requires PyObjC 1.3.1. I'm especially curious about the tutorial--is it up to date? I've read a lot about changes between PyObjC 1.x and 2.x, but it's not clear to me what those changes are. I do know that the differences between older Cocoa tutorials (pre-Leopard) and new tutorials are big enough to make it hard to learn from the old ones, owing especially to big changes in Interface Builder. My strong preference is to keep my Python toolchain reasonably close to what I'm doing already, i.e. doing my development outside of Xcode and using py2app for bundling, rather than using Xcode. Does this sound like a good approach, or am I missing something glaringly obvious? What do others who are shipping PyObjC apps do? --Kevin -- Kevin Walzer Code by Kevin http://www.codebykevin.com

2 1

Re: [Pythonmac-SIG] Using AHRegisterHelpBook
by has May 7, 2009

May 7, 2009

Ronald Oussoren wrote: > Another option is PyObjC, it definitly allows you to integrate with > the native Cocoa help API's. Out of interest, does PyObjC play nicely with wxPython/Tkinter? A further option, if it hasn't already been suggested, would be to call AHRegisterHelpBook directly via ctypes. Just because Python's Mac modules have all been deprecated and removed doesn't mean that all of the underlying OS X APIs have done the same. Some have (e.g. QuickTime, QuickDraw, and anything GUI-related are best avoided) but others are still fully supported. Or, if futzing with ctypes is too much hassle, consider grabbing the source for the Carbon.AH extension and repackage it as part of the project. This is what I did with Carbon.AE when developing appscript, for example. HTH has -- Control AppleScriptable applications from Python, Ruby and ObjC: http://appscript.sourceforge.net

1 0

Re: [Pythonmac-SIG] Using AHRegisterHelpBook
by Kevin Walzer May 6, 2009

May 6, 2009

Don McGuire wrote: > > I checked the Python 3.0 docs: all Carbon modules are removed, as you > stated. So to launch the Help viewer nowadays, are you making calls to > Cocoa? Or are you just launching the default web browser and skipping the > Help viewer altogether? > User help is one of the trickiest things to get right, I've found. Both Apple's help viewer and the browser present issues. My own solution is documented here: http://www.codebykevin.com/blosxom.cgi/2009/03/09#user-help Not all parts of this are relevant, since I'm using Tkinter and bumping up against Tk's limited support for displaying HTML, but it will give you an idea of the issues. Since you're using wxPython, can't you just call either the wxHelp API (a bit complicated if I recall correctly) or simply create a simple HTML viewer? I think something like that is in the wxPython demo code. -- Kevin Walzer Code by Kevin http://www.codebykevin.com

3 3

Re: [Pythonmac-SIG] AutoComplete in C++ Editor for Python
by Don McGuire May 4, 2009

May 4, 2009

flamz3d(a)gmail.com wrote: > >> Hello, >> I am embedding python support in my C++ application and was looking at >> adding "Intellisense" or "AutoComplete" support. >> >> I found a way to do it using the "dir" function, but this creates a >> problem. Here's why. Let's say I have the following code in my editor: >> >> import sys >> x = sys >> >> >> Now, I would like to get all attributes of the object called 'x'. I >> can "instrument" the code and add "print dir(x)" at the end, >> temporarily redirect the python output to a string and execute the >> code. >> >> But this is not safe: I do NOT want to execute the code while the user >> is typing! >> >> Is there a way to "compile" the python code and get access to the >> symbol table from that compiled block? >> >> Did anybody ever implement AutoComplete in a editor for Python? >> >> cheers. >> > I implemented autocomplete in my application by using the exec() function to load a namespace. To demonstrate, type the following into the interpreter: txt = "x = 'hello'\nprint x" exec(txt) You will get "hello" to print out. Not good. How about this? txt = "def say_hello():\n\tx = 'hello'\n\tprint x" exec(txt) Nothing happens. Because the print statement is inside the function say_hello(), exec() just loads the function into the globals() namespace. Now type: say_hello() "Hello" prints out. To answer your question, executing code is not necessarily a bad thing. Calling exec() on our function just loaded it into the globals namespace, where you can use introspection on the objects contained therein. None of the statements in the function were executed. My autocomplete system uses exec() on the user scripts to load a namespace. But before that occurs, the system checks for top-level statements that would execute. Assignment statements are usually pretty safe: exec("x = 42") is a pretty safe statement. Top-level calls to functions are bad: exec('launch_missiles()') would in fact launch the missiles. Remove any lines that have top-level function calls. Or you can create your own mini-parser, which I considered but thought it would be too much work.

2 1

Re: [Pythonmac-SIG] Using AHRegisterHelpBook
by Kevin Walzer May 3, 2009

May 3, 2009

Don McGuire wrote: > I checked the Python 3.0 docs: all Carbon modules are removed, as you > stated. So to launch the Help viewer nowadays, are you making calls to > Cocoa? Or are you just launching the default web browser and skipping the > Help viewer altogether? > You can also open the Help Viewer directly with something like this: os.system('open -a Help Viewer.app /path/to/help.html') -- Kevin Walzer Code by Kevin http://www.codebykevin.com

1 0

Using AHRegisterHelpBook
by Don McGuire May 3, 2009

May 3, 2009

Hi: I am attempting to build an application that uses the built-in Apple Help system to display my html help files. I'm getting a Mac OS Error -50, which corresponds to "Error in user parameter list." Here's what I've done thus far: 1. Info.plist has the following entries: <key>CFBundleHelpBookFolder</key> <string>help</string> <key>CFBundleHelpBookName</key> <string>MyAppName Help</string> My html files are in a directory called "help", and my top-level help doc has the Apple metatag "MyAppName Help". 2. In the initializing routine of my app, I have the following lines: from Carbon import AH app = os.path.dirname(os.path.dirname(sys.prefix)) AH.AHRegisterHelpBook(app) #This line causes Mac OS Error -50 The application is a wxpython gui and I'm using py2app to build it. Everything works like a champ, except for the help system. Thank you for your time, Don

2 1

XCode 3 and newly installed Python version
by Eric Shain May 2, 2009

May 2, 2009

I'm new to this list (and lists in general) so please advise if I break any rules. I'm running OS X 10.5.6 and XCode 3. I've been advised to leave system's python installation alone and since I need to install packages, I've installed Python 2.6.2 which went in the ~/Library/Frameworks/Python.framework directory. I've also installed some packages there. While I can run Python scripts without a problem from Idle and Terminal, I'm having problems with XCode. I tried to build a Python - Cocoa application and did a Build and Go. I got the following error in the Console: *Traceback (most recent call last):* * File "main.py", line 10, in <module>* * import objc* *ImportError: No module named objc* *2009-05-02 10:16:34.369 pyTest[1422:10b] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: '/Developer/Eric/pyTest/main.m:44 main() PyRun_SimpleFile failed with file '/Developer/Eric/pyTest/build/Debug/pyTest.app/Contents/Resources/main.py'. See console for errors.'* *2009-05-02 10:16:34.372 pyTest[1422:10b] Stack: (* * 2533839115,* * 2439867963,* * 2533838571,* * 2533838634* I'm assuming that the new version of Python is being used and that pyobjc isn't installed. Is the remedy to install pyobjc into the Python 2.6.2 installation? or are there other dependancies? Will "easy_install pyobjc" in terminal install the correct version (in the correct python)? Lastly, while I've a bit of experience in Python, I have little in XCode and Objective-C. I've worked through some tutorials, but I've not found a decent yet basic tutorial for doing a Python Cocoa application in XCode 3. Apple's tutorial is for XCode 2 and enough seems to have changed that I have trouble following it. All I really want to do now is create a simple UI, and receive a string from a text field and send result text to another text field or label. Thanks, Eric

1 0