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

setting up python
by tomtom Dec. 13, 1999

Dec. 13, 1999

hope these newbieish questions arent inappropriate for the list: i have installed python 1.52c1 (had the beta before that) some days ago. i had done some scripting involving the string and os modules and those work. however, today i tried doubleclicking some demos and the tkinter demos didnt work: they cant find the Tkinter module for some reason. it lives in the tk-lib in the lib and the lib *is* in the pythonpath (i checked it). do i have to separately put the path to lib:tk-lib there? i wanna be careful with those paths (pathes? path'th?) cause i dont want to foul anything up.. thought i'd rather ask. another question (maybe thats really a piddle question, dunno..): i installed piddle and put it in the pythonpath. some of the testing stuff gives me: cant find module 'w'. i dont know what that module is and if it belongs to piddle or not.. some of the piddle testing stuff that writes pdf does work and writes it to python.out until the window kindof overflows and starts flashing in a wild way. i guess i should redirect the output.. is there something mac-pythonish about doing that or should i read about it in the general docs? thanks for being patient.. Ni! lukas

2 1

Re: [Pythonmac-SIG] newbie's Q
by Jack Jansen Dec. 13, 1999

Dec. 13, 1999

> hello,all > I am a newbie to mac python. > when I double click a module in whatever folder > the interpreter says to me it can't find the module. > for example. > Double click $PYTHON:Lib:binhex.py > > --->PythonInterpreter:: can't open file 'binhex.py:' This is very strange. Try rebuilding your desktop to see whether that makes a difference. Also, could you give us the exact error message if it still fails after the desktop rebuild? And could you try dragging-and-dropping the .py file to the interpreter, to see whether that gives the same error message as double-clicking? -- 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] just one apple event
by Jack Jansen Dec. 13, 1999

Dec. 13, 1999

> I don't think I stated my problem clearly. Once I build modules with > gensuitemodule.py I am able to make the call as I (more or less) > normally would. But I am left with several k of python code that I > don't necessarily need or want. Somewhere in the files created by > gensuitemodule.py Python sends the appleevent "misc, dosc, > "----":"workspace.foo", &tran:63464" to "LAND". That event is > identical to the one sent by the applescript one liner I can write to > do this job except for the &tran which is replaced with &subj:'null'() > > For instance, in UserTalk (which bears a striking resemblance to > Python) there is the following call: appleevent("LAND", "misc", > "dosc", "----", "workspace.foo") which is pretty self explanatory. The gensuitemodule stuff is all meant to isolate you from these low-level details. If you want to do the lowlevel stuff yourself (but be aware that you're also responsible for argument conversion and such) you can do it like this: dummy, rv, dummy2 = aetools.Talker("LAND").send("misc", "dosc", {"----":"workspace.foo"}) rv will again be a dictionary mapping 4-char keys to return values. You may want to add the optional start=1 argument (to fire up the app if needed) to the Talker call. -- 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

just one apple event
by Dante Dec. 13, 1999

Dec. 13, 1999

I've been working with aetools and gensuitemodule.py trying to get Python to work smoothly with a scriptable app. It hasn't been going very well. What I truly desire is to be able to write a function to send an application ONE appleevent. I have gleaned the information I need from MacOS with CaptureAE and a one line applescript. So where in this mess of tools do I go to be able to do this? Dante _________________________________________________________ Dante - dante(a)oz.net - #FightThePower on Openprojects

2 3

Re: [Pythonmac-SIG] SWIG and making extension modules
by Jack Jansen Dec. 10, 1999

Dec. 10, 1999

> I have successfully used SWIG to wrap the Processor Manager > functions. At this time I have really only tested the > GetProcessInformation and the MacGetCurrentProcess functions. I set > this up to see how hard it would be to use SWIG for this purpose. > Mainly I wanted to be able to get the process name, Signature, and > active time. > > It turns out that it is not as easy to use as I would like. However, > it does give you a lot of flexibility. The main problems revolve > around trying to use the special objects that Jack provides for > things like FSspec pointers and OSTypes... I want to clean it up a > little and add some documentation and then hope to make it available. This is one of the reasons I've always stayed away from SWIG. SWIG is nice, but it has two drawbacks that are (to me, at least) showstoppers: - Any arguments other than the standard int/string/float/etc are difficult. Bgen has no trouble with this: as long as you can explain it the C code needed to wrap/unwrap argument types it'll do it for you. - SWIG exports a C-library more-or-less as-is, which means you often have to wrap it into an OO module in Python. Again, bgen is superior here: you can explain it if the first (or last, or whatever) argument is of type X the C function should be exported to Python as a method of the X type. -- 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

newbie's Q
by KAWASAKI Dec. 10, 1999

Dec. 10, 1999

hello,all I am a newbie to mac python. when I double click a module in whatever folder the interpreter says to me it can't find the module. for example. Double click $PYTHON:Lib:binhex.py --->PythonInterpreter:: can't open file 'binhex.py:' I can import the binhex.py from the interpreter command line. I suspect it is not a problem of path settings.( indeed $PYTHON:Lib: is in the path) PLUS, I can't open any file in IDE! it complains "can't find *****" I thought I had no trouble when I was using ver 1.4 Please tell me what's wrong. Thank you in advance. _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG(a)python.org http://www.python.org/mailman/listinfo/pythonmac-sig

1 0

SWIG and making extension modules
by Rob Managan Dec. 10, 1999

Dec. 10, 1999

I have successfully used SWIG to wrap the Processor Manager functions. At this time I have really only tested the GetProcessInformation and the MacGetCurrentProcess functions. I set this up to see how hard it would be to use SWIG for this purpose. Mainly I wanted to be able to get the process name, Signature, and active time. It turns out that it is not as easy to use as I would like. However, it does give you a lot of flexibility. The main problems revolve around trying to use the special objects that Jack provides for things like FSspec pointers and OSTypes... I want to clean it up a little and add some documentation and then hope to make it available. If you want to see it in its rough form let me know. *-*-*-*-*-*-*-*-*-*-**-*-*-*-*-*-*-*-*-*-*- Rob Managan <mailto://managan@llnl.gov> LLNL ph: 925-423-0903 P.O. Box 808, L-095 FAX: 925-422-3389 Livermore, CA 94551-0808

1 0

MacOS X Server installation documentation
by savageb Dec. 9, 1999

Dec. 9, 1999

Just installed Python 1.5.2 on MacOS X Server. I followed the instructions at http://xclave.macnn.com/Features/QuickNDirty/ to whit: > > And now Python 1.5.2. > Easy easy easy. Download the Python source code to /usr/local/src (or /tmp if > you don't care to store the source code). > In Terminal: > > cd *directory you chose* > gnutar xpzf Python-1.5.2.tar.gz > cd Python-1.5.2 > ./configure --with-host=powerpc-apple-netbsd -silent > The with-host (*#$ is because the installer doesn't understand Rhapsody, or > it's needsand it has needs, people. So, instead it just uses the template for > a PowerPC chip and NetBSD. If you are thinking that this sounds questionable, > don't. This is quick and dirty! > In Terminal: > > make > make install > ln -s /usr/local/lib/Python1.5 /usr/bin/python > The final line allows you to call python from the command line. > the link on "Python source code" above was http://www.python.org/ftp/python/src/py152.tgz I noticed one change from the above, however: I have "openup" installed and that takes care of the decompressing and detarring automatically, but it moves things to a different directory. (Just thought I would note this here in case someone searches the archives looking for this info, but if anyone wants to comment on this procedure, please speak up as I am quite unfit to judge if the "quick and dirty" nature of the configure procedure is a problem. BTW, the version information that comes up at first says I am running on "next5_3", and os.name == "posix".) Nota Bene: this is different from the config options mentioned in the previous post http://dinsdale.python.org/pipermail/pythonmac-sig/1999-May/002648.html which specifically mentioned compiling with threads so that Zope would run. Hope someone finds this stuff useful, Bob

2 1

Re: [Pythonmac-SIG] CGI on Mac/WebStar using Python
by Jack Jansen Dec. 9, 1999

Dec. 9, 1999

> This morning, I turned ON three startup options for Python on the mac > running WebStar. > Three options I turned on are: > 1) Disable Interactive option setting > 2) Disable argc/argv emulation > 3) Delay console window until needed. > With this setting, the phenomena I mentioned disappear. All CGI request > from WWW browser are handled > properly even if the CGI program is not running. So you can use set > self.quitting = 1 at the end of CGI callback > to terminate execution of the CGI program. I _think_ it is documented that you should turn these one, but I will check again. It is definitely necessary to do (2), I'm not sure about (1) and (3). -- 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

Appearance
by Jack Jansen Dec. 9, 1999

Dec. 9, 1999

Folks, I'm about to convert various (and, eventually, all) dialogs and such in MacPython to Appearance Manager. Moreover, I'm about to do so pretty soon, at least for some stuff like EasyDialogs, as I need appearance support quickly for GRiNS. The thing I'm still not 100% certain about is backward compatability. I see the following possible solutions which I'd like feedback on, but any other ideas are of course welcome too. 1. Forget about backwards compatability. This is definitely the easiest solution:-) I'm afraid it might be unacceptable, though, because there are people with machines that can't run Appearance. If so: please speak up. 2. Have a special non-appearance directory in sys.path, probably something like Mac:Lib:lib-noappearance. This directory would contain versions of EasyDialogs, Framework and others plus their resource files. This directory should be prepended to sys.path either by the installer or by the user (probably after a warning message by the appearance-EasyDialogs or so). The non-appearance modules would probably eventually start lagging behind in functionality. An alternative of this might be the reverse: have the appearance versions in lib-appearance and the compatible ones in the standard sys.path. 3. Have modules dynamically decide whether to provide appearance support or not. This is the most elegant solution from a user point of view, but quite a bit more work than I really care for, unless it turns out a large proportion of the MacPython users still have pre-appearance machines. Another issue is that of the dialogs in the interpreter itself and the surrounding applets like EditPythonPrefs (and IDE, which I'll leave to Just), but I think these can be handled in similar ways. -- 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

4 3