blob: b253f537dd77137e0c676106a51cb68080f46e34 [file] [log] [blame]
Jack Jansen83cab721997-08-26 13:25:06 +00001How to install Python 1.5a3 on your Macintosh
2-------------------------------------------
3
4If this is your first encounter with Python: you definitely need the
5common user documentation (common to all platforms). You can find this
6(in various forms) on www.python.org and ftp.python.org. Through
7there, or via http://www.cwi.nl/~jack/macpython.html you can also find
8the most recent MacPython distribution.
9
10Mac-specific documentation is included in this distribution in folder
11Mac:Demo. The documentation is sparse, but it will have to serve for
12now. The documentation is in HTML format, start with index.html.
13
14What to install
15---------------
16
17There are three flavors of Python: PowerPC, cfm68k and Classic 68k (the
18FAT flavor is just a combination of the first two, which is handy if you
19want to install Python on a fileserver or so). 68K-mac owners should
20definitely use the cfm68k version if possible, since it enables the use
21of applets and dynamically loaded modules and usually has a smaller
22memory footprint. It does however need the CFM68K Runtime Enabler which
23is available from Apple (available for free from
24<http://support.info.apple.com/ftp/swhome.html>, included since MacOS
257.6.1). If your machine is pre-68020 you cannot use cfm68k and you can
26install the classic 68k Python.
27
28If you have a pre-system 7 macintosh: sorry, this release will not work
29on your system. Too many sys7 features are used to make a sys6 python
30easy to create.
31
32If you don't have enough memory: the sizes choosen are somewhat
33arbitrary. Try lowering the application sizes in the finder "get info"
34window, and seeing whether the resulting python is still usable. Some
35modules (Tkinter comes to mind) need a lot of memory, so it may also be
36necessary to increase the application size.
37
38A final note to CFM68K (and possibly PPC) users: the Code Fragment
39Manager can (incorrectly) produce "library not found" and other strange
40error messages when it really means that there is not enough room in the
41system heap. Decreasing (yes, *de*creasing) the size of the interpreter
42and/or enabling virtual memory may solve these problems.
43
44After installing
45----------------
46
47It is probably a good idea to run "autotest.py" from :Lib:test at this
48point, this should not give any errors. It will, however, print some
49messages about optional features not supported. Running testall.py is
50done by double-clicking it or dropping it onto the interpreter.
51
52NOTE: as of 1.5a3 the tests test_time, test_strftime and test_rotor will
53fail. This is due to a problem with the tests. test_socket may also fail
54if you have no internet connection.
55
56Next, try "compileall.py" from :Lib to create all .pyc files (but this
57isn't really important).
58
59PPC and CFM68K users have a couple of applets in the main folder they
60may want to try, (68K users can use the corresponding scripts from the
61"scripts" folder):
62
63- EditPythonPrefs allows you to edit the preferences file, to change the
64python home folder or modify the initial sys.path setting. The default
65settings are somewhat arbitrary, you can remove tkinter if you don't use
66it and possibly add Extensions:img:Lib. - mkapplet creates a python
67applet, a tiny application written in python. Drop a python source on it
68and out comes the application. More information can be found in the
69"Mac:Demo" folder.
70
71PPC and CFM68K users will see one more file in the python folder:
72PythonApplet. This is the template for building applets, leave it alone.
73The applet is "fat", containing both PPC and CFM68K code. Hence, applets
74built with it can be transported to machines with the other
75architecture.
76
77Things to see
78-------------
79
80There are some readme files in the "Read me files" folder that may
81contain useful information. There is also a first stab at documentation
82(plus examples) in the Mac:Demo folder. The toplevel Demo folder has
83machine-independent demos. See the file Readme-mac for mac-specific
84notes. The Mac:Lib:test folder also has some programs that show simple
85capabilities of various modules.
86
87The "scripts" folder has some sample scripts. Some are useful, some are
88just interesting to look at to see how various things work. The MkDistr,
89mkapplet and fullbuild scripts (plus the ones mentioned above) may help
90you to understand how to use AppleEvents and various other toolboxes
91from python.
92
93The 'img' group of modules, which handles I/O of many different image
94formats (not pict yet, sigh:-) is included, but without documentation.
95You can find docs at ftp://ftp.cwi.nl/pub/jack/python/img (or somewhere
96around there).
97
98Upgrading from older Python releases
99------------------------------------
100
101Since release 1.4 Python releases are independent of each other, with
102separate Preferences files, shared library names, etc. The good news is
103that this means you can keep your older version around if you are unsure
104whether to upgrade. The bad news is that your old preference settings
105are lost and you have to set them again.
106
107After you are satisfied that 1.5a3 works as expected you can trash
108anything in the system folder that has "python" in the name and not
109"1.5a3".
110
111The installer
112-------------
113
114The installer for this product was created using Installer VISE Lite
115from MindVision Software. For more information on Installer VISE Lite,
116
117contact:
118MindVision Software
1197201 North 7th Street
120Lincoln, NE 68521-8913
121Voice: 402-477-3269
122Fax: 402-477-1395
123Internet: mindvision@mindvision.com
124http://www.mindvision.com
125
126
127Feedback
128--------
129
130Send bug reports, suggestions, contributions and fanmail to
131<jack@cwi.nl>. Be warned however that I'm pretty busy, so I may not
132always respond immedeately.
133
134A better way to discuss MacPython is to join the
135<pythonmac-sig@python.org> mailing list, which is explicitly meant for
136this purpose.
137
138Alternatively, you can try sending to comp.lang.python or
139python-list@cwi.nl, but since I read the newsgroup, not the mailinglist,
140I may miss it there (but other people may know quite a bit more than me
141anyway:-).
142
143Jack Jansen
144Centrum voor Wiskunde en Informatica
145Kruislaan 413
1461098 SJ Amsterdam
147the Netherlands
148
149<jack@cwi.nl>, http://www.cwi.nl/~jack