🌐 Mailman 3 May 1997 - Pythonmac-SIG - python.org

Re: [PYTHONMAC-SIG] Mac SWIG & dynamic loading MacPython modules
by Jack Jansen May 29, 1997

May 29, 1997

> > > Has anyone gotten MacSWIG to work with dynamically loaded Python > modules ? I keep getting link problems with the global "__file" > variable, which I assume, should not be exported from PythonCorePPC, > but should be part of the main program address space. It should definitely be exported from PythonCorePPC, otherwise you can't use stdio in your extension. The trick is that you should put PythonCorePPC *before* the C library in your link sequence, so that the __file symbol (and any other shared global data) is resolved from PythonCorePPC. This is documented somewhere, but the fact that I can't find it right now suggests that it might be stated a bit more clearly:-) -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)cwi.nl | ++++ if you agree copy these lines to your sig ++++ http://www.cwi.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm _______________ PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org _______________

1 0

Mac SWIG & dynamic loading MacPython modules
by Steven D. Majewski May 28, 1997

May 28, 1997

Has anyone gotten MacSWIG to work with dynamically loaded Python modules ? I keep getting link problems with the global "__file" variable, which I assume, should not be exported from PythonCorePPC, but should be part of the main program address space. Do I have to take out all of the fprintf's in the wrapper module to get it to work ? Is there an option to do this automagically ? ---| Steven D. Majewski (804-982-0831) <sdm7g(a)Virginia.EDU> |--- ---| Department of Molecular Physiology and Biological Physics |--- ---| University of Virginia Health Sciences Center |--- ---| P.O. Box 10011 Charlottesville, VA 22906-0011 |--- By doing just a little every day, you can gradually let the task completely overwhelm you. _______________ PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org _______________

1 1

Announce: A Python Programming Environment for Macintosh (alpha)
by just＠knoware.nl May 27, 1997

May 27, 1997

Dear Python People, I've put a binhexed & stuffed file at: ftp://starship.skyport.net/pub/mac/just/PythonIDE.sit.hqx I'll be away for the next week starting tomorrow way too early, so if you find terrible problems with it, let me know *now* ;-). I will respond to other feedback as soon as I get back. Please give it a try, it's pretty cool! Here follows the readme: Python Integrated Developement Environment for the Macintosh alpha 2 -- codenamed "Bruce" copyright 1997 Just van Rossum, Letterror -- just(a)knoware.nl May 27, 1997 This is the first public release of my stab at a Python programming environment for the Mac. There is still a lot on my wishlist, but I feel it can do enough to justify a release. I'd appreciate any feedback. It features a Python Interactive window, an integrated editor, an object browser, a module browser and a very cool traceback window. I hope to integrate Jack's debugger (TWIT) in a next release. Installation You need Python 1.4 installed; either the PPC, CFM68k or 68k Classic distibution will do. The 68k Small verion will *not* do. Set the interpreter's memory segment to at least 10 megs. (Note for MacOS 7.6.1 CFM68k users: startup might fail with an "ImportError: DragLib: library name not found in Frag registry" error message. You need to install NuDragLib. Mail me if you have trouble finding it) Unpack the archive with StuffIt expander. The unpacked folder may live anywhere, you don't need to edit sys.path. Leave it's contents alone however. Double-click PythonIDE.py. Startup time is a bit long, this should improve when I am able to distribute a semi-self-contained fat-applet under Python 1.5. Python Interactive Window This looks and feels as much as possible like the Python interpreter in interactive mode, minus the SIOUX bugs. It has undo, and the window remembers its size and position (and whether it was left open or not) between sessions. If it's not open when you start, look at the Windos menu. The Editor The are two buttons at the top: Run window and Run selection. The latter expands the selection to whole lines and then runs it. This means that you can only execute snippets at the top level of a module. I'm thinking of making this a bit more tolerant somehow. An edit window has its own namespace. However if a module with a name that matches the window's title has already been imported, the code will be executed in that module's namespace. Which effectively means that if you run such a window, it is equivalent to reload(module). The editor has borrowed some features and shortcuts of BBEdit, like indent/undent. Find & replace shortcut are BBEdit-ish as well. It indents automatically after a colon. There is a popupmenu at the right top side of the edit window which currently has only one entry: Font Settings. It does what you expect. It is not yet possible to set the default font for new windows. At the bottom on the left you find two more items of interest: a field showing the current line number (click on it to enter a different line number, then tab or enter or return or click elsewhere to jump) and a popup menu pointing to all function, class and method definitions in the module. For very big modules it might take some time before the menu gets drawn, especially on slower machines. I find it acceptable on my 68040, however. The Traceback Window Whenever an exception is raised (except in the Python interactive window, this might have to change), instead of the usual printout of the traceback you will be presented with a traceback window, with all stack frames neatly presented in a list. For each entry (stack frame) you can either open the file with the editor (which will jump to the corresponding line) or browse the local variables for that stack frame. There is currently also the option to browse the stack frame itself, but I have *never* used it so far, so I think I'm going to drop that feature. The Module Browser Here you'll find a list of all currently imported modules (= sys.modules). For builtin modules (or shared libs) there's the option to browse the module; for modules written in Python it allows you to open the module with the editor or reload it. An additional option is Open Other, which will give you a prompt to enter a module name (without .py). After you click OK sys.path will be searched for it. When successful, it opens it with the Editor. The Object Browser This is a browser I wrote quite some time ago, it works nicely (except for the still not functioning Update button). I have plans to rewrite it completely, and make it look more like CodeWarriors variable browser (with finder-like foldout arrows). You can start the browser in three different ways: - choose Browse Objects from the Python menu, this will start at sys.modules - choose Browse for one or more modules in the Module Browser - choose Browse Locals in a traceback window Menus Not much to say about the menus, but do check the Windows menu. Widgets All of the windows in the environment (except for the object browser, which is kindof obsolete) are built with a set of widgets, collected in the module W. You'll find some (mostly undocumented) demos in the WidgetsDemos folder. ModuleBrowser.py is a more serious example, while still not overly complex. Don't look at PyEdit.py, it's a mess. The widgets have a very simple interface, with a smart coordinate system (no grid yet, though). I will write up some docs for this at some point. The Python Font I have designed a bitmap font to do all my coding with. It's called Python-Sans. Originally (before it got it's current name, about 10 years ago) I made it as a replacement for Geneva 9 pt, to do Pascal coding. Even if you would rather die than use a proportional font for coding (you can choose a different one...), I recommend you to install it (drop it on the System Folder), since all user interface elements are sort of tuned to it. If you don't, it will default to Geneva, and everything will look a little less slick. Wishlist & Random notes - Intelligent filters for files that use spaces or spaces and tabs for indentation. Right now the editor is rather dumb about this issue. - Get rid of SIOUX (or at least I want to be able to *not* show it) - sys.stdin emulation. Currently SIOUX is still handling that. It's not great, but it works. - Default font settings for edit windows - being able to change tab settings, unfortunately this is currently not possible with the WASTE library. - Double clicking does not work the way I like it. Same problem as tab settings: hard to do with WASTE. - Syntax coloring (working on it!) - Save as Applet, with an option to semi-automatically collect modules. (freeze's findmodules.py would be excellent start for this, but it's not in the Mac distribution!) - A debugger. It's basically there: Jack's wonderful TWIT, but I'd like to adapt the look and feel to my app (= redesign the user interface) - Profiler -- A simple profiler stats window with sort options would be nice. - Modularize function like PTUI. Turn a script into a module. - Run window in __main__. (This to allow to run modules which contain the magic if __name__ == '__main__': etc. code.) Licence I am still pondering what exactly to do with it. For now: You *cannot* re-distribute it without my permission. This release lives exclusively at: ftp://starship.skyport.net/pub/mac/just/PythonIDE.sit.hqx If you have questions, feel free to email me at just(a)knoware.nl. Thank-you's I'd like to thank my Big Brother Guido and MacPython guru Jack Jansen for always being so patient with me. Also many thanks to Erik van Blokland and his Big Brother Petr for many early input and testing. Dooooh! Enjoy! Just van Rossum _______________ PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org _______________

1 0

AppleEvent "every"
by Bill Bedford May 23, 1997

May 23, 1997

I am working on an expanded findertools module, and would like to include the ability to get/set the property of every object. As in the applescript : get name of every disk. When I look at the ae that this script sends "every" is represented by seld:abso(«616C6C20») Can any one tell me what this long represents? Or where I can find more about it? I don't recall seeing anything in Inside Mac. Thanks. ----------------------------------------------------------------------- Bill Bedford Designer of Photo-Etches billb(a)mousa.demon.co.uk owner Brit_Rail-L --- british railways historical list ----------------------------------------------------------------------- _______________ PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org _______________

1 1

Re: [PYTHONMAC-SIG] MacPython serial IO
by Jack Jansen May 23, 1997

May 23, 1997

> > > Is anyone doing serial com-port I/O with MacPython ? > > How are you doing it ? > Is there an interface other than the Connection Manager module ? I use the CTB connection manager, and it works fine. There were one or two bugs in it at the time of 1.4 (one serious one, a memory leak), the fixed version will be in 1.5 (or let me know if you need it earlier and I can send you the sources). -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)cwi.nl | ++++ if you agree copy these lines to your sig ++++ http://www.cwi.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm _______________ PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org _______________

1 0

MacPython serial IO
by Steven D. Majewski May 22, 1997

May 22, 1997

Is anyone doing serial com-port I/O with MacPython ? How are you doing it ? Is there an interface other than the Connection Manager module ? ---| Steven D. Majewski (804-982-0831) <sdm7g(a)Virginia.EDU> |--- ---| Department of Molecular Physiology and Biological Physics |--- ---| University of Virginia Health Sciences Center |--- ---| P.O. Box 10011 Charlottesville, VA 22906-0011 |--- By doing just a little every day, you can gradually let the task completely overwhelm you. _______________ PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org _______________

1 0

calldll
by Steven D. Majewski May 22, 1997

May 22, 1997

There doesn't seem to be a external interface to get the names in the symbol table from calldll -- is that correct ? I'm giving calldll a try to use for debugging a third party device driver that isn't too well documented. If it works I'm sure I'll write something up about it, but while doing that, I realized that finding the symbols in a dynamic library is a useful programmers tool. Is there any standard tool that does this ? in Code Warrior or MPW ? When I last had to do this, I used the :verbose switch in my XlispStat CFM import module, which prints out the symbol table, but doesn't give you a list that you can do something with. If there is no tool that does this already, I may try to hack it into Jack's calldll -- either give it a __dict__ , or add a method to return the symbol table entries. ( Any comments Jack ? ) ---| Steven D. Majewski (804-982-0831) <sdm7g(a)Virginia.EDU> |--- ---| Department of Molecular Physiology and Biological Physics |--- ---| University of Virginia Health Sciences Center |--- ---| P.O. Box 10011 Charlottesville, VA 22906-0011 |--- By doing just a little every day, you can gradually let the task completely overwhelm you. _______________ PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org _______________

1 0

Re: [PYTHONMAC-SIG] apps freeze unless they print!
by Jack Jansen May 19, 1997

May 19, 1997

Joe, this has been reported before. It'll be fixed in the next release, until then the print is a workaround. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)cwi.nl | ++++ if you agree copy these lines to your sig ++++ http://www.cwi.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm _______________ PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org _______________

2 1

apps freeze unless they print!
by Joseph J. Strout May 19, 1997

May 19, 1997

I'm suddenly finding that Python locks up under the following conditions: I have a program in a loop which is working very hard (or snoozing) for a long time without printing anything to the console window (sample code below); I switch to the Finder or any other app; then I switch back -- presto, it's frozen. By "frozen" I mean that the window is not refreshed, I can't move it, and I can't switch back to the Finder or any other app; I have to hit command-period or kill the Python process. Perhaps the Mac guts are only being updated whenever the console window is updated. But I don't really want to clutter up my nice log window with useless garbage (and system.out.write('') doesn't work either, I tried it!). Is there any other way to trigger the Mac event-handling parts? I'm using Python 1.4 PPC, on a PowerBase 180 running MacOS 7.5.5. Sample code: ---------------------------------------------------------------------- from time import sleep t=0 while t < 9999: sleep(1) #print t # if this line is included, it works t = t+1 ---------------------------------------------------------------------- Any suggestions will be greatly appreciated! -- Joe ,------------------------------------------------------------------. | Joseph J. Strout Department of Neuroscience, UCSD | | jstrout(a)ucsd.edu http://www-acs.ucsd.edu/~jstrout/ | `------------------------------------------------------------------' _______________ PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org _______________

4 4

Python as CGI scripting language
by pr1＠club-internet.fr May 19, 1997

May 19, 1997

Has anybody succeeded in using Python as a CGI language? If so, how did you do it? The instructions provided in the PythonMac package did not help me much. I am using WebStar as server software. Many thanks. Philippe de Rochambeau ______________________________________________________________________________ Philippe de Rochambeau pr1(a)club-internet.fr _______________ PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org _______________

1 0