🌐 Mailman 3 - Pythonmac-SIG - python.org

Numerical Python
by Rob Managan Sept. 9, 1996

Sept. 9, 1996

I have compiled the Numeric python libraries for the Mac. For Power PC users it should be as easy as expanding the archive and adding two directories to the pythonpaths with EditPythonPrefs. AFter a few people test it I suggest I send the archive to Jack to store with the rest of the Mac software. I suggest this since I don't have a ftp site available to me. Currently this is compiled for version 1.4b3 of Python and 1.0a2 of the Numeric module. *-*-*-*-*-*-*-*-*-*-**-*-*-*-*-*-*-*-*-*-*- Rob Managan managan(a)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(a)python.org administrivia to: pythonmac-sig-request(a)python.org =================

1 0

Re: [PYTHONMAC-SIG] applet question
by Jack Jansen Sept. 9, 1996

Sept. 9, 1996

> one quick question: when an Applet is 'made', is the Python code > contained within the applet? or does it point to the code it needs? > primarily, with some of the Python code i'm working on, there is a > central Module/Framework i'm using, and a few different 'front ends' > that access that Module. the code in the front ends doesn't change too > much, but the Framework is. Do i have to rebuild the Applets that use > that Framework everytime i change it? It's no huge deal, but i'm just > wondering before i start building everything in my excitement over the > CFM version of Python :). Jeffrey, the compiled code for the main module is incorporated in the applet, nothing else. Actually, I use this fact for debugging applets: make your main code do nothing else than 'execfile("real_applet_code.py")' and you only have to run mkapplet once. Then, when I'm satisfied that the code works I rename real_applet_code.py to the real name and run mkapplet once. There is actually a way to create a fully self-contained applet, but I haven't documented it yet since the procedure is a bit involved and I want to streamline it (if I find the time). For the adventurous, here is the procedure: - Collect *all* modules used by your program into a folder. I really mean "all", so including anything from Lib, etc. - Run compileall.py on that folder. - Run PackLibDir on the folder, giving you a resource file with PYC resources for all your modules. - Temporarily replace PythonApplet by either PythonStandalone (PPC) or Python68K (68k). - Create your applet. (And don't forget to put PythonApplet back in its place). - Use ResEdit to copy the PYC resources from your PackLibDir output file to your applet. PYC resource numbers are not important (names are), so let resedit fix the duplicates. - Drop the applet onto EditPythonPrefs, remove all sys.path components and replace them by the single string $(APPLICATION) - I think you have to use ResEdit to remove the "alis" resource from the resulting applet to make it truly portable, but I'm not 100% sure. You now have a fully standalone application that you can give away to anyone, it does not depend on any Python infrastructure anymore, even if the program is run on a machine that has python already installed. -- 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

Update for MacPython 1.4b3 for CFM68K
by Jack Jansen Sept. 9, 1996

Sept. 9, 1996

If you are using the CFM68K version of MacPython 1.4b3 and you are experiencing problems with creating applets or with using Tkinter you should download <ftp://ftp.cwi.nl/pub/jack/python/mac/Python-14b3-CFM68K-update1.hqx>. This fixes the following bugs: - _tkinter was built so that you don't need to install a full Tcl/Tk distribution on your system, but this didn't work correctly. Now it does. - Applets were created with the same creator-code as the interpreter, making it difficult to run normal scripts after creating an applet. This has been fixed. -- 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

MSDOS floppies
by Jack Jansen Sept. 6, 1996

Sept. 6, 1996

I just noticed that Python doesn't like MSDOS floppies very much: - os.chdir('DOSDISK:') does not work (making an alias to the floppy and chdir()ing there does work!) - os.listdir(':') when your working directory is a dos floppy does not work. Personally, I couldn't care less:-), but if anyone feels the urge to dive into the problem I will graciously accept donations of working code... -- 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

Event handling bug in 1.4b3
by Jack Jansen Sept. 4, 1996

Sept. 4, 1996

Before you all start complaining (i.e. why haven't you complained yet:-): I just found a bug in the 1.4b3 event handling code, which effectively means that Python does not look at the event queue when your program is busy, with the exception of checking for command-dot. This means you are not able to switch applications, type ahead, etc. Sorry, it will be fixed in 1.4 (or contact me if this seriously inconveniences you). -- 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

System 6
by Jack Jansen Sept. 4, 1996

Sept. 4, 1996

Is anyone using Python under System 6, or does anyone know of people who do so? Sys6 compatability hasn't been tested for a long long time anyway, and I would like to rip out the System 6 compatability code (which needs to be taken out to prepare for MacOS 8 anyway). -- 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] Python + PaperPort?
by just＠knoware.nl Sept. 2, 1996

Sept. 2, 1996

At 11:14 AM 9/2/96, Jack Jansen wrote: >> Does anybody else using Python on the Mac have a PaperPort? Again with >> 1.4b3 (as with 1.3.3) when I tried to run MkPluginAliases, I got: >> >> Traceback (innermost last): >> File "flap:jack:Python:Mac:scripts:MkPluginAliases.py", line 11, in ? >> ImportError: No module named os >> >> I decided to try it with no extensions today, and <ta-dah> everything >> worked fine! 11 restarts after fiddling with extensions later, it comes >> down to the Paperport control panel. If it's loaded, I can't run Python; >> if it isn't, everything's fine. > >The error message seems to point at a problem with STR# resource 129, where >sys.path is stored. If the Paperport software somehow puts a new resource 129 >somewhere in the system resources Python will see this during startup and >attempt to use it as initialization for sys.path. > >I don't know of an easy fix, if this is indeed the problem. For the next >release I will access the "global" resources by name in stead of by number. > >Hmm, on second hands I *do* know a workaround. Start Python with extensions >off, and let it create the preferences file. With ResEdit, open the >preferences file and the interpreter, and copy STR# 128 from the preferences >file to the interpreter as STR# 129. If thats's indeed the problem, wouldn't it be easier to check for a STR# nr. 129 with Get1Resource(), to make sure only the current res file is searched? 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

Python + PaperPort?
by guzdial＠cc.gatech.edu Sept. 2, 1996

Sept. 2, 1996

Does anybody else using Python on the Mac have a PaperPort? Again with 1.4b3 (as with 1.3.3) when I tried to run MkPluginAliases, I got: Traceback (innermost last): File "flap:jack:Python:Mac:scripts:MkPluginAliases.py", line 11, in ? ImportError: No module named os I decided to try it with no extensions today, and <ta-dah> everything worked fine! 11 restarts after fiddling with extensions later, it comes down to the Paperport control panel. If it's loaded, I can't run Python; if it isn't, everything's fine. I'm hoping that someone has a fix. My Paperport software is 3.5.1. Suggestions? Thanks! Mark -------------------------- Mark Guzdial : Georgia Tech : College of Computing : Atlanta, GA 30332-0280 (404) 894-5618 : Fax (404) 894-0673 : guzdial(a)cc.gatech.edu <<STILL IN OLYMPICS-HIBERNATION -- EMAIL IS BEST WAY TO REACH ME>> http://www.cc.gatech.edu/gvu/people/Faculty/Mark.Guzdial.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 =================

2 1

Python 1.4beta3 for Macintosh released -- with Tkinter support!
by Guido van Rossum Aug. 28, 1996

Aug. 28, 1996

A port of Python 1.4beta3 for all Mac platforms is now available. You can get it via ftp from ftp.python.org, directory /pub/python/mac/. Or point your web browser to: http://www.python.org/ftp/python/mac/ The directory contains complete, ready-to-install, binary distributions for PowerPC Mac, 68K Mac, and 68K Mac using CFM68K (shared library support). There's also a full source distribution, which contains a whole subtree of Mac-specific files that aren't in the core distribution. Note that both the PPC and the 68K binaries contain full support for Tkinter. You don't need to install Tcl/Tk in order to use this -- it's all statically linked (even the *.tcl scripts are there, in the resource fork). The CFM68K version doesn't support Tkinter yet -- it appears to work but crashes as soon as you pop up or pull down a menu. Thanks to Jack Jansen who did most of the work on this release, as usual! Here's a copy of the README file from that directory: ====================================================================== Here you will find the 1.4 beta 3 distribution, available as binary distributions for 68K, CFM68K and PPC and as source: Python-14b3-68K.hqx Full distribution for 68K, classic memory model. Interpreter includes img, waste and tkinter modules. Python-14b3-small68kint.hqx Small 68K interpreter only (also load the above distribution) without img, waste and tkinter, for people with little memory. Python-14b3-CFM68K.hqx Full distribution for 68K, CFM68K memory model (includes cfm68k). Useable if you have 68020 or higher and run System 7.1.1 or newer. Python-14b3-PPC.hqx Full distribution for PPC. Python-14b3-src.hqx Source distribution. The libjpeg-v4.hqx, libpbmtiff.hqx and stdwin.hqx are versions of the IJG jpeg library, the pbmplus and libtiff library and the stdwin library, all preconfigured for building Python from source. It is probably unwise to use this distributions for anything else. Jack Jansen, jack(a)cwi.nl, 28-Aug-96 [updated by GvR, 28-Aug-96] ====================================================================== --Guido van Rossum (home page: http://www.python.org/~guido/) ================= 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

faceless background applet?
by Joseph Strout Aug. 21, 1996

Aug. 21, 1996

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.) Thanks, -- Joe ,------------------------------------------------------------------. | Joseph J. Strout Department of Neuroscience, UCSD | | jstrout(a)ucsd.edu http://www-acs.ucsd.edu/~jstrout/ | `------------------------------------------------------------------' ================= 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