-This is Python release 1.5.1
-============================
-
-This version is officially released on Tuesday, April 14, 1998. It is
-mostly a bugfix release on Python 1.5.
+This is Python release 1.5.2a1
+==============================
What's new in this release?
---------------------------
-See the Misc/NEWS file. Nothing spectacular this time, only small
-changes (as you would expect from a release called "1.5.1").
-
-One big organizational change: the documentation sources have been
-unbundled. We will release a version of the Doc subtree separately,
-but probably not simultaneously with the source release.
+See the Misc/NEWS file. Nothing spectacular this time. The BeOS port
+is now integrated, courtesy Chris Herborth (see below).
If you don't read instructions
activate everything that makes sense for your system... tested
here at QNX with the following modules:
- array, audioop, binascii, cPickle, cStringIO, cmath, crypt, curses,
- errno, fcntl, gdbm, grp, imageop, _locale, math, md5, new, operator,
- parser, pcre, posix, pwd, readline, regex, reop, rgbimg, rotor,
- select, signal, socket, soundex, strop, struct, syslog, termios,
- time, timing, zlib
+ array, audioop, binascii, cPickle, cStringIO, cmath,
+ crypt, curses, errno, fcntl, gdbm, grp, imageop,
+ _locale, math, md5, new, operator, parser, pcre,
+ posix, pwd, readline, regex, reop, rgbimg, rotor,
+ select, signal, socket, soundex, strop, struct,
+ syslog, termios, time, timing, zlib
Newly compiled/tested in 1.5.1:
4) make SHELL=/usr/local/bin/bash test
- The socket test might fail in the test harness; going through it by
- hand shows that they work.
+ The socket test might fail in the test harness; going
+ through it by hand shows that they work.
- A good exercise for the reader: make this work "out of the box".
-
- Using GNU readline 2.2 seems to behave strangely, but I think that's
- a problem with my readline 2.2 port. :-\
+ A good exercise for the reader: make this work "out of the
+ box".
+
+ Using GNU readline 2.2 seems to behave strangely, but I
+ think that's a problem with my readline 2.2 port. :-\
5) make SHELL=/usr/local/bin/bash install
- If you get SIGSEGVs while running Python (I haven't yet, but I've
- only run small programs and the test cases), you're probably running
- out of stack; the default 32k could be a little tight. To increase
- the stack size, edit the Makefile in the Modules directory to read:
- LDFLAGS = -N 48k
+ If you get SIGSEGVs while running Python (I haven't yet, but
+ I've only run small programs and the test cases), you're
+ probably running out of stack; the default 32k could be a
+ little tight. To increase the stack size, edit the Makefile
+ in the Modules directory to read: LDFLAGS = -N 48k
BeOS: Chris Herborth (chrish@qnx.com) writes:
See BeOS/README for notes about compiling/installing Python on
- BeOS R3 or later. Note that only the PowerPC platform is supported
- at this time, but feel free to try building it on x86.
+ BeOS R3 or later. Note that only the PowerPC platform is
+ supported at this time, but feel free to try building it on
+ x86.
Cray T3E: Konrad Hinsen writes:
- 1) Don't use gcc. It compiles Python/graminit.c into something that
- the Cray assembler doesn't like. Cray's cc seems to work fine.
- 2) Uncomment modules md5 (won't compile) and audioop (will crash
- the interpreter during the test suite).
- If you run the test suite, two tests will fail (rotate and binascii),
- but these are not the modules you'd expect to need on a Cray.
+ 1) Don't use gcc. It compiles Python/graminit.c into something
+ that the Cray assembler doesn't like. Cray's cc seems to work
+ fine.
+ 2) Uncomment modules md5 (won't compile) and audioop (will
+ crash the interpreter during the test suite).
+ If you run the test suite, two tests will fail (rotate and
+ binascii), but these are not the modules you'd expect to need
+ on a Cray.
SGI: SGI's standard "make" utility (/bin/make or /usr/bin/make)
does not check whether a command actually changed the file it
projects / python / commitdiff