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

os 9.2
by Suresh Krishna May 21, 2010

May 21, 2010

hi, i have to work with mac OS 9.2 for legacy reasons...is there a compiled version of python for this os ? i need to get input about variable values from the user and then print out some text files that make use of this input. a gui would be nice, but keyboard based input would be ok too... thanks much, suresh ps. if there isn't a version of python that will work, perhaps you could suggest some other scripting language for 0S 9.2 ?

3 3

32/64 bit intel universal build
by Robin Oct. 29, 2009

Oct. 29, 2009

Hi, I've been struggling with 32 vs 64 bit python on snow leopard. I built an intel universal with: ./build-installer.py --sdk-path=/Developer/SDKs/MacOSX10.6.sdk/ --dep-target=10.6 --universal-archs=intel It looks like it built correctly: robin-mbp:bin robince$ file ./python2.6 ./python2.6: Mach-O universal binary with 2 architectures ./python2.6 (for architecture i386): Mach-O executable i386 ./python2.6 (for architecture x86_64): Mach-O 64-bit executable x86_64 But I am unable to select 32 vs 64 bit with arch: robin-mbp:bin robince$ arch -x86_64 ./python2.6 -c "import sys; print sys.maxint" 9223372036854775807 robin-mbp:bin robince$ arch -i386 ./python2.6 -c "import sys; print sys.maxint" 9223372036854775807 which does work with the system python: robin-mbp:~ robince$ arch -i386 /usr/bin/python2.6 -c "import sys; print sys.maxint" 2147483647 robin-mbp:~ robince$ arch -x86_64 /usr/bin/python2.6 -c "import sys; print sys.maxint" 9223372036854775807 What am I missing? Cheers Robin

3 5

Python XMP Toolkit bundling
by Jim Skibbie Oct. 28, 2009

Oct. 28, 2009

I¹m a Python newbie... I am working on a project where I need to read and write XMP metadata to PDF files. I found the Python XMP Toolkit at http://code.google.com/p/python-xmp-toolkit/ and was able to download, compile and install all the pieces (boost, Exempi and Python XMP Toolkit) and write a script that can actually do what I want. Now, my question is, how can I distribute this kind of solution to other user¹s workstations? I don¹t want to have to repeat this whole process to create the necessary environment on each user machine to be able to run this python script. Is there a way that I can bundle all the necessary dependencies (boost, Exempi, Python XMP Toolkit) together so that to the user it is just a single application? And if so, what about the compiled versions on Intel vs. G5 machines? Below is the whole script. It basically takes a file path and two values as arguments and writes the two values into the XMP stream of the file. It seems pretty simple, but the distribution part seems daunting to me. Thanks. Jim import sys from libxmp import * path_to_file = sys.argv[1] vertical_shrink = sys.argv[2] horizontal_shrink = sys.argv[3] # Read file xmpfile = XMPFiles( file_path=path_to_file, open_forupdate=files.XMP_OPEN_FORUPDATE) # Get XMP from file. xmp = xmpfile.get_xmp() # Change the XMP property xmp.set_property( "http://ns.somenamespace.com/1.0/", 'vshrink', vertical_shrink ) xmp.set_property( "http://ns.somenamespace.com/1.0/", 'hshrink', horizontal_shrink ) # Check if XMP document can be written to file and write it. if xmpfile.can_put_xmp(xmp): xmpfile.put_xmp(xmp) xmpfile.close_file()

3 7

32/64 bit intel universal build
by Robin Oct. 28, 2009

Oct. 28, 2009

On Mon, Oct 26, 2009 at 3:17 PM, David Warde-Farley <dwf(a)cs.toronto.edu>wrote: > Check if there's a > /Library/Frameworks/Python.framework/Versions/2.6/bin/python-64 (or > /Library/Frameworks/Python.framework/Versions/2.6/bin/python2.6-64). IIRC > that's how the builds produced from source work; separate executables for 32 > and 64 bit mode. > Hi, Thanks... yes thats what I was expecting initially, but there is nothing there: jm-g26b101:bin robince$ ls /Library/Frameworks/Python.framework/Versions/2.6/bin/ 2to3 pydoc python-config pythonw smtpd2.6.py idle pydoc2.6 python2.6 pythonw2.6 idle2.6 python python2.6-config smtpd.py >From reading the documentation I think they may only be created with the universal-archs=all target (which includes ppc and ppc64 which I dont need). In any case - 'file' shows that it is a universal binary, just the 'arch' method of selecting architecture doesn't appear to work: jm-g26b101:bin robince$ file /Library/Frameworks/Python.framework/Versions/2.6/bin/python2.6 /Library/Frameworks/Python.framework/Versions/2.6/bin/python2.6: Mach-O universal binary with 2 architectures /Library/Frameworks/Python.framework/Versions/2.6/bin/python2.6 (for architecture i386): Mach-O executable i386 /Library/Frameworks/Python.framework/Versions/2.6/bin/python2.6 (for architecture x86_64): Mach-O 64-bit executable x86_64 Perhaps I will try the 'all' variant next. Cheers Robin

2 1

wxpython frames aren't raised on top
by Gabriel Rossetti Oct. 26, 2009

Oct. 26, 2009

Hello everyone, on Mac, my frames aren't raised on top of the window stack even when I do Show() & Raise(). If I set the style to wx.STAY_ON_TOP, but then if I get a msg dialog it freezes and I get the wheel of death, I suspect it is because they both want to be on top. This doesn't pos any problems on linux and windows, only on mac. Does anyone have an idea why this is happening and how to get it to raise on top without freezing everything? Thanks, Gabriel

2 1

Re: [Pythonmac-SIG] problems with Distributed Objects and PyObjC
by Hamish Sanderson Oct. 25, 2009

Oct. 25, 2009

Ronald Oussoren wrote: > On Tuesday, October 20, 2009, at 01:20PM, "Hamish Sanderson" <hsanderson(a)s-brandingsolutions.com > > wrote: >> Trying to use Distributed Objects to communicate between PyObjC-based >> processes on 10.5 and/or 10.6, but encountering various problems when >> passing Python values, as illustrated below. > > Full DO support requires defining new protocols, which won't work on > 64-bit builds. Even the limited DO support you need may or may not > work because it is a low-level library that might interfere with > PyObjC. I don't have unittests or sample code for this and hence > cannot guarantee that this will work. Hmm. Sounds like DO isn't a good way to go in Python (and I've already discounted Apple events), so I suspect I'll have to look elsewhere for a long-term solution. > I will look into your issues though, but not today. OK, it isn't urgent. I'm not passing anything complex so can work around the problem by ensuring all Python objects are converted to Cocoa instances before handing them off to DO. > An alternative to DO is to use a native Python library (Twisted, XML- > RPC, ...) combined with Bonjour. Will investigate these options. Irmen de Jong wrote: >> Anyone any thoughts? (Including suggestions for alternative LAN- >> capable IPC options.) > > Both ends are Python? Python + PyObjC. > If they are, maybe you should try Pyro (http://pyro.sourceforge.net). Reading the docs. A few questions, if you don't mind: - Will Pyro play well with PyObjC objects? - How does it compare to, say, DO+Bonjour (which is the only object- oriented IPC system I'm vaguely familiar with)? - And how well will it cope if some components stall or crash? (One of the reasons for moving to a more distributed design is that some parts of the system are inherently unreliable, so the rest of the system will need to survive if/when those processes go down, and be able to reconnect once they are restarted.) Thanks, Hamish -- Hamish Sanderson Production Workflow Developer Sun Branding Solutions Ltd Tel: +44(0)1274 200 700 www.s-brandingsolutions.com

3 2

Unwanted PPC build in setuptools
by Chris Fonnesbeck Oct. 22, 2009

Oct. 22, 2009

Is there any way of convincing setuptools to *not* build for PPC? For some reason, it tries to build a universal binary by default: g++ -arch i386 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk ...etc Which results in errors: ld warning: in /Developer/SDKs/MacOSX10.4u.sdk/Library/Frameworks/Python.framework/Versions/4.3.0/lib/libz.dylib, file is not of required architecture ld: in /Developer/SDKs/MacOSX10.4u.sdk/Library/Frameworks/Python.framework/Versions/4.3.0/lib/libz.1.dylib, file is not of required architecture for architecture ppc I have no interest in building universals -- how can I switch this off? I already tried putting "-arch i386" in my LDFLAGS, but to no avail. Thanks, cf

4 9

py2app/64-bit/Mach-O Headers
by Kevin Walzer Oct. 22, 2009

Oct. 22, 2009

I'm trying to bundle up a Python application that uses four-way universal builds of Python and Tk (64-bit/32-bit for PPC and x86). py2app chokes when trying to link the Tk frameworks in the app bundle: linking /Users/kevin/Programming/phynchronicity/dist/Phynchronicity.app/Contents/Frameworks/Tk.framework/Versions/Current -> 8.5 WARNING: Mach-O header may be too large to relocate WARNING: Mach-O header may be too large to relocate WARNING: Mach-O header may be too large to relocate WARNING: Mach-O header may be too large to relocate Traceback (most recent call last): File "/Library/Frameworks/Python64.framework/Versions/2.6/lib/python2.6/site-packages/py2app-0.4.2-py2.6.egg/py2app/build_app.py", line 589, in _run self.run_normal() File "/Library/Frameworks/Python64.framework/Versions/2.6/lib/python2.6/site-packages/py2app-0.4.2-py2.6.egg/py2app/build_app.py", line 660, in run_normal self.create_binaries(py_files, pkgdirs, extensions, loader_files) File "/Library/Frameworks/Python64.framework/Versions/2.6/lib/python2.6/site-packages/py2app-0.4.2-py2.6.egg/py2app/build_app.py", line 777, in create_binaries <snip> I ran across this error in the mailing list archives and saw that it may pertain to the "-headerpad_max_install_names" LD flag. I added this flag to LDFLAGS in my ~/.profile and rebuilt Tcl and Tk with the link flag, but py2app still returns this error. Not sure what to do here. I think py2app should be able to handle building a Tkinter application as 64-bit without these errors; Tkinter isn't some weird edge case. I've installed the latest dev versions of py2app and macholib. I'm also running 10.5.8. Thanks, Kevin -- Kevin Walzer Code by Kevin http://www.codebykevin.com

2 11

problems with Distributed Objects and PyObjC
by Hamish Sanderson Oct. 20, 2009

Oct. 20, 2009

Hi all, Trying to use Distributed Objects to communicate between PyObjC-based processes on 10.5 and/or 10.6, but encountering various problems when passing Python values, as illustrated below. The production code currently only passes Python strings as arguments so I can work around these issues for now by ensuring I always wrap them as NSStrings, but it's going to create headaches if I start to use DO for more advanced IPC. Anyone any thoughts? (Including suggestions for alternative LAN- capable IPC options.) Thanks, Hamish ------- doserver.py ------- from Cocoa import * class Server(NSObject): def test(self, arg): print 'received:', arg return NSString.stringWithString_(u"ok") receiveport = NSSocketPort.alloc().initWithTCPPort_(8080) connection = NSConnection.connectionWithReceivePort_sendPort_(receiveport, None) server = Server.alloc().init() connection.setRootObject_(server) NSRunLoop.mainRunLoop().run() ------- doclient.py ------- from Cocoa import * sendport = NSSocketPort.alloc().initRemoteWithTCPPort_host_(8080, u"localhost") connection = NSConnection.connectionWithReceivePort_sendPort_(None, sendport) proxy = connection.rootProxy() try: print "reply", proxy.test(43) except Exception, e: print e # doclient.py fails: # ValueError: NSInvalidArgumentException - *** -encodeInt:forKey: only defined for abstract class. # Define -[NSConcretePortCoder encodeInt:forKey:]! print "reply", proxy.test(NSNumber.numberWithInt_(43)) # OK try: print "reply", proxy.test([]) # OK on 10.6 except Exception, e: print e # doclient.py fails on 10.5 # ValueError: NSInvalidArgumentException - PyObjC: Encoding python objects of type list is not supported print "reply", proxy.test(True) # OK print "reply", proxy.test(NSString.stringWithString_(u'hello')) # OK print "reply", proxy.test(u'hello') # OK on 10.5 # doserver.py fails on 10.6: # ValueError: NSInvalidArgumentException - -[OC_PythonUnicode initWithBytes:length:encoding:]: # unrecognized selector sent to instance 0x100261a80 -- Hamish Sanderson Production Workflow Developer Sun Branding Solutions Ltd Tel: +44(0)1274 200 700 www.s-brandingsolutions.com

2 1

Re: [Pythonmac-SIG] problems with Distributed Objects and PyObjC
by Ronald Oussoren Oct. 20, 2009

Oct. 20, 2009

On Tuesday, October 20, 2009, at 01:20PM, "Hamish Sanderson" <hsanderson(a)s-brandingsolutions.com> wrote: >Hi all, > >Trying to use Distributed Objects to communicate between PyObjC-based >processes on 10.5 and/or 10.6, but encountering various problems when >passing Python values, as illustrated below. The production code >currently only passes Python strings as arguments so I can work around >these issues for now by ensuring I always wrap them as NSStrings, but >it's going to create headaches if I start to use DO for more advanced >IPC. > >Anyone any thoughts? (Including suggestions for alternative LAN- >capable IPC options.) Full DO support requires defining new protocols, which won't work on 64-bit builds. Even the limited DO support you need may or may not work because it is a low-level library that might interfere with PyObjC. I don't have unittests or sample code for this and hence cannot guarantee that this will work. I will look into your issues though, but not today. An alternative to DO is to use a native Python library (Twisted, XML-RPC, ...) combined with Bonjour. Ronald > >Thanks, > >Hamish > > >------- doserver.py ------- > >from Cocoa import * > >class Server(NSObject): > def test(self, arg): > print 'received:', arg > return NSString.stringWithString_(u"ok") > >receiveport = NSSocketPort.alloc().initWithTCPPort_(8080) >connection = >NSConnection.connectionWithReceivePort_sendPort_(receiveport, None) >server = Server.alloc().init() >connection.setRootObject_(server) >NSRunLoop.mainRunLoop().run() > > > >------- doclient.py ------- > >from Cocoa import * > >sendport = NSSocketPort.alloc().initRemoteWithTCPPort_host_(8080, >u"localhost") >connection = NSConnection.connectionWithReceivePort_sendPort_(None, >sendport) >proxy = connection.rootProxy() > >try: > print "reply", proxy.test(43) >except Exception, e: > print e ># doclient.py fails: ># ValueError: NSInvalidArgumentException - *** -encodeInt:forKey: only >defined for abstract class. ># Define -[NSConcretePortCoder encodeInt:forKey:]! > >print "reply", proxy.test(NSNumber.numberWithInt_(43)) # OK > >try: > print "reply", proxy.test([]) # OK on 10.6 >except Exception, e: > print e ># doclient.py fails on 10.5 ># ValueError: NSInvalidArgumentException - PyObjC: Encoding python >objects of type list is not supported > >print "reply", proxy.test(True) # OK > >print "reply", proxy.test(NSString.stringWithString_(u'hello')) # OK > >print "reply", proxy.test(u'hello') # OK on 10.5 ># doserver.py fails on 10.6: ># ValueError: NSInvalidArgumentException - -[OC_PythonUnicode >initWithBytes:length:encoding:]: ># unrecognized selector sent to instance 0x100261a80 > > > >-- > >Hamish Sanderson >Production Workflow Developer >Sun Branding Solutions Ltd >Tel: +44(0)1274 200 700 >www.s-brandingsolutions.com > > > > >_______________________________________________ >Pythonmac-SIG maillist - Pythonmac-SIG(a)python.org >http://mail.python.org/mailman/listinfo/pythonmac-sig > >

1 0