[Pythonmac-SIG] MacPython 2.1a3 available
Russell E Owen
owen@astro.washington.edu
Wed, 28 Feb 2001 09:50:18 -0800
The basics work -- the expected tests failed, some modules were
missing, most tests passed. Also, all of my code that I could test
(which excludes a lot due to the problems listed below) worked fine.
Two problems:
- I cannot figure out how to modify the module search path.
EditPythonPrefs exists in the Mac:Scripts folder, but fails to run
with error:
The application "EditPythonPrefs" could not be opened
because "PythonCore" could not be found.
(I did look at the prefs file with ResEdit and BBEdit, but didn't see
anything that looked relevant.)
- import Tkinter fails with error:
ImportError: No module named Tkinter
It is installed -- in Misc:RPM:Tkinter
Looking good!
-- Russell
>Folks,
>the next alfa release of MacPython is available. It is again a Carbon-only
>release, because of the problems encountered with the previous one.
>
>Download it from http://www.cwi.nl/ftp/jack/python/mac/MacPython21a3carbon.bin
>. MacOS X users should also download a post-last-minute fix:
>ConfigurePythonCarbon.bin fromthe same directory (see below for details).
>
>The most important difference with this release is that it should actually
>work with CarbonLib 1.0.4 through 1.2.5 and with MacOSX. Various other serious
>problems, like EasyDialogs and EditPythonPrefs not working have also been
>fixed. See the release notes for additional fixes.
>
>Something that has changed with this release is that ConfigurePython has been
>replaced by 2 applets: ConfigurePythonCarbon and ConfigurePythonClassic. These
>will allow MacOS 9 users to switch back and forth between the two runtime
>models. (Not in this release, because classic-ppc is not included, but in the
>next).
>As ConfigurePython{Carbon,Classic} also rebuild the applets for the given
>execution model the applets are not included in the distribution anymore
>(except the Configure... ones:-). But: that means that the configure process
>has become more important, as you'll have no applets if it fails. And, of
>course, I messed up for MacOSX, so that's why X users should grab the fixed
>ConfigurePythonCarbon as well, drop it in their Python folder (replacing the
>broken one) and run it.
>
>Please share your feedback on this release here on pythonmac-sig,
>--
>Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++
>Jack.Jansen@oratrix.com | ++++ if you agree copy these lines to your sig ++++
>www.oratrix.nl/~jack | ++++ see http://www.xs4all.nl/~tank/ ++++
>
>
>
>_______________________________________________
>Pythonmac-SIG maillist - Pythonmac-SIG@python.org
>http://mail.python.org/mailman/listinfo/pythonmac-sig