Mailman 3 August 2006 - Python-checkins

r51391 - python/branches/bcannon-objcap/BRANCHNEWS
by brett.cannon Aug. 18, 2006

Aug. 18, 2006

Author: brett.cannon Date: Sat Aug 19 01:54:14 2006 New Revision: 51391 Added: python/branches/bcannon-objcap/BRANCHNEWS (contents, props changed) Log: Create a file to keep track of changes. Added: python/branches/bcannon-objcap/BRANCHNEWS ============================================================================== --- (empty file) +++ python/branches/bcannon-objcap/BRANCHNEWS Sat Aug 19 01:54:14 2006 @@ -0,0 +1,7 @@ ++++++++++++ +Branch News ++++++++++++ + +Core and builtins +----------------- +

1 0

r51389 - peps/trunk/pep-3100.txt
by guido.van.rossum Aug. 18, 2006

Aug. 18, 2006

Author: guido.van.rossum Date: Fri Aug 18 23:34:25 2006 New Revision: 51389 Modified: peps/trunk/pep-3100.txt Log: Various status updates. Added some "?"s to items I'm not sure about. Modified: peps/trunk/pep-3100.txt ============================================================================== --- peps/trunk/pep-3100.txt (original) +++ peps/trunk/pep-3100.txt Fri Aug 18 23:34:25 2006 @@ -63,29 +63,26 @@ Core language ============= -* True division becomes default behavior [#pep238]_ +* True division becomes default behavior [#pep238]_ [done] * ``exec`` as a statement is not worth it -- make it a function -* Add optional declarations for static typing [11]_ -* Support only new-style classes; classic classes will be gone [1]_ +* (Maybe) add optional declarations for static typing [11]_ +* Support only new-style classes; classic classes will be gone [1]_ [done] * Replace ``print`` by a function [16]_ -* Do something so you can catch multiple exceptions using ``except E1, - E2:``. Probably use ``except E1, E2, E3 as err:`` if you want the - error variable? [3]_ -* ``None``, ``True`` and ``False`` become keywords [4]_ - (Or perhaps just ``None``?) +* Use ``except E1, E2, E3 as err:`` if you want the error variable. [3]_ +* ``None`` becomes a keyword [4]_ (What about ``True``, ``False``?) * ``...`` to become a general expression element [24]_ -* ``as`` becomes a keyword [5]_ (probably in 2.6 already) +* ``as`` becomes a keyword [5]_ (probably in 2.6 already) [done] * Have list comprehensions be syntactic sugar for passing an equivalent generator expression to ``list()``; as a consequence the loop variable will no longer be exposed [12]_ * Comparisons other than ``==`` and ``!=`` between disparate types will raise an exception unless explicitly supported by the type [6]_ -* Exceptions will grow an attribute to store the traceback [13]_ +* Exceptions might grow an attribute to store the traceback [13]_ * floats will not be acceptable as arguments in place of ints for operations where floats are inadvertantly accepted (PyArg_ParseTuple() i & l formats) -* Imports will be absolute by default. - Relative imports must be explicitly specified [#pep328]_ -* __init__.py will be optional in sub-packages. __init__.py will still +* Imports will be absolute by default. [done] + Relative imports must be explicitly specified [#pep328]_ [done] +* __init__.py might become optional in sub-packages. __init__.py will still be required for top-level packages. * Cleanup the Py_InitModule() variants {,3,4} (also import and parser APIs) * Cleanup the APIs exported in pythonrun, etc. @@ -110,17 +107,18 @@ NB. {range(x)} means set([range(x)]), NOT set(range(x)). There's no literal for an empty set; use set() (or {1}&{2} :-). There's no frozenset literal; they are too rarely needed. -* Reconsider PEP 299 [30]_: special __main__() function in modules. +* Might reconsider PEP 299 [30]_: special __main__() function in modules. To be removed: -* String exceptions: use instances of an Exception class [2]_ +* String exceptions: use instances of an Exception class [2]_ [done] * ``raise Exception, "message"``: use ``raise Exception("message")`` [14]_ * ```x```: use ``repr(x)`` [2]_ * The ``<>`` operator: use ``!=`` instead [3]_ * The __mod__ and __divmod__ special methods on float. [29]_ -* Unbound methods [7]_ -* METH_OLDARGS, WITH_CYCLE_GC +* Might drop unbound methods? [7]_ +* METH_OLDARGS +* WITH_CYCLE_GC [done] * __getslice__, __setslice__, __delslice__ [17]_ * Remove slice opcodes and use slice objects * C APIs (see code): @@ -140,17 +138,17 @@ The new string type will be called 'str'. * Return iterators instead of lists where appropriate for atomic type methods (e.g. ``dict.keys()``, ``dict.values()``, ``dict.items()``, etc.); iter* - methods will be removed - OR make keys(), etc. return views ala Java collections??? + methods will be removed. + Better: make keys(), etc. return views ala Java collections??? * Make ``string.join()`` stringify its arguments? [26]_ To be removed: * ``basestring.find()`` and ``basestring.rfind()``; use ``basestring.index()`` - or ``basestring.rindex()`` in a try/except block [15]_ -* ``file.xreadlines()`` method [#file-object]_ -* ``dict.setdefault()`` [22]_ -* ``dict.has_key()`` method + or ``basestring.rindex()`` in a try/except block??? [15]_ +* ``file.xreadlines()`` method [#file-object]_ [done] +* ``dict.setdefault()``? [22]_ +* ``dict.has_key()`` method [done] Built-in Namespace @@ -159,23 +157,23 @@ * Make built-ins return an iterator where appropriate (e.g. ``range()``, ``zip()``, etc.) * Relevant functions should consume iterators (e.g. ``min()``, - ``max()``) + ``max()``) [They already do, since 2.2.] * Introduce ``trunc()``, which would call the ``__trunc__()`` method on its argument; suggested use is for objects like float where calling ``__int__()`` - has data loss, but an integral representation is still desired [8]_ -* Exception hierarchy changes [#pep352]_ + has data loss, but an integral representation is still desired? [8]_ +* Exception hierarchy changes [#pep352]_ [done] To be removed: -* ``apply()``: use ``f(*args, **kw)`` instead [2]_ -* ``buffer()``: must die (use a bytes() type instead) [2]_ +* ``apply()``: use ``f(*args, **kw)`` instead [2]_ [done] +* ``buffer()``: must die (use a bytes() type instead) (?) [2]_ * ``callable()``: just call the object and catch the exception [2]_ * ``compile()``: put in ``sys`` (or perhaps in a module of its own) [2]_ * ``coerce()``: no longer needed [2]_ * ``execfile()``, ``reload()``: use ``exec()`` [2]_ * ``input()``: use ``eval(sys.stdin.readline())`` [2]_ * ``intern()``, ``id()``: put in ``sys`` [2]_ -* ``map()``, ``filter()``: use list comprehensions instead [1]_, [9]_ +* ``map()``, ``filter()``: use list comprehensions instead??? [1]_, [9]_ * ``reduce()``: write a loop instead [2]_, [9]_ * ``raw_input()``: use ``sys.stdin.readline()`` [2]_ * ``xrange()``: use ``range()`` instead [1]_ @@ -184,9 +182,10 @@ Standard library ================ -* Reorganize the standard library to not be as shallow +* Reorganize the standard library to not be as shallow? * Move test code to where it belongs, there will be no more test() functions in the standard library +* Convert all tests to use either doctest or unittest. * For the procedures of standard library improvement, see PEP 3001 [#pep3001]_ To be removed: @@ -222,7 +221,8 @@ ================== * Require C99, so we can use // comments, named initializers, declare variables - without introducing a new scope, among other benefits. + without introducing a new scope, among other benefits. (Also better support + for IEEE floating point issues like NaN and infinities?) * Remove support for old systems, including: BeOS, RISCOS, (SGI) Irix, Tru64

1 0

EGECTI0N not lasting as it has in the past?
by gbirdwellltsf＠jtibs.net Aug. 18, 2006

Aug. 18, 2006

1 0

r51379 - python/trunk/Modules/_ctypes/_ctypes.c
by thomas.heller Aug. 18, 2006

Aug. 18, 2006

Author: thomas.heller Date: Fri Aug 18 16:38:46 2006 New Revision: 51379 Modified: python/trunk/Modules/_ctypes/_ctypes.c Log: Add asserts to check for 'impossible' NULL values, with comments. In one place where I'n not 1000% sure about the non-NULL, raise a RuntimeError for safety. This should fix the klocwork issues that Neal sent me. If so, it should be applied to the release25-maint branch also. Modified: python/trunk/Modules/_ctypes/_ctypes.c ============================================================================== --- python/trunk/Modules/_ctypes/_ctypes.c (original) +++ python/trunk/Modules/_ctypes/_ctypes.c Fri Aug 18 16:38:46 2006 @@ -672,6 +672,7 @@ return PyInt_FromLong(0); /* NULL pointer */ typedict = PyType_stgdict(type); + assert(typedict); /* Cannot be NULL for pointer types */ /* If we expect POINTER(<type>), but receive a <type> instance, accept it by calling byref(<type>). @@ -3129,6 +3130,13 @@ } ob = PyTuple_GET_ITEM(argtypes, i); dict = PyType_stgdict(ob); + if (dict == NULL) { + /* Cannot happen: _validate_paramflags() + would not accept such an object */ + PyErr_Format(PyExc_RuntimeError, + "NULL stgdict unexpected"); + goto error; + } if (PyString_Check(dict->proto)) { PyErr_Format( PyExc_TypeError, @@ -3726,6 +3734,8 @@ assert(stgdict); /* Cannot be NULL for array object instances */ proto = stgdict->proto; itemdict = PyType_stgdict(proto); + assert(itemdict); /* proto is the item type of the array, a ctypes + type, so this cannot be NULL */ if (itemdict->getfunc == getentry("c")->getfunc) { char *ptr = (char *)self->b_ptr; return PyString_FromStringAndSize(ptr + ilow, len); @@ -4159,6 +4169,9 @@ proto = stgdict->proto; assert(proto); itemdict = PyType_stgdict(proto); + assert(itemdict); /* proto is the item type of the pointer, a ctypes + type, so this cannot be NULL */ + size = itemdict->size; offset = index * itemdict->size; @@ -4194,6 +4207,9 @@ assert(proto); itemdict = PyType_stgdict(proto); + assert(itemdict); /* Cannot be NULL because the itemtype of a pointer + is always a ctypes type */ + size = itemdict->size; offset = index * itemdict->size;

2 1

r51387 - peps/trunk/pep-3000.txt
by guido.van.rossum Aug. 18, 2006

Aug. 18, 2006

Author: guido.van.rossum Date: Fri Aug 18 18:17:21 2006 New Revision: 51387 Modified: peps/trunk/pep-3000.txt Log: Py3k will be implemented in C, by evolving Python 2.x. Modified: peps/trunk/pep-3000.txt ============================================================================== --- peps/trunk/pep-3000.txt (original) +++ peps/trunk/pep-3000.txt Fri Aug 18 18:17:21 2006 @@ -94,6 +94,19 @@ with -Qwarnall.) +Implementation Language +======================= + +Python 3000 will be implemented in C, and the implementation will be +derived as an evolution of the Python 2 code base. This reflects my +views (which I share with Joel Spolsky) on the dangers of complete +rewrites. Since Python 3000 as a language is a relatively mild +improvement on Python 2, we can gain a lot by not attempting to +reimplement the language from scratch. I am not against parallel +from-scratch implementation efforts, but my own efforts will be +directed at the language and implementation that I know best. + + Meta-Contributions ==================

1 0

r51378 - python/trunk/Doc/api/abstract.tex python/trunk/Doc/api/concrete.tex
by andrew.kuchling Aug. 18, 2006

Aug. 18, 2006

Author: andrew.kuchling Date: Fri Aug 18 15:57:13 2006 New Revision: 51378 Modified: python/trunk/Doc/api/abstract.tex python/trunk/Doc/api/concrete.tex Log: Minor edits Modified: python/trunk/Doc/api/abstract.tex ============================================================================== --- python/trunk/Doc/api/abstract.tex (original) +++ python/trunk/Doc/api/abstract.tex Fri Aug 18 15:57:13 2006 @@ -6,7 +6,7 @@ for which they do not apply, they will raise a Python exception. It is not possible to use these functions on objects that are not properly -initialized, such a list object that has been created by +initialized, such as a list object that has been created by \cfunction{PyList_New()}, but whose items have not been set to some non-\code{NULL} value yet. Modified: python/trunk/Doc/api/concrete.tex ============================================================================== --- python/trunk/Doc/api/concrete.tex (original) +++ python/trunk/Doc/api/concrete.tex Fri Aug 18 15:57:13 2006 @@ -1842,8 +1842,8 @@ failure. \note{If \var{length} is greater than zero, the returned list object's items are set to \code{NULL}. Thus you cannot use abstract - API functions such as \cfunction{PySequence_SetItem()} on it - or expose it to Python code before setting all items to a + API functions such as \cfunction{PySequence_SetItem()} + or expose the object to Python code before setting all items to a real object with \cfunction{PyList_SetItem()}.} \end{cfuncdesc}

1 0

r51377 - python/branches/release24-maint/Doc/api/abstract.tex python/branches/release24-maint/Doc/api/concrete.tex
by andrew.kuchling Aug. 18, 2006

Aug. 18, 2006

Author: andrew.kuchling Date: Fri Aug 18 15:56:50 2006 New Revision: 51377 Modified: python/branches/release24-maint/Doc/api/abstract.tex python/branches/release24-maint/Doc/api/concrete.tex Log: Minor edits Modified: python/branches/release24-maint/Doc/api/abstract.tex ============================================================================== --- python/branches/release24-maint/Doc/api/abstract.tex (original) +++ python/branches/release24-maint/Doc/api/abstract.tex Fri Aug 18 15:56:50 2006 @@ -6,7 +6,7 @@ for which they do not apply, they will raise a Python exception. It is not possible to use these functions on objects that are not properly -initialized, such a list object that has been created by +initialized, such as a list object that has been created by \cfunction{PyList_New()}, but whose items have not been set to some non-\code{NULL} value yet. Modified: python/branches/release24-maint/Doc/api/concrete.tex ============================================================================== --- python/branches/release24-maint/Doc/api/concrete.tex (original) +++ python/branches/release24-maint/Doc/api/concrete.tex Fri Aug 18 15:56:50 2006 @@ -1768,8 +1768,8 @@ failure. \note{If \var{length} is greater than zero, the returned list object's items are set to \code{NULL}. Thus you cannot use abstract - API functions such as \cfunction{PySequence_SetItem()} on it - or expose it to Python code before setting all items to a + API functions such as \cfunction{PySequence_SetItem()} + or expose the object to Python code before setting all items to a real object with \cfunction{PyList_SetItem()}.} \end{cfuncdesc}

1 0

r51376 - python/branches/release25-maint/Doc/api/abstract.tex python/branches/release25-maint/Doc/api/concrete.tex
by andrew.kuchling Aug. 18, 2006

Aug. 18, 2006

Author: andrew.kuchling Date: Fri Aug 18 15:54:33 2006 New Revision: 51376 Modified: python/branches/release25-maint/Doc/api/abstract.tex python/branches/release25-maint/Doc/api/concrete.tex Log: Minor edits Modified: python/branches/release25-maint/Doc/api/abstract.tex ============================================================================== --- python/branches/release25-maint/Doc/api/abstract.tex (original) +++ python/branches/release25-maint/Doc/api/abstract.tex Fri Aug 18 15:54:33 2006 @@ -6,7 +6,7 @@ for which they do not apply, they will raise a Python exception. It is not possible to use these functions on objects that are not properly -initialized, such a list object that has been created by +initialized, such as a list object that has been created by \cfunction{PyList_New()}, but whose items have not been set to some non-\code{NULL} value yet. Modified: python/branches/release25-maint/Doc/api/concrete.tex ============================================================================== --- python/branches/release25-maint/Doc/api/concrete.tex (original) +++ python/branches/release25-maint/Doc/api/concrete.tex Fri Aug 18 15:54:33 2006 @@ -1842,8 +1842,8 @@ failure. \note{If \var{length} is greater than zero, the returned list object's items are set to \code{NULL}. Thus you cannot use abstract - API functions such as \cfunction{PySequence_SetItem()} on it - or expose it to Python code before setting all items to a + API functions such as \cfunction{PySequence_SetItem()} + or expose the object to Python code before setting all items to a real object with \cfunction{PyList_SetItem()}.} \end{cfuncdesc}

1 0

buildbot warnings in alpha Debian trunk
by buildbot＠python.org Aug. 18, 2006

Aug. 18, 2006

The Buildbot has detected a new failure of alpha Debian trunk. Full details are available at: http://www.python.org/dev/buildbot/all/alpha%2520Debian%2520trunk/builds/517 Buildbot URL: http://www.python.org/dev/buildbot/all/ Build Reason: Build Source Stamp: [branch trunk] HEAD Blamelist: anthony.baxter,georg.brandl,neal.norwitz Build Had Warnings: warnings test sincerely, -The Buildbot

1 0