🌐 Mailman 3 November 2001 - Pythonmac-SIG - python.org

Problem making Python2.2 on OS 10.1.1
by Robin B. Lake Nov. 22, 2001

Nov. 22, 2001

"make"-ing python gives: cc -u __dummy -u _PyMac_Error -framework System -framework CoreServices -framework Foundation -o python \ Modules/python.o \ libpython2.2.a /usr/bin/ld: can't create output file: python (Is a directory, errno = 21) make: *** [python] Error 1 Any clues, please? Thanks, Rob Lake lake(a)cwru.edu

2 1

Re: [Pythonmac-SIG] Embedding in code resource
by Jack Jansen Nov. 21, 2001

Nov. 21, 2001

Recently, Jason Harper <JasonRandHarper(a)compuserve.com> said: > Running an interactive loop isn't the problem, it's what happens > afterwards... When my plug-in is deselected by the user, I need to clean= > ly > finalize the interpreter (free at least most of its memory, close the SIO= > UX > console if it was opened, etc.), and let the parent application continue > running. Py_Exit() and PyMac_Exit() eventually call exit(), and I'm not > sure that can be avoided anyway - it appears that SIOUX's cleanup is done= > > by an atexit() handler. Ah, sorry, now I understand. As to the main interpreter state: Py_Finalize() should clean up most things. What then remains to be cleaned up is stdio, GUSI, SIOUX and thereby the console window. Hmm, this doesn't seem to be simple. MSL's exit() does a lot of useful things, like cleaning up global chains and stdio and such. But: MSL has an __atexit() function (same signature as atexit), and these handlers are called really really late in the cleanup process, just before ExitToShell(). So maybe registering such a handler would help? But beware that at this point all sorts of useful things (like C++ global chain for destroying objects) have been cleaned up beyond repair, so you should probably immedeately unload your plugin. An alternative might be to call __stdio_atexit() to clean up stdio. This should also clean up GUSI, I think. And I think the cleanup is done in such a way that things might be re-initializable again. However, any file opened with os.open() or socket.socket() will probably stay open.... -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.cwi.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm

1 0

Re: [Pythonmac-SIG] Embedding in code resource
by Jason Harper Nov. 21, 2001

Nov. 21, 2001

Jack Jansen wrote: > what you want to do is probably > PyMac_Initialize(); > PyRun_AnyFile(stdin_for_python, "<stdin>"); > I think this should never call exit(), but always return. > > Depending on how your code resource is linked against PythonCore you may be > able to do simply "stdin" for stdin_for_python, but it could also be more work > to get at that. Running an interactive loop isn't the problem, it's what happens afterwards... When my plug-in is deselected by the user, I need to cleanly finalize the interpreter (free at least most of its memory, close the SIOUX console if it was opened, etc.), and let the parent application continue running. Py_Exit() and PyMac_Exit() eventually call exit(), and I'm not sure that can be avoided anyway - it appears that SIOUX's cleanup is done by an atexit() handler. I guess what I really need is a way to intercept the exit() in PythonCore before it can exit the parent application. Jason Harper

1 0

Hiding embedded Python console - revisited
by Paul Miller Nov. 21, 2001

Nov. 21, 2001

I was wondering if someone has found a reliable way to disable the Python console that appears after calling PyMac_Initialize()? I have hooked my own I/O functions and I don't want the console to appear at all. -- Paul T. Miller | paul(a)fxtech.com | http://www.fxtech.com

1 0

Problems with Findertools in OS x v.10.1.1? (Move)
by Schollnick, Benjamin Nov. 21, 2001

Nov. 21, 2001

I'm using a file copy routine that I just finished, and started to notice some oddities... Namely the findertools.move () command appears to work, but is returning an exception....... This may have just started with OS X v10.1.1, but I'm not positive... I just booted back to OS v9.21 and do *NOT* see this problem occuring there... So it's certainly an Mac OS X issue... Since the file copy does appear to work, I may have missed it when I added the exception coding.... (It appears to work so maybe I just wasn't observant enough). Anyone else notice this? - Benjamin def move_file ( old_path, new_path, filename ): try: if os.path.exists (new_path + os.sep + filename): Ask = EasyDialogs.AskYesNoCancel("Duplicate File Detected (%s), Overwrite?" % filename, default = 1, yes=None, no=None, cancel=None, id=262) if Ask == 1: if mac_mode: # Overwrite, by removing the old file # os.remove(new_path + os.sep + filename) elif Ask == 0: # # Do not overwrite, end routine, by returning # return 0 elif Ask == -1: # # Abort program, return error code # return -1 if mac_mode: findertools.move (old_path + filename, new_path) print old_path + filename, " --> Moved.." except: print "error" return None # of Files found : 6 filename : WAITING.JPG filename : WALL filename : WALL_1.JPG ------------------------------------- old: OS v9.1:Desktop Folder:python work:test: new: OS v9.1:Desktop Folder:python work:test:Wall filename: WALL_1.JPG old + file: OS v9.1:Desktop Folder:python work:test:WALL_1.JPG Traceback (most recent call last): File "OS v9.1:Desktop Folder:python work:re-dup-file.py", line 104, in ? move_file ( pathname, new_dir, filename ) File "OS v9.1:Desktop Folder:python work:re-dup-file.py", line 53, in move_file findertools.move (old_path + filename, new_path) File "OS v9.1:Applications (Mac OS 9):Python 2.1.1:Mac:Lib:findertools.py", line 74, in move return finder.move(src_fss, to=dst_fss) File "OS v9.1:Applications (Mac OS 9):Python 2.1.1:Mac:Lib:lib-scriptpackages:Finder:Standard_Suite.py", line 293, in move raise aetools.Error, aetools.decodeerror(_arguments) aetools.Error: (0, 'component result = no error', None)

1 0

Re: [Pythonmac-SIG] Embedding in code resource
by Jack Jansen Nov. 21, 2001

Nov. 21, 2001

> I'm trying to embed MacPython (Classic) in a plug-in code resource for > another application. Basically, I need to be able to start up an > interactive interpreter, let the user play around in it, then exit cleanly > to the calling application. I had little difficulty getting the first part > of that working, by linking against PythonCore and calling > PyMac_Initialize, etc. However, there's a big problem when trying to > return - all ways of exiting the interpreter seem to eventually involve a C > exit() call, which is a complete disaster from a code resource. Does > anyone know of a way to get the interpreter to exit cleanly to its caller? what you want to do is probably PyMac_Initialize(); PyRun_AnyFile(stdin_for_python, "<stdin>"); I think this should never call exit(), but always return. Depending on how your code resource is linked against PythonCore you may be able to do simply "stdin" for stdin_for_python, but it could also be more work to get at that. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.cwi.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm

1 0

Embedding in code resource
by Jason Harper Nov. 21, 2001

Nov. 21, 2001

I'm trying to embed MacPython (Classic) in a plug-in code resource for another application. Basically, I need to be able to start up an interactive interpreter, let the user play around in it, then exit cleanly to the calling application. I had little difficulty getting the first part of that working, by linking against PythonCore and calling PyMac_Initialize, etc. However, there's a big problem when trying to return - all ways of exiting the interpreter seem to eventually involve a C exit() call, which is a complete disaster from a code resource. Does anyone know of a way to get the interpreter to exit cleanly to its caller? The only solution I could think of was to register an atexit() handler (registered before any Python calls were made, so it should therefore execute after all of Python's atexit() handlers had run) that did a longjmp() back to my code. This crashed my machine hard, although I haven't yet tried to figure out why (I don't think this can possibly work more than once anyway, and I need to allow the user to invoke my plug-in multiple times). Jason Harper

2 1

Re: [Pythonmac-SIG] Python & MPW ToolServer
by Jack Jansen Nov. 21, 2001

Nov. 21, 2001

Wow, that's a very useful routine! Is it OK if I add it to the distribution? -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.cwi.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm

2 1

XDarwin, Python and Tkinter
by Patrick Curtain Nov. 19, 2001

Nov. 19, 2001

Hello All! Has anyone gotten a build of python working that taps into the Tcl/Tk (via Tkinter) under XDarwin (rootless X Windows on Aqua)? Haven't been able to myself, several compile errors. Mostly I'm looking to see if it's been done yet or I'm out at the bleed. :-) God Bless! --p Patrick Curtain, Husband & Father (i also write software) SWDev, Co. 503 781 6199 patrick(a)swdev.com

4 5

Native Tk/TCL on MacOSX.
by Kelvin Chu Nov. 16, 2001

Nov. 16, 2001

Greetings, MacPythonians. I've installed the latest Tcl/Tk from Tk.sf.net which has built-in Aqua support on MacOSX. I'm currently running Python from the fink build, but I can dl the source. My question is: How can I get python to use the Tk bundle that has just been released? Do I need to rebuild Python? We're one step closer to getting reasonable applications now... Thanks for read this and for any suggestions you have. -k -- kelvin.chu(a)uvm.edu (802) 656-0064 http://www.uvm.edu/~kchu/ FAX: (802) 656-0817

1 0