Mailman 3 July 2002 - Pythonmac-SIG

Re: [Pythonmac-SIG] ObjC stuff
by Jack Jansen March 20, 2003

March 20, 2003

Recently, Steve Spicklemire <steve(a)spvi.com> said: > So it's in CVS somewhere? I'll do a check-out and see if I can find it. I don't know, Steven Majewski may know (I think he is the one who looked at it). If it isn't in the repository it probably should be, preferrably in the Modules directory (because it is useful for non-Mac users) but if there's objections against that we'll put it in the Mac/Modules dir. > I just ordered CW-6 today so I might be able to pitch in a bit. While very useful for other things (like MacPython development) you don't need it for OSX unix-Python development: this is all make and gcc-based (and you have those on your OSX developer disc). -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.oratrix.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm

5 4

Python and Jaguar
by Dinu Gherman Aug. 16, 2002

Aug. 16, 2002

Hi, I heard that Jaguar (OS X 10.2) finally comes with Python 2.2 bundled, but I don't have any developer prerelease of it, so I can only guess it's a Unix compile of 2.2.1. Has anybody already been riding on it to give more details? Dinu

4 3

Python, Jython, Cocoa and Charleroi
by Ronald Oussoren Aug. 16, 2002

Aug. 16, 2002

Dinu Gherman wrote: > is anybody here interested in Python and Cocoa going to Charleroi? I'm definitely interested in Python and Cocoa, but not going to Chareroi. How are Jython and Cocoa working out? We (Frans Schippers, Jack Jansen and myself) are working on calling Cocoa from CPython, using the pyobjc module as a starting point. Loading NIB files works just fine, connecting the NIB to python will require some work. Ronald

4 4

Re: [Pythonmac-SIG] more on MacPython/OSX/shared lib
by Jack Jansen Aug. 14, 2002

Aug. 14, 2002

Recently, Paul Miller <paul(a)fxtech.com> said: > >My next step is to remove all my Python code and see if I get the error > >without linking against Python. > > Back to square 1 for me. I removed the Python lib and all my Python code > and I have the same problem. It must be something in global initialization > in my own code. For yucks I disabled the __initialize and __terminate entry > points in the linker options and I ended up with an assert in my code > (which was expecting the static initializations to happen). Hmm, my guess would be either a bug in CodeWarrior, or (probably more likely) you using the wrong runtime library. Especially if you use C++ you have to be careful with which runtime library you use where, because the zero-overhead exception handling will fail otherwise. And you shouldn't use Python as an example, because it doesn't follow the rules (but gets away with it being a C program). You might want to spell out the MW Targeting MacOS manual. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.cwi.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm

4 5

The signal module
by Yair Benita Aug. 5, 2002

Aug. 5, 2002

Hi all, I am trying to compile biopython for the mac but I get an import error for the signal module (no module error). Can anybody tell me what is the signal module and how do I get it? I use python 2.2.1 on macos x. Yair -- Yair Benita Pharmaceutical Proteomics Utrecht University

6 8

PythonLauncher - first stab available
by Jack Jansen Aug. 1, 2002

Aug. 1, 2002

Folks, the first stab at the PythonLauncher has just been checked in to the repository. It's in Mac/OSX/PythonLauncher. I would like people to check it out and comment on the functionality, interface, etc. Here's the checkin message: ------------------------------------- First stab at the launcher application. This will be run when the user doubleclicks a .py, .pyw or .pyc file. It runs the file by invoking the relevant interpreter (either the command line Python in a terminal window or a Python.app for GUI-based scripts). Interpreter to use and the options to pass are settable through preferences. If PythonLauncher wasn't running it does its thing for one script and exits. If it was manually started before a dialog is presented where the user can set the options to use, etc. To be done: - option-drag/doubleclick should always open the interactive dialog - Terminal-window isn't done yet - Should be reimplemented in Python, but pyobjc isn't part of the core. - Various menu entries should be disabled. ----------------------------------- I'd be especially grateful for help on the first, second and third "to be done" items, as I haven't a clue how to get these working. Also, this is my first Cocoa program (aside from doing the two tutorials), so I explicitly request comments on the organization of the classes, etc. -- - Jack Jansen <Jack.Jansen(a)oratrix.com> http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman -

4 8

Build of pyobjc and pyobjc-nib failures
by Zachery Bir July 31, 2002

July 31, 2002

Hey, all. I'm using a Python2.3 built from CVS, and I get the following failure when trying to build PyObjC: cc -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -Wno-long-double -no-cpp-precomp -I/opt/include/python2.3 -c OC_PythonBundle.m -o build/temp.darwin-5.5-Power Macintosh-2.3/OC_PythonBundle.o -g In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CFBase.h:33, from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation. h:5, from /System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:7, from ObjC.h:31, from OC_PythonBundle.m:17: /System/Library/Frameworks/CoreServices.framework/Headers/../Frameworks/CarbonCore. framework/Headers/MacTypes.h:291: warning: function declaration isn't a prototype /System/Library/Frameworks/CoreServices.framework/Headers/../Frameworks/CarbonCore. framework/Headers/MacTypes.h:292: warning: function declaration isn't a prototype OC_PythonBundle.m: In function `+[OC_PythonBundle mainBundle]': OC_PythonBundle.m:75: conflicting types for `getcwd' /usr/include/unistd.h:103: previous declaration of `getcwd' OC_PythonBundle.m:75: warning: extern declaration of `getcwd' doesn't match global one Traceback (most recent call last): File "setup.py", line 26, in ? package_dir = { '':'Examples' } File "/opt/lib/python2.3/distutils/core.py", line 159, in setup raise SystemExit, "error: " + str(msg) SystemExit: error: command 'cc' failed with exit status 1 Running 10.1.5 with the April Dev Tools (but not gcc 3.0) I've installed the 2.3 into /opt Zac

2 3

More NIB examples
by Ronald Oussoren July 30, 2002

July 30, 2002

I've some more examples of building NIB-based Cocoa applications in Python, and a heavily modified version of pyobjc to go with those. The 'CurrencyConvertor' applet that Jack posted a while back is now much shorter, and I've added a document based application (the Todo example from Learning Cocoa). The most important change to the pyobjc module is that you can now subclass Objective-C classes in python. These subclasses are both Python classes and Objective-C classes. This is very usefull when your building document based applications. The archive can be downloaded here: http://www.cistron.nl/~oussoren/pyobjc The code is work-in-progress, but usable. I'm developing using a Python 2.3 (from CVS), this is probably required to use the code. Check the readme in the archive for building and usage instructions. The layout of the archive is different from the original pyobjc, but that will change again when we merge the code into the pyobjc repository. Ronald

2 1

macostools copy function broken in MachoPython build?
by Kevin Altis July 29, 2002

July 29, 2002

A friend of mine wanted to start using Python and as his first program he wanted to be able to do a recursive backup of a directory of files to another volume. Since he's on a Mac that means using the copy or copytree functions in order to get the data and resource fork and Finder info. http://www.python.org/doc/current/mac/module-macostools.html However, he's trying to do this on Mac OS X, so I had him go get MachoPython-2.2.1-4.dmg from the wxPython distribution: http://sourceforge.net/project/showfiles.php?group_id=10718&release_id=56880 When we tried using copy function a file not found error was thrown for the destination file. If you go ahead and create a dummy file, the copy still seems to fail, though no errors are thrown. The actual message is: MacOS.Error: (-43, 'File not found') My friend installed MacPython on OS 9 and macostools.copy seemed to work there, though of course the path is done with ':' instead of '/'. Any ideas what we're doing wrong or is this a MachoPython macostools bug? Perhaps this is just a problem with how Robin did the 2.2.1-4 build? I've included some playing around I did in the shell under Mac OS X that shows the error. Sorry about the email line wrapping. ka --- Kevin Altis altis(a)semi-retired.com --- >>> import os >>> import macostools >>> os.getcwd() '/Users/altis/python/PythonCardPrototype/samples/minimal' >>> filename = 'readme.txt' >>> path = os.path.join(os.getcwd(), filename) >>> path '/Users/altis/python/PythonCardPrototype/samples/minimal/readme.txt' >>> os.path.exists(path) 1 >>> macostools.copy(path, path + '2') Traceback (most recent call last): File "<input>", line 1, in ? File "/Library/Frameworks/Python.framework/Versions/2.2/Mac/Lib/macostools.py", line 88, in copy dstfss = macfs.FSSpec(dst) MacOS.Error: (-43, 'File not found') >>> macostools.macfs <module 'macfs' from '/Library/Frameworks/Python.framework/Versions/2.2/lib/python2.2/lib-dynload /macfs.so'> >>> macostools.macfs.FSSpec(path) FSSpec((-100, 141127, 'readme.txt')) >>> macostools.macfs.FSSpec(path + '1') Traceback (most recent call last): File "<input>", line 1, in ? MacOS.Error: (-43, 'File not found')

2 1

Re: [Pythonmac-SIG] Need to hand-compile expat on OS X? (Fwd: [XML-SIG] Strange install issue)
by Michael Hudson July 29, 2002

July 29, 2002

Dinu Gherman <gherman(a)darwin.in-berlin.de> writes: > Jack Jansen: > > > This is fixed in 2.3a0: Python now simply includes the relevant > > parts of expat. > > But when? If it's still a configure/compile-time option when > building Python itself, it's hard to ship an expat executable > or its source without writing a long install readme and not > scare people of from compiling the Python interpreter. This > is, of course, true only for "typical" Mac users who probably > never run a compiler. Huh? It all gets built by setup.py like everything else. > If it was a wrapper module in the standard library or one I > could put in site-packages, great, but I think this is not > the case. Wrong! Cheers, M. -- Or here's an even simpler indicator of how much C++ sucks: Print out the C++ Public Review Document. Have someone hold it about three feet above your head and then drop it. Thus you will be enlightened. -- Thant Tessman

1 0