[Python-checkins] CVS: python/dist/src/Mac ReadMe,1.34,1.35

2001年10月23日 15:20:45 -0700

Update of /cvsroot/python/python/dist/src/Mac
In directory usw-pr-cvs1:/tmp/cvs-serv16320/Python/Mac
Modified Files:
	ReadMe 
Log Message:
Tweaks for MacPython 2.2b1
Index: ReadMe
===================================================================
RCS file: /cvsroot/python/python/dist/src/Mac/ReadMe,v
retrieving revision 1.34
retrieving revision 1.35
diff -C2 -d -r1.34 -r1.35
*** ReadMe	2001年09月08日 21:37:01	1.34
--- ReadMe	2001年10月23日 22:20:43	1.35
***************
*** 1,3 ****
! How to install Python 2.2a3 on your Macintosh
 ---------------------------------------------

--- 1,3 ----
! How to install Python 2.2b1 on your Macintosh
 ---------------------------------------------

***************
*** 7,11 ****

 You should definitely read the Relnotes file too, and the section below about
! toolbox module reorganization.

 A special note about the active installer: do not background it, it may hang
--- 7,12 ----

 You should definitely read the Relnotes file too, and the section below about
! toolbox module reorganization. You should also read :Misc:NEWS, which lists
! the general (non-mac-dependent) new features of this Python release.

 A special note about the active installer: do not background it, it may hang
***************
*** 13,19 ****
 are working on it.

- Aside from the general new Python 2.2a3 listed in the general relnotes file
- there is some other new machine-independent stuff in this release as well, as
- it was built from newer sources than unix/windows 2.2a3.
 ------

--- 14,17 ----
***************
*** 65,89 ****
 modules you may think of as toolbox modules (such as Waste) really are not,
 and they are not in the Carbon package.
- 
- Some open issues I would like to discuss on the PythonMac-SIG, please join
- in if you have views on the matter:
- - Is this all a good idea?
- - Some modules are not in the Carbon package (icglue, for instance, or
- supporting module such as aetools and aepack) and maybe they should be,
- some are (ControlAccessors) which arguably should not. Opinions are welcome.
- - I'm tempted to put Qt and QuickTime into their own package, especially
- since I'm also working on porting it to Windows. It would also be in line
- with Apple's organization. Opinions?
- - Should we get rid of the Res/Resource dichotomy, where the first is the
- extension module and the second is the Python module with the constants?
- We could simply import the extension module functionality into the Python
- module, at the expense of a rather large namespace.
- - Should we have a Carbon.Carbon module that simply imports the whole world,
- so that "from Carbon.Carbon import *" is pretty much equivalent to the C
- #include <Carbon/Carbon.h>?
- - Should we put all the other Mac modules into a Mac package? This will make
- MacPython programs a lot more verbose, but that is a good thing too if people
- try to port Mac Python scripts to other platforms.
- Should the Carbon package then be a sub-package of the Mac package?

 Another change related to the OSX growth path is that there is a new module
--- 63,66 ----
***************
*** 95,102 ****
 OSX MachO Python.

! ... and more
! ------------
! 
! A feature that I am not sure about (so: feedback!) is that if you open a textfile
 for reading MacPython will now accept either unix linefeeds (LF, '\n') or
 Macintosh linefeeds (CR, '\r') and present both of them as '\n'. This is done on
--- 72,76 ----
 OSX MachO Python.

! Another feature to help with the OSX transition is that if you open a textfile
 for reading MacPython will now accept either unix linefeeds (LF, '\n') or
 Macintosh linefeeds (CR, '\r') and present both of them as '\n'. This is done on
***************
*** 152,161 ****

 test_time will fail because MacPython accepts bogus values for mktime(), this
! will be fixed later.

 test_descrtut will fail because of a problem with the test itself.

 Three tests will fail on MacOS9 with MemoryErrors:
! test_longexp, test_sha and test_zlib (on MacOSX nothing should fail).

 If you increase the PythonInterpreter memory
--- 126,135 ----

 test_time will fail because MacPython accepts bogus values for mktime(), this
! will be fixed later (it is not a very serious problem).

 test_descrtut will fail because of a problem with the test itself.

 Three tests will fail on MacOS9 with MemoryErrors:
! test_longexp, test_sha and test_zlib (on MacOSX these should pass).

 If you increase the PythonInterpreter memory
***************
*** 182,186 ****
 Two items are installed in the system folder: the interpreter shared
 libraries PythonCore and PythonCoreCarbon lives in the Extensions folder and the
! "Python 2.2a3 Preferences" file in the Python subfolder in the
 Preferences folder. All the rest of Python lives in the folder you
 installed in.
--- 156,160 ----
 Two items are installed in the system folder: the interpreter shared
 libraries PythonCore and PythonCoreCarbon lives in the Extensions folder and the
! "Python 2.2b1 Preferences" file in the Python subfolder in the
 Preferences folder. All the rest of Python lives in the folder you
 installed in.
***************
*** 231,237 ****
 are lost and you have to set them again.

! After you are satisfied that 2.2a3 works as expected you can trash
 anything in the system folder that has "python" in the name and not
! "2.2a3".

 The ConfigurePython... applets will try to detect incompatible preferences
--- 205,211 ----
 are lost and you have to set them again.

! After you are satisfied that 2.2b1 works as expected you can trash
 anything in the system folder that has "python" in the name and not
! "2.2b1".

 The ConfigurePython... applets will try to detect incompatible preferences