From sdm7g@virginia.edu Wed Oct 2 18:38:02 1996 From: sdm7g@virginia.edu (Steven D. Majewski) Date: Wed, 2 Oct 1996 13:38:02 -0400 (EDT) Subject: [PYTHONMAC-SIG] PowerPlant? In-Reply-To: <32486588.6FEA@inconnect.com> Message-ID: I'm resurrecting an old thread -- sorry I was out of town for a while ( visiting NIST for a non-Python workshop, but I managed to drop into Mike McLay's office to chat about Python developments for a bit! ): Re: GUI Frameworks. ODF (OpenDoc Framework) 2 has just been released for the Mac -- I haven't yet played with it, so I can't comment on how well it would fit into Python, but the plus is that it will be cross platform someday ( IBM, I believe, is doing the MS-Win port. ) and it supports drag&drop and embedding and other cool stuff. ( IBM has a beta of OpenDoc for AIX -- I don't know if they have done ODF. Sun and Apple have announced a new alliance to support QuickTime and some other technologies on SunOS -- perhaps this will hasten a Sun OpenDoc port. ) [ Now that I've got an alpha, on it's way to beta, of my xlisp-stat application, I hope to get some time to play with both MacPython and ODF/OpenDoc/CyberDog a bit. I'll post my impression once I've written a bit of code using ODF. I haven't programmed with CyberDog yet, either, but as a user, I have to say it's way cool! ] ---| Steven D. Majewski (804-982-0831) |--- ---| Computer Systems Engineer University of Virginia |--- ---| Department of Molecular Physiology and Biological Physics |--- ---| Box 449 Health Science Center Charlottesville,VA 22908 |--- [ "The grass is always greener, except at t=0" - Stan Kelly-Bootle ] ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From jdunning@mfactory.com Fri Oct 4 20:23:40 1996 From: jdunning@mfactory.com (John Dunning) Date: Fri, 4 Oct 1996 12:23:40 -0700 Subject: [PYTHONMAC-SIG] Python and Alpha? Message-ID: I was wondering if anyone had created a Python mode for Alpha. If you haven't heard of Alpha, I strongly suggest you check it out at http://www.cs.umd.edu/~keleher/alpha.html. It's a very powerful Mac text editor that is completely customizable using Tcl. It has various modes for C++, HTML, etc., which it uses for syntax coloring and so on. So I wanted to find one for Python. I also wanted to find out if anyone has looked at adding a simple DoScript AppleEvent to the Python shell. You can send an MPW script to ToolSever in a DoScript event and it then returns the shell's response. With this functionality it's possible to create a simple shell inside Alpha that would send scripts to Python and would give you much better editing capabilities while using Python in interactive mode. John ______________________________________________________________________________ John Dunning Interface Designer jdunning@mfactory.com ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From managan@llnl.gov Fri Oct 4 13:06:47 1996 From: managan@llnl.gov (Rob Managan) Date: Fri, 4 Oct 1996 13:06:47 +0100 Subject: [PYTHONMAC-SIG] Python and Alpha? In-Reply-To: Message-ID: John, On 9/16 Bill Bedford mailto:billb@mousa.demon.co.uk posted a preliminary python mode. I have attached what I am currently using.(only to John directly). It would be nice to be able to set up a menu like with CodeWarrior to send the current window to Python as a script to run. I don't know if the Python apps support that yet. The mode file could use a mark routine that strips off the arguments of a function so they don't show up in the popup menu. >I was wondering if anyone had created a Python mode for Alpha. If you >haven't heard of Alpha, I strongly suggest you check it out at >http://www.cs.umd.edu/~keleher/alpha.html. It's a very powerful Mac text >editor that is completely customizable using Tcl. It has various modes for >C++, HTML, etc., which it uses for syntax coloring and so on. So I wanted >to find one for Python. > >I also wanted to find out if anyone has looked at adding a simple DoScript >AppleEvent to the Python shell. You can send an MPW script to ToolSever in >a DoScript event and it then returns the shell's response. With this >functionality it's possible to create a simple shell inside Alpha that >would send scripts to Python and would give you much better editing >capabilities while using Python in interactive mode. > >John *-*-*-*-*-*-*-*-*-*-**-*-*-*-*-*-*-*-*-*-*- Rob Managan managan@llnl.gov LLNL ph: 510-423-0903 P.O. Box 808, L-178 FAX: 510-423-5804 Livermore, CA 94551-0808 ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From jeff@cynapses.com Sun Oct 6 22:30:49 1996 From: jeff@cynapses.com (jeffrey P. Shell) Date: Sun, 06 Oct 1996 15:30:49 -0600 Subject: [PYTHONMAC-SIG] Python mode on Alpha Message-ID: <32582509.5F9E@cynapses.com> Last time i tried Python mode in Alpha 6.5, i couldn't get ANYTHING to work really.. no colorizing or anything else was going on.. I like Alpha, but continue programming in BBEdit 3.5.2 (full). In Alpha i spend too much time trying to figure out Python mode and/or learning TCL and very little time actually programming.. :) But if a good Python mode that works could be passed my way, i think i'll get a clean copy of Alpha start over. This has also given me reason to toy with the notion of making my own Text editor in CodeWarrior (when i get it, hopefully this month) with embedded Python. But Alpha is so good already, i don't think i could make anything that would compare, so it would be more of an experiment in embedding Python. -- .jPS || jeff@cynapses.com || http://www.cynapses.com/ry/ ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From Jack.Jansen@cwi.nl Mon Oct 7 12:05:26 1996 From: Jack.Jansen@cwi.nl (Jack Jansen) Date: Mon, 07 Oct 1996 13:05:26 +0200 Subject: [PYTHONMAC-SIG] Python and Alpha? In-Reply-To: Message by John Dunning , Fri, 4 Oct 1996 12:23:40 -0700 , Message-ID: <9610071105.AA27748=jack@schelvis.cwi.nl> > I also wanted to find out if anyone has looked at adding a simple DoScript > AppleEvent to the Python shell. If you mean "have the Python react to the DoScript AppleEvent": this is underway. Just's Python engine that accompanies his BBEdit extension does just that, but with a private AppleEvent. I will fix this before the next release. If you mean "Implement a call in Python by which Python programs can send DoScript commands": the is easy to implement yourself. Check out the AppleEvent section of the Demo folder. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@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@python.org administrivia to: pythonmac-sig-request@python.org ================= From jstrout@ucsd.edu Wed Oct 9 01:16:33 1996 From: jstrout@ucsd.edu (Joseph Strout) Date: Tue, 8 Oct 1996 17:16:33 -0700 (PDT) Subject: [PYTHONMAC-SIG] faceless background applet? In-Reply-To: <9608221118.AA01171=jack@schelvis.cwi.nl> Message-ID: Ages ago, I wrote... > > Would anyone happen to know how I could make a Python applet faceless -- > > that is, run in the background, and not callable to the front? (I want to > > make a background server that casual users can't easily quit.) And Jack and I tried it, and it reliably crashed. Well, there's a new technote on background-only apps at: http://devworld.apple.com/dev/technotes/tn/tn1070.html ...the key things that I can see are: (1) The app must not call InitWindows(), InitMenus(), or any toolbox function that might draw on the screen (2) The app gets a stack size of only 2K, and must expand this itself if it will need more (which surely we would!). It doesn't seem like it would be too hard to comply with these... ideally, the MacPython main program would check its backgroundOnly bit, and if set, comply with the above requirements. (In addition, it is vital that the app respond to a Quit AppleEvent; otherwise, the Mac will refuse to shut down or restart.) This would be a very handy capability, allowing us to write faceless daemons in Python. ,------------------------------------------------------------------. | Joseph J. Strout Department of Neuroscience, UCSD | | jstrout@ucsd.edu http://www-acs.ucsd.edu/~jstrout/ | `------------------------------------------------------------------' ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From managan@llnl.gov Wed Oct 9 09:32:39 1996 From: managan@llnl.gov (Rob Managan) Date: Wed, 9 Oct 1996 09:32:39 +0100 Subject: [PYTHONMAC-SIG] plplot module Message-ID: Tom, I downloaded your plmodule and trimodule to look at. In particular I was interested in the plotting interface. The plmodule on your ftp server works with python lists. Has anyone written a version of it that works with array arguments from NumPy? The tutorial for your triangulation code sounded like it worked with NumPy arrays so I thought you might have a version for arrays. Anyone else written such a module? PS. I have the list oriented version working on my Mac, a 7600 and can send it to anyone interested. I hope to clean up the project files and send them off to the plplot archive. *-*-*-*-*-*-*-*-*-*-**-*-*-*-*-*-*-*-*-*-*- Rob Managan mailto://managan@llnl.gov LLNL ph: 510-423-0903 P.O. Box 808, L-178 FAX: 510-423-5804 Livermore, CA 94551-0808 ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From managan@llnl.gov Wed Oct 9 10:20:21 1996 From: managan@llnl.gov (Rob Managan) Date: Wed, 9 Oct 1996 10:20:21 +0100 Subject: [PYTHONMAC-SIG] UNIX files Message-ID: Just to hopefully save someone else difficulty: I learned today that on the Mac Python seems to ignore a script that has UNIX line endings. Unfortunately editors like Alpha read such files easily and you have to look closely to notice that the file uses unix line endings. So check those line endings when working with scripts from a package that are developed on a unix box! *-*-*-*-*-*-*-*-*-*-**-*-*-*-*-*-*-*-*-*-*- Rob Managan mailto://managan@llnl.gov LLNL ph: 510-423-0903 P.O. Box 808, L-178 FAX: 510-423-5804 Livermore, CA 94551-0808 ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From jstrout@ucsd.edu Wed Oct 9 18:51:34 1996 From: jstrout@ucsd.edu (Joseph Strout) Date: Wed, 9 Oct 1996 10:51:34 -0700 (PDT) Subject: [PYTHONMAC-SIG] UNIX files In-Reply-To: Message-ID: On Wed, 9 Oct 1996, Rob Managan wrote: > I learned today that on the Mac Python seems to ignore a script that has > UNIX line endings. Unfortunately editors like Alpha read such files easily > and you have to look closely to notice that the file uses unix line > endings. BBEdit too, and sure enough, this has caused me some problems. I've even found that when downloading scripts from a Unix host with Netscape, the line endings may not be converted (though you'd expect it to -- it must not realize that it's a text file...). Then you wonder why it won't run! Hmm, Jack, what would be required to make Python interpret Unix line endings, or at least recognize them and display a warning? ,------------------------------------------------------------------. | Joseph J. Strout Department of Neuroscience, UCSD | | jstrout@ucsd.edu http://www-acs.ucsd.edu/~jstrout/ | `------------------------------------------------------------------' ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From guido@CNRI.Reston.Va.US Wed Oct 9 19:08:49 1996 From: guido@CNRI.Reston.Va.US (Guido van Rossum) Date: Wed, 09 Oct 1996 14:08:49 -0400 Subject: [PYTHONMAC-SIG] UNIX files In-Reply-To: Your message of "Wed, 09 Oct 1996 10:51:34 PDT." References: Message-ID: <199610091808.OAA01187@monty> > Hmm, Jack, what would be required to make Python interpret Unix line > endings, or at least recognize them and display a warning? I'm not Jack, but I think there's only one or two places where modules are opened. I wonder if we could open the file in binary mode and if we detect a CR in the first 512 bytes, reopen it in text mode... The same hack should work for Windows! On Unix, don't do this at all. --Guido van Rossum (home page: http://www.python.org/~guido/) ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From jon@aggroup.com Wed Oct 9 23:07:46 1996 From: jon@aggroup.com (Jon Stevens) Date: Wed, 9 Oct 1996 14:07:46 -0800 Subject: [PYTHONMAC-SIG] UNIX files Message-ID: <9610091407.AA46196@jon.clearink.com> > I'm not Jack, but I think there's only one or two places where modules > are opened. I wonder if we could open the file in binary mode and if > we detect a CR in the first 512 bytes, reopen it in text mode... The > same hack should work for Windows! On Unix, don't do this at all. > > --Guido van Rossum (home page: http://www.python.org/~guido/) not really knowing how python reads in the files...would something like this work for you guys? --just trying to be slightly helpful..:) // this function gets one line from a file regardless of unix/mac/dos int getline ( char *s, FILE *in ) { int c, i =3D 0; while ( MAXLINE >=3D i ) { c =3D fgetc(in); if ( c =3D=3D EOF ) return 0; if ( c =3D=3D '\r' || c =3D=3D '\n' ) { s[i] =3D '\0'; return ( 1 ); } s[i] =3D c; i++; } return ( 0 ); } -jon Jon (no h) S. Stevens kid@latchkey.com ClearInk WebMagus http://www.clearink.com/ finger pgp@sparc.clearink.com for pgp pub key people in cars cause accidents accidents in cars cause people ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From just@knoware.nl Wed Oct 9 22:13:46 1996 From: just@knoware.nl (Just van Rossum) Date: Wed, 9 Oct 1996 22:13:46 +0100 Subject: [PYTHONMAC-SIG] UNIX files Message-ID: At 2:08 PM 10/9/96, Guido van Rossum wrote: >> Hmm, Jack, what would be required to make Python interpret Unix line >> endings, or at least recognize them and display a warning? > >I'm not Jack, but I think there's only one or two places where modules >are opened. I wonder if we could open the file in binary mode and if >we detect a CR in the first 512 bytes, reopen it in text mode... The >same hack should work for Windows! On Unix, don't do this at all. I once suggested something like that to Jack (right after my first encounter with the problem ;-) and he didn't sound too thrilled. I'd already be *very* happy if it would raise a more descriptive error, instead of the rather vague: File "DevDev:JustPy:unixfiletest.py", line 1 sys.stdo sys.stdout = s#raw_input("--usb2x, b2y)1y, a2x,lccu b1y = a1y + 2.0*(by- return b1x, b1y magic = calcQmagic(pi/2))/3 midx = radius:xoffset + radius * m b2y = yoffse + xoffsetdy = radius * cos(pi/4) + yoffset y = yost + radius * magic - radiusff print B1x, B1y, Boffset, yoffset, mx, midy, b1x, def b1y = yoffset x = b2xc():agic = ca print "def dra for i in ran x = ra print x, y, "l".5 * pi * (i+1)) / segmentsngle tprint "S"t = sys.stdoutsymain()u dr finally:", "w")e()c()ter-") ^ SyntaxError: invalid syntax Or something. (And it takes forever to print that, since python thinks the whole file is *one* line, and thinks it has to show the line with the Syntax error) Just ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From Jack.Jansen@cwi.nl Thu Oct 10 11:58:04 1996 From: Jack.Jansen@cwi.nl (Jack Jansen) Date: Thu, 10 Oct 1996 12:58:04 +0200 Subject: [PYTHONMAC-SIG] UNIX files In-Reply-To: Message by Guido van Rossum , Wed, 09 Oct 1996 14:08:49 -0400 , <199610091808.OAA01187@monty> Message-ID: <9610101058.AA26183=jack@schelvis.cwi.nl> > > Hmm, Jack, what would be required to make Python interpret Unix line > > endings, or at least recognize them and display a warning? > > I'm not Jack, but I think there's only one or two places where modules > are opened. I wonder if we could open the file in binary mode and if > we detect a CR in the first 512 bytes, reopen it in text mode... The > same hack should work for Windows! On Unix, don't do this at all. I was originally thinking about a solution in this vein, but I think that it is better to give an error. The problem with such an "accept everything" approach is that it will cause confusion in another place: when you open a unix textfile in your python program. My suggestion would be to make \r be illegal to the parser. There is currently code in tokenizer.c that explicitly turns \r into \n, if this were disabled (and a decent error message was given, such as "SyntaxError, \r in line (non-native text file?)" this problem would easily be catched. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@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@python.org administrivia to: pythonmac-sig-request@python.org ================= From guido@CNRI.Reston.Va.US Thu Oct 10 15:49:09 1996 From: guido@CNRI.Reston.Va.US (Guido van Rossum) Date: Thu, 10 Oct 1996 10:49:09 -0400 Subject: [PYTHONMAC-SIG] UNIX files In-Reply-To: Your message of "Thu, 10 Oct 1996 12:58:04 +0200." <9610101058.AA26183=jack@schelvis.cwi.nl> References: <9610101058.AA26183=jack@schelvis.cwi.nl> Message-ID: <199610101449.KAA03850@monty> > I was originally thinking about a solution in this vein, but I think that it > is better to give an error. The problem with such an "accept everything" > approach is that it will cause confusion in another place: when you open a > unix textfile in your python program. Hmm... This is really a problem with the CW stdio library -- it appears to *swap* CR and LF in text translation mode. If it just mapped CR to LF and left LF alone, we'd have no problems (until someone tries a DOS file, which will appear to be double-spaced). > My suggestion would be to make \r be illegal to the parser. There is > currently code in tokenizer.c that explicitly turns \r into \n, if > this were disabled (and a decent error message was given, such as > "SyntaxError, \r in line (non-native text file?)" this problem would > easily be catched. The only code I can find turns CR LF into LF, which would be fine to convert DOS files when read in binary mode. --Guido van Rossum (home page: http://www.python.org/~guido/) ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From Jack.Jansen@cwi.nl Thu Oct 10 16:59:45 1996 From: Jack.Jansen@cwi.nl (Jack Jansen) Date: Thu, 10 Oct 1996 17:59:45 +0200 Subject: [PYTHONMAC-SIG] UNIX files In-Reply-To: Message by Guido van Rossum , Thu, 10 Oct 1996 10:49:09 -0400 , <199610101449.KAA03850@monty> Message-ID: <9610101559.AA28598=jack@schelvis.cwi.nl> > Hmm... This is really a problem with the CW stdio library -- it > appears to *swap* CR and LF in text translation mode. If it just > mapped CR to LF and left LF alone, we'd have no problems (until > someone tries a DOS file, which will appear to be double-spaced). Actually, I quite like this behaviour... > The only code I can find turns CR LF into LF, which would be fine to > convert DOS files when read in binary mode. You're right, I didn't look well enough at the code. That means that the \r are passed through and ignored as whitespace sometime later. This means that we would probably need an explicit check for \r somewhere (provided I can convince you that an error is better than transparency in this case). Ok, let me know which behaviour people prefer and I'll implement it. (Of course, if there are votes to be taken the votes of some will weigh heavier than those of others:-) -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@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@python.org administrivia to: pythonmac-sig-request@python.org ================= From obsidian@shore.net Sat Oct 12 18:29:04 1996 From: obsidian@shore.net (Kevin Swope) Date: Sat, 12 Oct 1996 17:29:04 +0000 Subject: [PYTHONMAC-SIG] joining Message-ID: <325FD560.4388@shore.net> ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From Jack.Jansen@cwi.nl Sun Oct 13 22:30:08 1996 From: Jack.Jansen@cwi.nl (Jack Jansen) Date: Sun, 13 Oct 1996 23:30:08 +0200 Subject: [PYTHONMAC-SIG] Re: problem importing macurl2path.py In-Reply-To: Message by cmore@spdcc.com (Charles Morehead) , Sat, 12 Oct 1996 17:16:00 -0400 , Message-ID: <9610132130.AA27241=jack@schelvis.cwi.nl> Guido (and the rest of you), Charles Morehead just pointed out that the times returned by os.stat() aren't very useful, since they're mac-style unsigned longs (and, hence, currently negative). A possible solution would be to return them as floats, as all times are on the mac, but this will make stat() incompatible with unix for people who depend on the times being ints. What do you think? Any other solutions? -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@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@python.org administrivia to: pythonmac-sig-request@python.org ================= From guido@CNRI.Reston.Va.US Mon Oct 14 00:39:19 1996 From: guido@CNRI.Reston.Va.US (Guido van Rossum) Date: Sun, 13 Oct 1996 19:39:19 -0400 Subject: [PYTHONMAC-SIG] Re: problem importing macurl2path.py In-Reply-To: Your message of "Sun, 13 Oct 1996 23:30:08 +0200." <9610132130.AA27241=jack@schelvis.cwi.nl> References: <9610132130.AA27241=jack@schelvis.cwi.nl> Message-ID: <199610132339.TAA22795@monty> > Guido (and the rest of you), > Charles Morehead just pointed out that the times returned by os.stat() > aren't very useful, since they're mac-style unsigned longs (and, > hence, currently negative). A possible solution would be to return > them as floats, as all times are on the mac, but this will make stat() > incompatible with unix for people who depend on the times being ints. > > What do you think? Any other solutions? Making them floats sounds like a good idea -- after all, time.time() also returns a float (and for exactly the same reason!). --Guido van Rossum (home page: http://www.python.org/~guido/) ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From billpy@mail.demon.net Mon Oct 14 18:52:05 1996 From: billpy@mail.demon.net (Bill Bedford) Date: Mon, 14 Oct 1996 17:52:05 +0000 Subject: [PYTHONMAC-SIG] Q: How To Tell The Finder To Launch An App With A Doc? In-Reply-To: Message-ID: At 1:19 am +0000 18/09/96, Just van Rossum wrote: ~Although this is not a Python specific question, I hope you don't mind ~asking here. It's still Python related. ~ ~In my BBEdit extension in which I can send Python code to the interpreter I ~would like to give a prompt when the slave script is not running, asking ~the user to locate it and then: Launch The Interpreter With The Script. ~I am told I have to send an AppleEvent to the Finder to do this, but I've ~crawled through most of the stuff on my Inside Mac CD and I Can't Bleedin' ~Find It. Does anyone know what event to send? Or what else to do? I think ~Jack would also like to know, so we can also make a convenient call for ~this in Python / aetools.py. No More Connection Invalid Errors. Please? ~ I've just spent the whole weekend trying to do this and at last Eureka!!!!! You can use talker = Finder(FINDERSIG) talker.open(f) but you have to remember that FINDERSIG="MACS" Then everything works Duh - Talk about a blinding glimpse of the bleedin' obvious ----------------------------------------------------------------------- Bill Bedford Designer of Photo-Etches billb@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@python.org administrivia to: pythonmac-sig-request@python.org ================= From managan@llnl.gov Tue Oct 15 10:40:22 1996 From: managan@llnl.gov (Rob Managan) Date: Tue, 15 Oct 1996 10:40:22 +0100 Subject: [PYTHONMAC-SIG] plplot module Message-ID: I have been working on the Mac version of the plplot module. I have a library that works fine in a C program. It seems to work fine in Python as well. The problem is that after the python script is done and I quit the interpreter that I drop into the debugger with the message PowerPC unmapped memory exception at FFD60E6C PtInRect+0008 Any ideas of what went wrong? How could plplot be messing up? I logged some Macsbugs results and got this: Disassembling PowerPC code from FFD60E44 MapRect +00018 FFD60E44 addic r3,r3,0x0004 | 30630004 +0001C FFD60E48 lwz r4,0x0038(SP) | 80810038 +00020 FFD60E4C lwz r5,0x003C(SP) | 80A1003C +00024 FFD60E50 bl MapPt ; 0xFFD60D54 | 4BFFFF05 +00028 FFD60E54 lwz r12,0x0048(SP) | 81810048 +0002C FFD60E58 addic SP,SP,0x0040 | 30210040 +00030 FFD60E5C mtlr r12 ; LR = 0x0008 | 7D8803A6 +00034 FFD60E60 blr | 4E800020 PtInRect +00000 FFD60E64 li r0,0x0000 | 38000000 +00004 FFD60E68 sth r0,0x0D6E(0) | B0000D6E +00008 FFD60E6C *lha r5,0x0000(r4) | A8A40000 +0000C FFD60E70 srawi r6,r3,0x10 | 7C668670 +00010 FFD60E74 cmpw r6,r5 | 7C062800 +00014 FFD60E78 lha r5,0x0004(r4) | A8A40004 +00018 FFD60E7C stw r3,0x0018(SP) | 90610018 +0001C FFD60E80 cmpw cr1,r6,r5 | 7C862800 +00020 FFD60E84 bge PtInRect+0002C; 0xFFD60E90 | 4080000C +00024 FFD60E88 clrlwi r3,r0,0x18 | 5403063E +00028 FFD60E8C blr | 4E800020 Calling chain using A6/R1 links Back chain ISA Caller 00000000 PPC 0557E218 04384F80 PPC 0557E178 04384F40 PPC 0593A964 PyMac_InitApplication+00088 04384DF0 PPC 0593B18C Py_Main+00270 04384D80 PPC 0590746C PyRun_AnyFile+0004C 04384D40 PPC 059075A8 PyRun_InteractiveLoop+000E8 04384CF0 PPC 059076C8 PyRun_InteractiveOne+000D0 04384C80 PPC 05907068 PyParser_ParseFile+00090 04384C30 PPC 05907114 parsetok+0006C 04384BC0 PPC 058EB6B4 PyTokenizer_Get+00054 04384B60 PPC 058EAF9C tok_nextc+000F0 04384B00 PPC 058F5484 PyOS_Readline+00080 04384AB0 PPC 058F5380 my_fgets+00028 04384A70 PPC 059621B4 fgets+000CC 04384A20 PPC 05963958 _Frprep+0010C 043849E0 PPC 0596AF10 _Fread+00024 043849A0 PPC 05948B3C read+000A8 04384950 PPC 0595EA34 SIOUXSocket::read(void*, int)+00030 04384910 PPC 0596CAA0 ReadCharsFromConsole+00130 043848B0 PPC 0595F9BC exit+00068 04384860 PPC 0595FA04 _exit+00024 04384810 PPC 059787D8 __destroy_global_chain+0002C 043847D0 PPC 0594AA6C SocketTable::~SocketTable()+00044 04384780 PPC 0595F7E4 fwalk+00040 04384730 PPC 05961D9C fclose+00040 043846E0 PPC 059431F8 free+00040 04384690 PPC 05942F3C botch+00020 04384650 PPC 0596241C fprintf+0003C 04384610 PPC 05965B00 _Printf+000A8 04384540 PPC 059623AC fopen+00110 04384500 PPC 05962AFC fwrite+00134 043844A0 PPC 05961F8C fflush+0009C 04384450 PPC 0596B040 _Fwrite+000B4 04384400 PPC 05949070 write+0005C 043843B0 PPC 0594B140 GUSIDefaultSpin+001C8 *-*-*-*-*-*-*-*-*-*-**-*-*-*-*-*-*-*-*-*-*- Rob Managan mailto://managan@llnl.gov LLNL ph: 510-423-0903 P.O. Box 808, L-178 FAX: 510-423-5804 Livermore, CA 94551-0808 ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From doug@sonosphere.com Tue Oct 15 19:44:17 1996 From: doug@sonosphere.com (Doug Wyatt) Date: Tue, 15 Oct 1996 14:44:17 -0400 Subject: [PYTHONMAC-SIG] plplot module In-Reply-To: Message-ID: At 10:40 +0100 10/15/96, Rob Managan wrote: > I logged some Macsbugs results and got this: > Calling chain using A6/R1 links > Back chain ISA Caller > 00000000 PPC 0557E218 > 04384F80 PPC 0557E178 > 04384F40 PPC 0593A964 PyMac_InitApplication+00088 > 04384DF0 PPC 0593B18C Py_Main+00270 > 04384D80 PPC 0590746C PyRun_AnyFile+0004C > 04384D40 PPC 059075A8 PyRun_InteractiveLoop+000E8 > 04384CF0 PPC 059076C8 PyRun_InteractiveOne+000D0 > 04384C80 PPC 05907068 PyParser_ParseFile+00090 > 04384C30 PPC 05907114 parsetok+0006C > 04384BC0 PPC 058EB6B4 PyTokenizer_Get+00054 > 04384B60 PPC 058EAF9C tok_nextc+000F0 > 04384B00 PPC 058F5484 PyOS_Readline+00080 > 04384AB0 PPC 058F5380 my_fgets+00028 > 04384A70 PPC 059621B4 fgets+000CC > 04384A20 PPC 05963958 _Frprep+0010C > 043849E0 PPC 0596AF10 _Fread+00024 > 043849A0 PPC 05948B3C read+000A8 > 04384950 PPC 0595EA34 SIOUXSocket::read(void*, int)+00030 > 04384910 PPC 0596CAA0 ReadCharsFromConsole+00130 > 043848B0 PPC 0595F9BC exit+00068 > 04384860 PPC 0595FA04 _exit+00024 > 04384810 PPC 059787D8 __destroy_global_chain+0002C > 043847D0 PPC 0594AA6C SocketTable::~SocketTable()+00044 > 04384780 PPC 0595F7E4 fwalk+00040 > 04384730 PPC 05961D9C fclose+00040 > 043846E0 PPC 059431F8 free+00040 > 04384690 PPC 05942F3C botch+00020 > 04384650 PPC 0596241C fprintf+0003C > 04384610 PPC 05965B00 _Printf+000A8 > 04384540 PPC 059623AC fopen+00110 > 04384500 PPC 05962AFC fwrite+00134 > 043844A0 PPC 05961F8C fflush+0009C > 04384450 PPC 0596B040 _Fwrite+000B4 > 04384400 PPC 05949070 write+0005C > 043843B0 PPC 0594B140 GUSIDefaultSpin+001C8 Looks like the malloc pool is corrupt, as evidenced by free() calling botch(), which is apparently trying to write to the console while it's being closed. Speaking of GUSI, I'm having no luck at all with it -- the FTP class seems to hang in reads, then _Fread gets into a bad state where it's counting down from 0xFFFFFFFF. Oh well. Doug -- Doug Wyatt software development, Opcode Systems Inc. doug@opcode.com http://www.sonosphere.com/doug/ ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From Jack.Jansen@cwi.nl Wed Oct 16 08:58:45 1996 From: Jack.Jansen@cwi.nl (Jack Jansen) Date: Wed, 16 Oct 1996 09:58:45 +0200 Subject: [PYTHONMAC-SIG] plplot module In-Reply-To: Message by Doug Wyatt , Tue, 15 Oct 1996 14:44:17 -0400 , Message-ID: <9610160758.AA22625=jack@schelvis.cwi.nl> Doug is right, I think. It looks as if you're freeing a file structure that has already been freed. The 1.4b3 distribution has a number of patches to GUSI, have you applied these? I remember a similar crash in the exit code, but I can't remember what I did exactly to fix it, but the patches did seem to fix it. You can also try running Python under CW Debug and setting a breakboint at malloc.c:botch(). The you might be able to find out what it is that is double-freed. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@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@python.org administrivia to: pythonmac-sig-request@python.org ================= From doug@sonosphere.com Wed Oct 16 16:39:13 1996 From: doug@sonosphere.com (Doug Wyatt) Date: Wed, 16 Oct 1996 11:39:13 -0400 Subject: [PYTHONMAC-SIG] Re: GUSI In-Reply-To: <9610160758.AA22625=jack@schelvis.cwi.nl> References: Message by Doug Wyatt , Tue, 15 Oct 1996 14:44:17 -0400 , Message-ID: At 9:58 +0200 10/16/96, Jack Jansen wrote: > The 1.4b3 distribution has a number of patches to GUSI, have you applied > these? I remember a similar crash in the exit code, but I can't remember >what > I did exactly to fix it, but the patches did seem to fix it. Jack, I looked around a bit in the 1.4b3 distribution for something labelled as a patch to GUSI (I have CWGUSI 1.80) but didn't find anything. Are there GUSI source files to be modified? Or does one only have to take care that the linker uses the Python version of some routines instead of GUSI's? Please elaborate. Thanks, Doug -- Doug Wyatt software development, Opcode Systems Inc. doug@opcode.com http://www.sonosphere.com/doug/ ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From doug@sonosphere.com Wed Oct 16 17:41:46 1996 From: doug@sonosphere.com (Doug Wyatt) Date: Wed, 16 Oct 1996 12:41:46 -0400 Subject: No subject Message-ID: <199610161641.MAA22115@light.lightlink.com> ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From doug@sonosphere.com Wed Oct 16 17:40:51 1996 From: doug@sonosphere.com (Doug Wyatt) Date: Wed, 16 Oct 1996 12:40:51 -0400 Subject: No subject Message-ID: <199610161640.MAA22091@light.lightlink.com> ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From Jack.Jansen@cwi.nl Thu Oct 17 10:49:14 1996 From: Jack.Jansen@cwi.nl (Jack Jansen) Date: Thu, 17 Oct 1996 11:49:14 +0200 Subject: [PYTHONMAC-SIG] Re: GUSI In-Reply-To: Message by Doug Wyatt , Wed, 16 Oct 1996 11:39:13 -0400 , Message-ID: <9610170949.AA03563=jack@schelvis.cwi.nl> > > The 1.4b3 distribution has a number of patches to GUSI, have you applied > > these? I remember a similar crash in the exit code, but I can't remember > >what > > I did exactly to fix it, but the patches did seem to fix it. > > I looked around a bit in the 1.4b3 distribution for something labelled as a > patch to GUSI (I have CWGUSI 1.80) but didn't find anything. You're right: I didn't do the GUSI mods until after the 1.4b3 distribution. They are mods relative to GUSI 1.7.2. I will get the 1.8 distribution, see whether it still needs the mods and include them in the forthcoming 1.4 release. Is the code that exhibits the bug easily isolated? If so I would like a copy to test it here... -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@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@python.org administrivia to: pythonmac-sig-request@python.org ================= From doug@sonosphere.com Thu Oct 17 16:47:10 1996 From: doug@sonosphere.com (Doug Wyatt) Date: Thu, 17 Oct 1996 11:47:10 -0400 Subject: [PYTHONMAC-SIG] Re: GUSI Message-ID: At 11:49 +0200 10/17/96, Jack Jansen wrote: > > > The 1.4b3 distribution has a number of patches to GUSI, have you applied > > > these? I remember a similar crash in the exit code, but I can't remember > > >what > > > I did exactly to fix it, but the patches did seem to fix it. > > > > > I looked around a bit in the 1.4b3 distribution for something labelled as a > > patch to GUSI (I have CWGUSI 1.80) but didn't find anything. > > You're right: I didn't do the GUSI mods until after the 1.4b3 distribution. > They are mods relative to GUSI 1.7.2. I will get the 1.8 distribution, see > whether it still needs the mods and include them in the forthcoming 1.4 > release. > > Is the code that exhibits the bug easily isolated? If so I would like a copy > to test it here... Yes, I did the following (this is from memory, I don't want to crash my Mac at the moment): from ftplib import FTP x = FTP() x.set_debuglevel(2) x.connect("anyoldhost", 21) # FTP_PORT = 21 Somewhere in here the TCP receive routines would hang waiting for a long time (despite some of the server's welcome text getting printed), and _Fread would get into the bad state of counting down from 0xFFFFFFFF. Thanks for looking into this. Doug -- Doug Wyatt software development, Opcode Systems Inc. doug@opcode.com http://www.sonosphere.com/doug/ ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From Jack.Jansen@cwi.nl Fri Oct 18 09:29:27 1996 From: Jack.Jansen@cwi.nl (Jack Jansen) Date: Fri, 18 Oct 1996 10:29:27 +0200 Subject: [PYTHONMAC-SIG] Re: GUSI In-Reply-To: Message by Doug Wyatt , Thu, 17 Oct 1996 11:47:10 -0400 , Message-ID: <9610180829.AA13668=jack@schelvis.cwi.nl> > > from ftplib import FTP > x = FTP() > x.set_debuglevel(2) > x.connect("anyoldhost", 21) # FTP_PORT = 21 > > Somewhere in here the TCP receive routines would hang waiting for a long > time (despite some of the server's welcome text getting printed), and > _Fread would get into the bad state of counting down from 0xFFFFFFFF. No problem here, it works fine. One change I made since the 1.4b3 distribution is that I changed all the makefile('r') to makefile('rb') in ftplib.py, maybe that makes a difference? -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@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@python.org administrivia to: pythonmac-sig-request@python.org ================= From uzs90z@ibm.rhrz.uni-bonn.de Wed Oct 23 00:48:43 1996 From: uzs90z@ibm.rhrz.uni-bonn.de (Michael Schuerig) Date: Wed, 23 Oct 1996 01:48:43 +0200 Subject: [PYTHONMAC-SIG] OSA version of Python? Message-ID: Does an OSA (i.e. Open Scripting Architecture) version of Mac Python exist or is somebody working on one? Michael ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From Jack.Jansen@cwi.nl Wed Oct 23 10:43:57 1996 From: Jack.Jansen@cwi.nl (Jack Jansen) Date: Wed, 23 Oct 1996 11:43:57 +0200 Subject: [PYTHONMAC-SIG] OSA version of Python? In-Reply-To: Message by "Michael Schuerig" , Wed, 23 Oct 1996 01:48:43 +0200 , Message-ID: <9610230943.AA00933=jack@schelvis.cwi.nl> > > Does an OSA (i.e. Open Scripting Architecture) version of Mac Python exist > or is somebody working on one? Many people have expressed interest in OSA-python, but I don't have the time to look into it. Maybe some people on the list could form a taskforce and see how much work it would be? -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@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@python.org administrivia to: pythonmac-sig-request@python.org ================= From Jack.Jansen@cwi.nl Mon Oct 28 12:37:03 1996 From: Jack.Jansen@cwi.nl (Jack Jansen) Date: Mon, 28 Oct 1996 13:37:03 +0100 Subject: [PYTHONMAC-SIG] Macintosh distributions of Python 1.4 available Message-ID: <9610281237.AA10767=jack@schelvis.cwi.nl> The Macintosh distributions of Python 1.4 are available at (and they will probably show up at ftp.python.org sometime this or next week). There are 4 distributions available: PPC, Classic 68K, CFM68K and source. The CFM68K distribution (which has the same shared code model as the PPC distribution and allows use of dynamically loaded modules and applets in Python) is the preferred distribution for 68K macs, the classic distribution is only meant for people who cannot run cfm68k on their machine. In addition, for people with old machines with little memory there is a "lite" version of the classic interpreter, without tkinter and img support. Main mac-specific differences with the 1.4b4 distribution (aside from bug fixes) are a different preference file handling, AppleScript server support (and, hence, an initial framework for writing CGI scripts in Python) and interfaces to let the finder start applications for you, copy files, etc. The Relnotes-1.4 file has full details. The distributions do not include the numeric and pil extensions, I will ship these separately. And, as proscribed by the Python Distribution Dictum "Thou shalt plan great voyages mere seconds after releasing a distribution": I will be gone to Athens for a few days. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@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@python.org administrivia to: pythonmac-sig-request@python.org ================= From jeff@cynapses.com Tue Oct 29 16:32:20 1996 From: jeff@cynapses.com (jeffrey P. Shell) Date: Tue, 29 Oct 1996 09:32:20 -0700 Subject: [PYTHONMAC-SIG] MacPython 1.4 bug! Message-ID: <32763194.17C4@cynapses.com> eep! found a nasty nasty nasty li'l bug in MacPython 1.4 (CFM68k): .pyc files are messed up. here's the story: I got MacPython 1.4 yesterday, and noticed a way cool speed improvement in SIOUX. I was wanting to profile some code i was working on (the Pummel project) and wrote a small test function in the source file so i could Profile it. But the test function wasn't showing up in the interpreter at all, wether i quit and restarted and imported the module, or wether i did reload(module). So, i scrapped all my .pyc files in the directory i was working in and lo! it showed up. "No biggie," i thought, "just a change in releases changed the .pyc format". But now, all the new .pyc files were of type/creator TEXT/ttxt (Simpletext). (But, the new .pyc files being generated in the lib directory were of the correct type/creator). I ran all the profiler stuff, and went back to working on the source. I decided to test something: i changed a __version__ reference in one of my modules. Then i reloaded the interpreter and imported that module. when i tried to print the __version__, i got "0.6b1", the old value (in the .pyc file). i kept the interpreter open and trashed the .pyc file and did a reload(module), and printed the __version__ and got "0.6b2". Is anyone else having problems with this? of course, Jack would have to run to Athens for a few days.. -- .jPS || jeff@cynapses.com || http://www.cynapses.com/ry/ ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From sdm7g@virginia.edu Tue Oct 29 17:48:02 1996 From: sdm7g@virginia.edu (Steven D. Majewski) Date: Tue, 29 Oct 1996 12:48:02 -0500 (EST) Subject: [PYTHONMAC-SIG] Building WxPyMac & WxPython Message-ID: Ok -- I've gotten and built Python-1.4 for Mac ( I haven't tested it with Tcl 7.6 and Tk 4.2 yet ) and I've built the WxPyMac161 (d-a5 release) library. Are there any notes on how to build Python with the WxPyMac library ? ---| Steven D. Majewski (804-982-0831) |--- ---| 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@python.org administrivia to: pythonmac-sig-request@python.org ================= From sdm7g@virginia.edu Tue Oct 29 22:23:30 1996 From: sdm7g@virginia.edu (Steven D. Majewski) Date: Tue, 29 Oct 1996 17:23:30 -0500 (EST) Subject: [PYTHONMAC-SIG] Drag & Drop ? In-Reply-To: Message-ID: Anyone tried to write a Drag and Drop applet in Mac Python ? My guess is that it can be done using the MacOS high level event functions, but I haven't yet figured it out. If anyone has already done this and has an example at hand, please post! I'ld like to convert one of my file conversion scripts so I can just drop a folder full of files onto it. ---| Steven D. Majewski (804-982-0831) |--- ---| 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@python.org administrivia to: pythonmac-sig-request@python.org ================= From managan@llnl.gov Tue Oct 29 15:35:30 1996 From: managan@llnl.gov (Rob Managan) Date: Tue, 29 Oct 1996 16:35:30 +0100 Subject: [PYTHONMAC-SIG] MacPython 1.4 & Numeric Python Message-ID: Has anyone built version 1.4 from the source? I have had a few problems. the file macgetpath.c references GUSILoadConfiguration which is not resolved. I guess this means that Jack modified the standard GUSI distribution since this routine is not in the CWGUSI distribution. I do have NumPy working with the 1.4b3 release if anyone wants it. *-*-*-*-*-*-*-*-*-*-**-*-*-*-*-*-*-*-*-*-*- Rob Managan mailto://managan@llnl.gov LLNL ph: 510-423-0903 P.O. Box 808, L-178 FAX: 510-423-5804 Livermore, CA 94551-0808 ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From jeff@cynapses.com Wed Oct 30 01:05:53 1996 From: jeff@cynapses.com (jeffrey P. Shell) Date: Tue, 29 Oct 1996 18:05:53 -0700 Subject: [PYTHONMAC-SIG] Drag & Drop ? References: Message-ID: <3276A9F1.4CB9@cynapses.com> > Anyone tried to write a Drag and Drop applet in Mac Python ? In 1.4b3, all elements Dropped into an applet were treated as sys.argv[1:], just like you had passed them on a command line. The build i have (jack's) of 1.4 is acting too goofy to try this out.. i know that 1.4 is supposed to allow some different options (at least that's what i gather from one of the README files, but don't quote me) :). -- .jPS || jeff@cynapses.com || http://www.cynapses.com/ry/ ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From Steven D. Majewski" Message-ID: On Tue, 29 Oct 1996, jeffrey P. Shell wrote: > > Anyone tried to write a Drag and Drop applet in Mac Python ? > > In 1.4b3, all elements Dropped into an applet were treated as > sys.argv[1:], just like you had passed them on a command line. > > The build i have (jack's) of 1.4 is acting too goofy to try this out.. I'm not (yet) seeing any of the problems you described. Although I'm in the midst of rebuilding Mac Python from sources, I'm using Jack's PPC binaries. ( Are you sure you replaced the Python Core alias in the extensions folder, and ran the mkplugin aliases applet? ) Anyway -- thanks for the tip -- its very simple and it *ALMOST* works! ;-) It seems to only work for TEXT files - but what I was working on was a binary data to text converter applet, so no luck. If you drop a non text file onto the applet, it doesn't hilight or respond. If you select a bunch of files, it seems to only catch the text files, and ignore the others. ---| Steven D. Majewski (804-982-0831) |--- ---| 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@python.org administrivia to: pythonmac-sig-request@python.org =================