🌐 Mailman 3 December 1999 - Pythonmac-SIG - python.org

Re: [Pythonmac-SIG] reposting: Q: emulating os.system() on macs?
by Jack Jansen Dec. 2, 1999

Dec. 2, 1999

> [BTW, the application I need to run is nsgmls, a SGML-based validator > (http://www.jclark.com/sp/). ] And are you going to port nsgmls yourself, or is it already available for the mac? If you're doing the port yourself you could think of wrapping the whole thing up in a Python extension module, so you don't have to fire up a separate program at all. If you have a port of nsgmls and it understands the "Open Document" Appleevent you can use the applescript modules to first ask the finder to open the application (see aetools.TalkTo for sample code) and then use the standard scripting methods to ask the application to open the file (an example is in the Mac:Demo folder). And if nsgmls has a nice unique signature you can even skip the first step if your input file has the correct creator: send the "open document" command to the finder and it'll open the app as well. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.oratrix.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm

1 0

Re: [Pythonmac-SIG] console vs. BuildApplication
by Jack Jansen Dec. 2, 1999

Dec. 2, 1999

> On 12/2/99 6:20 AM, Jack Jansen wrote: > > > Just that we're talking about the same thing: you do understand that the > > console will pop up as soon as you write something to it > > Yes, I understand that. This very same code works as expected when run as > an applet. Hmm, interesting. Could you have a look at the GU<sigma>I resources in both the working applet and nonworking application? Both should be the same, and have resource ID 10241. I'm asking this because the only thing I can think of right now is that somehow your application didn't get a 10241 GU<sigma>I resource but a 10240 one, which is overridden by any preferences setting you have. For the curious, and for the record as I don't think this process is documented anywhere yet: for all resources (python path initialization, options, gusi options) we search four places and use the first match: 1. Preference file, override resource ID 2. Application, override resource ID 3. Preference file, normal resource ID 4. Application, normal resource ID The first one doesn't normally find anything, the second one finds EditPythonPrefs settings in the applet/application, the third one finds system-wide EditPythonPrefs settings and the last one finds the "factory defaults" in the interpreter. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.oratrix.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm

1 0

Re: [Pythonmac-SIG] reposting: Q: emulating os.system() on macs?
by Jack Jansen Dec. 2, 1999

Dec. 2, 1999

I'm afraid this is impossible, as MacOS has no concept of stdin/stdout/stderr. You can make this work for some applications, on a per-application basis, but there is no general solution. If you can give some details on the program you're trying to execute someone here may be able to come up with a solution that'll work for this particular case. > I'm in the process of planning to port a Python application that > is being developed on Linux to the Mac. One of the many questions I > have is how to emulate in Python/Mac something like: > > > def doit(infile, outfile, errfile, exefile): > """ > execute "exefile" on "infile" and write "outfile" and "errfile" > """ > cmd = '%s < "%s" > "%s" 2> "%s"'%(exefile, infile, outfile, errfile) > os.system(cmd) > return (outfile, errfile) -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.oratrix.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm

2 1

Re: [Pythonmac-SIG] console vs. BuildApplication
by Jack Jansen Dec. 2, 1999

Dec. 2, 1999

> I have built a python/tk application using the BuildApplication utility and > it appears that the console window cannot be hidden when using applications > built in this manner. I have specified the "Delay console window until > needed" option for the application but the console still comes up when the > application launches. This wouldn't be all that annoying if it at least > came up in behind the tk window. Is there an alternate method used to hide > the console for python applications? Hmm, strange. Just that we're talking about the same thing: you do understand that the console will pop up as soon as you write something to it or read from it, even with the "hidden until needed" bit on? It may be that someone is writing to it, somewhere, which you could circumvene by redirecting stdin/stdout/stderr somewhere. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.oratrix.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm

2 1

Re: [Pythonmac-SIG] not very Standard_Suite
by Jack Jansen Dec. 2, 1999

Dec. 2, 1999

I don't fully understand how OSA inheritance works, so that's why the current scheme is a bit clumsy. The inheritance _is_ specified in the various Inside Mac chapters, so if someone cares to implement this correctly: please be my guest. I think the inheritance goes something like 1. If you declare the suite without any content you get the standard one. 2. If you put content in you have to add empty placeholders for all things you want to inherit as-is. 3. For anything you want to modify (add extra optional parameters, for instance) you have to fully specify it. This could be implemented in Python with a bit of redesign: currently the suite name is used both as module name and class name, but you should use the suite name as class name only and the application name as module name. Then you could do something like # File CodeWarrior.py import Applescript class Standard_Suite(Applescript.Standard_Suite): ... override anything you want ... -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.oratrix.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm

1 0

console vs. BuildApplication
by Anthony M. Ingraldi Dec. 1, 1999

Dec. 1, 1999

Hello, I have built a python/tk application using the BuildApplication utility and it appears that the console window cannot be hidden when using applications built in this manner. I have specified the "Delay console window until needed" option for the application but the console still comes up when the application launches. This wouldn't be all that annoying if it at least came up in behind the tk window. Is there an alternate method used to hide the console for python applications? -- Tony Ingraldi A.M.INGRALDI(a)LaRC.NASA.GOV Phone : (757) 864-3039 Fax : (757) 864-7892

1 0

not very Standard_Suite
by Erik van Blokland Dec. 1, 1999

Dec. 1, 1999

hello, I've been playing around with gensuitemodule and ran into something odd. Gensuitemodule creates a Standard_Suite.py file for each application it wraps. I assumed that this file was the same as the Standard_Suite.py included in the python distribution at Python 1.5.1:Mac:Lib:lib-scripting:Standard_Suite.py and I threw the newly generated Standard_Suite in favor of the standard-python-standard-suite. Then I discovered several missing methods and a bunch of missing constants. I needed to import functionality from both Standard_Suites: I regenerated the new one, renamed it. Then my final object inherits from both and it seems to work. But it's a bit clumsy. Does each application have it's own ideas about what is needed in a Standard_Suite? are there more elegant ways of dealing with this? erik van blokland -- letterror

1 0