Mailman 3 August 1997 - Pythonmac-SIG

Graphing capablility in Mac Python
by Anthony M. Ingraldi Aug. 23, 1998

Aug. 23, 1998

Hello, Is there a module available that will provide routines for creating simple line graphs and scatter plots? I was thinking of using AppleEvents to send data to KaleidaGraph or some other package but that seems sluggish. Another alternative would be to use a Canvas widget from Tk. I would prefer to use a module designed specifically for plotting rather than writing one via Tkinter. -- Tony Ingraldi | e-mail: A.M.INGRALDI(a)LaRC.NASA.GOV NASA Langley Research Center | Mail Stop 267 | Phone : (757) 864-3039 Hampton, VA 23681-0001 | Fax : (757) 864-7892 _______________ 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 _______________

3 3

Re: [PYTHONMAC-SIG] daemons on the Mac
by Jack Jansen Sept. 3, 1997

Sept. 3, 1997

Well, I tried your script under 1.5a3 (which'll be available to PSA members sometime this week) and it works fine (even with the listen(0)). It also doesn't eat CPU time and is responsive to events when in the foreground. The whole event handling in the mainloop has been revamped for 1.5a3, so I'd definitely like feedback if people still find funny behaviour with it... As to FBA's: I can't get them to work. Is anyone on the list familiar with writing them? I think the problem is related either to someone (Sioux? Python itself?) trying to install a menubar or someone calling WaitNextEvent. Does anyone happen to know whether either of these is illegal for FBA's? Also: is there a runtime call I can do to see whether I run as a FBA or a normal application (so I can try to refrain from any illegal behaviour when running an FBA-applet)? (In case it helps: my FBA *does* create an entry in the applications menu, but it is an empty entry, i.e. without a name. Trying to select the entry means immedeate death to your system). Once we can write FBA's in Python the only hurdle left is device drivers:-) -- 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

Re: [PYTHONMAC-SIG] AppleEvent question
by Jack Jansen Aug. 30, 1997

Aug. 30, 1997

Recently, "Anthony M. Ingraldi" <A.M.INGRALDI(a)larc.nasa.gov> said: > Hello, > > I am working with AppleEvents to use gnuplot. Is there a way to launch an > application via AppleEvents without bringing it to the front? (That is the > way it works in UserLand Frontier.) Unfortunately not, currently. The reason is that there's no Python interface to the process manager at the moment (anyone willing to write one? I can help with the bgen-stuff, if needed), so to launch the application we use the finder. This has the side-effect of bringing the application to the front. -- 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 _______________

5 5

QuickTime and CFM68k?
by Just van Rossum Aug. 27, 1997

Aug. 27, 1997

Dear all, Importing Qt fails on my CFM68k machine in Python 1.4 and both 1.5 alfas: >>> import Qt Traceback (innermost last): File "<stdin>", line 1, in ? ImportError: QuickTimeLib: library name not found in Frag registry >>> (It *does* work with 1.4/1.5 stand-alone) I tried AltaVista, and found similar questions, although they didn't seem CFM68k specific (or at least were not specified as such). The answers were just a tad useless, like: something's wrong with QuickTime... Anyway, I would be grateful if other CFM68k users could tell me whether Qt works for them (a non-failing "import Qt" would suffice ;-). I am running MacOS 7.6.1 on a Quadra 840 AV with QuickTime 2.5 and QuickTime PowerPlug installed (although I'm almost certain that the latter doesn't help me, since it is a PPC extension...). Thanks for any clues. Just _______________ 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

My email address has changed
by Jay Koutavas Aug. 22, 1997

Aug. 22, 1997

Please change the destionation of my pythonmac-sig email from jay(a)tinkeri.com to jay(a)heynow.com. Thanks, /Jay ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' Jay Koutavas mailto:jay@tinkeri.com Tinkeri, Inc. http://www.tinkeri.com Windham, NH, USA ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' _______________ 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

Re: [PYTHONMAC-SIG] Compiling PythonCorePPC
by Jack Jansen Aug. 21, 1997

Aug. 21, 1997

> Hi, > > I'm in serious trouble, I try to compile PythonCorePPC using the CodeWarrior Pro and I getting a lot of link errors that I can not resolve. > > Does anyone succeed compiling PythonCorePPC using CodeWarrior Pro IDE 2.01? This is not easy: CW Pro uses the new MSL libraries, and quite some things have to be changed for that (not really in Python, mostly in GUSI, but a few minor things in Python too). The easiest thing to do is to wait for Python 1.5 beta, which'll probably be out within months. Or Python 1.5a3 if you're a PSA member, which'll be out in one or two weeks, I hope. If you really need it now: either load the obsolete ANSI libraries from the CodeWarrior CD and link with that, or revert to CW10 or CW11 (again with the obsolete ANSI libraries). -- 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

Compiling PythonCorePPC
by Robert Viens Aug. 20, 1997

Aug. 20, 1997

Hi, I'm in serious trouble, I try to compile PythonCorePPC using the CodeWarrior Pro and I getting a lot of link errors that I can not resolve. Does anyone succeed compiling PythonCorePPC using CodeWarrior Pro IDE 2.01? Jack please help me! / Robert Viens (viens(a)pubnix.net) / / 2675, Préfontaine / / Robert Viens consultant enr. / / Montréal (Québec) / / (514) 527-4296 / / Canada H1W 2P6 / / Fax (514) 524-9214 Paget: (514) 330-9446 / _______________ 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

Re: [PYTHONMAC-SIG] Planning The Installer for MacPython 1.5
by Jack Jansen Aug. 20, 1997

Aug. 20, 1997

> With "Custom Install" we can separate everything into packages (with the > Lite version we'll have to use, we can't make sub packages). > Does it make sense to do this? And if yes, what do you think of the > following subdivision: > > - interpreter + core (also makes prefs file) > - all "plug ins" (also makes plug in aliasses) > (some pseudo sub-packages? overkill?) > - toolboxmodules (Qd, Res, Win, the lot) > - _tkinter > - waste > - img > - ... what else? A minimal install needs at least toolboxmodules, all of Lib and Mac:Lib to be remotely useful. Things that could be factored out are img and Tk, and some tiny things like waste, gdbm, icconfig. I don't think I'm in favor of leaving things out, though, the diskspace used isn't all that big, if you don't use them you don't pay for them and having them available will get people to play with them. What I can imagine that we include optionally are the two "common" extensions pil and numpy. -- 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

Planning The Installer for MacPython 1.5
by Just van Rossum Aug. 19, 1997

Aug. 19, 1997

Hi, We're in the process of getting a free licence for MindVision's installer package, and I have a good feeling that this is going to work out. Many thanks to Jeffrey C. Ollie for pointing us toward MindVision, it seems a great package, much easier to use than StuffIt InstallerMaker. Anyway, I have volunteered to set it up, and (when the license works out) am starting to plan it. There's a couple of things I am not so sure about, so I'd like your opinion. The installer would has two main options, "Easy Install" and "Custom Install". Question number one: should the "Easy Install" install fat binaries by default or binaries for the system we're installing to? What is usual? With "Custom Install" we can separate everything into packages (with the Lite version we'll have to use, we can't make sub packages). Does it make sense to do this? And if yes, what do you think of the following subdivision: - interpreter + core (also makes prefs file) - all "plug ins" (also makes plug in aliasses) (some pseudo sub-packages? overkill?) - toolboxmodules (Qd, Res, Win, the lot) - _tkinter - waste - img - ... what else? - library - tools (EditPythonPrefs, MakeApplet, applet template, scripts, ...?) - demos (:Demo & :Mac:Demo ?) - ... what else? Is this handy? Thanks for any feedback, Just _______________ 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 3

Re: [GUSI] Working directories under MacOS 8
by Matthias Ulrich Neeracher Aug. 16, 1997

Aug. 16, 1997

Jack Jansen <Jack.Jansen(a)cwi.nl> writes: >I just got an error report which seems to indicate that GUSI's working >directory code stopped working under MacOS 8. It appears that getcwd() >returns the correct path, but open() will always try to open >something in the disk toplevel folder. I've been running 100% on MacOS8 (b5 and final) in the last few months and have run fairly extensive Perl tests without observing this phenomenon. However, this behaviour is similar to what I have seen on CFM68K machines when linking GUSI programs with the Metrowerks-provided version of PLStringFuncs for CFM68K (which is severely broken). Matthias ----- Matthias Neeracher <neeri(a)iis.ee.ethz.ch> http://www.iis.ee.ethz.ch/~neeri "One fine day in my odd past..." -- Pixies, _Planet of Sound_ _______________ 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