🌐 Mailman 3 December 2005 - Pythonmac-SIG - python.org

F2PY, F90, and Mac os x Tiger: linking problem
by Louis Wicker Dec. 6, 2005

Dec. 6, 2005

All: Back in April I upgraded to Tiger, and I should have known better. I cannot get any f90/5 programs to link with f2py (except that I have not tried the g95/gfortran compilers). This problem started when I "upgraded" to Tiger from 10.3.9. I thought I would ask over to here to see if anyone has any ideas. I get the same linking problem using the XLF, Absoft 9.2, and even the NAG compiler. I can get g77 programs to compile and link correctly. Here is the linking problem...it occurs at the end of the f2py process (see full output below). /usr/bin/ld: /usr/lib/crt1.o has external relocation entries in non- writable section (__TEXT,__text) for symbols: __mh_execute_header This external relocation problem exists for all of the above named compilers. I am using gcc 3.3. My online research and my simple brain has figured out this is something to do with the gcc libs, and the fact that something changed with 10.4. The NAG README hints that something is weird with Tiger and that they are temporarily supporting a "-unshared" flag - which I think allows me to link statically somehow to a dynamic library. I can successfully link using that flag, but the fortran module is dead when I import it into python (it imports, but nothing happens when I try to access it). This occurs with Python 2.3.5 and 2.4.1. I cannot find anything anywhere on how to deal with this. I have tried tricky other things, like compiling with f90 and linking with g77 or gcc, but I get other types of errors. Any thoughts would be appreciated, as this is irritating the hell out of me (for the third time this year). Lou ======= Full output ==== f2py --fcompiler=ibm -c -m hello hello.f numpy_info: FOUND: define_macros = [('NUMERIC_VERSION', '"\\"24.0b2\\""')] include_dirs = ['/System/Library/Frameworks/Python.framework/ Versions/2.3/include/python2.3'] running build running config_fc running build_src building extension "hello" sources f2py:> /tmp/tmpEAl_LK/src/hellomodule.c creating /tmp/tmpEAl_LK creating /tmp/tmpEAl_LK/src Reading fortran codes... Reading file 'hello.f' Post-processing... Block: hello Block: foo Post-processing (stage 2)... Building modules... Building module "hello"... Constructing wrapper function "foo"... foo(a) Wrote C/API module "hello" to file "/tmp/tmpEAl_LK/src/ hellomodule.c" adding '/tmp/tmpEAl_LK/src/fortranobject.c' to sources. adding '/tmp/tmpEAl_LK/src' to include_dirs. copying /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ python2.3/site-packages/f2py2e/src/fortranobject.c -> /tmp/tmpEAl_LK/src copying /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ python2.3/site-packages/f2py2e/src/fortranobject.h -> /tmp/tmpEAl_LK/src running build_ext customize UnixCCompiler customize UnixCCompiler using build_ext customize IbmFCompiler customize IbmFCompiler using build_ext building 'hello' extension compiling C sources gcc options: '-fno-strict-aliasing -Wno-long-double -no-cpp-precomp - mno-fused-madd -fno-common -dynamic -DNDEBUG -g -O3 -Wall -Wstrict- prototypes' creating /tmp/tmpEAl_LK/tmp creating /tmp/tmpEAl_LK/tmp/tmpEAl_LK creating /tmp/tmpEAl_LK/tmp/tmpEAl_LK/src compile options: '-I/System/Library/Frameworks/Python.framework/ Versions/2.3/include/python2.3 -I/tmp/tmpEAl_LK/src -I/System/Library/ Frameworks/Python.framework/Versions/2.3/include/python2.3 -c' gcc: /tmp/tmpEAl_LK/src/fortranobject.c /tmp/tmpEAl_LK/src/fortranobject.c: In function `fortran_doc': /tmp/tmpEAl_LK/src/fortranobject.c:123: warning: int format, long unsigned int arg (arg 3) gcc: /tmp/tmpEAl_LK/src/hellomodule.c compiling Fortran sources xlf(f77) options: '-qextname -O5' xlf90(f90) options: '-qextname -O5' xlf90(fix) options: '-qfixed -qextname -O5' compile options: '-I/System/Library/Frameworks/Python.framework/ Versions/2.3/include/python2.3 -I/tmp/tmpEAl_LK/src -I/System/Library/ Frameworks/Python.framework/Versions/2.3/include/python2.3 -c' xlf:f77: hello.f ** foo === End of Compilation 1 === 1501-510 Compilation successful for file hello.f. xlf95 -Wl,-bundle,-flat_namespace,-undefined,suppress /tmp/tmpEAl_LK/ tmp/tmpEAl_LK/src/hellomodule.o /tmp/tmpEAl_LK/tmp/tmpEAl_LK/src/ fortranobject.o /tmp/tmpEAl_LK/hello.o -o ./hello.so /usr/bin/ld: /usr/lib/gcrt1.o has external relocation entries in non- writable section (__TEXT,__text) for symbols: __mh_execute_header /usr/bin/ld: /usr/lib/gcrt1.o has external relocation entries in non- writable section (__TEXT,__text) for symbols: __mh_execute_header error: Command "xlf95 -Wl,-bundle,-flat_namespace,- undefined,suppress /tmp/tmpEAl_LK/tmp/tmpEAl_LK/src/hellomodule.o / tmp/tmpEAl_LK/tmp/tmpEAl_LK/src/fortranobject.o /tmp/tmpEAl_LK/ hello.o -o ./hello.so" failed with exit status 1

2 1

Database (SQL prefered) access on MacPython
by Schollnick, Benjamin Dec. 3, 2005

Dec. 3, 2005

Folks, On the PC side, I use an ODBC connection.... But I'm considering writing an Database application on the Macintosh via Python... I asked earlier and ODBC seems to be mostly out on the MacPython front. What methods do you folks use for accessing an database (SQL based database prefered) via macpython? - Benjamin

3 2

Python QT module, etc.
by Shaun Richard Moon Dec. 2, 2005

Dec. 2, 2005

Hey all, i saw that there was some chatter here about caputring an image from a webcam back in April did anybody have any luck? I'm very new and basically I've seen a couple of different possibilities in Cocoa.Qt, Jack Jansen's QuickTime module (don't know how to get that one) and PyQTSequence (so far *import PyQTSequence" or "PyQT" doesn't work). For all I can tell, these seem potentially workable but I don't know how. Any suggestions? Any help would be very highly appreciated. shaun

1 0

problem trying to use aemreceive with Tkinter app
by Kennedy, Andrew (GE Healthcare) Dec. 2, 2005

Dec. 2, 2005

Hi folks, I'm trying to use aemreceive to process AppleEvents in a Tkinter-GUI'd Python app. I have been able to use argvemulator.py from plat-mac to handle double clicking on a file and having it open in the application automatically. I'm now trying to catch 'ocon' and 'odoc' AppleEvents within the application to handle dragging files onto the icon and double clicking on files while the application is running. I can add the event handler per the code below: if sys.platform == 'darwin': import aemreceive aemreceive.installeventhandler(AEOpenFile, 'aevtodoc', ('----','AliasList', aemreceive.ArgListOf(aemreceive.kAE.typeAlias))) What am I missing? Do I need to modify my main loop to handle the events? I never seem to get into the event handler code this way, so there must be something else at work here. Is my event handler at the wrong level of the stack? The crash log is included after my signature. Any assistance anyone can offer would be greatly appreciated. Thanks in advance, Andrew Andrew Kennedy Applications Developer Preclinical Imaging GE Healthcare P +1 519 474 5190 F +1 519 472 9492 E Andrew.Kennedy(a)med.ge.com http://www.gehealthcare.com/ Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000008 Thread 0 Crashed: 0 org.python.python 0x10022408 PyFrame_New + 0x20 (frameobject.c:540) 1 org.python.python 0x100734a8 PyEval_EvalCodeEx + 0x88 (ceval.c:2456) 2 org.python.python 0x10024e74 function_call + 0x158 (funcobject.c:504) 3 org.python.python 0x1000c134 PyObject_Call + 0x30 (abstract.c:1756) 4 org.python.python 0x10074ca4 PyEval_CallObjectWithKeywords + 0x100 (ceval.c:3347) 5 _AE.so 0x0f2e9a30 GenericEventHandler + 0x154 (_AEmodule.c:1587) 6 com.apple.AE 0x98fa8a10 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) + 0xd0 7 com.apple.AE 0x98fab858 dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 0x2c 8 com.apple.AE 0x98fa8c50 aeProcessAppleEvent + 0x11c 9 com.apple.HIToolbox 0x92975224 AEProcessAppleEvent + 0x3c 10 com.tcltk.tklibrary 0x0b07dcac TkMacOSXDoHLEvent + 0x10 11 com.tcltk.tklibrary 0x0b07bb3c TkMacOSXProcessAppleEvent + 0x3c 12 com.tcltk.tklibrary 0x0b07bc80 TkMacOSXProcessEvent + 0xb0 13 com.tcltk.tklibrary 0x0b07bd14 ReceiveAndProcessEvent + 0x74 14 com.tcltk.tklibrary 0x0b07bad8 TkMacOSXCountAndProcessMacEvents + 0x30 15 com.tcltk.tklibrary 0x0b0870c0 TkMacOSXWaitForEvent + 0x250 16 com.tcltk.tcllibrary 0x0a078370 Tcl_WaitForEvent + 0x64 17 com.tcltk.tcllibrary 0x0a0565f8 Tcl_DoOneEvent + 0x128 18 _tkinter.so 0x002872c0 Tkapp_MainLoop + 0x150 (_tkinter.c:2530) 19 org.python.python 0x10074e18 call_function + 0x130 (ceval.c:3440) 20 org.python.python 0x10072a54 eval_frame + 0x2568 (ceval.c:2116) 21 org.python.python 0x10073d04 PyEval_EvalCodeEx + 0x8e4 (ceval.c:2663) 22 org.python.python 0x100750f8 fast_function + 0x164 (ceval.c:3533) 23 org.python.python 0x10074ef0 call_function + 0x208 (ceval.c:3458) 24 org.python.python 0x10072a54 eval_frame + 0x2568 (ceval.c:2116) 25 org.python.python 0x10075068 fast_function + 0xd4 (ceval.c:3520) 26 org.python.python 0x10074ef0 call_function + 0x208 (ceval.c:3458) 27 org.python.python 0x10072a54 eval_frame + 0x2568 (ceval.c:2116) 28 org.python.python 0x10073d04 PyEval_EvalCodeEx + 0x8e4 (ceval.c:2663) 29 org.python.python 0x10076b64 PyEval_EvalCode + 0x30 (ceval.c:537) 30 org.python.python 0x100a8258 run_node + 0x4c (pythonrun.c:1265) 31 org.python.python 0x100a7a2c PyRun_SimpleFileExFlags + 0x250 (pythonrun.c:865) 32 org.python.python 0x100b41e0 Py_Main + 0x858 (main.c:415) 33 MicroView 0x00001b10 0x1000 + 0xb10 34 dyld 0x8fe1a278 _dyld_start + 0x64 Thread 1: 0 libSystem.B.dylib 0x9494746c select + 0xc 1 com.tcltk.tklibrary 0x0b087290 NotifierThreadProc + 0x1b0 2 libSystem.B.dylib 0x94960990 _pthread_body + 0x28 PPC Thread State: srr0: 0x10022408 srr1: 0x0200f030 vrsave: 0x00000000 cr: 0x42822228 xer: 0x20000004 lr: 0x100734a8 ctr: 0x100223e8 r0: 0x100734a8 r1: 0xbfffe770 r2: 0x10024e74 r3: 0x00000000 r4: 0x0f4b90a0 r5: 0x0f4ae4b0 r6: 0x00000000 r7: 0x00000002 r8: 0x42822228 r9: 0x100734a8 r10: 0x00000000 r11: 0x1010eda0 r12: 0x100223e8 r13: 0x00000000 r14: 0x00000000 r15: 0x0f302ec4 r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x0028717c r20: 0x00000000 r21: 0x00000000 r22: 0x00000002 r23: 0x00000000 r24: 0x00000000 r25: 0x0f4b90a0 r26: 0x00000000 r27: 0x00000000 r28: 0x11aeb62c r29: 0x0f4b90a0 r30: 0x00000000 r31: 0x10073428

2 1

Re: [Pythonmac-SIG] Database (SQL prefered) access on MacPython
by Schollnick, Benjamin Dec. 2, 2005

Dec. 2, 2005

> Python's Db API, of course. http://www.python.org/peps/pep-0249.html > > There are a lot of databases out there, and there's a Python > driver for most of them. http://www.python.org/topics/database/ > I guess you'll find most help for MySQL, even if PostgreSQL > or something is better. If you don't need a db server, > perhaps try SQLite. When the heck did that come out? It's a nice step forward to standarding the Database modules that exist... I'll have to explore that more further... - Ben

2 1

Re: [Pythonmac-SIG] Database (SQL prefered) access on MacPython
by Henning.Ramm＠mediapro-gmbh.de Dec. 2, 2005

Dec. 2, 2005

>I asked earlier and ODBC seems to be mostly out on the MacPython >front. What methods do you folks use for accessing an database >(SQL based database prefered) via macpython? Python's Db API, of course. http://www.python.org/peps/pep-0249.html There are a lot of databases out there, and there's a Python driver for most of them. http://www.python.org/topics/database/ I guess you'll find most help for MySQL, even if PostgreSQL or something is better. If you don't need a db server, perhaps try SQLite. Greetlings, HR

1 0

Re: [Pythonmac-SIG] iphoto, slow
by has Dec. 1, 2005

Dec. 1, 2005

Gábor Farkas wrote: >i am trying to print out all my photo's names, together with their keywords. >[...] >this code works, but it's TERRIBLY slow :) > >the problem is the parsePhoto function... >those keyword.name(), photo.name(), photo.keywords() calls take nearly a >second to complete... That sounds really awful, though I don't have a scriptable copy of iPhoto to confirm it myself. (Smoked my copy of iPhoto 2.0 in the last reinstall and am too cheap to buy iLife, so am back on v1 now.) Quite possible though - I seem to recall reading complaints in the past about its GUI bogging down on large numbers of images, so may be more of the same problem. >is there a better way to do this? >perharps get the data about multiple photos at the same time? Always a good idea to do that if you can. At the moment you're sending about the most commands you can. You could certainly reduce that a bit; perhaps right down to just two with a bit of luck: one to get all the photo names, and one to get all the keyword names for every photo. Not sure how well iPhoto can resolve more complex queries, but here's the code to try: p = app('iPhoto') print zip(p.photos.name(), p.photos.keywords.name()) If that doesn't work, let me know and I'll suggest ways to unroll it a bit. BTW, the next release of appscript (whenever that is) will include a chapter on optimising code for efficiency; I just haven't gotten around to finishing it yet. FWIW, I've temporarily posted some of the notes here: http://freespace.virgin.net/hamish.sanderson/appscript_efficiency_example.t… HTH has -- http://freespace.virgin.net/hamish.sanderson/

1 0

iphoto, slow
by Gábor Farkas Dec. 1, 2005

Dec. 1, 2005

hi, i am trying to print out all my photo's names, together with their keywords. import appscript app = appscript.app('iphoto') def parsePhoto(photo): tags = [keyword.name() for keyword in photo.keywords()] return (photo.name(),tags) for photo in app.photos(): print parsePhoto(photo) this code works, but it's TERRIBLY slow :) the problem is the parsePhoto function... those keyword.name(), photo.name(), photo.keywords() calls take nearly a second to complete... when printing out info about 3000photos, this will take some time :) is there a better way to do this? perharps get the data about multiple photos at the same time? i just cannot believe iPhoto itself is so slow to provide the required data... thanks, gabor

1 0

ANN: SPE 0.8.0.b Python IDE (Mac support, doc viewer and workspaces)
by SPE Stani's Python Editor Dec. 1, 2005

Dec. 1, 2005

:**What's new?**: SPE 'Kay release' 0.8.0.b This release is a major step forward for all platforms, especially for MacOS X. It offers you basic project management through workspaces (thanks to Thurston Stone), an improved sidebar and pydoc viewer. This is the first release which is also developed and tested on the Mac. If SPE is stable enough, I'll try to build SPE as an application for the Mac. This version aims stability, so please help to report and fix all bugs! You can get involved on the SPE dev mailing list: https://developer.berlios.de/mail/?group_id=4161 The advertisements on SPE's websites generate a moderate, but necesssary income. From now on if you donate, you can ask me by email an ad-free, nice pdf version of the manual. :**About SPE**: SPE is a python IDE with auto-indentation, auto completion, call tips, syntax coloring, uml viewer, syntax highlighting, class explorer, source index, auto todo list, sticky notes, integrated pycrust shell, python file browser, recent file browser, drag&drop, context help, ... Special is its blender support with a blender 3d object browser and its ability to run interactively inside blender. Spe ships with wxGlade (gui designer), PyChecker (source code doctor) and Kiki (regular expression console). :**New features**: - stability - workspaces to manage your projects - documentation viewer (pydoc) - smart indentation: dedent after break, return, etc... - realtime updating of sidebar: explore, todo & index - check source realtime for syntax errors (optional) - backup files (.py.bak) are now optional :**Improved features**: - find in files :**Bug fixes**: - Workspace bugs (closing files) - Installer (Windows) - all these mac bugs are fixed: + Find dialog focus + Sticky notes + Find in files tab + Toolbar keyboard shortcut display + Kiki: regex console + SPE crashes on close + preferences dialog: combobox bug + debug dialog: combobox bug + wxGlade won't launch + winPdb won't launch + 2x window menu bug + context menu bug + open & run in terminal emulator + pythonw debug message + spe script bug + exception when closing file + PyChecker :**Installation**: See http://pythonide.stani.be/manual/html/manual2.html There is now an update section for MacOS X! :**Websites**: - homepage: http://pythonide.stani.be - manual: http://pythonide.stani.be/manual/html/manual.html - news blog: http://pythonide.stani.be/blog :**Contributors**: - Thurston Stone (workspaces) - Glenn Washburn (patches) - Henning Hraban Ramm (Mac support) - Kay Fricke (Mac support) - Stefan Csomor (wxMac support) - and many more... :**Donations**: Special thanks to Richard Brown of Dartware for starting the fund raising campaign of the mini-mac for SPE. A lot of the donations below are done specifically for this purpose. Impressive that the smallest user base of SPE generated generously the largest donations ever. Many thanks. Maybe it's time now for Window and Linux users to catch up! - Dartware (250 euro) - Rick Thomas (161 euro) - Brian Myers (100 euro) - Advanced Concepts AG (50 euro) - Ernesto Costa (50 euro) - Henning Hraban Ramm (50 euro) - Peter Koppatz (50 euro) - Kevin Murphy (50 euro) - Stefano Morandi (50 euro) - Kenneth McDonald (40 euro) - Barrett Smith (25 euro) - Irakli Nadareishvili (20 euro) - Jonathan Roadley-Battin (20 euro) - Brendan Simons (15 euro) - Edwin Ellis (15 euro) - Ian Ozsvald (15 euro) - Michael Smith (15 euro) - Eduardo Gonzalez (10 euro) - Phil Hargett (10 euro) - David Diskin (5 euro) Thanks for this generous support! Stani

1 0

Re: [Pythonmac-SIG] Selecting in BBEdit & Python Indenting style(spaces)
by Kent Quirk Nov. 30, 2005

Nov. 30, 2005

Just because there seems to be an orgy of people agreeing that Tabs are the One True Way, I feel a need to point out that there are those of us who fervently believe that Tabs Are Evil. The reason is that tabs are interpreted differently in different places, and they're indistinguishable from spaces upon casual inspection. So the visual appearance of mixed spaces and tabs can be highly misleading and confusing, especially in an environment with multiple developers, each of whom may have a different tab setting. Spaces are unambiguous. As it's the meaning of the source that matters, and editors can be tuned to personal taste, I'm in favor of leaving the source clean of tabs and letting people tweak their editors to their own liking. In my view, Python should consider leading tabs to be a syntax error (and yes, I know about the -tt switch). Kent -----Original Message----- From: pythonmac-sig-bounces(a)python.org [mailto:pythonmac-sig-bounces@python.org] On Behalf Of Jan Erik Moström Sent: Tuesday, November 29, 2005 4:18 PM To: Chris Barker Cc: Louis Pecora; pythonmac-sig(a)python.org Subject: Re: [Pythonmac-SIG] Selecting in BBEdit & Python Indenting style(spaces) Chris Barker <Chris.Barker(a)noaa.gov> 2005-11-29 20:40: > > I would think that TAB would be infinitely better and avoid the > > problems you point out that probably plague a lot of editors when > > doing Python code. > > I agree. Tabs would be easier in most cases, but: Thank you, while I really like Python I've never figured this one out. But I have other style things also that isn't "true" python ;-) jem -- Jan Erik Moström, www.mostrom.pp.se _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG(a)python.org http://mail.python.org/mailman/listinfo/pythonmac-sig

5 5