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

CFM68K
by Thomas Tiemann June 17, 1997

June 17, 1997

I want to follow the instructions of CFM68K Mac and first I have to install CFM68K before I install Python. But I don't find a folder with the name "CFM68K for System Folder". So if I try to start Python 1.4 CFM68K my Computer crashed. Can you tell me, where I can find CFM68K for install? Thomas. _______________ 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] Re: 'alis' in AppleEvent
by Jack Jansen June 16, 1997

June 16, 1997

> > > The Precompile command requires a "Save_As" (alis) second argument. The > > trouble is that I can make an FSSpec of a file that does not exist yet, but > > I get a -43 error when I try to make an alias out of that FSSpec. I've > > worked around this for now so it's not a big deal. > > Hmm. I'll check whether I can let NewAlias succeed on -43 (file not found). I > do the same for FSSpec. Following up on my own post: this appears to be impossible. However, I have implemented NewAliasMinimalFromFullPath(), which is apparently the only way to create an alias to a non-existing file, and I've modified alias.Resolve() to allow fnfErr's. So, in 1.5 you'll be able to make an alias to a non-existing file. -- 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

Re: [PYTHONMAC-SIG] Re: 'alis' in AppleEvent
by Jack Jansen June 16, 1997

June 16, 1997

> The Precompile command requires a "Save_As" (alis) second argument. The > trouble is that I can make an FSSpec of a file that does not exist yet, but > I get a -43 error when I try to make an alias out of that FSSpec. I've > worked around this for now so it's not a big deal. Hmm. I'll check whether I can let NewAlias succeed on -43 (file not found). I do the same for FSSpec. This whole fsspec/alias/pathname business has me really confused. If I understand OSA correctly it should do automatic conversions, and they appear to work sometimes but alias records are the one case where they seem to fail. It could be that I do something wrong in the way I handle arguments, because in AppleScript it is no problem to pass, say, a pathname where an alias is expected by the receiving program. In Python this doesn't work, however:-( Has anyone got any light to shed on this? -- 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

Re: 'alis' in AppleEvent
by Doug Wyatt June 16, 1997

June 16, 1997

Oops, I answered my own question. The Precompile command requires a "Save_As" (alis) second argument. The trouble is that I can make an FSSpec of a file that does not exist yet, but I get a -43 error when I try to make an alias out of that FSSpec. I've worked around this for now so it's not a big deal. Doug ~~~~~~~~~~~~~~~~~~~~~~~~~ Hello, I'm trying to script CodeWarrior Pro 1's Precompile command, which takes an 'alis' as a direct argument. I have "path" which a full path to the source file as a string, and have tried various things like: from macfs import * def MakeAlias(f): fs = FSSpec(f) return fs.NewAlias() class CodeWarrior(aetools.TalkTo, MWPro1_ShellSuite.Metrowerks_Shell_Suite, etc): def DoPrecompile(self, path): self.Precompile(MakeAlias(path)) # error -1701 self.Precompile(path) # error -1701 I think it was The errors are coming in the AppleEvent return values. It looks like I haven't figured out how to give CW the right type of argument. I'm not terribly knowledgeable about AppleEvents and even less so about how they work in Python. But I'm willing to dig into this further and could use a tip about where to start looking at what the problem is. How and where do various Python data types get converted into the right AEDesc types? Thanks in advance. Doug --- Doug Wyatt music [,] software doug(a)sonosphere.com http://www.sonosphere.com/ new streaming audio samples: http://www.sonosphere.com/doug/music.html _______________ 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

'alis' in AppleEvent
by Doug Wyatt June 16, 1997

June 16, 1997

Hello, I'm trying to script CodeWarrior Pro 1's Precompile command, which takes an 'alis' as a direct argument. I have "path" which a full path to the source file as a string, and have tried various things like: from macfs import * def MakeAlias(f): fs = FSSpec(f) return fs.NewAlias() class CodeWarrior(aetools.TalkTo, MWPro1_ShellSuite.Metrowerks_Shell_Suite, etc): def DoPrecompile(self, path): self.Precompile(MakeAlias(path)) # error -1701 self.Precompile(path) # error -1701 I think it was The errors are coming in the AppleEvent return values. It looks like I haven't figured out how to give CW the right type of argument. I'm not terribly knowledgeable about AppleEvents and even less so about how they work in Python. But I'm willing to dig into this further and could use a tip about where to start looking at what the problem is. How and where do various Python data types get converted into the right AEDesc types? Thanks in advance. Doug --- Doug Wyatt music [,] software doug(a)sonosphere.com http://www.sonosphere.com/ new streaming audio samples: http://www.sonosphere.com/doug/music.html _______________ 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

New URL for Mac Python Programming Environment
by just＠knoware.nl June 6, 1997

June 6, 1997

I've relocated my MacPython IDE to: ftp://starship.skyport.net/pub/crew/just/PythonIDE.sit.hqx There's a link to it from my starship home page: http://starship.skyport.net/~just/ It's still the same version. I'm still intersted in feedback, also how it compares to the PythonWin IDE, which I don't know, since I have no access to Windows machines right now. Eventually it would be nice to combine the efforts, and make something that works and looks similar on both Mac and PC. 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

Need help compiling my extension
by zack＠lems.brown.edu June 4, 1997

June 4, 1997

Hello all, I'm home for a fews weeks and I would like to play with my Python extension PythonMagick. Unfortunately I don't have a compiler. Would someone compile a bare bones ImageMagick library and my extension and put it on the Starship ftp site? I know it is a lot to ask... Here are the urls for both distributions: Mac Sources for ImageMagick: ftp://ftp.wizards.dupont.com/pub/ImageMagick/mac/ImageMagick-3.8.6.sit.hqx Sources for PythonMagick: ftp://ftp.lems.brown.edu/pub/turtles/magick/pymagick-0.1a6.tar.gz I will be glad to credit/include project files, etc. hopefully-not-wishfully-thinkingly-yours-Zack _______________ 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] Incompatible change
by just＠knoware.nl June 3, 1997

June 3, 1997

At 1:18 PM 6/3/97, Jack Jansen wrote: >Sorry, what I meant with Add/Remove was that you could have multiple event >handlers. Ah, I see, sorry. I don't have a need for this now, and it might complicate things too much. Also, if you have one event handler in Python, you can always redirect them to the right package. >How about SetScheduleTimes? I didn't know about it until a couple of weeks ago, so I don't care ;-). 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

Re: [PYTHONMAC-SIG] Incompatible change
by just＠knoware.nl June 3, 1997

June 3, 1997

>> Hmm, I would like a callback function that gets called instead of >> MacOS.HandleEvent(), so I can do my own updates. > >Good idea. How about > MacOS.SetEventHandler(callable) Excellent! >where callable() is called for each event and should return non-zero if the >event is fully handled (otherwise the sioux and other handlers are called) be >good enough, or should I have AddEventHandler/RemoveEventHandler so that >different packages can all have their own event handlers? Could MacOS.SetEventHandler(None) be shorthand for RemoveEventHandler()? And MacOS.SetEventHandler(callable) would replace any previously installed handlers. >> And how about making the checkevents arg the event mask? 0 mask == no events. > >Ok. That was easy ;-). >> ... so I would prefer backward compatibility for now. > >Hmm. I see that it's harder to keep the old functionality alive, but since many people do not update right away, I'd like have some sort of mechanism to allow my code to run either in 1.4 or 1.5 (whenever that will be). I can think of a b/w compat hack myself, so if it would make coding the new functionality too much harder: get rid of the old stuff. Perhaps we (I) can write a little .py module that provides the b/w compatibility. At least you could leave a dummy MacOS.EnableAppswitch() function in, so that old code doesn't break right away. 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 1

Re: [PYTHONMAC-SIG] Incompatible change
by just＠knoware.nl June 3, 1997

June 3, 1997

At 2:07 PM 6/2/97, Jack Jansen wrote: >I'm planning to replace the rather unintellegible MacOS.SetScheduleTimes() and >MacOS.EnableAppSwitch() with a single call, probably something like > MacOS.SetEventLoop(checkabort, checkevents, checkinterval, yieldfg, > yieldbg) Hmm, I would like a callback function that gets called instead of MacOS.HandleEvent(), so I can do my own updates. And how about making the checkevents arg the event mask? 0 mask == no events. >- can I remove the old two calls or should I leave them for compatability? I use MacOS.EnableAppswitch() a lot, due to all the event problems with SIOUX, so I would prefer backward compatibility for now. 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 1