Kaydet (Commit) 5dee5e7d authored tarafından Guido van Rossum's avatar Guido van Rossum

bugfix release

üst 635649f9
......@@ -9,30 +9,54 @@ nother to make an entry in this file, unless it was a serious bug
BUGS found in 1.1 and fixed in 1.1.1
------------------------------------
(*) printing name of lambda in traceback dereferences NULL
(*) A built-in function using getargs() and expecting >= 1 argument
may dump core when called without arguments
(*) newgetargs() dumps core in compat mode when NULL is passed in but
max is >0
(*) pow() should be declared varargs since it uses newgetargs
BUGS found in 1.1 and not yet fixed
-----------------------------------
(*) newmodule.c doesn't compile on SunOS 4.1.3 due to non-K&R backslashes
(-) A built-in function using getargs() and expecting >= 1 argument
may dump core when called without arguments
(*) some typos in tut.tex
BUGS found in 1.0.3 and fixed in 1.1
------------------------------------
(*) test for broken static forward is not strong enough
(*) Doc/Makefile assumes . is in $PATH in call to whichlibs
(*) If class C doesn't define __cmp__, cmp(a,b) will return -2 and
[a,b].sort() will fail
(*) math module misses hypot() function
BUGS found in 1.0.3 and not yet fixed
-------------------------------------
(*) structmember.h should include stddef.h (for offsetof macro)
(*) gdbmmodule.c frees the wrong structures
(-) print_error raises and then masks an error if softspace is not
defined (can't reproduce this one?)
(*) makesetup script misses some dollars and backslashes
(*) getargs.obj missing from NT makefile
(*) sorting class instances broken if no __cmp__ defined
BUGS found in 1.1 and not yet fixed
-----------------------------------
(-) HP doesn't compile out of the box (needs LIBS=-ldld or
LIBS=/usr/lib/libdld.sl)
(-) something fishy with softspace and print_error (flushline clears
the error)
(-) tkinter doesn't seem to see any declaration of malloc on sunos 4.1.3
======================================================================
BUGS found in 1.0.3 and fixed in 1.1
------------------------------------
(*) If class C doesn't define __cmp__, cmp(a,b) will return -2 and
[a,b].sort() will fail
(*) Syntax errors are reported in a silly way if multi-line tokens are
involved.
......
===================================
==> Release 1.1.1 (10 Nov 1994) <==
===================================
Thu Nov 10 13:09:26 1994 Guido van Rossum <guido@tesla>
* Objects/classobject.c (instance_compare): don't ever raise an
exception or return -2
* Python/compile.c: stick "<lambda>" in function name instead of
NULL or None
* Doc/tut.tex: corrected a few typos
* Modules/tkintermodule.c: added timer and file handler interfaces
and made mainloop/quit global functions (as well still being tk
methods)
* Modules/newmodule.c: made it compile on SunOS4.1.3 (there were
continuation backslashes on non-cpp lines :-)
* Modules/gdbmmodule.c: fix some bugs (freed the wrong objects)
* Modules/Setup.in: clarified some things a little in the comments
* Modules/Makefile.pre.in (sharedinstall): don't fail if there
aren't any shared modules
* Include/structmember.h: include stddef.h (for offsetof)
* Include/rename1.h: added PyArg_ParseTuple for newgetargs
* Python/bltinmodule.c: fix core dump in pow() (should be declared
varargs in methodlist array)
* Python/ceval.c: replace abort() calls with fatal() calls
* Python/errors.c (err_setval): call err_clear() to clear existing
error instead of calling XDECREF
* Python/getargs.c: fix core dump when old style call expecting
some arguments receives none
* Lib/test/{test_b[12].py,testall.out}: added more tests (now all
built-ins are covered again)
Thu Oct 20 08:31:02 1994 Guido van Rossum <guido@tesla>
* Modules/makesetup: should use $cc not cc
......
Python release 1.1
==================
Python release 1.1.1
====================
==> This is Python version 1.1.
==> This is Python version 1.1.1.
==> Python 1.1 contains many improvements over 1.0.3, but is almost
backward compatible (though the magic number for .pyc file has
changed). It is portable to many more non-UNIX platforms.
==> Python 1.1.1 is a pure bugfix release. It fixes two core dumps
related to the changed implementation of (new)getargs, some
portability bugs, and some very minor things here and there. If
you have 1.1, you only need to install 1.1 if bugs in it are
bugging you.
==> If you don't know yet what Python is: it's an interpreted,
extensible, embeddable, interactive, object-oriented programming
......
(*) newgetargs() dumps core in compat mode when NULL is passed in but
max is >0
(-) stack frame correspondence problem (Jim Roskind)
(-) invent new style (rename1.h) name for newgetargs
(-) make lots of places use newgetargs
(-) no tp_str member in typeobject
(-) getargs has small bugs (e.g. strange error msgs)
(-) sorting class instances broken if no __com__ defined
(-) readline 2.0 on sequent has ^C problem (works only first time)
(-) add explanatory comments to Setup (especially about SGI modules
like 'cd')
(-) Q3 ftp mail archive
(-) need to add truncate() and ftruncate() to posixmodule.c (Windows:
chsize(fd, size)
======================================================================
Release 1.1 (11 Oct 1994)
======================================================================
(*) 2 specific leaks: 1 PYTHONPATH; 2 reading code from .pyc
(-) if __getattr__ prints something, calling repr(x) from cmd line
......
......@@ -123,7 +123,8 @@ then
fi
# checks for libraries
AC_HAVE_LIBRARY(dl)
AC_HAVE_LIBRARY(dl) # Dynamic linking for SunOS/Solaris (and SYSV?)
AC_HAVE_LIBRARY(dld) # Dynamic linking for HP-UX
AC_CHECKING(for --with-svr4)
AC_WITH(svr4, [
......@@ -239,9 +240,15 @@ AC_CHECKING(for bad static forward)
AC_TEST_PROGRAM([
struct s { int a; int b; };
static struct s foo;
int foobar() { return !foo.a; }
int foobar() {
static int random;
random = (int) &foo;
return random;
}
static struct s foo = { 1, 2 };
main() { exit(foobar()); }
main() {
exit(!((int)&foo == foobar()));
}
], , AC_DEFINE(BAD_STATIC_FORWARD))
# checks for system services
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment