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

Python based apps woes on MacOs X (was :Re: [Pythoncard-users] Re: PythonCard on OS X 10.4 with Python 2.4.1)
by catonano＠inwind.it May 7, 2006

May 7, 2006

> >There's a current thread about this in the PythonCard-users group, > >under the non-clear subject name: > > > > Re: update (was: Re: [Pythoncard-users] supposed bug in > >PythonCard) > > > > > >Yes I originated the thread. I found a bug in Pythoncard with python 2.4.1 and wxPython 2.6.1.0 and > >PythonCard 0.8.1 > > > >It's not "supposed". It's a quite clearly a bug. > > > > > > > Adriano - > the only reason the subject line says "supposed bug ..." is because > that's the subject line you chose for your initial posting to the > Pythoncard list on this topic :-) Yes, Alex, you're right. It was a supposed bug when I opened the thread, so the subject line was quite good at the moment. Later it became a bit obscure ;-) > Something appears to have changed wrt the path that Python's sys.modules > reports for imported files. >As far as I know, no-one has yet verified > for sure whether it is a Python bug or merely a platform-specific change > that Pythoncard will need to adjust for. (Nor do I know how we'll be > able to adjust - but I'm hoping that some of the PythonCard / Mac users > are investigating ....) That python user could be me ! Alex, would you discuss a bit more about this Python issue ? sys.modules reportings about the imported files has changed ? Since when ? Does this affect the Apple installed python or the "third parties" ones ? Thanks! Bye Adriano ____________________________________________________________ Libero Flat, sempre a 4 Mega a 19,95 euro al mese! Abbonati subito su http://www.libero.it

4 5

general rule
by Zhi Peng Dec. 29, 2005

Dec. 29, 2005

Hi! All If I would like to use C (Coddewarrior for example) to call Applescript for iTune or Finder or other application, what is the general rule or code should be except ask OS to run the script especially when I would like to pass data back and forth between C and applescript? Thanks Zhi __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com

1 0

general rule
by Zhi Peng Dec. 29, 2005

Dec. 29, 2005

Hi! All If I would like to use C (Coddewarrior for example) to call Applescript for iTune or Finder or other application, what is the general rule or code should be except ask OS to run the script especially when I would like to pass data back and forth between C and applescript? Thanks Zhi __________________________________ Yahoo! for Good - Make a difference this year. http://brand.yahoo.com/cybergivingweek2005/

1 0

general rule
by Zhi Peng Dec. 29, 2005

Dec. 29, 2005

Hi! All If I would like to use C (Coddewarrior for example) to call Applescript for iTune or Finder or other application, what is the general rule or code should be except ask OS to run the script especially when I would like to pass data back and forth between C and applescript? Thanks Zhi __________________________________ Yahoo! for Good - Make a difference this year. http://brand.yahoo.com/cybergivingweek2005/

1 0

PyCon TX 2006: Early-bird registration ends Dec. 31!
by David Goodger Dec. 28, 2005

Dec. 28, 2005

Early bird registration for PyCon TX 2006 ends on December 31st, so there are only a few days LEFT. To register, please visit: http://us.pycon.org/TX2006/Registration You can still register after Dec. 31st, but the cost will go up by US$65 (US$25 for students). This year PyCon will feature a day of tutorials before the three days of regular presentations. Course outlines for all the tutorials have been posted; see http://wiki.python.org/moin/PyCon2006/Tutorials All of the PyCon tutorials are still open for new registrations, but space is limited, and we suspect they'll all be filled up by the time early-bird registration closes. Don't forget to book your hotel room, too. PyCon TX 2006 is being held at a Dallas/Addison hotel, and we have negotiated a special low rate: http://us.pycon.org/Addison/Hotels We hope to see you in Texas! -- David Goodger (on behalf of A.M. Kuchling, Chair, PyCon 2006)

1 0

Re: [Pythonmac-SIG] PyObjC + AEInstallEventHandler crash?
by Bob Ippolito Dec. 28, 2005

Dec. 28, 2005

> Bob Ippolito wrote: > >> > Trying to figure why the following test app crashes when a 'testtest' >> > Apple event is sent to it: >> >>My guess is that there's a refcount or GIL bug in >>Carbon.AE.AEInstallEventHandler. > > How would a GIL bug manifest itself? I always assumed it only became an > issue with multiple threads, but it's not something I understand all that > well. When you release the GIL and call into Python before acquiring it again, it'll almost definitely crash. It doesn't matter if there are multiple threads running, the threading machinery is probably active (it definitely is if PyObjC is imported), which means that you'll have the threadstate as NULL and you'll dereference a NULL pointer somewhere in Python machinery -- boom. >>I'd use NSAppleEventManager... I've used it before and it works just >> fine. > > As I said, the reason I'm interested in why this example fails is because > I get a very similar crash in very similar code when using PyObjC with > CarbonX.OSA. (OSA.c's GenericSendFunction is cribbed from AE.c's > GenericEventHandler.) I didn't show that code because it's a bit more > complex, but that's the crash I'm really interested in fixing. If my guess is right, you probably borrowed broken code :) The handler that gets called into needs to do something like this. There is an older style of doing this with threadstates and whatnot, but the PyGILState API is much easier to deal with. void callback_from_c(void *data) { PyGILState_STATE state; PyObject *result; state = PyGILState_Ensure(); /* call into Python */ result = PyObject_CallFunctionObjArgs((PyObject *)data); /* clean up */ if (result == NULL) { PyErr_Print(); PyErr_Clear(); } else { Py_DECREF(result); } PyGILState_Release(state); } -bob

3 2

ANN: PyXG 0.2.0
by Brian Granger Dec. 23, 2005

Dec. 23, 2005

Hello fellow Xgrid/Python users, This is to announce the second release (0.2.0) of PyXG. PyXG is an object oriented Python interface to Xgrid. New in this release: - A new website (pyxg.scipy.org) - A google mailing list - A Subversion repository to speed development - Overhauled documentation - Package installers for two distributions of python - Kerberos support - More flexible handling of job and grid identifiers - More consistent coding style With PyXG you can: - Start and manage Xgrid jobs quickly using Python's elegant syntax. - Use Xgrid from within python scripts as well as in interactive Python sessions. - Submit and manage simple (one task) and batch (many task) Xgrid jobs. - Get job information and retrieve job results - Work with multiple Xgrid controllers and grids simultaneously. This is a new release with lots of changes, so if you find any bugs, please let me know. Brian Granger bgranger(a)scu.edu

1 0

PyObjC + AEInstallEventHandler crash?
by has Dec. 21, 2005

Dec. 21, 2005

Hi all, Trying to figure why the following test app crashes when a 'testtest' Apple event is sent to it: ------------------------------------------------------------ # cocoatest.py from PyObjCTools import AppHelper from Carbon.AE import AEInstallEventHandler AEInstallEventHandler('test', 'test', lambda evt, res:0) AppHelper.runEventLoop() ------------------------------------------------------------ # setup.py from distutils.core import setup import py2app setup(app=['cocoatest.py'], data_files=['MainMenu.nib']) # default IB application nib ------------------------------------------------------------ -- test.applescript tell application "cocoatest" to «event testtest» ------------------------------------------------------------ The test app builds and runs fine, but running the test.applescript causes it to fall over with the following traceback: ------------------------------------------------------------ Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000008 Thread 0 Crashed: 0 org.python.python 0x10023684 PyFrame_New + 32 (frameobject.c:540) 1 org.python.python 0x1007aab0 PyEval_EvalCodeEx + 148 (ceval.c:2523) 2 org.python.python 0x10026274 function_call + 344 (funcobject.c:548) 3 org.python.python 0x1000c348 PyObject_Call + 48 (abstract.c:1752) 4 org.python.python 0x1007c26c PyEval_CallObjectWithKeywords + 256 (ceval.c:3420) 5 _AE.so 0x0024b9d8 _AEDesc_NewBorrowed + 476 6 com.apple.AE 0x914ab960 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) + 208 7 com.apple.AE 0x914ab7fc dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 44 8 com.apple.AE 0x914ab654 aeProcessAppleEvent + 284 9 com.apple.HIToolbox 0x93188940 AEProcessAppleEvent + 60 10 com.apple.AppKit 0x93683adc _DPSNextEvent + 856 11 com.apple.AppKit 0x936835c8 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 116 12 com.apple.AppKit 0x9367fb0c -[NSApplication run] + 472 13 com.apple.AppKit 0x93770618 NSApplicationMain + 452 14 _AppKit.so 0x0040810c init_AppKit + 6484 15 org.python.python 0x1007c5ec call_function + 828 (ceval.c:3547) 16 org.python.python 0x1007a140 PyEval_EvalFrame + 8888 (ceval.c:2163) 17 org.python.python 0x1007b284 PyEval_EvalCodeEx + 2152 (ceval.c:2730) 18 org.python.python 0x1007c8cc fast_function + 356 (ceval.c:3644) 19 org.python.python 0x1007c6c4 call_function + 1044 (ceval.c:3568) 20 org.python.python 0x1007a140 PyEval_EvalFrame + 8888 (ceval.c:2163) 21 org.python.python 0x1007b284 PyEval_EvalCodeEx + 2152 (ceval.c:2730) 22 org.python.python 0x1007e678 PyEval_EvalCode + 48 (ceval.c:484) 23 org.python.python 0x100b2ee0 run_node + 76 (pythonrun.c:1265) 24 org.python.python 0x10070af4 builtin_execfile + 520 (bltinmodule.c:623) 25 org.python.python 0x1007c5ec call_function + 828 (ceval.c:3547) 26 org.python.python 0x1007a140 PyEval_EvalFrame + 8888 (ceval.c:2163) 27 org.python.python 0x1007b284 PyEval_EvalCodeEx + 2152 (ceval.c:2730) 28 org.python.python 0x1007c8cc fast_function + 356 (ceval.c:3644) 29 org.python.python 0x1007c6c4 call_function + 1044 (ceval.c:3568) 30 org.python.python 0x1007a140 PyEval_EvalFrame + 8888 (ceval.c:2163) 31 org.python.python 0x1007b284 PyEval_EvalCodeEx + 2152 (ceval.c:2730) 32 org.python.python 0x1007e678 PyEval_EvalCode + 48 (ceval.c:484) 33 org.python.python 0x100b2ee0 run_node + 76 (pythonrun.c:1265) 34 org.python.python 0x100b266c PyRun_SimpleFileExFlags + 592 (pythonrun.c:863) 35 ...onmac.unspecified.cocoatest 0x00003db0 0x1000 + 11696 36 ...onmac.unspecified.cocoatest 0x00003e50 0x1000 + 11856 37 ...onmac.unspecified.cocoatest 0x00002414 0x1000 + 5140 38 dyld 0x8fe01048 _dyld_start + 60 ------------------------------------------------------------ Additional notes: the test app doesn't crash when AppKit.NSAppleEventManager is used to install the event handler function, nor when CarbonEvt is used instead of PyObjC. I'm getting a similar crash in some CarbonX.OSA code within a PyObjC-based app and reckon identifying what's causing the test app to crash will help me solve the problem there. Any ideas as to the cause, suggestions where to look, how to debug it more effectively, etc. would be a big help as I've been stuck on this for more than a day now and have only just fitted a new laptop case after the last temper tantrum. :p Many thanks, has -- http://freespace.virgin.net/hamish.sanderson/

3 2

ANN: SPE 0.8.1.c IDE (realtime error underlining & script tooltips)
by SPE Stani's Python Editor Dec. 21, 2005

Dec. 21, 2005

Release news from http://pythonide.stani.be This new release is for under your Christmas tree. (If you want more presents, just donate to SPE and receive the manual in your mailbox ;-) There are so many changes and fixes. The new cool features not to be missed are the realtime error underlinging and the tooltips for the file tabs, which gives you a preview of the file by the docstring. Mac users should upgrade as this fixed the most critical bug of SPE on Mac, the click inside selection crash. So just open the package and discover the present... :**New features**: - errors are underlined in red as you type (as preference) - tooltips on tabs showing path and docstring - drag and drop for script tabs - Edit>Show docstring (Ctrl+Shift+Space) - middle click pastes selected text - single instance application (enable it as preference) :**Improved features**: - file tabs (thanks to Andrea Gavana's NotebookCtrl) - add single click toggle for explore (not for Mac) - better code completion and docstring - dialog popup to confirm save before executing whole file - if signature not specified opens a choose file dialog - selected text is now always copied to the find dialog :**Fixes**: - clicking inside selection=deselect(no mac crash anymore) - launching debugger - removed unnecessary print statement - find in files clear behavior (by Thurston Stone) - ask to save before running a modified file - changed text 'save before run' to 'save before execute' - run with sys.executable (movable python) - info.PYTHON_EXEC to pythonw for Mac - __name__ in shell is now "__main__" for executing scripts - Kiki dialog box (by Andrea Gavana) - import sys when right version wxPython is not found **Changes**: - auto reload change file is off by default :**Contributors**: - Andrea Gavana - Thurston Stone - Bill Peterson (manual review) - Michael Foord (manual review) - Theo de Ridder (for a lot of suggestions & critical feedback) :**Donations**: - Ramon Diaz-Uriarte, http://ligarto.org/rdiaz (15 euro) - Dmeetry Raizman, Symula Inc, http://www.symula.com (20 dollar) Both donators received the SPE manual. :**Installation**: - See http://pythonide.stani.be/manual/html/manual2.html - There is now an update section for MacOS X! :**Development**: - http://developer.berlios.de/mail/?group_id=4161\ SVN 117 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 integrates with XRCed (gui designer) and ships with wxGlade (gui designer), PyChecker (source code doctor), Kiki (regular expression console) and WinPdb (remote, multi-threaded debugger). SPE is looking for people who can take screenshots for the new tutorial. The development of SPE is driven by its donations. Anyone who donates can ask for an nice pdf version of the manual without ads (60 pages). -- http://pythonide.stani.be http://pythonide.stani.be/screenshots http://pythonide.stani.be/manual/html/manual.html

1 0

Re: [Pythonmac-SIG] Linking against a Python extension
by Bob Ippolito Dec. 21, 2005

Dec. 21, 2005

> > bob(a)redivi.com schrieb am 20.12.2005 22:25:28: > >> > First question: Is it possible to link against a normally built Python >> > extension? >> > >> > More specifically, I want to pass the '.so' file of some Python > extension >> > as an extra link argument to the 'weave.inline' function. This seems >> to >> > work quite well on Linux. But I suspect, on Mac OS X the answer is > 'no'. >> > I just want this confirmed. >> >> No. That's not the right way to do it anyway, you need to make a table > of >> pointers available as a PyCObject or similar and get at it that way. > Look >> at how something like Numeric exports its interface. > > After some hours of googling, reading and blind trying I now (hopefully) > understand why: On OS X a Python extension is not a "shared object" (in > the > Linux sense) and not a dynamic library, but a (Mach-O) bundle, and a > Mach-O > bundle is more similar to an executable file than to an object file. In > particular: It cannot be input to the linker again. Dead end. Period. > Correct? Correct. I think it might be possible to use a MH_DYLIB as a Python extension just by implementation detail, but distutils doesn't link that way and you shouldn't. Using a table of function pointers is the only right way to share C functionality between Python extensions, despite what you're able to make work on one platform or another. -bob

1 0