diff options
author | Jack Jansen <jack.jansen@cwi.nl> | 1998-01-06 12:13:16 +0000 |
---|---|---|
committer | Jack Jansen <jack.jansen@cwi.nl> | 1998-01-06 12:13:16 +0000 |
commit | 43419d0ec7db2e998949d919c196746a32f342dc (patch) | |
tree | 2b62f4faa4689736dcf4459b59a75043c52f19f4 /Mac/ReadMe | |
parent | cfc0a6f1c75b43667f6f0d925948ec17253ccf64 (diff) | |
download | cpython-43419d0ec7db2e998949d919c196746a32f342dc.tar.gz |
Release notes and readme for 1.5b3
Diffstat (limited to 'Mac/ReadMe')
-rw-r--r-- | Mac/ReadMe | 44 |
1 files changed, 28 insertions, 16 deletions
diff --git a/Mac/ReadMe b/Mac/ReadMe index 9bc2644465..b31e336417 100644 --- a/Mac/ReadMe +++ b/Mac/ReadMe @@ -1,4 +1,4 @@ -How to install Python 1.5a4 on your Macintosh +How to install Python 1.5b3 on your Macintosh --------------------------------------------- If this is your first encounter with Python: you definitely need the @@ -11,6 +11,19 @@ Mac-specific documentation is included in this distribution in folder Mac:Demo. The documentation is sparse, but it will have to serve for now. The documentation is in HTML format, start with index.html. +Why 1.5b3? +---------- +The reason for distributing a third beta release for the Mac (unlike for +other platforms) is that there are still some problems. The main problem +is that packages ("dotted import") seem to have problems when used +under cfm68k. Other outstanding problems are tkinter problems with menus +(all platforms) and NumPy printing problems (cfm68k). Please report your +findings with this distribution to pythonmac-sig@python.org, so we can +try to iron out the problems and have a normal 1.5 distribution in a few +weeks time. + +The non-system-dependent part of this distribution is identical to 1.5 final. + What to install --------------- @@ -50,14 +63,16 @@ After installing ---------------- It is probably a good idea to run the automatic tests. Start Python and -"import test.autotest". This should not print any errors. It will, -however, print some messages about optional features not supported. -Running testall.py is done by double-clicking it or dropping it onto the -interpreter. +"import test.autotest" and "test.autotest.main()". This should not print +any errors. It will, however, print some messages about optional +features not supported. Running testall.py is done by double-clicking it +or dropping it onto the interpreter. -NOTE: as of 1.5a4 the tests test_time and test_strftime will -fail. This is due to a problem with the tests. test_socket may also fail -if you have no internet connection. +NOTE: as of 1.5b3 the test test_strftime will fail. This is due to a +problem with the way the MetroWerks handles %% escapes in strftime() +strings, and there is little I can do about it. test_socket may also +fail if you have no internet connection. Please also read the Relnotes +file for other minor problems with this distribution. Next, try "compileall.py" from :Lib to create all .pyc files (but this isn't really important). @@ -88,8 +103,8 @@ Uninstalling ------------ Two items are installed in the system folder: the interpreter shared -library "PythonCore 1.5a4" lives in the Extensions folder and the -"Python 1.5a4 Preferences" file in the Preferences folder. All the rest +library "PythonCore 1.5b3" lives in the Extensions folder and the +"Python 1.5b3 Preferences" file in the Preferences folder. All the rest of Python lives in the folder you installed in. Things to see @@ -122,9 +137,9 @@ that this means you can keep your older version around if you are unsure whether to upgrade. The bad news is that your old preference settings are lost and you have to set them again. -After you are satisfied that 1.5a4 works as expected you can trash +After you are satisfied that 1.5b2 works as expected you can trash anything in the system folder that has "python" in the name and not -"1.5a4". +"1.5b2". The installer ------------- @@ -147,10 +162,7 @@ Feedback -------- Send bug reports, suggestions, contributions and fanmail to -<jack@cwi.nl>. Be warned however that I'm on holiday for most of october -and november, so I may not always respond immedeately. - -A better way to discuss MacPython is to join the +<jack@cwi.nl>. However, a better way to discuss MacPython is to join the <pythonmac-sig@python.org> mailing list, which is explicitly meant for this purpose. |