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

MySQLdb on OS X 10.6
by Brian Zambrano Oct. 30, 2010

Oct. 30, 2010

Hi all, Like many others before me, I'm banging my head against the wall trying to get MySQLdb working on my new MacBook Pro with Snow Leopard. I have MySql 5.1 x86_64 installed, configured and running. I'm building MySQLdb 1.2.3c1 like this: export ARCHFLAGS='-arch x86_64' python setup.py build python setup.py install But it simply doesn't work....and apparently I'm not the only one<http://bit.ly/3iQy2> : (eb)brianz@eb-brianz$ python -c "import MySQLdb" Traceback (most recent call last): File "<string>", line 1, in <module> File "MySQLdb/__init__.py", line 19, in <module> import _mysql ImportError: dlopen(./_mysql.so, 2): no suitable image found. Did find: ./_mysql.so: mach-o, but wrong architecture Everything *looks* ok: (eb)brianz@eb-brianz$ file _mysql.so _mysql.so: Mach-O 64-bit bundle x86_64 (eb)brianz@eb-brianz$ otool -L _mysql.so _mysql.so: /usr/local/mysql/lib/libmysqlclient_r.16.dylib (compatibility version 17.0.0, current version 17.0.0) /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 124.1.1) (eb)brianz@eb-brianz$ (eb)brianz@eb-brianz$ file /usr/local/mysql/lib/libmysqlclient_r.16.dylib /usr/local/mysql/lib/libmysqlclient_r.16.dylib: Mach-O 64-bit dynamically linked shared library x86_64 Huh? Something is not right here. It sucks that the OS X builds are so painful. I'm sort of at a loss at where to go next. Suggestions? Any help greatly appreciated! BZ BTW...here are the relevant lines from the build: creating build/temp.macosx-10.6-i386-2.5 gcc-4.2 -fno-strict-aliasing -mno-fused-madd -fno-common -dynamic -DNDEBUG -g -fwrapv -Os -Wall -Wstrict-prototypes -DMACOSX -I/usr/include/ffi -DENABLE_DTRACE -pipe -Dversion_info=(1,2,3,'gamma',1) -D__version__=1.2.3c1 -I/usr/local/mysql/include -I/System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5 -c _mysql.c -o build/temp.macosx-10.6-i386-2.5/_mysql.o -g -Os -arch x86_64 -fno-common -D_P1003_1B_VISIBLE -DSIGNAL_WITH_VIO_CLOSE -DSIGNALS_DONT_BREAK_READ -DIGNORE_SIGHUP_SIGQUIT -DDONT_DECLARE_CXA_PURE_VIRTUAL In file included from _mysql.c:36: /usr/local/mysql/include/my_config.h:1049:1: warning: "HAVE_WCSCOLL" redefined In file included from /System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/Python.h:8, from pymemcompat.h:10, from _mysql.c:29: /System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/pyconfig.h:725:1: warning: this is the location of the previous definition gcc-4.2 -Wl,-F. -bundle -undefined dynamic_lookup -arch x86_64 build/temp.macosx-10.6-i386-2.5/_mysql.o -L/usr/local/mysql/lib -lmysqlclient_r -lz -lm -lmygcc -o build/lib.macosx-10.6-i386-2.5/_mysql.so

4 6

Weird Carbon: gestalt: wxPython issue/bug
by Christopher Barker Oct. 13, 2010

Oct. 13, 2010

Hi folks, Peter Hanson, on the wxPython list, seems to have identified a bug in the gestalt module, that may be a Carbon issue. It's a bit of an unusual case: it freezes up wxPython, when wx is called from other than the main thread. Robin Dunn suspects that it's a Carbon issue -- gestalt is calling Carbon, and doing so in the main thread, so you are then trying to call Carbon from more than one thread, which may be the cause of the problem. I've confirmed that if you call gestalt from the same thread as wxPython, there is no failure. A link to Robin Dunn's assessment: http://permalink.gmane.org/gmane.comp.python.wxpython/76590 As Carbon is deprecated anyway, I guess it's time for gestalt ( or platform.mac_ver ) to be re-written I've tested on OS-X 10.4.11, Python 2.5 and Python2.6 Here is Peter's summary and sample code: # Demonstration of application freeze on OSX. # Running "python osx_freeze.py" shows the symptom: # non-responsiveness after about 3 seconds. In theory # this will occur in any wxPython app which runs # the GUI event loop in a thread other than the one # in which the failing gestalt('sysu') call (see below) # is first executed. # Enabling any of these imports can trigger the problem # as each one imports the next one down in the list. # This will happen only with pkg_resources v0.6c10 or later # although it's not pkg_resources' fault. # import matplotlib.figure # import matplotlib.axes # import matplotlib.dates # import pytz # import pkg_resources # The next import alone doesn't lead to failure, # but the function call does. # This same code is executed by pkg_resources starting # with setuptools v0.6c10. # from platform import mac_ver; mac_ver() # The platform.mac_ver() call does the following, which # is what ultimately leads to the failure. Calls # to gestalt() with 'sysa' (for example) do not # trigger the problem, either because the problem is # related to the 'sysu' itself, or to the fact that # an exception is raised because the selector "sysu" # is no longer recognized. from gestalt import gestalt try: print gestalt('sysu') except Exception, ex: print 'gestalt call failed' if __name__ == '__main__': def gui(): import wx app = wx.App(False) frame = wx.Frame(None) wx.StaticText(frame, label='Goodbye, cruel world') frame.Show() app.MainLoop() import threading threading.Thread(target=gui).start() -- 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

5 14

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

Problems with py2app and qt
by aditya bhargava April 22, 2010

April 22, 2010

Hi python users, I'm getting some strange results running py2app on my machine. It works fine with most scripts, but any time I use it with a script that uses PyQt, the built application immediately quits and gives me an "unexpectedly quit" message. It's not the code, because I tried py2app with a couple of the example scripts that come with PyQt and got the same result. Any thoughts? I'm on mac OS X 10.4 running Python 2.5. My copy of py2app is very recent, I just got the latest one yesterday. Thanks for your help! Aditya

5 5

GTK2, Snow Leopard, py2app
by pirat＠ookami.cz April 8, 2010

April 8, 2010

Hello all, For historical reasons I have Python application for Mac with GTK gui. For Leopard GTK was build via jhbuild and everything "works" (there's a special shell script for running it which takes care of setting environmental variables). However, for Snow Leopard all my attempts failed - as soon as you start using threads, it's impossible to quit application :) So I've tried macports. They work, but I was unable to create working independent package by hand - it's still missing something from /opt/local and I've run out of ideas here. py2app creates nice package which tries to start and fails with error 255 (I think). Does anyone know about any reasonably small (not Gimp :) GTK apllication running successfully on Snow Leopard? The one created with py2app would be even better. Thank you very much, Jirka Znamenacek

2 3

argv emulation with python 2.6.5
by Brendan Simon (eTRIX) March 30, 2010

March 30, 2010

I'm porting an app from python 2.5 (2.5.4) to python 2.6 (2.6.5) and having timeout issues with argv emulation. Does argv emulation with with python 2.6 (2.6.5) ?? How do I get argv emulation working with 2.6 and/or what is the work around or alternative solution ?? Thanks, Brendan.

2 2

PyQt apps on Mac
by Kevin Walzer March 30, 2010

March 30, 2010

Hi all, I'm interested in taking a look at PyQt apps on the Mac. Problem is--I can't find any that are already bundled as standalone apps. Right now I don't have the time or inclination to build PyQt from scratch to test things out...are there any PyQt developers on this list who can post links to standalone PyQt apps wrapped with py2app that run on Leopard? Thanks, Kevin -- Kevin Walzer Code by Kevin http://www.codebykevin.com

4 5

Re: [Pythonmac-SIG] appscript fails to notice System Events is not running
by has March 29, 2010

March 29, 2010

Noah Coccaro wrote: > I have a long running server that uses appscript to send keystroke commands to System Events. > It seems that System Events does not run constantly, or frequently dies. > Quite often, appscript seems to be in a state where it incorrectly thinks System Events is running, and still sends commands to it, resulting in failures. Appscript makes no assumptions as to whether an application is running or not, except for the first time you use a newly created app object. By default, that is the only time that appscript will automatically launch an application for you if it is not already running. This is different to AppleScript's behaviour but is quite deliberate: if a target application crashes halfway through your script, you generally want to know about this as any documents your script may have been working on will be lost, so there is no point in trying to manipulate them further. In some cases, the default appscript behaviour may not be what you want. In this case, you have several options: 1. Create a new app object before sending a series of commands. This is a fairly cheap option as you are only doing a search of currently running processes for the one you want. (The main cost in creating app objects is in parsing the application dictionary, and appscript caches parsed dictionaries for efficiency.) One downside is that this won't affect existing references that your script created before the application quit, but chances are these references will no longer be valid anyway so no great loss in practice. 2. Send a 'run' or 'launch' command before sending a series of commands. By default, these commands will automatically relaunch the application if necessary and update the app object to point to the current process. 3. Create an app object, then set its 'relaunchmode' property to "always". This will allow the app object to relaunch and reconnect to the target application before sending any command (i.e. equivalent to the AppleScript behaviour). See chapter 7 of the appscript manual for more information. HTH has -- Control AppleScriptable applications from Python, Ruby and ObjC: http://appscript.sourceforge.net

1 0

appscript fails to notice System Events is not running
by Noah Coccaro March 28, 2010

March 28, 2010

I have a long running server that uses appscript to send keystroke commands to System Events. It seems that System Events does not run constantly, or frequently dies. Quite often, appscript seems to be in a state where it incorrectly thinks System Events is running, and still sends commands to it, resulting in failures. Is there a workaround for this? A way to tell appscript that an app definitly is not running, or clear some cache maybe that is lingering? I notice if I start a different python instance, and send commands to System Events, it correctly starts it up. Here is a error dump from running essentially app('System Events').run() when it thought it was already running -- the same happens with launch, or any other command -- appscript can't get the terminology for System Events because it isn't running: File "./avjamasserver.py", line 102, in do_POST result = self.CallFunction(request, av.activity) File "./avjamasserver.py", line 74, in CallFunction return function(*function_args) File "/Users/noah/Software/RS232/avcontrol.py", line 300, in AudioMode SafeStart(sys_events) File "/Users/noah/Software/RS232/avcontrol.py", line 20, in SafeStart app_instance.run() File "build/bdist.macosx-10.5-i386/egg/appscript/reference.py", line 578, in __getattr__ selectortype, code = self.AS_appdata.referencebyname()[name] File "build/bdist.macosx-10.5-i386/egg/appscript/reference.py", line 260, in referencebyname self.connect() File "build/bdist.macosx-10.5-i386/egg/appscript/reference.py", line 229, in connect self._terms = terminology.tablesforapp(t) File "build/bdist.macosx-10.5-i386/egg/appscript/terminology.py", line 171, in tablesforapp _terminologycache[aemapp.AEM_identity] = tablesforaetes(aetesforapp(aemapp)) File "build/bdist.macosx-10.5-i386/egg/appscript/terminology.py", line 143, in aetesforapp raise RuntimeError("Can't get terminology for application (%r): %s" % (aemapp, e)) RuntimeError: Can't get terminology for application (aem.Application(u'/System/Library/CoreServices/System Events.app')): Command failed: Application isn't runnin g. (-600)

2 1

Build hell resolved: 10.4/10.5/10.6
by Aahz March 22, 2010

March 22, 2010

[cross-posted to both pythonmac-sig and pyobjc-dev for max audience, Reply-To set to pyobjc-dev for discussion] I finally figured out how to build my app: Turns out that in order to use PyObjC 2.2 you need py2app 0.4.3 -- but PyObjC 1.4 needs py2app 0.3.6. (PyObjC 1.4 is for the main app running on 10.4/10.5/10.6; PyObjC 2.2 is used for FSEvents on 10.5/10.6, previously PyObjC 2.2b2 for 10.5 only, but 2.2b2 doesn't work on 10.6) I built PyObjC 2.2 on 10.5 from source. It's a right royal pain (partly because PyPI has no mechanism for downloading *source* dependencies), and I really hope that the next release of PyObjC makes it much easier to build from source. (Or that binaries for 10.5 get included.) My clue that py2app was the issue was when I figured out that from Foundation import NSAutoreleasePool, NSMutableArray, NSString causing ValueError: Don't know CF type for typestr '^{__CFAllocator=}', cannot create special wrapper only and always occurred in a build, not from plain Python, even on 10.6, meaning that PyObjC wasn't the problem. Incidentally, using py2app 0.4.3 with PyObjC 1.4 resulted in some error about corrupted NIB file that I didn't record exactly. Before someone asks how I can use both PyObjC 1.4 and PyObjC 2.2, I'm playing games with ~/Library/Python/2.6 being a symlink that gets swapped during the build process. (Obviously, I end up with two different apps built.) -- Aahz (aahz(a)pythoncraft.com) <*> http://www.pythoncraft.com/ "Many customs in this life persist because they ease friction and promote productivity as a result of universal agreement, and whether they are precisely the optimal choices is much less important." --Henry Spencer

2 1