🌐 Mailman 3 June 2007 - Pythonmac-SIG - python.org

QuickTime: BeginFullScreen
by Edward Hartley June 12, 2007

June 12, 2007

Hi I've been examining the functions exposed in the PythonMac Qt and QuickTime libraries and it seems that whilst the EndFullScreen call and the appropriate flags are exposed as can be seen from this snip from ipython help(Qt) EndFullScreen(...) (Ptr fullState, long flags) -> None however the corresponding BeginFullScreen is not available. My question is what is needed to make BeginFullScreen available to the MacPython API. I am willing to commit time to doing the development and have comnsiderable experience of using SWIG under Linux. I am not familiar with the build mechanism for MacPython but I am willing to learn. I had initially thought that this might depend on having QuickTime Pro but further investigation shows that BeginFullScreen is an integral part of the framework and available in from Movies.h which I'm assuming is the basis for the MacPython Quicktime wrapper The declaration is in /System/Frameworks/QuickTime.framework/Headers as follows: /* * BeginFullScreen() * * Availability: * Mac OS X: in version 10.0 and later in QuickTime.framework * CarbonLib: in CarbonLib 1.0 and later * Non-Carbon CFM: in QuickTimeLib 2.5 and later * Windows: in qtmlClient.lib 3.0 and later */ extern OSErr BeginFullScreen( Ptr * restoreState, GDHandle whichGD, short * desiredWidth, short * desiredHeight, WindowRef * newWindow, RGBColor * eraseColor, long flags) AVAILABLE_MAC_OS_X_VERSION_10_0_AND_LATER; Interestingly the Java Quicktime quicktime bridge has BeginFullScreen available. http://developer.apple.com/documentation/Java/Reference/1.4.1/Java141API_QT… Also there is an example of the use of the C API available in the developer documentation: http://developer.apple.com/samplecode/qtfullscreen/listing1.html So I'm assuming that any restrictions on exposing BeginFullScreen that may have applied in the past are no longer in force. TIA Ed Hartley

2 1

Re: [Pythonmac-SIG] findertools.launch reports "no eligible process"
by has June 11, 2007

June 11, 2007

Ronald Oussoren wrote: >> i was wondering if anyone else has seen this behavior with the >> findertools.launch() function. the docs indicate that when given a >> pathname, launch(path) will launch a Finder window with that path. >> but >> when i try to launch any valid path i get this error: > > Please file a bug at http://sourceforge.net/projects/python, this > seems to be yet another byteorder bug in the OSA support in the > core python distribution. You might add a note that since findertools uses aetools which is [over]due for deprecation, findertools should be deprecated as well. Anyway, simplest solution here is: import subprocess subprocess.call(['open', '/Users/drew/Documents']) Or you can do it with appscript if you prefer: from appscript import * from mactypes import Alias path = '/Users/drew/Documents' app('Finder').items[Alias(path)].open() has -- http://appscript.sourceforge.net http://rb-appscript.rubyforge.org http://appscript.sourceforge.net/objc-appscript.html

5 9

findertools.launch reports "no eligible process"
by Drew Houston June 8, 2007

June 8, 2007

hi there, i was wondering if anyone else has seen this behavior with the findertools.launch() function. the docs indicate that when given a pathname, launch(path) will launch a Finder window with that path. but when i try to launch any valid path i get this error: >>> os.path.exists("/Users/drew/Documents") True >>> findertools.launch("/Users/drew/Documents") Traceback (most recent call last): File "<stdin>", line 1, in ? File "/Library/Frameworks/Python.framework/Versions/2.4//lib/python2.4/plat-mac/findertools.py", line 45, in launch return finder.open(fss) File "/Library/Frameworks/Python.framework/Versions/2.4//lib/python2.4/plat-mac/lib-scriptpackages/Finder/Standard_Suite.py", line 248, in open _arguments, _attributes) File "/Library/Frameworks/Python.framework/Versions/2.4//lib/python2.4/plat-mac/aetools.py", line 226, in send return self.sendevent(self.newevent(code, subcode, parameters, attributes)) File "/Library/Frameworks/Python.framework/Versions/2.4//lib/python2.4/plat-mac/aetools.py", line 220, in sendevent self.send_timeout) MacOS.Error: (-600, 'no eligible process with specified descriptor') >>> i get the same error across reboots, on real hardware (x86) or a VM; from a Terminal window or IDLE; with directories or files or applications, etc. -- all this -600 error; (if i specify an invalid path i do get a file not found error.) i mostly come from windows land (and basically looking for a stand-in for ShellExecute), so if i'm doing something horribly wrong please let me know :) i'm using OS X 10.4.9 and MacPython 2.4.4 and can't think of anything unusual that might be causing it. (killing the finder and restarting it also does not help; the process is certainly running.) thanks! drew

2 1

Re: [Pythonmac-SIG] newbie: threads in PyObjC
by Ian Baird June 5, 2007

June 5, 2007

Tom, One problem you have here is that you need to create an instance of the Threaded class to point to as your selector's target object. This error is causing the message: 2007-06-04 20:53:11.415 PyThread[555] *** +[Threaded newThread:]: selector not recognized Plus, you have an unneeded NSAutoreleasePool instance, so I'd rewrite the code as follows: --- def go_(self, sender): print 'go_' self.myNewThreadedInst = Threaded.alloc().init() NSThread.detachNewThreadSelector_toTarget_withObject_( 'newThread:', myNewThreadedInst, None) --- Try that out, it should work. Ian On 6/4/07, Tom Elliott <telliott99(a)mac.com> wrote: > I'm using the PyObjC bridge. I have a computation that will be triggered by > a user. It takes about 2 minutes depending on the database we're using. > I'd like the user to be able to kill it if he decides it's taking too long. > > It seems like threading should be the solution. My simple demo based on > what I read in NSThread related docs is as follows. (I've put the > NSAutoreleasePool call in twice here, but tried it in either place, > separately). > > from Foundation import * > from AppKit import * > import objc, time > > from PyObjCTools import NibClassBuilder > > class PyThreadAppDelegate(NibClassBuilder.AutoBaseClass): > def init(self): > self = super(PyThreadAppDelegate, self).init() > return self > > > def go_(self, sender): > print 'go_' > pool = NSAutoreleasePool.alloc().init() > > NSThread.detachNewThreadSelector_toTarget_withObject_( > 'newThread:', Threaded, None) > del pool > > > def kill_(self, sender): > pass > > > class Threaded(NSObject): > > @objc.signature('v:@') > def newThread_(obj): > print 'Threaded' > pool = NSAutoreleasePool.alloc().init() > for i in range(5): > time.sleep(1) > print i > del pool > > This dies with: > > ===== Monday, June 4, 2007 8:53:09 PM US/Eastern ===== > go_ > 2007-06-04 20:53:11.414 PyThread[555] *** _NSAutoreleaseNoPool(): Object > 0x1419cc0 of class NSCFString autoreleased with no pool in place - just > leaking > 2007-06-04 20:53:11.415 PyThread[555] *** +[Threaded newThread:]: selector > not recognized > 2007-06-04 20:53:11.415 PyThread[555] *** _NSAutoreleaseNoPool(): Object > 0x146cb10 of class NSCFString autoreleased with no pool in place - just > leaking > 2007-06-04 20:53:11.415 PyThread[555] *** _NSAutoreleaseNoPool(): Object > 0x146c9a0 of class NSCFString autoreleased with no pool in place - just > leaking > 2007-06-04 20:53:11.415 PyThread[555] *** _NSAutoreleaseNoPool(): Object > 0x146c980 of class NSException autoreleased with no pool in place - just > leaking > 2007-06-04 20:53:11.415 PyThread[555] An uncaught exception was raised > 2007-06-04 20:53:11.415 PyThread[555] *** +[Threaded newThread:]: selector > not recognized > 2007-06-04 20:53:11.415 PyThread[555] *** Uncaught exception: > <NSInvalidArgumentException> *** +[Threaded newThread:]: selector not > recognized > Jun 4 20:53:12 joan-olsons-computer-2 crashdump[556]: PyThread crashed > Jun 4 20:53:12 joan-olsons-computer-2 crashdump[556]: crash report written > to: > /Users/jolson/Library/Logs/CrashReporter/PyThread.crash.log > > In addition, I don't know how to talk to the thread to kill it. > > Thanks for any help, > > Tom Elliott > _______________________________________________ > Pythonmac-SIG maillist - Pythonmac-SIG(a)python.org > http://mail.python.org/mailman/listinfo/pythonmac-sig > >

2 1

mxtextools, py2app, and intel vs. PPC
by Ian York June 5, 2007

June 5, 2007

(This is an updated version of my question from yesterday, hopefully with more, and more useful, information) I've been packaging a set of scripts using py2app, and until now the app that results has run without issues on MacOS10.4, either intel or ppc. The latest version made by py2app, however, only runs on intel (on which I made the py2app package). The problem seems to be with eGenix mx base package (which is needed for BioPython; specifically mxtexttools, TextTools). The package when run on PPC gets the error "No module named TextTools", although TextTools is included and works fine on intel. If I include TextTools specifically in the Resources folder within the package, instead I get an error "ImportError: Inappropriate file type for dynamic loading". Again, these errors only appeared on the ppc platform, not on intel. I worked around the problem by including (in the Resources folder) the TextTools folder from a PPC machine, and the package then runs on both machines. This isn't a great solution, because I don't always have easy access to a PPC machine running MacOS10.4. I presume that the problem is that the mx package I have on the Intel machine isn't actually a Universal binary, and so the PPC has no access to that module. I've tried installing the mx package from source, or from the prebuilt binary, without fixing the problem. Anyone know if my guess is right, that the mx package isn't coming in as a universal? And if so, if there's a way to force it to be universal, or some other simple fix for my problem? Thanks, Ian -- Ian York (iayork(a)panix.com) <http://www.iayork.com/> "-but as he was a York, I am rather inclined to suppose him a very respectable Man." -Jane Austen, The History of England

1 0

newbie: threads in PyObjC
by Tom Elliott June 5, 2007

June 5, 2007

I'm using the PyObjC bridge. I have a computation that will be triggered by a user. It takes about 2 minutes depending on the database we're using. I'd like the user to be able to kill it if he decides it's taking too long. It seems like threading should be the solution. My simple demo based on what I read in NSThread related docs is as follows. (I've put the NSAutoreleasePool call in twice here, but tried it in either place, separately). from Foundation import * from AppKit import * import objc, time from PyObjCTools import NibClassBuilder class PyThreadAppDelegate(NibClassBuilder.AutoBaseClass): def init(self): self = super(PyThreadAppDelegate, self).init() return self def go_(self, sender): print 'go_' pool = NSAutoreleasePool.alloc().init() NSThread.detachNewThreadSelector_toTarget_withObject_( 'newThread:', Threaded, None) del pool def kill_(self, sender): pass class Threaded(NSObject): @objc.signature('v:@') def newThread_(obj): print 'Threaded' pool = NSAutoreleasePool.alloc().init() for i in range(5): time.sleep(1) print i del pool This dies with: ===== Monday, June 4, 2007 8:53:09 PM US/Eastern ===== go_ 2007-06-04 20:53:11.414 PyThread[555] *** _NSAutoreleaseNoPool(): Object 0x1419cc0 of class NSCFString autoreleased with no pool in place - just leaking 2007-06-04 20:53:11.415 PyThread[555] *** +[Threaded newThread:]: selector not recognized 2007-06-04 20:53:11.415 PyThread[555] *** _NSAutoreleaseNoPool(): Object 0x146cb10 of class NSCFString autoreleased with no pool in place - just leaking 2007-06-04 20:53:11.415 PyThread[555] *** _NSAutoreleaseNoPool(): Object 0x146c9a0 of class NSCFString autoreleased with no pool in place - just leaking 2007-06-04 20:53:11.415 PyThread[555] *** _NSAutoreleaseNoPool(): Object 0x146c980 of class NSException autoreleased with no pool in place - just leaking 2007-06-04 20:53:11.415 PyThread[555] An uncaught exception was raised 2007-06-04 20:53:11.415 PyThread[555] *** +[Threaded newThread:]: selector not recognized 2007-06-04 20:53:11.415 PyThread[555] *** Uncaught exception: <NSInvalidArgumentException> *** +[Threaded newThread:]: selector not recognized Jun 4 20:53:12 joan-olsons-computer-2 crashdump[556]: PyThread crashed Jun 4 20:53:12 joan-olsons-computer-2 crashdump[556]: crash report written to: /Users/jolson/Library/Logs/CrashReporter/PyThread.crash.log In addition, I don't know how to talk to the thread to kill it. Thanks for any help, Tom Elliott

1 0

which fortran for pythonmac.org binaries?
by Paul Kienzle June 4, 2007

June 4, 2007

Hi, I've downloaded scipy for python2.4 from pythonmac.org today: http://pythonmac.org/packages/py24-fat/index.html and saw the following problem: File "../chisq.py", line 6, in ? import scipy.interpolate File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/interpolate/__init__.py", line 7, in ? from interpolate import * File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/interpolate/interpolate.py", line 13, in ? import fitpack File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/interpolate/fitpack.py", line 34, in ? import _fitpack ImportError: Inappropriate file type for dynamic loading Some web searching suggests that it may be a fortran versioning problem. Indeed, otool -L reports: $ otool -L /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/interpolate/_fitpack.so /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/interpolate/_fitpack.so: /usr/local/lib/libg2c.0.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/local/lib/libgcc_s.1.0.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.1.6) which suggests a pre-4.0 version of fortran was used to compile. The new library replacing g2c is gfortran. I have gfortran 4.2 downloaded from: http://r.research.att.com/exp/ and installed in /usr/local. Until Apple shows some leadership and picks a fortran compiler, is there some way to package scipy on pythonmac.org so that it contains it's own fortran libraries? At the very least, can somebody please point me to the fortran version that was used to build scipy so that I can drop the libraries in /Librar/Frames/Python.framework/Versions/2.4/lib and set DYLD_LIBRARY_PATH to find them? Thanks in advance, - Paul Paul Kienzle pkienzle(a)nist.gov

4 13

Py2App intel/PPC: "
by Ian York June 4, 2007

June 4, 2007

I've been packaging a set of scripts using py2app, and until now the app that results has run without issues on MacOS10.4, either intel or ppc. The latest version, however, only runs on intel (on which I made the py2app package). The problem seems to be with eGenix mx base package (which is needed for BioPython). The package run on PPC gets the error "No module named TextTools", although TextTools is included and works fine on intel. If I include TextTools specifically with --include TextTools (or if I --include mx), instead I get an error "ImportError: Inappropriate file type for dynamic loading". Again, these errors only appear on the ppc platform, not on intel. What am I doing wrong, and how do I fix it? Ian -- Ian York (iayork(a)panix.com) <http://www.iayork.com/> "-but as he was a York, I am rather inclined to suppose him a very respectable Man." -Jane Austen, The History of England

1 0

mdutils
by Jan H. Jensen June 1, 2007

June 1, 2007

Hi, has anyone managed to use mdutils on a mac? Thanks, Jan -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Jan H. Jensen Associate Research Professor Department of Chemistry jhjensen(a)kemi.ku.dk University of Copenhagen Phone: +45 35 32 02 39 Universitetsparken 5 FAX: +45 35 32 02 14 2100 Copenhagen Denmark http://propka.ki.ku.dk/~jhjensen =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

2 1