--- python3.3-3.3.0.orig/debian/libPVER-dbg.overrides.in +++ python3.3-3.3.0/debian/libPVER-dbg.overrides.in @@ -0,0 +1,13 @@ +lib@PVER@-dbg binary: package-name-doesnt-match-sonames +lib@PVER@-dbg binary: non-dev-pkg-with-shlib-symlink + +# no, it's not unusual +lib@PVER@-dbg binary: unusual-interpreter + +# just the gdb debug file +@PVER@-dbg binary: python-script-but-no-python-dep + +# pointless lintian ... +lib@PVER@-dbg binary: hardening-no-fortify-functions + +lib@PVER@-dbg binary: arch-dependent-file-not-in-arch-specific-directory --- python3.3-3.3.0.orig/debian/pydoc.1.in +++ python3.3-3.3.0/debian/pydoc.1.in @@ -0,0 +1,53 @@ +.TH PYDOC@VER@ 1 +.SH NAME +pydoc@VER@ \- the Python documentation tool +.SH SYNOPSIS +.PP +.B pydoc@VER@ +.I name +.PP +.B pydoc@VER@ -k +.I keyword +.PP +.B pydoc@VER@ -p +.I port +.PP +.B pydoc@VER@ -g +.PP +.B pydoc@VER@ -w +.I module [...] +.SH DESCRIPTION +.PP +.B pydoc@VER@ +.I name +Show text documentation on something. +.I name +may be the name of a +Python keyword, topic, function, module, or package, or a dotted +reference to a class or function within a module or module in a +package. If +.I name +contains a '/', it is used as the path to a +Python source file to document. If name is 'keywords', 'topics', +or 'modules', a listing of these things is displayed. +.PP +.B pydoc@VER@ -k +.I keyword +Search for a keyword in the synopsis lines of all available modules. +.PP +.B pydoc@VER@ -p +.I port +Start an HTTP server on the given port on the local machine. +.PP +.B pydoc@VER@ -g +Pop up a graphical interface for finding and serving documentation. +.PP +.B pydoc@VER@ -w +.I name [...] +Write out the HTML documentation for a module to a file in the current +directory. If +.I name +contains a '/', it is treated as a filename; if +it names a directory, documentation is written for all the contents. +.SH AUTHOR +Moshe Zadka, based on "pydoc --help" --- python3.3-3.3.0.orig/debian/locale-gen +++ python3.3-3.3.0/debian/locale-gen @@ -0,0 +1,31 @@ +#!/bin/sh + +LOCPATH=`pwd`/locales +export LOCPATH + +[ -d $LOCPATH ] || mkdir -p $LOCPATH + +umask 022 + +echo "Generating locales..." +while read locale charset; do + case $locale in \#*) continue;; esac + [ -n "$locale" -a -n "$charset" ] || continue + echo -n " `echo $locale | sed 's/\([^.\@]*\).*/\1/'`" + echo -n ".$charset" + echo -n `echo $locale | sed 's/\([^\@]*\)\(\@.*\)*/\2/'` + echo -n '...' + if [ -f $LOCPATH/$locale ]; then + input=$locale + else + input=`echo $locale | sed 's/\([^.]*\)[^@]*\(.*\)/\1\2/'` + fi + localedef -i $input -c -f $charset $LOCPATH/$locale #-A /etc/locale.alias + echo ' done'; \ +done <&1 | awk '/Maximum/ {print int($NF / 4)}') + dpkg -L $pkg \ + | awk -F/ 'BEGIN {OFS="/"} /\.py$/ {$NF=sprintf("__pycache__/%s.*.py[co]", substr($NF,1,length($NF)-3)); print}' \ + | xargs --max-chars=$max echo \ + | while read files; do rm -f $files; done + if [ -d /usr/bin/__pycache__ ]; then + rmdir --ignore-fail-on-non-empty /usr/bin/__pycache__ + fi +} + +case "$1" in + remove) + remove_bytecode @PVER@-dbg + ;; + upgrade) + remove_bytecode @PVER@-dbg + ;; + deconfigure) + ;; + failed-upgrade) + ;; + *) + echo "prerm called with unknown argument \`$1'" >&2 + exit 1 + ;; +esac + +#DEBHELPER# --- python3.3-3.3.0.orig/debian/libPVER-minimal.postrm.in +++ python3.3-3.3.0/debian/libPVER-minimal.postrm.in @@ -0,0 +1,15 @@ +#! /bin/sh -e + +if [ "$1" = "purge" ]; then + for d in `find /usr/lib/@PVER@ -depth -type d -empty 2> /dev/null`; do \ + while rmdir $d 2> /dev/null; do d=`dirname $d`; done; \ + done + rm -rf /etc/@PVER@/site.py /etc/@PVER@/sitecustomize.py /etc/@PVER@/__pycache__ + if [ -d /etc/@PVER@ ]; then + rmdir --ignore-fail-on-non-empty /etc/@PVER@ + fi +fi + +#DEBHELPER# + +exit 0 --- python3.3-3.3.0.orig/debian/idle-PVER.postinst.in +++ python3.3-3.3.0/debian/idle-PVER.postinst.in @@ -0,0 +1,30 @@ +#! /bin/sh -e +# +# postinst script for the Debian idle-@PVER@ package. +# Written 1998 by Gregor Hoffleit . +# + +DIRLIST="/usr/lib/python@VER@/idlelib" + +case "$1" in + configure|abort-upgrade|abort-remove|abort-deconfigure) + + for i in $DIRLIST ; do + @PVER@ /usr/lib/@PVER@/compileall.py -q $i + if grep -sq '^byte-compile[^#]*optimize' /etc/python/debian_config + then + @PVER@ -O /usr/lib/@PVER@/compileall.py -q $i + fi + done + ;; + + *) + echo "postinst called with unknown argument \`$1'" >&2 + exit 1 + ;; + +esac + +#DEBHELPER# + +exit 0 --- python3.3-3.3.0.orig/debian/idle-PVER.postrm.in +++ python3.3-3.3.0/debian/idle-PVER.postrm.in @@ -0,0 +1,9 @@ +#! /bin/sh -e + +if [ "$1" = "purge" ]; then + rm -rf /etc/idle-@PVER@ +fi + +#DEBHELPER# + +exit 0 --- python3.3-3.3.0.orig/debian/watch +++ python3.3-3.3.0/debian/watch @@ -0,0 +1,3 @@ +version=3 +opts=dversionmangle=s/.*\+//,uversionmangle=s/([abcr]+[1-9])$/~$1/ \ + http://www.python.org/ftp/python/3\.2(\.\d)?/Python-(3\.2[.\dabcr]*)\.tgz --- python3.3-3.3.0.orig/debian/PVER-examples.overrides.in +++ python3.3-3.3.0/debian/PVER-examples.overrides.in @@ -0,0 +1,2 @@ +# don't care about permissions of the example files +@PVER@-examples binary: executable-not-elf-or-script --- python3.3-3.3.0.orig/debian/control +++ python3.3-3.3.0/debian/control @@ -0,0 +1,194 @@ +Source: python3.3 +Section: python +Priority: optional +Maintainer: Ubuntu Core Developers +XSBC-Original-Maintainer: Matthias Klose +Build-Depends: debhelper (>= 5.0.51~), quilt, autoconf, lsb-release, sharutils, + libreadline6-dev, libncursesw5-dev (>= 5.3), + zlib1g-dev, libbz2-dev, liblzma-dev, + libgdbm-dev, libdb-dev, + tk8.5-dev, blt-dev (>= 2.4z), libssl-dev, + libexpat1-dev, + libbluetooth-dev [!hurd-i386 !kfreebsd-i386 !kfreebsd-amd64], + locales [!armel !avr32 !hppa !ia64 !mipsel], + libsqlite3-dev, libffi-dev (>= 3.0.5), + libgpm2 [!hurd-i386 !kfreebsd-i386 !kfreebsd-amd64], + mime-support, netbase, bzip2, gdb, python3:any, + xvfb, xauth +Build-Depends-Indep: python-sphinx +Standards-Version: 3.9.3 +Vcs-Browser: https://code.launchpad.net/~doko/python/pkg3.3-debian +Vcs-Bzr: http://bazaar.launchpad.net/~doko/python/pkg3.3-debian + +Package: python3.3 +Architecture: any +Multi-Arch: allowed +Priority: optional +Depends: python3.3-minimal (= ${binary:Version}), libpython3.3-stdlib (= ${binary:Version}), mime-support, ${shlibs:Depends}, ${misc:Depends} +Suggests: python3.3-doc, binutils +Description: Interactive high-level object-oriented language (version 3.3) + Version 3.3 of the high-level, interactive object oriented language, + includes an extensive class library with lots of goodies for + network programming, system administration, sounds and graphics. + +Package: libpython3.3-stdlib +Architecture: any +Multi-Arch: same +Priority: optional +Pre-Depends: multiarch-support +Depends: libpython3.3-minimal (= ${binary:Version}), mime-support, ${shlibs:Depends}, ${misc:Depends} +Suggests: python3.3-profiler +Provides: python3.3-cjkcodecs, python3.3-ctypes, python3.3-elementtree, python3.3-celementtree, python3.3-wsgiref, python3.3-gdbm, python3.3-profiler, python3.3-lzma +Replaces: python3.3 (<< 3.3.0~rc1-1~) +Description: Interactive high-level object-oriented language (version 3.3) + Version 3.3 of the high-level, interactive object oriented language, + includes an extensive class library with lots of goodies for + network programming, system administration, sounds and graphics. + . + This package contains the standard library. It is normally not + used on it's own, but as a dependency of python3.3. + +Package: python3.3-minimal +Architecture: any +Multi-Arch: allowed +Priority: optional +Depends: libpython3.3-minimal (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends} +Recommends: python3.3 +Suggests: binfmt-support +Replaces: python3.3 (<< 3.3~a4-1~) +Conflicts: binfmt-support (<< 1.1.2) +Description: Minimal subset of the Python language (version 3.3) + This package contains the interpreter and some essential modules. It can + be used in the boot process for some basic tasks. + See /usr/share/doc/python3.3-minimal/README.Debian for a list of the modules + contained in this package. + +Package: libpython3.3-minimal +Architecture: any +Multi-Arch: same +Priority: optional +Pre-Depends: multiarch-support +Depends: ${shlibs:Depends}, ${misc:Depends} +Recommends: libpython3.3-stdlib +Replaces: python3.3 (<< 3.3~a4-1~), python3.3-minimal (<< 3.3.0~rc1-1~) +Conflicts: binfmt-support (<< 1.1.2) +Description: Minimal subset of the Python language (version 3.3) + This package contains some essential modules. It is normally not + used on it's own, but as a dependency of python3.3-minimal. + +Package: libpython3.3 +Architecture: any +Multi-Arch: same +Section: libs +Priority: optional +Pre-Depends: multiarch-support +Depends: libpython3.3-stdlib (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends} +Replaces: python3.3 (<< 3.0~rc1) +Description: Shared Python runtime library (version 3.3) + Version 3.3 of the high-level, interactive object oriented language, + includes an extensive class library with lots of goodies for + network programming, system administration, sounds and graphics. + . + This package contains the shared runtime library, normally not needed + for programs using the statically linked interpreter. + +Package: python3.3-examples +Architecture: all +Depends: python3.3 (>= ${source:Version}), ${misc:Depends} +Description: Examples for the Python language (v3.3) + Examples, Demos and Tools for Python (v3.3). These are files included in + the upstream Python distribution (v3.3). + +Package: python3.3-dev +Architecture: any +Multi-Arch: allowed +Depends: python3.3 (= ${binary:Version}), libpython3.3-dev (= ${binary:Version}), libpython3.3 (= ${binary:Version}), libexpat1-dev, ${shlibs:Depends}, ${misc:Depends} +Replaces: python3.3 (<< 3.2~rc1-2) +Recommends: libc6-dev | libc-dev +Description: Header files and a static library for Python (v3.3) + Header files, a static library and development tools for building + Python (v3.3) modules, extending the Python interpreter or embedding + Python (v3.3) in applications. + . + Maintainers of Python packages should read README.maintainers. + +Package: libpython3.3-dev +Section: libdevel +Architecture: any +Multi-Arch: same +Pre-Depends: multiarch-support +Depends: libpython3.3-stdlib (= ${binary:Version}), libpython3.3 (= ${binary:Version}), libexpat1-dev, ${shlibs:Depends}, ${misc:Depends} +Replaces: python3.3 (<< 3.2~rc1-2), python3.3-dev (<< 3.3.0~b1-2), python3.3-minimal (<< 3.3.0~rc1-1~) +Recommends: libc6-dev | libc-dev +Description: Header files and a static library for Python (v3.3) + Header files, a static library and development tools for building + Python (v3.3) modules, extending the Python interpreter or embedding + Python (v3.3) in applications. + . + Maintainers of Python packages should read README.maintainers. + . + This package contains development files. It is normally not + used on it's own, but as a dependency of python3.3-dev. + +Package: idle-python3.3 +Architecture: all +Depends: python3.3, python3-tk, python3.3-tk, ${misc:Depends} +Enhances: python3.3 +Description: IDE for Python (v3.3) using Tkinter + IDLE is an Integrated Development Environment for Python (v3.3). + IDLE is written using Tkinter and therefore quite platform-independent. + +Package: python3.3-doc +Section: doc +Architecture: all +Depends: libjs-jquery, libjs-underscore, ${misc:Depends} +Suggests: python3.3 +Description: Documentation for the high-level object-oriented language Python (v3.3) + These is the official set of documentation for the interactive high-level + object-oriented language Python (v3.3). All documents are provided + in HTML format. The package consists of ten documents: + . + * What's New in Python3.3 + * Tutorial + * Python Library Reference + * Macintosh Module Reference + * Python Language Reference + * Extending and Embedding Python + * Python/C API Reference + * Installing Python Modules + * Documenting Python + * Distributing Python Modules + +Package: python3.3-dbg +Section: debug +Architecture: any +Multi-Arch: allowed +Priority: extra +Depends: python3.3 (= ${binary:Version}), libpython3.3-dbg (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}, python +Suggests: python3-gdbm-dbg, python3-tk-dbg +Description: Debug Build of the Python Interpreter (version 3.3) + The package holds two things: + . + - A Python interpreter configured with --pydebug. Dynamically loaded modules + are searched as _d.so first. Third party extensions need a separate + build to be used by this interpreter. + - Debug information for standard python interpreter and extensions. + . + See the README.debug for more information. + +Package: libpython3.3-dbg +Section: debug +Architecture: any +Multi-Arch: same +Priority: extra +Pre-Depends: multiarch-support +Depends: libpython3.3-stdlib (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}, python +Suggests: python3-gdbm-dbg, python3-tk-dbg +Replaces: python3.3-dbg (<< 3.3.0~rc1-1) +Description: Debug Build of the Python Interpreter (version 3.3) + The package holds two things: + . + - Extensions for a Python interpreter configured with --pydebug. + - Debug information for standard python extensions. + . + See the README.debug for more information. --- python3.3-3.3.0.orig/debian/idle-PVER.prerm.in +++ python3.3-3.3.0/debian/idle-PVER.prerm.in @@ -0,0 +1,31 @@ +#! /bin/sh -e + +remove_bytecode() +{ + pkg=$1 + max=$(LANG=C LC_ALL=C xargs --show-limits < /dev/null 2>&1 | awk '/Maximum/ {print int($NF / 4)}') + dpkg -L $pkg \ + | awk -F/ 'BEGIN {OFS="/"} /\.py$/ {$NF=sprintf("__pycache__/%s.*.py[co]", substr($NF,1,length($NF)-3)); print}' \ + | xargs --max-chars=$max echo \ + | while read files; do rm -f $files; done + find /usr/lib/@PVER@ -name dist-packages -prune -o -name __pycache__ -empty -print \ + | xargs -r rm -rf +} + +case "$1" in + remove|upgrade) + remove_bytecode idle-@PVER@ + ;; + deconfigure) + ;; + failed-upgrade) + ;; + *) + echo "prerm called with unknown argument \`$1'" >&2 + exit 1 + ;; +esac + +#DEBHELPER# + +exit 0 --- python3.3-3.3.0.orig/debian/PVER-dbg.README.Debian.in +++ python3.3-3.3.0/debian/PVER-dbg.README.Debian.in @@ -0,0 +1,52 @@ +Contents of the @PVER@-dbg package +------------------------------------- + +For debugging python and extension modules, you may want to add the contents +of /usr/share/doc/@PVER@/gdbinit (found in the @PVER@-dev package) to your +~/.gdbinit file. + +@PVER@-dbg contains two sets of packages: + + - debugging symbols for the standard @PVER@ build. When this package + is installed, gdb will automatically load up the debugging symbols + from it when debugging @PVER@ or one of the included extension + modules. + + - a separate @PVER@-dbg binary, configured --with-pydebug, enabling the + additional debugging code to help debug memory management problems. + +For the latter, all extension modules have to be recompiled to +correctly load with an pydebug enabled build. + + +Debian and Ubuntu specific changes to the debug interpreter +----------------------------------------------------------- +The python2.4 and python2.5 packages in Ubuntu feisty are modified to +first look for extension modules under a different name. + + normal build: foo.so + debug build: foo_d.so foo.so + +This naming schema allows installation of the extension modules into +the same path (The naming is directly taken from the Windows builds +which already uses this naming scheme). + +See https://wiki.ubuntu.com/PyDbgBuilds for more information. + + +Using the python-dbg builds +--------------------------- + + * Call the python-dbg or the pythonX.Y-dbg binaries instead of the + python or pythonX.Y binaries. + + * Properties of the debug build are described in + /usr/share/doc/@PVER@/SpecialBuilds.txt.gz. + The debug interpreter is built with Py_DEBUG defined. + + * From SpecialBuilds.txt: This is what is generally meant by "a debug + build" of Python. Py_DEBUG implies LLTRACE, Py_REF_DEBUG, + Py_TRACE_REFS, and PYMALLOC_DEBUG (if WITH_PYMALLOC is enabled). + In addition, C assert()s are enabled (via the C way: by not defining + NDEBUG), and some routines do additional sanity checks inside + "#ifdef Py_DEBUG" blocks. --- python3.3-3.3.0.orig/debian/copyright +++ python3.3-3.3.0/debian/copyright @@ -0,0 +1,1027 @@ +This package was put together by Klee Dienes from +sources from ftp.python.org:/pub/python, based on the Debianization by +the previous maintainers Bernd S. Brentrup and +Bruce Perens. Current maintainer is Matthias Klose . + +It was downloaded from http://python.org/ + +Copyright: + +Upstream Author: Guido van Rossum and others. + +License: + +The following text includes the Python license and licenses and +acknowledgements for incorporated software. The licenses can be read +in the HTML and texinfo versions of the documentation as well, after +installing the pythonx.y-doc package. Licenses for files not licensed +under the Python Licenses are found at the end of this file. + + +Python License +============== + +A. HISTORY OF THE SOFTWARE +========================== + +Python was created in the early 1990s by Guido van Rossum at Stichting +Mathematisch Centrum (CWI, see http://www.cwi.nl) in the Netherlands +as a successor of a language called ABC. Guido remains Python's +principal author, although it includes many contributions from others. + +In 1995, Guido continued his work on Python at the Corporation for +National Research Initiatives (CNRI, see http://www.cnri.reston.va.us) +in Reston, Virginia where he released several versions of the +software. + +In May 2000, Guido and the Python core development team moved to +BeOpen.com to form the BeOpen PythonLabs team. In October of the same +year, the PythonLabs team moved to Digital Creations (now Zope +Corporation, see http://www.zope.com). In 2001, the Python Software +Foundation (PSF, see http://www.python.org/psf/) was formed, a +non-profit organization created specifically to own Python-related +Intellectual Property. Zope Corporation is a sponsoring member of +the PSF. + +All Python releases are Open Source (see http://www.opensource.org for +the Open Source Definition). Historically, most, but not all, Python +releases have also been GPL-compatible; the table below summarizes +the various releases. + + Release Derived Year Owner GPL- + from compatible? (1) + + 0.9.0 thru 1.2 1991-1995 CWI yes + 1.3 thru 1.5.2 1.2 1995-1999 CNRI yes + 1.6 1.5.2 2000 CNRI no + 2.0 1.6 2000 BeOpen.com no + 1.6.1 1.6 2001 CNRI yes (2) + 2.1 2.0+1.6.1 2001 PSF no + 2.0.1 2.0+1.6.1 2001 PSF yes + 2.1.1 2.1+2.0.1 2001 PSF yes + 2.2 2.1.1 2001 PSF yes + 2.1.2 2.1.1 2002 PSF yes + 2.1.3 2.1.2 2002 PSF yes + 2.2.1 2.2 2002 PSF yes + 2.2.2 2.2.1 2002 PSF yes + 2.2.3 2.2.2 2003 PSF yes + 2.3 2.2.2 2002-2003 PSF yes + 2.3.1 2.3 2002-2003 PSF yes + 2.3.2 2.3.1 2002-2003 PSF yes + 2.3.3 2.3.2 2002-2003 PSF yes + 2.3.4 2.3.3 2004 PSF yes + 2.3.5 2.3.4 2005 PSF yes + 2.4 2.3 2004 PSF yes + 2.4.1 2.4 2005 PSF yes + 2.4.2 2.4.1 2005 PSF yes + 2.4.3 2.4.2 2006 PSF yes + 2.5 2.4 2006 PSF yes + 2.5.1 2.5 2007 PSF yes + 2.5.2 2.5.1 2008 PSF yes + 2.5.3 2.5.2 2008 PSF yes + 2.6 2.5 2008 PSF yes + 2.6.1 2.6 2008 PSF yes + 2.6.2 2.6.1 2009 PSF yes + 2.6.3 2.6.2 2009 PSF yes + 2.6.4 2.6.3 2009 PSF yes + 2.6.5 2.6.4 2010 PSF yes + 3.0 2.6 2008 PSF yes + 3.0.1 3.0 2009 PSF yes + 3.1 3.0.1 2009 PSF yes + 3.1.1 3.1 2009 PSF yes + 3.1.2 3.1.1 2010 PSF yes + 3.1.3 3.1.2 2010 PSF yes + 3.1.4 3.1.3 2011 PSF yes + 3.2 3.1 2011 PSF yes + 3.2.1 3.2 2011 PSF yes + 3.2.2 3.2.1 2011 PSF yes + 3.3 3.2 2012 PSF yes + +Footnotes: + +(1) GPL-compatible doesn't mean that we're distributing Python under + the GPL. All Python licenses, unlike the GPL, let you distribute + a modified version without making your changes open source. The + GPL-compatible licenses make it possible to combine Python with + other software that is released under the GPL; the others don't. + +(2) According to Richard Stallman, 1.6.1 is not GPL-compatible, + because its license has a choice of law clause. According to + CNRI, however, Stallman's lawyer has told CNRI's lawyer that 1.6.1 + is "not incompatible" with the GPL. + +Thanks to the many outside volunteers who have worked under Guido's +direction to make these releases possible. + + +B. TERMS AND CONDITIONS FOR ACCESSING OR OTHERWISE USING PYTHON +=============================================================== + +PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 +-------------------------------------------- + +1. This LICENSE AGREEMENT is between the Python Software Foundation +("PSF"), and the Individual or Organization ("Licensee") accessing and +otherwise using this software ("Python") in source or binary form and +its associated documentation. + +2. Subject to the terms and conditions of this License Agreement, PSF +hereby grants Licensee a nonexclusive, royalty-free, world-wide +license to reproduce, analyze, test, perform and/or display publicly, +prepare derivative works, distribute, and otherwise use Python +alone or in any derivative version, provided, however, that PSF's +License Agreement and PSF's notice of copyright, i.e., "Copyright (c) +2001, 2002, 2003, 2004, 2005, 2006, 2007 Python Software Foundation; +All Rights Reserved" are retained in Python alone or in any derivative +version prepared by Licensee. + +3. In the event Licensee prepares a derivative work that is based on +or incorporates Python or any part thereof, and wants to make +the derivative work available to others as provided herein, then +Licensee hereby agrees to include in any such work a brief summary of +the changes made to Python. + +4. PSF is making Python available to Licensee on an "AS IS" +basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR +IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND +DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS +FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT +INFRINGE ANY THIRD PARTY RIGHTS. + +5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON +FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS +A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON, +OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. + +6. This License Agreement will automatically terminate upon a material +breach of its terms and conditions. + +7. Nothing in this License Agreement shall be deemed to create any +relationship of agency, partnership, or joint venture between PSF and +Licensee. This License Agreement does not grant permission to use PSF +trademarks or trade name in a trademark sense to endorse or promote +products or services of Licensee, or any third party. + +8. By copying, installing or otherwise using Python, Licensee +agrees to be bound by the terms and conditions of this License +Agreement. + + +BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0 +------------------------------------------- + +BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1 + +1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an +office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the +Individual or Organization ("Licensee") accessing and otherwise using +this software in source or binary form and its associated +documentation ("the Software"). + +2. Subject to the terms and conditions of this BeOpen Python License +Agreement, BeOpen hereby grants Licensee a non-exclusive, +royalty-free, world-wide license to reproduce, analyze, test, perform +and/or display publicly, prepare derivative works, distribute, and +otherwise use the Software alone or in any derivative version, +provided, however, that the BeOpen Python License is retained in the +Software, alone or in any derivative version prepared by Licensee. + +3. BeOpen is making the Software available to Licensee on an "AS IS" +basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR +IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND +DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS +FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT +INFRINGE ANY THIRD PARTY RIGHTS. + +4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE +SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS +AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY +DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. + +5. This License Agreement will automatically terminate upon a material +breach of its terms and conditions. + +6. This License Agreement shall be governed by and interpreted in all +respects by the law of the State of California, excluding conflict of +law provisions. Nothing in this License Agreement shall be deemed to +create any relationship of agency, partnership, or joint venture +between BeOpen and Licensee. This License Agreement does not grant +permission to use BeOpen trademarks or trade names in a trademark +sense to endorse or promote products or services of Licensee, or any +third party. As an exception, the "BeOpen Python" logos available at +http://www.pythonlabs.com/logos.html may be used according to the +permissions granted on that web page. + +7. By copying, installing or otherwise using the software, Licensee +agrees to be bound by the terms and conditions of this License +Agreement. + + +CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1 +--------------------------------------- + +1. This LICENSE AGREEMENT is between the Corporation for National +Research Initiatives, having an office at 1895 Preston White Drive, +Reston, VA 20191 ("CNRI"), and the Individual or Organization +("Licensee") accessing and otherwise using Python 1.6.1 software in +source or binary form and its associated documentation. + +2. Subject to the terms and conditions of this License Agreement, CNRI +hereby grants Licensee a nonexclusive, royalty-free, world-wide +license to reproduce, analyze, test, perform and/or display publicly, +prepare derivative works, distribute, and otherwise use Python 1.6.1 +alone or in any derivative version, provided, however, that CNRI's +License Agreement and CNRI's notice of copyright, i.e., "Copyright (c) +1995-2001 Corporation for National Research Initiatives; All Rights +Reserved" are retained in Python 1.6.1 alone or in any derivative +version prepared by Licensee. Alternately, in lieu of CNRI's License +Agreement, Licensee may substitute the following text (omitting the +quotes): "Python 1.6.1 is made available subject to the terms and +conditions in CNRI's License Agreement. This Agreement together with +Python 1.6.1 may be located on the Internet using the following +unique, persistent identifier (known as a handle): 1895.22/1013. This +Agreement may also be obtained from a proxy server on the Internet +using the following URL: http://hdl.handle.net/1895.22/1013". + +3. In the event Licensee prepares a derivative work that is based on +or incorporates Python 1.6.1 or any part thereof, and wants to make +the derivative work available to others as provided herein, then +Licensee hereby agrees to include in any such work a brief summary of +the changes made to Python 1.6.1. + +4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS" +basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR +IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND +DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS +FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT +INFRINGE ANY THIRD PARTY RIGHTS. + +5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON +1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS +A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1, +OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. + +6. This License Agreement will automatically terminate upon a material +breach of its terms and conditions. + +7. This License Agreement shall be governed by the federal +intellectual property law of the United States, including without +limitation the federal copyright law, and, to the extent such +U.S. federal law does not apply, by the law of the Commonwealth of +Virginia, excluding Virginia's conflict of law provisions. +Notwithstanding the foregoing, with regard to derivative works based +on Python 1.6.1 that incorporate non-separable material that was +previously distributed under the GNU General Public License (GPL), the +law of the Commonwealth of Virginia shall govern this License +Agreement only as to issues arising under or with respect to +Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this +License Agreement shall be deemed to create any relationship of +agency, partnership, or joint venture between CNRI and Licensee. This +License Agreement does not grant permission to use CNRI trademarks or +trade name in a trademark sense to endorse or promote products or +services of Licensee, or any third party. + +8. By clicking on the "ACCEPT" button where indicated, or by copying, +installing or otherwise using Python 1.6.1, Licensee agrees to be +bound by the terms and conditions of this License Agreement. + + ACCEPT + + +CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2 +-------------------------------------------------- + +Copyright (c) 1991 - 1995, Stichting Mathematisch Centrum Amsterdam, +The Netherlands. All rights reserved. + +Permission to use, copy, modify, and distribute this software and its +documentation for any purpose and without fee is hereby granted, +provided that the above copyright notice appear in all copies and that +both that copyright notice and this permission notice appear in +supporting documentation, and that the name of Stichting Mathematisch +Centrum or CWI not be used in advertising or publicity pertaining to +distribution of the software without specific, written prior +permission. + +STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO +THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND +FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE +FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT +OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. + + +Licenses and Acknowledgements for Incorporated Software +======================================================= + +Mersenne Twister +---------------- + +The `_random' module includes code based on a download from +`http://www.math.keio.ac.jp/~matumoto/MT2002/emt19937ar.html'. The +following are the verbatim comments from the original code: + + A C-program for MT19937, with initialization improved 2002/1/26. + Coded by Takuji Nishimura and Makoto Matsumoto. + + Before using, initialize the state by using init_genrand(seed) + or init_by_array(init_key, key_length). + + Copyright (C) 1997 - 2002, Makoto Matsumoto and Takuji Nishimura, + All rights reserved. + + Redistribution and use in source and binary forms, with or without + modification, are permitted provided that the following conditions + are met: + + 1. Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. + + 2. Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in the + documentation and/or other materials provided with the distribution. + + 3. The names of its contributors may not be used to endorse or promote + products derived from this software without specific prior written + permission. + + THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS + "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT + LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR + A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT + OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, + SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED + TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR + PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF + LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING + NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS + SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + + Any feedback is very welcome. + http://www.math.keio.ac.jp/matumoto/emt.html + email: matumoto@math.keio.ac.jp + + +Sockets +------- + +The `socket' module uses the functions, `getaddrinfo', and +`getnameinfo', which are coded in separate source files from the WIDE +Project, `http://www.wide.ad.jp/about/index.html'. + + Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project. + All rights reserved. + + Redistribution and use in source and binary forms, with or without + modification, are permitted provided that the following conditions + are met: + 1. Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. + 2. Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in the + documentation and/or other materials provided with the distribution. + 3. Neither the name of the project nor the names of its contributors + may be used to endorse or promote products derived from this software + without specific prior written permission. + + THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND + GAI_ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE + IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE + FOR GAI_ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR + CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF + SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS + INTERRUPTION) HOWEVER CAUSED AND ON GAI_ANY THEORY OF LIABILITY, WHETHER + IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) + ARISING IN GAI_ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED + OF THE POSSIBILITY OF SUCH DAMAGE. + + +Floating point exception control +-------------------------------- + +The source for the `fpectl' module includes the following notice: + + --------------------------------------------------------------------- + / Copyright (c) 1996. \ + | The Regents of the University of California. | + | All rights reserved. | + | | + | Permission to use, copy, modify, and distribute this software for | + | any purpose without fee is hereby granted, provided that this en- | + | tire notice is included in all copies of any software which is or | + | includes a copy or modification of this software and in all | + | copies of the supporting documentation for such software. | + | | + | This work was produced at the University of California, Lawrence | + | Livermore National Laboratory under contract no. W-7405-ENG-48 | + | between the U.S. Department of Energy and The Regents of the | + | University of California for the operation of UC LLNL. | + | | + | DISCLAIMER | + | | + | This software was prepared as an account of work sponsored by an | + | agency of the United States Government. Neither the United States | + | Government nor the University of California nor any of their em- | + | ployees, makes any warranty, express or implied, or assumes any | + | liability or responsibility for the accuracy, completeness, or | + | usefulness of any information, apparatus, product, or process | + | disclosed, or represents that its use would not infringe | + | privately-owned rights. Reference herein to any specific commer- | + | cial products, process, or service by trade name, trademark, | + | manufacturer, or otherwise, does not necessarily constitute or | + | imply its endorsement, recommendation, or favoring by the United | + | States Government or the University of California. The views and | + | opinions of authors expressed herein do not necessarily state or | + | reflect those of the United States Government or the University | + | of California, and shall not be used for advertising or product | + \ endorsement purposes. / + --------------------------------------------------------------------- + + +Cookie management +----------------- + +The `Cookie' module contains the following notice: + + Copyright 2000 by Timothy O'Malley + + All Rights Reserved + + Permission to use, copy, modify, and distribute this software + and its documentation for any purpose and without fee is hereby + granted, provided that the above copyright notice appear in all + copies and that both that copyright notice and this permission + notice appear in supporting documentation, and that the name of + Timothy O'Malley not be used in advertising or publicity + pertaining to distribution of the software without specific, written + prior permission. + + Timothy O'Malley DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS + SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY + AND FITNESS, IN NO EVENT SHALL Timothy O'Malley BE LIABLE FOR + ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES + WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, + WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS + ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR + PERFORMANCE OF THIS SOFTWARE. + + +Execution tracing +----------------- + +The `trace' module contains the following notice: + + portions copyright 2001, Autonomous Zones Industries, Inc., all rights... + err... reserved and offered to the public under the terms of the + Python 2.2 license. + Author: Zooko O'Whielacronx + http://zooko.com/ + mailto:zooko@zooko.com + + Copyright 2000, Mojam Media, Inc., all rights reserved. + Author: Skip Montanaro + + Copyright 1999, Bioreason, Inc., all rights reserved. + Author: Andrew Dalke + + Copyright 1995-1997, Automatrix, Inc., all rights reserved. + Author: Skip Montanaro + + Copyright 1991-1995, Stichting Mathematisch Centrum, all rights reserved. + + Permission to use, copy, modify, and distribute this Python software and + its associated documentation for any purpose without fee is hereby + granted, provided that the above copyright notice appears in all copies, + and that both that copyright notice and this permission notice appear in + supporting documentation, and that the name of neither Automatrix, + Bioreason or Mojam Media be used in advertising or publicity pertaining + to distribution of the software without specific, written prior + permission. + + +UUencode and UUdecode functions +------------------------------- + +The `uu' module contains the following notice: + + Copyright 1994 by Lance Ellinghouse + Cathedral City, California Republic, United States of America. + All Rights Reserved + Permission to use, copy, modify, and distribute this software and its + documentation for any purpose and without fee is hereby granted, + provided that the above copyright notice appear in all copies and that + both that copyright notice and this permission notice appear in + supporting documentation, and that the name of Lance Ellinghouse + not be used in advertising or publicity pertaining to distribution + of the software without specific, written prior permission. + LANCE ELLINGHOUSE DISCLAIMS ALL WARRANTIES WITH REGARD TO + THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND + FITNESS, IN NO EVENT SHALL LANCE ELLINGHOUSE CENTRUM BE LIABLE + FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES + WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN + ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT + OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. + + Modified by Jack Jansen, CWI, July 1995: + - Use binascii module to do the actual line-by-line conversion + between ascii and binary. This results in a 1000-fold speedup. The C + version is still 5 times faster, though. + - Arguments more compliant with python standard + + +XML Remote Procedure Calls +-------------------------- + +The `xmlrpclib' module contains the following notice: + + The XML-RPC client interface is + + Copyright (c) 1999-2002 by Secret Labs AB + Copyright (c) 1999-2002 by Fredrik Lundh + + By obtaining, using, and/or copying this software and/or its + associated documentation, you agree that you have read, understood, + and will comply with the following terms and conditions: + + Permission to use, copy, modify, and distribute this software and + its associated documentation for any purpose and without fee is + hereby granted, provided that the above copyright notice appears in + all copies, and that both that copyright notice and this permission + notice appear in supporting documentation, and that the name of + Secret Labs AB or the author not be used in advertising or publicity + pertaining to distribution of the software without specific, written + prior permission. + + SECRET LABS AB AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD + TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANT- + ABILITY AND FITNESS. IN NO EVENT SHALL SECRET LABS AB OR THE AUTHOR + BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY + DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, + WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS + ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE + OF THIS SOFTWARE. + +Licenses for Software linked to +=============================== + +Note that the choice of GPL compatibility outlined above doesn't extend +to modules linked to particular libraries, since they change the +effective License of the module binary. + + +GNU Readline +------------ + +The 'readline' module makes use of GNU Readline. + + The GNU Readline Library is free software; you can redistribute it + and/or modify it under the terms of the GNU General Public License as + published by the Free Software Foundation; either version 2, or (at + your option) any later version. + + On Debian systems, you can find the complete statement in + /usr/share/doc/readline-common/copyright'. A copy of the GNU General + Public License is available in /usr/share/common-licenses/GPL-2'. + + +OpenSSL +------- + +The '_ssl' module makes use of OpenSSL. + + The OpenSSL toolkit stays under a dual license, i.e. both the + conditions of the OpenSSL License and the original SSLeay license + apply to the toolkit. Actually both licenses are BSD-style Open + Source licenses. Note that both licenses are incompatible with + the GPL. + + On Debian systems, you can find the complete license text in + /usr/share/doc/openssl/copyright'. + + +Files with other licenses than the Python License +------------------------------------------------- + +Files: Include/dynamic_annotations.h +Files: Python/dynamic_annotations.c +Copyright: (c) 2008-2009, Google Inc. +License: Redistribution and use in source and binary forms, with or without + modification, are permitted provided that the following conditions are + met: + + * Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. + * Neither the name of Google Inc. nor the names of its + contributors may be used to endorse or promote products derived from + this software without specific prior written permission. + + THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS + "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT + LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR + A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT + OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, + SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT + LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, + DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY + THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT + (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE + OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + +Files: Include/unicodeobject.h +Copyright: (c) Corporation for National Research Initiatives. +Copyright: (c) 1999 by Secret Labs AB. +Copyright: (c) 1999 by Fredrik Lundh. +License: By obtaining, using, and/or copying this software and/or its + associated documentation, you agree that you have read, understood, + and will comply with the following terms and conditions: + + Permission to use, copy, modify, and distribute this software and its + associated documentation for any purpose and without fee is hereby + granted, provided that the above copyright notice appears in all + copies, and that both that copyright notice and this permission notice + appear in supporting documentation, and that the name of Secret Labs + AB or the author not be used in advertising or publicity pertaining to + distribution of the software without specific, written prior + permission. + + SECRET LABS AB AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO + THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND + FITNESS. IN NO EVENT SHALL SECRET LABS AB OR THE AUTHOR BE LIABLE FOR + ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES + WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN + ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT + OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. + +Files: Lib/logging/* +Copyright: 2001-2010 by Vinay Sajip. All Rights Reserved. +License: Permission to use, copy, modify, and distribute this software and + its documentation for any purpose and without fee is hereby granted, + provided that the above copyright notice appear in all copies and that + both that copyright notice and this permission notice appear in + supporting documentation, and that the name of Vinay Sajip + not be used in advertising or publicity pertaining to distribution + of the software without specific, written prior permission. + VINAY SAJIP DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING + ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL + VINAY SAJIP BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR + ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER + IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT + OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. + +Files: Lib/multiprocessing/* +Files: Modules/_multiprocessing/* +Copyright: (c) 2006-2008, R Oudkerk. All rights reserved. +License: Redistribution and use in source and binary forms, with or without + modification, are permitted provided that the following conditions + are met: + + 1. Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. + 2. Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in the + documentation and/or other materials provided with the distribution. + 3. Neither the name of author nor the names of any contributors may be + used to endorse or promote products derived from this software + without specific prior written permission. + + THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND + ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE + IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE + FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS + OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) + HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT + LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY + OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + SUCH DAMAGE. + +Files: Lib/sqlite3/* +Files: Modules/_sqlite/* +Copyright: (C) 2004-2005 Gerhard Häring +License: This software is provided 'as-is', without any express or implied + warranty. In no event will the authors be held liable for any damages + arising from the use of this software. + + Permission is granted to anyone to use this software for any purpose, + including commercial applications, and to alter it and redistribute it + freely, subject to the following restrictions: + + 1. The origin of this software must not be misrepresented; you must not + claim that you wrote the original software. If you use this software + in a product, an acknowledgment in the product documentation would be + appreciated but is not required. + 2. Altered source versions must be plainly marked as such, and must not be + misrepresented as being the original software. + 3. This notice may not be removed or altered from any source distribution. + +Files: Lib/async* +Copyright: Copyright 1996 by Sam Rushing +License: Permission to use, copy, modify, and distribute this software and + its documentation for any purpose and without fee is hereby + granted, provided that the above copyright notice appear in all + copies and that both that copyright notice and this permission + notice appear in supporting documentation, and that the name of Sam + Rushing not be used in advertising or publicity pertaining to + distribution of the software without specific, written prior + permission. + + SAM RUSHING DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, + INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN + NO EVENT SHALL SAM RUSHING BE LIABLE FOR ANY SPECIAL, INDIRECT OR + CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS + OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, + NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN + CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. + +Files: Lib/tarfile.py +Copyright: (C) 2002 Lars Gustaebel +License: Permission is hereby granted, free of charge, to any person + obtaining a copy of this software and associated documentation + files (the "Software"), to deal in the Software without + restriction, including without limitation the rights to use, + copy, modify, merge, publish, distribute, sublicense, and/or sell + copies of the Software, and to permit persons to whom the + Software is furnished to do so, subject to the following + conditions: + + The above copyright notice and this permission notice shall be + included in all copies or substantial portions of the Software. + + THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, + EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES + OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND + NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT + HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, + WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING + FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR + OTHER DEALINGS IN THE SOFTWARE. + +Files: Lib/turtle.py +Copyright: (C) 2006 - 2010 Gregor Lingl +License: This software is provided 'as-is', without any express or implied + warranty. In no event will the authors be held liable for any damages + arising from the use of this software. + + Permission is granted to anyone to use this software for any purpose, + including commercial applications, and to alter it and redistribute it + freely, subject to the following restrictions: + + 1. The origin of this software must not be misrepresented; you must not + claim that you wrote the original software. If you use this software + in a product, an acknowledgment in the product documentation would be + appreciated but is not required. + 2. Altered source versions must be plainly marked as such, and must not be + misrepresented as being the original software. + 3. This notice may not be removed or altered from any source distribution. + + is copyright Gregor Lingl and licensed under a BSD-like license + +Files: Modules/_ctypes/libffi/* +Copyright: Copyright (C) 1996-2011 Red Hat, Inc and others. + Copyright (C) 1996-2011 Anthony Green + Copyright (C) 1996-2010 Free Software Foundation, Inc + Copyright (c) 2003, 2004, 2006, 2007, 2008 Kaz Kojima + Copyright (c) 2010, 2011, Plausible Labs Cooperative , Inc. + Copyright (c) 2010 CodeSourcery + Copyright (c) 1998 Andreas Schwab + Copyright (c) 2000 Hewlett Packard Company + Copyright (c) 2009 Bradley Smith + Copyright (c) 2008 David Daney + Copyright (c) 2004 Simon Posnjak + Copyright (c) 2005 Axis Communications AB + Copyright (c) 1998 Cygnus Solutions + Copyright (c) 2004 Renesas Technology + Copyright (c) 2002, 2007 Bo Thorsen + Copyright (c) 2002 Ranjit Mathew + Copyright (c) 2002 Roger Sayle + Copyright (c) 2000, 2007 Software AG + Copyright (c) 2003 Jakub Jelinek + Copyright (c) 2000, 2001 John Hornkvist + Copyright (c) 1998 Geoffrey Keating + Copyright (c) 2008 Björn König + +License: Permission is hereby granted, free of charge, to any person obtaining + a copy of this software and associated documentation files (the + ``Software''), to deal in the Software without restriction, including + without limitation the rights to use, copy, modify, merge, publish, + distribute, sublicense, and/or sell copies of the Software, and to + permit persons to whom the Software is furnished to do so, subject to + the following conditions: + + The above copyright notice and this permission notice shall be included + in all copies or substantial portions of the Software. + + THE SOFTWARE IS PROVIDED ``AS IS'', WITHOUT WARRANTY OF ANY KIND, + EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF + MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND + NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT + HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, + WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, + OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER + DEALINGS IN THE SOFTWARE. + + Documentation: + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU General Public License as published by the + Free Software Foundation; either version 2, or (at your option) any + later version. A copy of the license is included in the + section entitled ``GNU General Public License''. + +Files: Modules/_gestalt.c +Copyright: 1991-1997 by Stichting Mathematisch Centrum, Amsterdam. +License: Permission to use, copy, modify, and distribute this software and its + documentation for any purpose and without fee is hereby granted, + provided that the above copyright notice appear in all copies and that + both that copyright notice and this permission notice appear in + supporting documentation, and that the names of Stichting Mathematisch + Centrum or CWI not be used in advertising or publicity pertaining to + distribution of the software without specific, written prior permission. + + STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO + THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND + FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE + FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES + WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN + ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT + OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. + +Files: Modules/syslogmodule.c +Copyright: 1994 by Lance Ellinghouse +License: Permission to use, copy, modify, and distribute this software and its + documentation for any purpose and without fee is hereby granted, + provided that the above copyright notice appear in all copies and that + both that copyright notice and this permission notice appear in + supporting documentation, and that the name of Lance Ellinghouse + not be used in advertising or publicity pertaining to distribution + of the software without specific, written prior permission. + + LANCE ELLINGHOUSE DISCLAIMS ALL WARRANTIES WITH REGARD TO + THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND + FITNESS, IN NO EVENT SHALL LANCE ELLINGHOUSE BE LIABLE FOR ANY SPECIAL, + INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING + FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, + NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION + WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. + +Files: Modules/zlib/* +Copyright: (C) 1995-2010 Jean-loup Gailly and Mark Adler +License: This software is provided 'as-is', without any express or implied + warranty. In no event will the authors be held liable for any damages + arising from the use of this software. + + Permission is granted to anyone to use this software for any purpose, + including commercial applications, and to alter it and redistribute it + freely, subject to the following restrictions: + + 1. The origin of this software must not be misrepresented; you must not + claim that you wrote the original software. If you use this software + in a product, an acknowledgment in the product documentation would be + appreciated but is not required. + 2. Altered source versions must be plainly marked as such, and must not be + misrepresented as being the original software. + 3. This notice may not be removed or altered from any source distribution. + + Jean-loup Gailly Mark Adler + jloup@gzip.org madler@alumni.caltech.edu + + If you use the zlib library in a product, we would appreciate *not* receiving + lengthy legal documents to sign. The sources are provided for free but without + warranty of any kind. The library has been entirely written by Jean-loup + Gailly and Mark Adler; it does not include third-party code. + +Files: Modules/expat/* +Copyright: Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd + and Clark Cooper + Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006 Expat maintainers +License: Permission is hereby granted, free of charge, to any person obtaining + a copy of this software and associated documentation files (the + "Software"), to deal in the Software without restriction, including + without limitation the rights to use, copy, modify, merge, publish, + distribute, sublicense, and/or sell copies of the Software, and to + permit persons to whom the Software is furnished to do so, subject to + the following conditions: + + The above copyright notice and this permission notice shall be included + in all copies or substantial portions of the Software. + + THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, + EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF + MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. + IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY + CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, + TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE + SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. + +Files: Modules/_decimal/libmpdec/* +Copyright: Copyright (c) 2008-2012 Stefan Krah. All rights reserved. +License: Redistribution and use in source and binary forms, with or without + modification, are permitted provided that the following conditions + are met: + . + 1. Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. + . + 2. Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in the + documentation and/or other materials provided with the distribution. + , + THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND + ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE + IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE + FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS + OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) + HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT + LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY + OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + SUCH DAMAGE. + +Files: Misc/python-mode.el +Copyright: Copyright (C) 1992,1993,1994 Tim Peters +License: This software is provided as-is, without express or implied + warranty. Permission to use, copy, modify, distribute or sell this + software, without fee, for any purpose and by any individual or + organization, is hereby granted, provided that the above copyright + notice and this paragraph appear in all copies. + +Files: Python/dtoa.c +Copyright: (c) 1991, 2000, 2001 by Lucent Technologies. +License: Permission to use, copy, modify, and distribute this software for any + purpose without fee is hereby granted, provided that this entire notice + is included in all copies of any software which is or includes a copy + or modification of this software and in all copies of the supporting + documentation for such software. + + THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED + WARRANTY. IN PARTICULAR, NEITHER THE AUTHOR NOR LUCENT MAKES ANY + REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY + OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE. + +Files: Python/getopt.c +Copyright: 1992-1994, David Gottner +License: Permission to use, copy, modify, and distribute this software and its + documentation for any purpose and without fee is hereby granted, + provided that the above copyright notice, this permission notice and + the following disclaimer notice appear unmodified in all copies. + + I DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL + IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL I + BE LIABLE FOR ANY SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY + DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA, OR PROFITS, WHETHER + IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT + OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. + +Files: PC/_subprocess.c +Copyright: Copyright (c) 2004 by Fredrik Lundh + Copyright (c) 2004 by Secret Labs AB, http://www.pythonware.com + Copyright (c) 2004 by Peter Astrand +License: + * Permission to use, copy, modify, and distribute this software and + * its associated documentation for any purpose and without fee is + * hereby granted, provided that the above copyright notice appears in + * all copies, and that both that copyright notice and this permission + * notice appear in supporting documentation, and that the name of the + * authors not be used in advertising or publicity pertaining to + * distribution of the software without specific, written prior + * permission. + * + * THE AUTHORS DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, + * INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. + * IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY SPECIAL, INDIRECT OR + * CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS + * OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, + * NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION + * WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. + +Files: PC/winsound.c +Copyright: Copyright (c) 1999 Toby Dickenson +License: * Permission to use this software in any way is granted without + * fee, provided that the copyright notice above appears in all + * copies. This software is provided "as is" without any warranty. + */ + +/* Modified by Guido van Rossum */ +/* Beep added by Mark Hammond */ +/* Win9X Beep and platform identification added by Uncle Timmy */ + +Files: Tools/pybench/* +Copyright: (c), 1997-2006, Marc-Andre Lemburg (mal@lemburg.com) + (c), 2000-2006, eGenix.com Software GmbH (info@egenix.com) +License: Permission to use, copy, modify, and distribute this software and its + documentation for any purpose and without fee or royalty is hereby + granted, provided that the above copyright notice appear in all copies + and that both that copyright notice and this permission notice appear + in supporting documentation or portions thereof, including + modifications, that you make. + + THE AUTHOR MARC-ANDRE LEMBURG DISCLAIMS ALL WARRANTIES WITH REGARD TO + THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND + FITNESS, IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, + INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING + FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, + NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION + WITH THE USE OR PERFORMANCE OF THIS SOFTWARE ! --- python3.3-3.3.0.orig/debian/python3-config.1 +++ python3.3-3.3.0/debian/python3-config.1 @@ -0,0 +1,102 @@ +.TH PYTHON\-CONFIG 1 "November 27, 2011" +.SH NAME +python\-config \- output build options for python C/C++ extensions or embedding +.SH SYNOPSIS +.BI "python\-config" +[ +.BI "\-\-prefix" +] +[ +.BI "\-\-exec\-prefix" +] +[ +.BI "\-\-includes" +] +[ +.BI "\-\-libs" +] +[ +.BI "\-\-cflags" +] +[ +.BI "\-\-ldflags" +] +[ +.BI "\-\-extension\-suffix" +] +[ +.BI "\-\-abiflags" +] +[ +.BI "\-\-help" +] +.SH DESCRIPTION +.B python\-config +helps compiling and linking programs, which embed the Python interpreter, or +extension modules that can be loaded dynamically (at run time) into +the interpreter. +.SH OPTIONS +.TP +.BI "\-\-abiflags" +print the the ABI flags as specified by PEP 3149. +.TP +.BI "\-\-cflags" +print the C compiler flags. +.TP +.BI "\-\-ldflags" +print the flags that should be passed to the linker. +.TP +.BI "\-\-includes" +similar to \fI\-\-cflags\fP but only with \-I options (path to python header files). +.TP +.BI "\-\-libs" +similar to \fI\-\-ldflags\fP but only with \-l options (used libraries). +.TP +.BI "\-\-prefix" +prints the prefix (base directory) under which python can be found. +.TP +.BI "\-\-exec\-prefix" +print the prefix used for executable program directories (such as bin, sbin, etc). +.TP +.BI "\-\-extension\-suffix" +print the extension suffix used for binary extensions. +.TP +.BI "\-\-help" +print the usage message. +.PP + +.SH EXAMPLES +To build the singe\-file c program \fIprog\fP against the python library, use +.PP +.RS +gcc $(python\-config \-\-cflags \-\-ldflags) progr.cpp \-o progr.cpp +.RE +.PP +The same in a makefile: +.PP +.RS +CFLAGS+=$(shell python\-config \-\-cflags) +.RE +.RS +LDFLAGS+=$(shell python\-config \-\-ldflags) +.RE +.RS +all: progr +.RE + +To build a dynamically loadable python module, use +.PP +.RS +gcc $(python\-config \-\-cflags \-\-ldflags) \-shared \-fPIC progr.cpp \-o progr.so +.RE + +.SH "SEE ALSO" +python (1) +.br +http://docs.python.org/extending/extending.html +.br +/usr/share/doc/python/faq/extending.html + +.SH AUTHORS +This manual page was written by Johann Felix Soden +for the Debian project (and may be used by others). --- python3.3-3.3.0.orig/debian/libPVER.symbols.in +++ python3.3-3.3.0/debian/libPVER.symbols.in @@ -0,0 +1,5 @@ +libpython@VER@m.so.1.0 libpython@VER@ #MINVER# +#include "libpython.symbols" + PyModule_Create2@Base @SVER@ + + (optional)__gnu_lto_v1@Base @SVER@ --- python3.3-3.3.0.orig/debian/PVER-doc.doc-base.PVER-lib.in +++ python3.3-3.3.0/debian/PVER-doc.doc-base.PVER-lib.in @@ -0,0 +1,15 @@ +Document: @PVER@-lib +Title: Python Library Reference (v@VER@) +Author: Guido van Rossum +Abstract: This library reference manual documents Python's standard library, + as well as many optional library modules (which may or may not be + available, depending on whether the underlying platform supports + them and on the configuration choices made at compile time). It + also documents the standard types of the language and its built-in + functions and exceptions, many of which are not or incompletely + documented in the Reference Manual. +Section: Programming/Python + +Format: HTML +Index: /usr/share/doc/@PVER@/html/library/index.html +Files: /usr/share/doc/@PVER@/html/library/*.html --- python3.3-3.3.0.orig/debian/idle-PVER.menu.in +++ python3.3-3.3.0/debian/idle-PVER.menu.in @@ -0,0 +1,5 @@ +?package(idle-@PVER@):needs="X11" section="Applications/Programming"\ + title="IDLE (Python v@VER@)"\ + icon="/usr/share/pixmaps/@PVER@.xpm"\ + command="/usr/bin/idle-@PVER@" \ + hints="Environments" --- python3.3-3.3.0.orig/debian/PVER-doc.overrides.in +++ python3.3-3.3.0/debian/PVER-doc.overrides.in @@ -0,0 +1,2 @@ +# this is referenced by the html docs +@PVER@-doc binary: extra-license-file --- python3.3-3.3.0.orig/debian/source.lintian-overrides +++ python3.3-3.3.0/debian/source.lintian-overrides @@ -0,0 +1,2 @@ +# generated during the build +python3.3 source: quilt-build-dep-but-no-series-file --- python3.3-3.3.0.orig/debian/PVER-minimal.prerm.in +++ python3.3-3.3.0/debian/PVER-minimal.prerm.in @@ -0,0 +1,53 @@ +#! /bin/sh -e + +syssite=/usr/lib/@PVER@/site-packages +localsite=/usr/local/lib/@PVER@/dist-packages + +remove_bytecode() +{ + pkg=$1 + max=$(LANG=C LC_ALL=C xargs --show-limits < /dev/null 2>&1 | awk '/Maximum/ {print int($NF / 4)}') + dpkg -L $pkg \ + | awk -F/ 'BEGIN {OFS="/"} /\.py$/ {$NF=sprintf("__pycache__/%s.*.py[co]", substr($NF,1,length($NF)-3)); print}' \ + | xargs --max-chars="$max" echo \ + | while read files; do rm -f $files; done + find /usr/lib/python3 /usr/lib/@PVER@ -name dist-packages -prune -o -name __pycache__ -empty -print \ + | xargs -r rm -rf +} + +case "$1" in + remove) + if [ "$DEBIAN_FRONTEND" != noninteractive ]; then + echo "Unlinking and removing bytecode for runtime @PVER@" + fi + for hook in /usr/share/python3/runtime.d/*.rtremove; do + [ -x $hook ] || continue + $hook rtremove @PVER@ || continue + done + + remove_bytecode @PVER@-minimal + + if which update-binfmts >/dev/null; then + update-binfmts --package @PVER@ --remove @PVER@ /usr/bin/@PVER@ + fi + + if [ -h $syssite ]; then + rm -f $syssite + fi + [ -d $localsite ] && rmdir $localsite 2>/dev/null || true + [ -d $(dirname $localsite) ] && rmdir $(dirname $localsite) 2>/dev/null || true + ;; + upgrade) + remove_bytecode @PVER@-minimal + ;; + deconfigure) + ;; + failed-upgrade) + ;; + *) + echo "prerm called with unknown argument \`$1'" >&2 + exit 1 + ;; +esac + +#DEBHELPER# --- python3.3-3.3.0.orig/debian/PVER-minimal.postinst.in +++ python3.3-3.3.0/debian/PVER-minimal.postinst.in @@ -0,0 +1,91 @@ +#! /bin/sh + +set -e + +if [ ! -f /etc/@PVER@/sitecustomize.py ]; then + cat <<-EOF + # Empty sitecustomize.py to avoid a dangling symlink +EOF +fi + +if [ "$1" = configure ]; then + if [ -d /usr/lib/@PVER@/config ] && [ ! -h /usr/lib/@PVER@/config ]; then + if rmdir /usr/lib/@PVER@/config 2> /dev/null; then + ln -sf config-@VER@mu /usr/lib/@PVER@/config + else + echo >&2 "WARNING: non-empty directory on upgrade: /usr/lib/@PVER@/config" + ls -l /usr/lib/@PVER@/config + fi + fi +fi + +syssite=/usr/lib/@PVER@/site-packages +localsite=/usr/local/lib/@PVER@/dist-packages +syslink=../../${localsite#/usr/*} + +case "$1" in + configure) + # Create empty directories in /usr/local + if [ ! -e /usr/local/lib/@PVER@ ]; then + mkdir -p /usr/local/lib/@PVER@ 2> /dev/null || true + chmod 2775 /usr/local/lib/@PVER@ 2> /dev/null || true + chown root:staff /usr/local/lib/@PVER@ 2> /dev/null || true + fi + if [ ! -e $localsite ]; then + mkdir -p $localsite 2> /dev/null || true + chmod 2775 $localsite 2> /dev/null || true + chown root:staff $localsite 2> /dev/null || true + fi + #if [ ! -h $syssite ]; then + # ln -s $syslink $syssite + #fi + + if which update-binfmts >/dev/null; then + update-binfmts --import @PVER@ + fi + + ;; +esac + +if [ "$1" = configure ]; then + + # only available before removal of the packaging package + rm -f /etc/@PVER@/sysconfig.cfg + + ( + files=$(dpkg -L @PVER@-minimal | sed -n '/^\/usr\/lib\/@PVER@\/.*\.py$/p') + @PVER@ /usr/lib/@PVER@/py_compile.py $files + if grep -sq '^byte-compile[^#]*optimize' /etc/python/debian_config; then + @PVER@ -O /usr/lib/@PVER@/py_compile.py $files + fi + ) + bc=no + #if [ -z "$2" ] || dpkg --compare-versions "$2" lt 2.5-3 \ + # || [ -f /var/lib/python/@PVER@_installed ]; then + # bc=yes + #fi + if ! grep -sq '^supported-versions[^#]*@PVER@' /usr/share/python/debian_defaults + then + # FIXME: byte compile anyway? + bc=no + fi + if [ "$bc" = yes ]; then + # new installation or installation of first version with hook support + if [ "$DEBIAN_FRONTEND" != noninteractive ]; then + echo "Linking and byte-compiling packages for runtime @PVER@..." + fi + version=$(dpkg -s @PVER@-minimal | awk '/^Version:/ {print $2}') + for hook in /usr/share/python3/runtime.d/*.rtinstall; do + [ -x $hook ] || continue + $hook rtinstall @PVER@ "$2" "$version" + done + if [ -f /var/lib/python/@PVER@_installed ]; then + rm -f /var/lib/python/@PVER@_installed + rmdir --ignore-fail-on-non-empty /var/lib/python 2>/dev/null + fi + fi +fi + +#DEBHELPER# + +exit 0 --- python3.3-3.3.0.orig/debian/PVER.desktop.in +++ python3.3-3.3.0/debian/PVER.desktop.in @@ -0,0 +1,10 @@ +[Desktop Entry] +Name=Python (v@VER@) +Comment=Python Interpreter (v@VER@) +Exec=/usr/bin/@PVER@ +Icon=/usr/share/pixmaps/@PVER@.xpm +Terminal=true +Type=Application +Categories=Development; +StartupNotify=true +NoDisplay=true --- python3.3-3.3.0.orig/debian/control.udeb +++ python3.3-3.3.0/debian/control.udeb @@ -0,0 +1,11 @@ + +Package: @PVER@-udeb +XC-Package-Type: udeb +Section: debian-installer +Architecture: any +Depends: ${shlibs:Depends}, ${misc:Depends} +XB-Python-Runtime: @PVER@ +XB-Python-Version: @VER@ +Description: A minimal subset of the Python language (version @VER@) + This package contains the interpreter and some essential modules, packaged + for use in the installer. --- python3.3-3.3.0.orig/debian/pyhtml2devhelp.py +++ python3.3-3.3.0/debian/pyhtml2devhelp.py @@ -0,0 +1,222 @@ +#! /usr/bin/python + +import formatter, htmllib +import os, sys, re + +class PyHTMLParser(htmllib.HTMLParser): + pages_to_include = set(('whatsnew/index.html', 'tutorial/index.html', 'using/index.html', + 'reference/index.html', 'library/index.html', 'howto/index.html', + 'extending/index.html', 'c-api/index.html', 'install/index.html', + 'distutils/index.html')) + + def __init__(self, formatter, basedir, fn, indent, parents=set()): + htmllib.HTMLParser.__init__(self, formatter) + self.basedir = basedir + self.dir, self.fn = os.path.split(fn) + self.data = '' + self.parents = parents + self.link = {} + self.indent = indent + self.last_indent = indent - 1 + self.sub_indent = 0 + self.sub_count = 0 + self.next_link = False + + def process_link(self): + new_href = os.path.join(self.dir, self.link['href']) + text = self.link['text'] + indent = self.indent + self.sub_indent + if self.last_indent == indent: + print '%s' % (' ' * self.last_indent) + self.sub_count -= 1 + print '%s' % (' ' * indent, new_href, text) + self.sub_count += 1 + self.last_indent = self.indent + self.sub_indent + + def start_li(self, attrs): + self.sub_indent += 1 + self.next_link = True + + def end_li(self): + indent = self.indent + self.sub_indent + if self.sub_count > 0: + print '%s' % (' ' * self.last_indent) + self.sub_count -= 1 + self.last_indent -= 1 + self.sub_indent -= 1 + + def start_a(self, attrs): + self.link = {} + for attr in attrs: + self.link[attr[0]] = attr[1] + self.data = '' + + def end_a(self): + process = False + text = self.data.replace('\t', '').replace('\n', ' ').replace('&', '&').replace('<', '<').replace('>', '>') + self.link['text'] = text + # handle a tag without href attribute + try: + href = self.link['href'] + except KeyError: + return + + abs_href = os.path.join(self.basedir, href) + if abs_href in self.parents: + return + if href.startswith('..') or href.startswith('http:') \ + or href.startswith('mailto:') or href.startswith('news:'): + return + if href in ('', 'about.html', 'modindex.html', 'genindex.html', 'glossary.html', + 'search.html', 'contents.html', 'download.html', 'bugs.html', + 'license.html', 'copyright.html'): + return + + if self.link.has_key('class'): + if self.link['class'] in ('biglink'): + process = True + if self.link['class'] in ('reference external'): + if self.next_link: + process = True + next_link = False + + if process == True: + self.process_link() + if href in self.pages_to_include: + self.parse_file(os.path.join(self.dir, href)) + + def finish(self): + if self.sub_count > 0: + print '%s' % (' ' * self.last_indent) + + def handle_data(self, data): + self.data += data + + def parse_file(self, href): + # TODO basedir bestimmen + parent = os.path.join(self.basedir, self.fn) + self.parents.add(parent) + parser = PyHTMLParser(formatter.NullFormatter(), + self.basedir, href, self.indent + 1, + self.parents) + text = file(self.basedir + '/' + href).read() + parser.feed(text) + parser.finish() + parser.close() + if parent in self.parents: + self.parents.remove(parent) + +class PyIdxHTMLParser(htmllib.HTMLParser): + def __init__(self, formatter, basedir, fn, indent): + htmllib.HTMLParser.__init__(self, formatter) + self.basedir = basedir + self.dir, self.fn = os.path.split(fn) + self.data = '' + self.link = {} + self.indent = indent + self.active = False + self.indented = False + self.nolink = False + self.header = '' + self.last_letter = 'Z' + self.last_text = '' + + def process_link(self): + new_href = os.path.join(self.dir, self.link['href']) + text = self.link['text'] + if not self.active: + return + if text.startswith('['): + return + if self.link.get('rel', None) in ('prev', 'parent', 'next', 'contents', 'index'): + return + if self.indented: + text = self.last_text + ' ' + text + else: + # Save it in case we need it again + self.last_text = re.sub(' \([\w\-\.\s]+\)', '', text) + indent = self.indent + print '%s' % (' ' * indent, new_href, text) + + def start_dl(self, attrs): + if self.last_text: + # Looks like we found the second part to a command + self.indented = True + + def end_dl(self): + self.indented = False + + def start_dt(self, attrs): + self.data = '' + self.nolink = True + + def end_dt(self): + if not self.active: + return + if self.nolink == True: + # Looks like we found the first part to a command + self.last_text = re.sub(' \([\w\-\.\s]+\)', '', self.data) + self.nolink = False + + def start_h2(self, attrs): + for k, v in attrs: + if k == 'id': + self.header = v + if v == '_': + self.active = True + + def start_td(self, attrs): + self.indented = False + self.last_text = '' + + def start_table(self, attrs): + pass + + def end_table(self): + if self.header == self.last_letter: + self.active = False + + def start_a(self, attrs): + self.nolink = False + self.link = {} + for attr in attrs: + self.link[attr[0]] = attr[1] + self.data = '' + + def end_a(self): + text = self.data.replace('\t', '').replace('\n', ' ').replace('&', '&').replace('<', '<').replace('>', '>') + self.link['text'] = text + # handle a tag without href attribute + try: + href = self.link['href'] + except KeyError: + return + self.process_link() + + def handle_data(self, data): + self.data += data + +def main(): + base = sys.argv[1] + fn = sys.argv[2] + version = sys.argv[3] + + parser = PyHTMLParser(formatter.NullFormatter(), base, fn, indent=0) + print '' + print '' % (version, version, version) + print '' + parser.parse_file(fn) + print '' + + print '' + + fn = 'genindex-all.html' + parser = PyIdxHTMLParser(formatter.NullFormatter(), base, fn, indent=1) + text = file(base + '/' + fn).read() + parser.feed(text) + parser.close() + + print '' + print '' + +main() --- python3.3-3.3.0.orig/debian/2to3-3.1 +++ python3.3-3.3.0/debian/2to3-3.1 @@ -0,0 +1,41 @@ +.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.40.4. +.TH 2TO3-3.3 "1" "January 2012" "2to3-3.3 3.3" "User Commands" +.SH NAME +2to3-3.3 \- Python2 to Python3 converter +.SH SYNOPSIS +.B 2to3 +[\fIoptions\fR] \fIfile|dir \fR... +.SH OPTIONS +.TP +\fB\-h\fR, \fB\-\-help\fR +show this help message and exit +.TP +\fB\-d\fR, \fB\-\-doctests_only\fR +Fix up doctests only +.TP +\fB\-f\fR FIX, \fB\-\-fix\fR=\fIFIX\fR +Each FIX specifies a transformation; default: all +.TP +\fB\-j\fR PROCESSES, \fB\-\-processes\fR=\fIPROCESSES\fR +Run 2to3 concurrently +.TP +\fB\-x\fR NOFIX, \fB\-\-nofix\fR=\fINOFIX\fR +Prevent a transformation from being run +.TP +\fB\-l\fR, \fB\-\-list\-fixes\fR +List available transformations +.TP +\fB\-p\fR, \fB\-\-print\-function\fR +Modify the grammar so that print() is a function +.TP +\fB\-v\fR, \fB\-\-verbose\fR +More verbose logging +.TP +\fB\-\-no\-diffs\fR +Don't show diffs of the refactoring +.TP +\fB\-w\fR, \fB\-\-write\fR +Write back modified files +.TP +\fB\-n\fR, \fB\-\-nobackups\fR +Don't write backups for modified files --- python3.3-3.3.0.orig/debian/README.PVER.in +++ python3.3-3.3.0/debian/README.PVER.in @@ -0,0 +1,95 @@ + + Python @VER@ for Debian + --------------------- + +This is Python @VER@ packaged for Debian. + +This document contains information specific to the Debian packages of +Python @VER@. + + + + [TODO: This document is not yet up-to-date with the packages.] + +Currently, it features those two main topics: + + 1. Release notes for the Debian packages: + 2. Notes for developers using the Debian Python packages: + +Release notes and documentation from the upstream package are installed +in /usr/share/doc/@PVER@/. + +There's a mailing list for discussion of issues related to Python on Debian +systems: debian-python@lists.debian.org. The list is not intended for +general Python problems, but as a forum for maintainers of Python-related +packages and interested third parties. + + + +1. Release notes for the Debian packages: + + +Results of the regression test: +------------------------------ + +The package does successfully run the regression tests for all included +modules. Seven packages are skipped since they are platform-dependent and +can't be used with Linux. + + +2. Notes for developers using the Debian python packages: + +See the draft of the Debian Python policy in /usr/share/doc/python. + +distutils can be found in the @PVER@-dev package. Development files +like the python library or Makefiles can be found in the @PVER@-dev +package in /usr/lib/@PVER@/config. Therefore, if you need to install +a pure python extension, you only need @PVER@. On the other hand, to +install a C extension, you need @PVER@-dev. + +a) Locally installed Python add-ons + + /usr/local/lib/@PVER@/site-packages/ + /usr/local/lib/site-python/ (version-independent modules) + +b) Python add-ons packaged for Debian + + /usr/lib/@PVER@/site-packages/ + /usr/lib/site-python/ (version-independent modules) + +Note that no package must install files directly into /usr/lib/@PVER@/ +or /usr/local/lib/@PVER@/. Only the site-packages directory is allowed +for third-party extensions. + +Use of the new `package' scheme is strongly encouraged. The `ni' interface +is obsolete in python 1.5. + +Header files for extensions go into /usr/include/@PVER@/. + + +Installing extensions for local use only: +---------------------------------------- + +Consider using distutils ... + +Most extensions use Python's Makefile.pre.in. Note that Makefile.pre.in +by default will install files into /usr/lib/, not into /usr/local/lib/, +which is not allowed for local extensions. You'll have to change the +Makefile accordingly. Most times, "make prefix=/usr/local install" will +work. + + +Packaging python extensions for Debian: +-------------------------------------- + +Maintainers of Python extension packages should read + + /usr/share/doc/python/python-policy.txt.gz + + + + + 03/09/98 + Gregor Hoffleit + +Last change: 2001-12-14 --- python3.3-3.3.0.orig/debian/libPVER-dbg.symbols.in +++ python3.3-3.3.0/debian/libPVER-dbg.symbols.in @@ -0,0 +1,38 @@ +libpython@VER@dm.so.1.0 libpython@VER@-dbg #MINVER# +#include "libpython.symbols" + _PyDict_Dummy@Base @SVER@ + _PyMem_DebugFree@Base @SVER@ + _PyMem_DebugMalloc@Base @SVER@ + _PyMem_DebugRealloc@Base @SVER@ + _PyObject_DebugCheckAddress@Base @SVER@ + _PyObject_DebugCheckAddressApi@Base @SVER@ + _PyObject_DebugDumpAddress@Base @SVER@ + _PyObject_DebugFree@Base @SVER@ + _PyObject_DebugFreeApi@Base @SVER@ + _PyObject_DebugMalloc@Base @SVER@ + _PyObject_DebugMallocApi@Base @SVER@ + _PyObject_DebugMallocStats@Base @SVER@ + _PyObject_DebugRealloc@Base @SVER@ + _PyObject_DebugReallocApi@Base @SVER@ + _PySet_Dummy@Base @SVER@ + _PyUnicode_CheckConsistency@Base @SVER@ + _PyUnicode_Dump@Base @SVER@ + _PyUnicode_compact_data@Base @SVER@ + _PyUnicode_data@Base @SVER@ + _PyUnicode_utf8@Base @SVER@ + _Py_AddToAllObjects@Base @SVER@ + _Py_Dealloc@Base @SVER@ + _Py_ForgetReference@Base @SVER@ + _Py_GetObjects@Base @SVER@ + _Py_GetRefTotal@Base @SVER@ + _Py_HashSecret_Initialized@Base @SVER@ + _Py_NegativeRefcount@Base @SVER@ + _Py_NewReference@Base @SVER@ + _Py_PrintReferenceAddresses@Base @SVER@ + _Py_PrintReferences@Base @SVER@ + _Py_RefTotal@Base @SVER@ + _Py_dumptree@Base @SVER@ + _Py_printtree@Base @SVER@ + _Py_showtree@Base @SVER@ + _Py_tok_dump@Base @SVER@ + PyModule_Create2TraceRefs@Base @SVER@ --- python3.3-3.3.0.orig/debian/PVER-doc.doc-base.PVER-ref.in +++ python3.3-3.3.0/debian/PVER-doc.doc-base.PVER-ref.in @@ -0,0 +1,18 @@ +Document: @PVER@-ref +Title: Python Reference Manual (v@VER@) +Author: Guido van Rossum +Abstract: This reference manual describes the syntax and "core semantics" of + the language. It is terse, but attempts to be exact and complete. + The semantics of non-essential built-in object types and of the + built-in functions and modules are described in the *Python + Library Reference*. For an informal introduction to the language, + see the *Python Tutorial*. For C or C++ programmers, two + additional manuals exist: *Extending and Embedding the Python + Interpreter* describes the high-level picture of how to write a + Python extension module, and the *Python/C API Reference Manual* + describes the interfaces available to C/C++ programmers in detail. +Section: Programming/Python + +Format: HTML +Index: /usr/share/doc/@PVER@/html/reference/index.html +Files: /usr/share/doc/@PVER@/html/reference/*.html --- python3.3-3.3.0.orig/debian/README.maintainers.in +++ python3.3-3.3.0/debian/README.maintainers.in @@ -0,0 +1,88 @@ + +Hints for maintainers of Debian packages of Python extensions +------------------------------------------------------------- + +Most of the content of this README can be found in the Debian Python policy. +See /usr/share/doc/python/python-policy.txt.gz. + +Documentation Tools +------------------- + +If your package ships documentation produced in the Python +documentation format, you can generate it at build-time by +build-depending on @PVER@-dev, and you will find the +templates, tools and scripts in /usr/lib/@PVER@/doc/tools -- +adjust your build scripts accordingly. + + +Makefile.pre.in issues +---------------------- + +Python comes with a `universal Unix Makefile for Python extensions' in +/usr/lib/@PVER@/config/Makefile.pre.in (with Debian, this is included +in the python-dev package), which is used by most Python extensions. + +In general, packages using the Makefile.pre.in approach can be packaged +simply by running dh_make or by using one of debhelper's rules' templates +(see /usr/doc/debhelper/examples/). Makefile.pre.in works fine with e.g. +"make prefix=debian/tmp/usr install". + +One glitch: You may be running into the problem that Makefile.pre.in +doesn't try to create all the directories when they don't exist. Therefore, +you may have to create them manually before "make install". In most cases, +the following should work: + + ... + dh_installdirs /usr/lib/@PVER@ + $(MAKE) prefix=debian/tmp/usr install + ... + + +Byte-compilation +---------------- + +For speed reasons, Python internally compiles source files into a byte-code. +To speed up subsequent imports, it tries to save the byte-code along with +the source with an extension .pyc (resp. pyo). This will fail if the +libraries are installed in a non-writable directory, which may be the +case for /usr/lib/@PVER@/. + +Not that .pyc and .pyo files should not be relocated, since for debugging +purposes the path of the source for is hard-coded into them. + +To precompile files in batches after installation, Python has a script +compileall.py, which compiles all files in a given directory tree. The +Debian version of compileall has been enhanced to support incremental +compilation and to feature a ddir (destination dir) option. ddir is +used to compile files in debian/usr/lib/python/ when they will be +installed into /usr/lib/python/. + + +Currently, there are two ways to use compileall for Debian packages. The +first has a speed penalty, the second has a space penalty in the package. + +1.) Compiling and removing .pyc files in postinst/prerm: + + Use dh_python(1) from the debhelper packages to add commands to byte- + compile on installation and to remove the byte-compiled files on removal. + Your package has to build-depend on: debhelper (>= 4.1.67), python. + + In /usr/share/doc/@PVER@, you'll find sample.postinst and sample.prerm. + If you set the directory where the .py files are installed, these + scripts will install and remove the .pyc and .pyo files for your + package after unpacking resp. before removing the package. + +2.) Compiling the .pyc files `out of place' during installation: + + As of 1.5.1, compileall.py allows you to specify a faked installation + directory using the "-d destdir" option, so that you can precompile + the files in their temporary directory + (e.g. debian/tmp/usr/lib/python2.1/site-packages/PACKAGE). + + + + 11/02/98 + Gregor Hoffleit + + +Last modified: 2007-10-14 --- python3.3-3.3.0.orig/debian/pygettext.1 +++ python3.3-3.3.0/debian/pygettext.1 @@ -0,0 +1,108 @@ +.TH PYGETTEXT 1 "" "pygettext 1.4" +.SH NAME +pygettext \- Python equivalent of xgettext(1) +.SH SYNOPSIS +.B pygettext +[\fIOPTIONS\fR] \fIINPUTFILE \fR... +.SH DESCRIPTION +pygettext is deprecated. The current version of xgettext supports +many languages, including Python. + +pygettext uses Python's standard tokenize module to scan Python +source code, generating .pot files identical to what GNU xgettext generates +for C and C++ code. From there, the standard GNU tools can be used. +.PP +pygettext searches only for _() by default, even though GNU xgettext +recognizes the following keywords: gettext, dgettext, dcgettext, +and gettext_noop. See the \fB\-k\fR/\fB\--keyword\fR flag below for how to +augment this. +.PP +.SH OPTIONS +.TP +\fB\-a\fR, \fB\-\-extract\-all\fR +Extract all strings. +.TP +\fB\-d\fR, \fB\-\-default\-domain\fR=\fINAME\fR +Rename the default output file from messages.pot to name.pot. +.TP +\fB\-E\fR, \fB\-\-escape\fR +Replace non-ASCII characters with octal escape sequences. +.TP +\fB\-D\fR, \fB\-\-docstrings\fR +Extract module, class, method, and function docstrings. +These do not need to be wrapped in _() markers, and in fact cannot +be for Python to consider them docstrings. (See also the \fB\-X\fR option). +.TP +\fB\-h\fR, \fB\-\-help\fR +Print this help message and exit. +.TP +\fB\-k\fR, \fB\-\-keyword\fR=\fIWORD\fR +Keywords to look for in addition to the default set, which are: _ +.IP +You can have multiple \fB\-k\fR flags on the command line. +.TP +\fB\-K\fR, \fB\-\-no\-default\-keywords\fR +Disable the default set of keywords (see above). +Any keywords explicitly added with the \fB\-k\fR/\fB\--keyword\fR option +are still recognized. +.TP +\fB\-\-no\-location\fR +Do not write filename/lineno location comments. +.TP +\fB\-n\fR, \fB\-\-add\-location\fR +Write filename/lineno location comments indicating where each +extracted string is found in the source. These lines appear before +each msgid. The style of comments is controlled by the +\fB\-S\fR/\fB\--style\fR option. This is the default. +.TP +\fB\-o\fR, \fB\-\-output\fR=\fIFILENAME\fR +Rename the default output file from messages.pot to FILENAME. +If FILENAME is `-' then the output is sent to standard out. +.TP +\fB\-p\fR, \fB\-\-output\-dir\fR=\fIDIR\fR +Output files will be placed in directory DIR. +.TP +\fB\-S\fR, \fB\-\-style\fR=\fISTYLENAME\fR +Specify which style to use for location comments. +Two styles are supported: +.RS +.IP \(bu 4 +Solaris # File: filename, line: line-number +.IP \(bu 4 +GNU #: filename:line +.RE +.IP +The style name is case insensitive. +GNU style is the default. +.TP +\fB\-v\fR, \fB\-\-verbose\fR +Print the names of the files being processed. +.TP +\fB\-V\fR, \fB\-\-version\fR +Print the version of pygettext and exit. +.TP +\fB\-w\fR, \fB\-\-width\fR=\fICOLUMNS\fR +Set width of output to columns. +.TP +\fB\-x\fR, \fB\-\-exclude\-file\fR=\fIFILENAME\fR +Specify a file that contains a list of strings that are not be +extracted from the input files. Each string to be excluded must +appear on a line by itself in the file. +.TP +\fB\-X\fR, \fB\-\-no\-docstrings\fR=\fIFILENAME\fR +Specify a file that contains a list of files (one per line) that +should not have their docstrings extracted. This is only useful in +conjunction with the \fB\-D\fR option above. +.PP +If `INPUTFILE' is -, standard input is read. +.SH BUGS +pygettext attempts to be option and feature compatible with GNU xgettext +where ever possible. However some options are still missing or are not fully +implemented. Also, xgettext's use of command line switches with option +arguments is broken, and in these cases, pygettext just defines additional +switches. +.SH AUTHOR +pygettext is written by Barry Warsaw . +.PP +Joonas Paalasmaa put this manual page together +based on "pygettext --help". --- python3.3-3.3.0.orig/debian/libPVER-dbg.symbols.i386.in +++ python3.3-3.3.0/debian/libPVER-dbg.symbols.i386.in @@ -0,0 +1,40 @@ +libpython@VER@dm.so.1.0 libpython@VER@-dbg #MINVER# +#include "libpython.symbols" + _Py_force_double@Base @SVER@ + _Py_get_387controlword@Base @SVER@ + _Py_set_387controlword@Base @SVER@ + _PyDict_Dummy@Base @SVER@ + _PyMem_DebugFree@Base @SVER@ + _PyMem_DebugMalloc@Base @SVER@ + _PyMem_DebugRealloc@Base @SVER@ + _PyObject_DebugCheckAddress@Base @SVER@ + _PyObject_DebugCheckAddressApi@Base @SVER@ + _PyObject_DebugDumpAddress@Base @SVER@ + _PyObject_DebugFree@Base @SVER@ + _PyObject_DebugFreeApi@Base @SVER@ + _PyObject_DebugMalloc@Base @SVER@ + _PyObject_DebugMallocApi@Base @SVER@ + _PyObject_DebugMallocStats@Base @SVER@ + _PyObject_DebugRealloc@Base @SVER@ + _PyObject_DebugReallocApi@Base @SVER@ + _PySet_Dummy@Base @SVER@ + _PyUnicode_CheckConsistency@Base @SVER@ + _PyUnicode_Dump@Base @SVER@ + _PyUnicode_compact_data@Base @SVER@ + _PyUnicode_data@Base @SVER@ + _PyUnicode_utf8@Base @SVER@ + _Py_AddToAllObjects@Base @SVER@ + _Py_Dealloc@Base @SVER@ + _Py_ForgetReference@Base @SVER@ + _Py_GetObjects@Base @SVER@ + _Py_GetRefTotal@Base @SVER@ + _Py_NegativeRefcount@Base @SVER@ + _Py_NewReference@Base @SVER@ + _Py_PrintReferenceAddresses@Base @SVER@ + _Py_PrintReferences@Base @SVER@ + _Py_RefTotal@Base @SVER@ + _Py_dumptree@Base @SVER@ + _Py_printtree@Base @SVER@ + _Py_showtree@Base @SVER@ + _Py_tok_dump@Base @SVER@ + PyModule_Create2TraceRefs@Base @SVER@ --- python3.3-3.3.0.orig/debian/script.py +++ python3.3-3.3.0/debian/script.py @@ -0,0 +1,51 @@ +#! /usr/bin/python + +# Copyright (C) 2012 Colin Watson . +# +# Permission is hereby granted, free of charge, to any person obtaining +# a copy of this software and associated documentation files (the +# "Software"), to deal in the Software without restriction, including +# without limitation the rights to use, copy, modify, merge, publish, +# distribute, sublicense, and/or sell copies of the Software, and to +# permit persons to whom the Software is furnished to do so, subject +# to the following conditions: +# +# The above copyright notice and this permission notice shall be included +# in all copies or substantial portions of the Software. +# +# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, +# EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF +# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. +# IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY +# CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, +# TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE +# SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. + +"""Trivial script(1) workalike, but without reading from standard input.""" + +import os +import pty +import select +import sys + +filename = sys.argv[1] +command = sys.argv[2] + +pid, master = pty.fork() +if pid == 0: # child + os.execlp("sh", "sh", "-c", command) + +# parent +with open(filename, "wb") as logfile: + try: + while True: + rfds, _, _ = select.select([master], [], []) + if master in rfds: + data = os.read(master, 65536) + os.write(1, data) + logfile.write(data) + logfile.flush() + except (IOError, OSError): + pass + +os.close(master) --- python3.3-3.3.0.orig/debian/PVER.overrides.in +++ python3.3-3.3.0/debian/PVER.overrides.in @@ -0,0 +1,8 @@ +# yes, we have to +@PVER@ binary: depends-on-python-minimal + +@PVER@ binary: desktop-command-not-in-package +@PVER@ binary: menu-command-not-in-package + +# no, not useless +@PVER@ binary: manpage-has-useless-whatis-entry --- python3.3-3.3.0.orig/debian/sitecustomize.py.in +++ python3.3-3.3.0/debian/sitecustomize.py.in @@ -0,0 +1,7 @@ +# install the apport exception handler if available +try: + import apport_python_hook +except ImportError: + pass +else: + apport_python_hook.install() --- python3.3-3.3.0.orig/debian/pysetup3.1 +++ python3.3-3.3.0/debian/pysetup3.1 @@ -0,0 +1,42 @@ +.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.40.4. +.TH PYSETUP3.3 "1" "January 2012" "pysetup3.3 3.3" "User Commands" +.SH NAME +pysetup3.3 \- pysetup tool +.SH SYNOPSIS +.B pysetup +[\fIoptions\fR] \fIaction \fR[\fIaction_options\fR] +.SH DESCRIPTION +.SS "Actions:" +.IP +run: Run one or several commands +metadata: Display the metadata of a project +install: Install a project +remove: Remove a project +search: Search for a project in the indexes +list: List installed projects +graph: Display a graph +create: Create a project +generate\-setup: Generate a backward\-compatible setup.py +.PP +To get more help on an action, use: +.IP +pysetup action \fB\-\-help\fR +.SS "Global options:" +.TP +\fB\-\-verbose\fR (\fB\-v\fR) +run verbosely (default) +.TP +\fB\-\-quiet\fR (\fB\-q\fR) +run quietly (turns verbosity off) +.TP +\fB\-\-dry\-run\fR (\fB\-n\fR) +don't actually do anything +.TP +\fB\-\-help\fR (\fB\-h\fR) +show detailed help message +.TP +\fB\-\-no\-user\-cfg\fR +ignore pydistutils.cfg in your home directory +.TP +\fB\-\-version\fR +Display the version --- python3.3-3.3.0.orig/debian/README.idle-PVER.in +++ python3.3-3.3.0/debian/README.idle-PVER.in @@ -0,0 +1,14 @@ + + The Python IDLE package for Debian + ---------------------------------- + +This package contains Python @VER@'s Integrated DeveLopment Environment, IDLE. + +IDLE is included in the Python @VER@ upstream distribution (Tools/idle) and +depends on Tkinter (available as @PVER@-tk package). + +I have written a simple man page. + + + 06/16/1999 + Gregor Hoffleit --- python3.3-3.3.0.orig/debian/control.in +++ python3.3-3.3.0/debian/control.in @@ -0,0 +1,193 @@ +Source: @PVER@ +Section: python +Priority: optional +Maintainer: Matthias Klose +Build-Depends: debhelper (>= 5.0.51~), quilt, autoconf, lsb-release, sharutils, + libreadline6-dev, libncursesw5-dev (>= 5.3), + zlib1g-dev, libbz2-dev, liblzma-dev, + libgdbm-dev, libdb-dev, + tk8.5-dev, blt-dev (>= 2.4z), libssl-dev, + libexpat1-dev, + libbluetooth-dev [!hurd-i386 !kfreebsd-i386 !kfreebsd-amd64], + locales [!armel !avr32 !hppa !ia64 !mipsel], + libsqlite3-dev, libffi-dev (>= 3.0.5), + libgpm2 [!hurd-i386 !kfreebsd-i386 !kfreebsd-amd64], + mime-support, netbase, bzip2, gdb, python3:any, + xvfb, xauth +Build-Depends-Indep: python-sphinx +Standards-Version: 3.9.3 +Vcs-Browser: https://code.launchpad.net/~doko/python/pkg@VER@-debian +Vcs-Bzr: http://bazaar.launchpad.net/~doko/python/pkg@VER@-debian + +Package: @PVER@ +Architecture: any +Multi-Arch: allowed +Priority: @PRIO@ +Depends: @PVER@-minimal (= ${binary:Version}), lib@PVER@-stdlib (= ${binary:Version}), mime-support, ${shlibs:Depends}, ${misc:Depends} +Suggests: @PVER@-doc, binutils +Description: Interactive high-level object-oriented language (version @VER@) + Version @VER@ of the high-level, interactive object oriented language, + includes an extensive class library with lots of goodies for + network programming, system administration, sounds and graphics. + +Package: lib@PVER@-stdlib +Architecture: any +Multi-Arch: same +Priority: @PRIO@ +Pre-Depends: multiarch-support +Depends: lib@PVER@-minimal (= ${binary:Version}), mime-support, ${shlibs:Depends}, ${misc:Depends} +Suggests: @PVER@-profiler +Provides: python@VER@-cjkcodecs, python@VER@-ctypes, python@VER@-elementtree, python@VER@-celementtree, python@VER@-wsgiref, @PVER@-gdbm, @PVER@-profiler, @PVER@-lzma +Replaces: @PVER@ (<< 3.3.0~rc1-1~) +Description: Interactive high-level object-oriented language (version @VER@) + Version @VER@ of the high-level, interactive object oriented language, + includes an extensive class library with lots of goodies for + network programming, system administration, sounds and graphics. + . + This package contains the standard library. It is normally not + used on it's own, but as a dependency of @PVER@. + +Package: @PVER@-minimal +Architecture: any +Multi-Arch: allowed +Priority: @MINPRIO@ +Depends: lib@PVER@-minimal (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends} +Recommends: @PVER@ +Suggests: binfmt-support +Replaces: @PVER@ (<< 3.3~a4-1~) +Conflicts: binfmt-support (<< 1.1.2) +Description: Minimal subset of the Python language (version @VER@) + This package contains the interpreter and some essential modules. It can + be used in the boot process for some basic tasks. + See /usr/share/doc/@PVER@-minimal/README.Debian for a list of the modules + contained in this package. + +Package: lib@PVER@-minimal +Architecture: any +Multi-Arch: same +Priority: @MINPRIO@ +Pre-Depends: multiarch-support +Depends: ${shlibs:Depends}, ${misc:Depends} +Recommends: lib@PVER@-stdlib +Replaces: @PVER@ (<< 3.3~a4-1~), @PVER@-minimal (<< 3.3.0~rc1-1~) +Conflicts: binfmt-support (<< 1.1.2) +Description: Minimal subset of the Python language (version @VER@) + This package contains some essential modules. It is normally not + used on it's own, but as a dependency of @PVER@-minimal. + +Package: lib@PVER@ +Architecture: any +Multi-Arch: same +Section: libs +Priority: @PRIO@ +Pre-Depends: multiarch-support +Depends: lib@PVER@-stdlib (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends} +Replaces: @PVER@ (<< 3.0~rc1) +Description: Shared Python runtime library (version @VER@) + Version @VER@ of the high-level, interactive object oriented language, + includes an extensive class library with lots of goodies for + network programming, system administration, sounds and graphics. + . + This package contains the shared runtime library, normally not needed + for programs using the statically linked interpreter. + +Package: @PVER@-examples +Architecture: all +Depends: @PVER@ (>= ${source:Version}), ${misc:Depends} +Description: Examples for the Python language (v@VER@) + Examples, Demos and Tools for Python (v@VER@). These are files included in + the upstream Python distribution (v@VER@). + +Package: @PVER@-dev +Architecture: any +Multi-Arch: allowed +Depends: @PVER@ (= ${binary:Version}), lib@PVER@-dev (= ${binary:Version}), lib@PVER@ (= ${binary:Version}), libexpat1-dev, ${shlibs:Depends}, ${misc:Depends} +Replaces: @PVER@ (<< 3.2~rc1-2) +Recommends: libc6-dev | libc-dev +Description: Header files and a static library for Python (v@VER@) + Header files, a static library and development tools for building + Python (v@VER@) modules, extending the Python interpreter or embedding + Python (v@VER@) in applications. + . + Maintainers of Python packages should read README.maintainers. + +Package: lib@PVER@-dev +Section: libdevel +Architecture: any +Multi-Arch: same +Pre-Depends: multiarch-support +Depends: lib@PVER@-stdlib (= ${binary:Version}), lib@PVER@ (= ${binary:Version}), libexpat1-dev, ${shlibs:Depends}, ${misc:Depends} +Replaces: @PVER@ (<< 3.2~rc1-2), @PVER@-dev (<< 3.3.0~b1-2), @PVER@-minimal (<< 3.3.0~rc1-1~) +Recommends: libc6-dev | libc-dev +Description: Header files and a static library for Python (v@VER@) + Header files, a static library and development tools for building + Python (v@VER@) modules, extending the Python interpreter or embedding + Python (v@VER@) in applications. + . + Maintainers of Python packages should read README.maintainers. + . + This package contains development files. It is normally not + used on it's own, but as a dependency of @PVER@-dev. + +Package: idle-@PVER@ +Architecture: all +Depends: @PVER@, python3-tk, @PVER@-tk, ${misc:Depends} +Enhances: @PVER@ +Description: IDE for Python (v@VER@) using Tkinter + IDLE is an Integrated Development Environment for Python (v@VER@). + IDLE is written using Tkinter and therefore quite platform-independent. + +Package: @PVER@-doc +Section: doc +Architecture: all +Depends: libjs-jquery, libjs-underscore, ${misc:Depends} +Suggests: @PVER@ +Description: Documentation for the high-level object-oriented language Python (v@VER@) + These is the official set of documentation for the interactive high-level + object-oriented language Python (v@VER@). All documents are provided + in HTML format. The package consists of ten documents: + . + * What's New in Python@VER@ + * Tutorial + * Python Library Reference + * Macintosh Module Reference + * Python Language Reference + * Extending and Embedding Python + * Python/C API Reference + * Installing Python Modules + * Documenting Python + * Distributing Python Modules + +Package: @PVER@-dbg +Section: debug +Architecture: any +Multi-Arch: allowed +Priority: extra +Depends: @PVER@ (= ${binary:Version}), lib@PVER@-dbg (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}, python +Suggests: python3-gdbm-dbg, python3-tk-dbg +Description: Debug Build of the Python Interpreter (version @VER@) + The package holds two things: + . + - A Python interpreter configured with --pydebug. Dynamically loaded modules + are searched as _d.so first. Third party extensions need a separate + build to be used by this interpreter. + - Debug information for standard python interpreter and extensions. + . + See the README.debug for more information. + +Package: lib@PVER@-dbg +Section: debug +Architecture: any +Multi-Arch: same +Priority: extra +Pre-Depends: multiarch-support +Depends: lib@PVER@-stdlib (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}, python +Suggests: python3-gdbm-dbg, python3-tk-dbg +Replaces: @PVER@-dbg (<< 3.3.0~rc1-1) +Description: Debug Build of the Python Interpreter (version @VER@) + The package holds two things: + . + - Extensions for a Python interpreter configured with --pydebug. + - Debug information for standard python extensions. + . + See the README.debug for more information. --- python3.3-3.3.0.orig/debian/PVER-dbg.overrides.in +++ python3.3-3.3.0/debian/PVER-dbg.overrides.in @@ -0,0 +1,5 @@ +# just the gdb debug file +@PVER@-dbg binary: python-script-but-no-python-dep + +# pointless lintian ... +@PVER@-dbg binary: hardening-no-fortify-functions --- python3.3-3.3.0.orig/debian/source.lintian-overrides.in +++ python3.3-3.3.0/debian/source.lintian-overrides.in @@ -0,0 +1,2 @@ +# generated during the build +@PVER@ source: quilt-build-dep-but-no-series-file --- python3.3-3.3.0.orig/debian/PVER-doc.doc-base.PVER-ext.in +++ python3.3-3.3.0/debian/PVER-doc.doc-base.PVER-ext.in @@ -0,0 +1,16 @@ +Document: @PVER@-ext +Title: Extending and Embedding the Python Interpreter (v@VER@) +Author: Guido van Rossum +Abstract: This document describes how to write modules in C or C++ to extend + the Python interpreter with new modules. Those modules can define + new functions but also new object types and their methods. The + document also describes how to embed the Python interpreter in + another application, for use as an extension language. Finally, + it shows how to compile and link extension modules so that they + can be loaded dynamically (at run time) into the interpreter, if + the underlying operating system supports this feature. +Section: Programming/Python + +Format: HTML +Index: /usr/share/doc/@PVER@/html/extending/index.html +Files: /usr/share/doc/@PVER@/html/extending/*.html --- python3.3-3.3.0.orig/debian/idle.desktop.in +++ python3.3-3.3.0/debian/idle.desktop.in @@ -0,0 +1,9 @@ +[Desktop Entry] +Name=IDLE (using Python-@VER@) +Comment=Integrated Development Environment for Python (using Python-@VER@) +Exec=/usr/bin/idle-@PVER@ +Icon=/usr/share/pixmaps/@PVER@.xpm +Terminal=false +Type=Application +Categories=Application;Development; +StartupNotify=true --- python3.3-3.3.0.orig/debian/mkbinfmt.py +++ python3.3-3.3.0/debian/mkbinfmt.py @@ -0,0 +1,18 @@ +# mkbinfmt.py +import imp, sys, os.path + +magic = "".join(["\\x%.2x" % c for c in imp.get_magic()]) + +name = sys.argv[1] + +binfmt = '''\ +package %s +interpreter /usr/bin/%s +magic %s\ +''' % (name, name, magic) + +#filename = '/usr/share/binfmts/' + name +#open(filename,'w+').write(binfmt) + +sys.stdout.write(binfmt) +sys.stdout.write('\n') --- python3.3-3.3.0.orig/debian/PVER-doc.doc-base.PVER-new.in +++ python3.3-3.3.0/debian/PVER-doc.doc-base.PVER-new.in @@ -0,0 +1,10 @@ +Document: @PVER@-new +Title: What's new in Python @VER@ +Author: A.M. Kuchling +Abstract: This documents lists new features and changes worth mentioning + in Python @VER@. +Section: Programming/Python + +Format: HTML +Index: /usr/share/doc/@PVER@/html/whatsnew/@VER@.html +Files: /usr/share/doc/@PVER@/html/whatsnew/@VER@.html --- python3.3-3.3.0.orig/debian/compat +++ python3.3-3.3.0/debian/compat @@ -0,0 +1 @@ +5 --- python3.3-3.3.0.orig/debian/FAQ.html +++ python3.3-3.3.0/debian/FAQ.html @@ -0,0 +1,8997 @@ + + +The Whole Python FAQ + + + +

The Whole Python FAQ

+Last changed on Wed Feb 12 21:31:08 2003 CET + +

(Entries marked with ** were changed within the last 24 hours; +entries marked with * were changed within the last 7 days.) +

+ +

+


+

1. General information and availability

+ + +

+


+

2. Python in the real world

+ + +

+


+

3. Building Python and Other Known Bugs

+ + +

+


+

4. Programming in Python

+ + +

+


+

5. Extending Python

+ + +

+


+

6. Python's design

+ + +

+


+

7. Using Python on non-UNIX platforms

+ + +

+


+

8. Python on Windows

+ + +
+

1. General information and availability

+ +
+

1.1. What is Python?

+Python is an interpreted, interactive, object-oriented programming +language. It incorporates modules, exceptions, dynamic typing, very +high level dynamic data types, and classes. Python combines +remarkable power with very clear syntax. It has interfaces to many +system calls and libraries, as well as to various window systems, and +is extensible in C or C++. It is also usable as an extension language +for applications that need a programmable interface. Finally, Python +is portable: it runs on many brands of UNIX, on the Mac, and on PCs +under MS-DOS, Windows, Windows NT, and OS/2. +

+To find out more, the best thing to do is to start reading the +tutorial from the documentation set (see a few questions further +down). +

+See also question 1.17 (what is Python good for). +

+ +Edit this entry / +Log info + +/ Last changed on Mon May 26 16:05:18 1997 by +GvR +

+ +


+

1.2. Why is it called Python?

+Apart from being a computer scientist, I'm also a fan of "Monty +Python's Flying Circus" (a BBC comedy series from the seventies, in +the -- unlikely -- case you didn't know). It occurred to me one day +that I needed a name that was short, unique, and slightly mysterious. +And I happened to be reading some scripts from the series at the +time... So then I decided to call my language Python. +

+By now I don't care any more whether you use a Python, some other +snake, a foot or 16-ton weight, or a wood rat as a logo for Python! +

+ +Edit this entry / +Log info + +/ Last changed on Thu Aug 24 00:50:41 2000 by +GvR +

+ +


+

1.3. How do I obtain a copy of the Python source?

+The latest Python source distribution is always available from +python.org, at http://www.python.org/download. The latest development sources can be obtained via anonymous CVS from SourceForge, at http://www.sf.net/projects/python . +

+The source distribution is a gzipped tar file containing the complete C source, LaTeX +documentation, Python library modules, example programs, and several +useful pieces of freely distributable software. This will compile and +run out of the box on most UNIX platforms. (See section 7 for +non-UNIX information.) +

+Older versions of Python are also available from python.org. +

+ +Edit this entry / +Log info + +/ Last changed on Tue Apr 9 17:06:16 2002 by +A.M. Kuchling +

+ +


+

1.4. How do I get documentation on Python?

+All documentation is available on-line, starting at http://www.python.org/doc/. +

+The LaTeX source for the documentation is part of the source +distribution. If you don't have LaTeX, the latest Python +documentation set is available, in various formats like postscript +and html, by anonymous ftp - visit the above URL for links to the +current versions. +

+PostScript for a high-level description of Python is in the file nluug-paper.ps +(a separate file on the ftp site). +

+ +Edit this entry / +Log info + +/ Last changed on Wed Jan 21 12:02:55 1998 by +Ken Manheimer +

+ +


+

1.5. Are there other ftp sites that mirror the Python distribution?

+The following anonymous ftp sites keep mirrors of the Python +distribution: +

+USA: +

+

+        ftp://ftp.python.org/pub/python/
+        ftp://gatekeeper.dec.com/pub/plan/python/
+        ftp://ftp.uu.net/languages/python/
+        ftp://ftp.wustl.edu/graphics/graphics/sgi-stuff/python/
+        ftp://ftp.sterling.com/programming/languages/python/
+        ftp://uiarchive.cso.uiuc.edu/pub/lang/python/
+        ftp://ftp.pht.com/mirrors/python/python/
+	ftp://ftp.cdrom.com/pub/python/
+
+Europe: +

+

+        ftp://ftp.cwi.nl/pub/python/
+        ftp://ftp.funet.fi/pub/languages/python/
+        ftp://ftp.sunet.se/pub/lang/python/
+        ftp://unix.hensa.ac.uk/mirrors/uunet/languages/python/
+        ftp://ftp.lip6.fr/pub/python/
+        ftp://sunsite.cnlab-switch.ch/mirror/python/
+        ftp://ftp.informatik.tu-muenchen.de/pub/comp/programming/languages/python/
+
+Australia: +

+

+        ftp://ftp.dstc.edu.au/pub/python/
+
+

+ +Edit this entry / +Log info + +/ Last changed on Wed Mar 24 09:20:49 1999 by +A.M. Kuchling +

+ +


+

1.6. Is there a newsgroup or mailing list devoted to Python?

+There is a newsgroup, comp.lang.python, +and a mailing list. The newsgroup and mailing list are gatewayed into +each other -- if you can read news it's unnecessary to subscribe to +the mailing list. To subscribe to the mailing list +(python-list@python.org) visit its Mailman webpage at +http://www.python.org/mailman/listinfo/python-list +

+More info about the newsgroup and mailing list, and about other lists, +can be found at +http://www.python.org/psa/MailingLists.html. +

+Archives of the newsgroup are kept by Deja News and accessible +through the "Python newsgroup search" web page, +http://www.python.org/search/search_news.html. +This page also contains pointer to other archival collections. +

+ +Edit this entry / +Log info + +/ Last changed on Wed Jun 23 09:29:36 1999 by +GvR +

+ +


+

1.7. Is there a WWW page devoted to Python?

+Yes, http://www.python.org/ is the official Python home page. +

+ +Edit this entry / +Log info + +/ Last changed on Fri May 23 14:42:59 1997 by +Ken Manheimer +

+ +


+

1.8. Is the Python documentation available on the WWW?

+Yes. Python 2.0 documentation is available from +http://www.pythonlabs.com/tech/python2.0/doc/ and from +http://www.python.org/doc/. Note that most documentation +is available for on-line browsing as well as for downloading. +

+ +Edit this entry / +Log info + +/ Last changed on Tue Jan 2 03:14:08 2001 by +Moshe Zadka +

+ +


+

1.9. Are there any books on Python?

+Yes, many, and more are being published. See +the python.org Wiki at http://www.python.org/cgi-bin/moinmoin/PythonBooks for a list. +

+You can also search online bookstores for "Python" +(and filter out the Monty Python references; or +perhaps search for "Python" and "language"). +

+ +Edit this entry / +Log info + +/ Last changed on Mon Aug 5 19:08:49 2002 by +amk +

+ +


+

1.10. Are there any published articles about Python that I can reference?

+If you can't reference the web site, and you don't want to reference the books +(see previous question), there are several articles on Python that you could +reference. +

+Most publications about Python are collected on the Python web site: +

+

+    http://www.python.org/doc/Publications.html
+
+It is no longer recommended to reference this +very old article by Python's author: +

+

+    Guido van Rossum and Jelke de Boer, "Interactively Testing Remote
+    Servers Using the Python Programming Language", CWI Quarterly, Volume
+    4, Issue 4 (December 1991), Amsterdam, pp 283-303.
+
+

+ +Edit this entry / +Log info + +/ Last changed on Sat Jul 4 20:52:31 1998 by +GvR +

+ +


+

1.11. Are there short introductory papers or talks on Python?

+There are several - you can find links to some of them collected at +http://www.python.org/doc/Hints.html#intros. +

+ +Edit this entry / +Log info + +/ Last changed on Fri May 23 15:04:05 1997 by +Ken Manheimer +

+ +


+

1.12. How does the Python version numbering scheme work?

+Python versions are numbered A.B.C or A.B. A is the major version +number -- it is only incremented for really major changes in the +language. B is the minor version number, incremented for less +earth-shattering changes. C is the micro-level -- it is +incremented for each bugfix release. See PEP 6 for more information +about bugfix releases. +

+Not all releases have bugfix releases. +Note that in the past (ending with 1.5.2), +micro releases have added significant changes; +in fact the changeover from 0.9.9 to 1.0.0 was the first time +that either A or B changed! +

+Alpha, beta and release candidate versions have an additional suffixes. +The suffix for an alpha version is "aN" for some small number N, the +suffix for a beta version is "bN" for some small number N, and the +suffix for a release candidate version is "cN" for some small number N. +

+Note that (for instance) all versions labeled 2.0aN precede the +versions labeled 2.0bN, which precede versions labeled 2.0cN, and +those precede 2.0. +

+As a rule, no changes are made between release candidates and the final +release unless there are show-stopper bugs. +

+You may also find version numbers with a "+" suffix, e.g. "2.2+". +These are unreleased versions, built directly from the CVS trunk. +

+See also the documentation for sys.version, sys.hexversion, and +sys.version_info. +

+ +Edit this entry / +Log info + +/ Last changed on Mon Jan 14 06:34:17 2002 by +GvR +

+ +


+

1.13. How do I get a beta test version of Python?

+All releases, including alphas, betas and release candidates, are announced on +comp.lang.python and comp.lang.python.announce newsgroups, +which are gatewayed into the python-list@python.org and +python-announce@python.org. In addition, all these announcements appear on +the Python home page, at http://www.python.org. +

+You can also access the development version of Python through CVS. See http://sourceforge.net/cvs/?group_id=5470 for details. If you're not familiar with CVS, documents like http://linux.oreillynet.com/pub/a/linux/2002/01/03/cvs_intro.html +provide an introduction. +

+ +Edit this entry / +Log info + +/ Last changed on Mon Jun 3 00:57:08 2002 by +Neal Norwitz +

+ +


+

1.14. Are there copyright restrictions on the use of Python?

+Hardly. You can do anything you want with the source, as long as +you leave the copyrights in, and display those copyrights in any +documentation about Python that you produce. Also, don't use the +author's institute's name in publicity without prior written +permission, and don't hold them responsible for anything (read the +actual copyright for a precise legal wording). +

+In particular, if you honor the copyright rules, it's OK to use Python +for commercial use, to sell copies of Python in source or binary form, +or to sell products that enhance Python or incorporate Python (or part +of it) in some form. I would still like to know about all commercial +use of Python! +

+ +Edit this entry / +Log info +

+ +


+

1.15. Why was Python created in the first place?

+Here's a very brief summary of what got me started: +

+I had extensive experience with implementing an interpreted language +in the ABC group at CWI, and from working with this group I had +learned a lot about language design. This is the origin of many +Python features, including the use of indentation for statement +grouping and the inclusion of very-high-level data types (although the +details are all different in Python). +

+I had a number of gripes about the ABC language, but also liked many +of its features. It was impossible to extend the ABC language (or its +implementation) to remedy my complaints -- in fact its lack of +extensibility was one of its biggest problems. +I had some experience with using Modula-2+ and talked with the +designers of Modula-3 (and read the M3 report). M3 is the origin of +the syntax and semantics used for exceptions, and some other Python +features. +

+I was working in the Amoeba distributed operating system group at +CWI. We needed a better way to do system administration than by +writing either C programs or Bourne shell scripts, since Amoeba had +its own system call interface which wasn't easily accessible from the +Bourne shell. My experience with error handling in Amoeba made me +acutely aware of the importance of exceptions as a programming +language feature. +

+It occurred to me that a scripting language with a syntax like ABC +but with access to the Amoeba system calls would fill the need. I +realized that it would be foolish to write an Amoeba-specific +language, so I decided that I needed a language that was generally +extensible. +

+During the 1989 Christmas holidays, I had a lot of time on my hand, +so I decided to give it a try. During the next year, while still +mostly working on it in my own time, Python was used in the Amoeba +project with increasing success, and the feedback from colleagues made +me add many early improvements. +

+In February 1991, after just over a year of development, I decided +to post to USENET. The rest is in the Misc/HISTORY file. +

+ +Edit this entry / +Log info + +/ Last changed on Fri May 23 00:06:23 1997 by +GvR +

+ +


+

1.16. Do I have to like "Monty Python's Flying Circus"?

+No, but it helps. Pythonistas like the occasional reference to SPAM, +and of course, nobody expects the Spanish Inquisition +

+The two main reasons to use Python are: +

+

+ - Portable
+ - Easy to learn
+
+The three main reasons to use Python are: +

+

+ - Portable
+ - Easy to learn
+ - Powerful standard library
+
+(And nice red uniforms.) +

+And remember, there is no rule six. +

+ +Edit this entry / +Log info + +/ Last changed on Wed May 28 10:39:21 1997 by +GvR +

+ +


+

1.17. What is Python good for?

+Python is used in many situations where a great deal of dynamism, +ease of use, power, and flexibility are required. +

+In the area of basic text +manipulation core Python (without any non-core extensions) is easier +to use and is roughly as fast as just about any language, and this makes Python +good for many system administration type tasks and for CGI programming +and other application areas that manipulate text and strings and such. +

+When augmented with +standard extensions (such as PIL, COM, Numeric, oracledb, kjbuckets, +tkinter, win32api, etc.) +or special purpose extensions (that you write, perhaps using helper tools such +as SWIG, or using object protocols such as ILU/CORBA or COM) Python +becomes a very convenient "glue" or "steering" +language that helps make heterogeneous collections of unrelated +software packages work together. +For example by combining Numeric with oracledb you can help your +SQL database do statistical analysis, or even Fourier transforms. +One of the features that makes Python excel in the "glue language" role +is Python's simple, usable, and powerful C language runtime API. +

+Many developers also use Python extensively as a graphical user +interface development aide. +

+ +Edit this entry / +Log info + +/ Last changed on Sat May 24 10:13:11 1997 by +Aaron Watters +

+ +


+

1.18. Can I use the FAQ Wizard software to maintain my own FAQ?

+Sure. It's in Tools/faqwiz/ of the python source tree. +

+ +Edit this entry / +Log info + +/ Last changed on Fri Mar 29 06:50:32 2002 by +Aahz +

+ +


+

1.19. Which editor has good support for editing Python source code?

+On Unix, the first choice is Emacs/XEmacs. There's an elaborate +mode for editing Python code, which is available from the Python +source distribution (Misc/python-mode.el). It's also bundled +with XEmacs (we're still working on legal details to make it possible +to bundle it with FSF Emacs). And it has its own web page: +

+

+    http://www.python.org/emacs/python-mode/index.html
+
+There are many other choices, for Unix, Windows or Macintosh. +Richard Jones compiled a table from postings on the Python newsgroup: +

+

+    http://www.bofh.asn.au/~richard/editors.html
+
+See also FAQ question 7.10 for some more Mac and Win options. +

+ +Edit this entry / +Log info + +/ Last changed on Mon Jun 15 23:21:04 1998 by +Gvr +

+ +


+

1.20. I've never programmed before. Is there a Python tutorial?

+There are several, and at least one book. +All information for beginning Python programmers is collected here: +

+

+    http://www.python.org/doc/Newbies.html
+
+

+ +Edit this entry / +Log info + +/ Last changed on Wed Sep 5 05:34:07 2001 by +GvR +

+ +


+

1.21. Where in the world is www.python.org located?

+It's currently in Amsterdam, graciously hosted by XS4ALL: +

+

+    http://www.xs4all.nl
+
+Thanks to Thomas Wouters for setting this up!!!! +

+ +Edit this entry / +Log info + +/ Last changed on Fri Aug 3 21:49:27 2001 by +GvR +

+ +


+

2. Python in the real world

+ +
+

2.1. How many people are using Python?

+Certainly thousands, and quite probably tens of thousands of users. +More are seeing the light each day. The comp.lang.python newsgroup is +very active, but overall there is no accurate estimate of the number of subscribers or Python users. +

+Jacek Artymiak has created a Python Users Counter; you can see the +current count by visiting +http://www.wszechnica.safenet.pl/cgi-bin/checkpythonuserscounter.py +(this will not increment the counter; use the link there if you haven't +added yourself already). Most Python users appear not to have registered themselves. +

+ +Edit this entry / +Log info + +/ Last changed on Thu Feb 21 23:29:18 2002 by +GvR +

+ +


+

2.2. Have any significant projects been done in Python?

+At CWI (the former home of Python), we have written a 20,000 line +authoring environment for transportable hypermedia presentations, a +5,000 line multimedia teleconferencing tool, as well as many many +smaller programs. +

+At CNRI (Python's new home), we have written two large applications: +Grail, a fully featured web browser (see +http://grail.cnri.reston.va.us), +and the Knowbot Operating Environment, +a distributed environment for mobile code. +

+The University of Virginia uses Python to control a virtual reality +engine. See http://alice.cs.cmu.edu. +

+The ILU project at Xerox PARC can generate Python glue for ILU +interfaces. See ftp://ftp.parc.xerox.com/pub/ilu/ilu.html. ILU +is a free CORBA compliant ORB which supplies distributed object +connectivity to a host of platforms using a host of languages. +

+Mark Hammond and Greg Stein and others are interfacing Python to +Microsoft's COM and ActiveX architectures. This means, among other +things, that Python may be used in active server pages or as a COM +controller (for example to automatically extract from or insert information +into Excel or MSAccess or any other COM aware application). +Mark claims Python can even be a ActiveX scripting host (which +means you could embed JScript inside a Python application, if you +had a strange sense of humor). Python/AX/COM is distributed as part +of the PythonWin distribution. +

+The University of California, Irvine uses a student administration +system called TELE-Vision written entirely in Python. Contact: Ray +Price rlprice@uci.edu. +

+The Melbourne Cricket Ground (MCG) in Australia (a 100,000+ person venue) +has it's scoreboard system written largely in Python on MS Windows. +Python expressions are used to create almost every scoring entry that +appears on the board. The move to Python/C++ away from exclusive C++ +has provided a level of functionality that would simply not have been +viable otherwise. +

+See also the next question. +

+Note: this FAQ entry is really old. +See http://www.python.org/psa/Users.html for a more recent list. +

+ +Edit this entry / +Log info + +/ Last changed on Wed Oct 25 13:24:15 2000 by +GvR +

+ +


+

2.3. Are there any commercial projects going on using Python?

+Yes, there's lots of commercial activity using Python. See +http://www.python.org/psa/Users.html for a list. +

+ +Edit this entry / +Log info + +/ Last changed on Wed Oct 14 18:17:33 1998 by +ken +

+ +


+

2.4. How stable is Python?

+Very stable. New, stable releases have been coming out roughly every 3 to 12 months since 1991, and this seems likely to continue. +

+With the introduction of retrospective "bugfix" releases the stability of the language implementations can be, and is being, improved independently of the new features offered by more recent major or minor releases. Bugfix releases, indicated by a third component of the version number, only fix known problems and do not gratuitously introduce new and possibly incompatible features or modified library functionality. +

+Release 2.2 got its first bugfix on April 10, 2002. The new version +number is now 2.2.1. The 2.1 release, at 2.1.3, can probably be +considered the "most stable" platform because it has been bugfixed +twice. +

+ +Edit this entry / +Log info + +/ Last changed on Tue Jul 23 10:20:04 2002 by +Jens Kubieziel +

+ +


+

2.5. What new developments are expected for Python in the future?

+See http://www.python.org/peps/ for the Python Enhancement +Proposals (PEPs). PEPs are design +documents +describing a suggested new feature for Python, providing +a concise technical specification and a rationale. +

+Also, follow the discussions on the python-dev mailing list. +

+ +Edit this entry / +Log info + +/ Last changed on Tue Apr 9 17:09:51 2002 by +A.M. Kuchling +

+ +


+

2.6. Is it reasonable to propose incompatible changes to Python?

+In general, no. There are already millions of lines of Python code +around the world, so any changes in the language that invalidates more +than a very small fraction of existing programs has to be frowned +upon. Even if you can provide a conversion program, there still is +the problem of updating all documentation. Providing a gradual +upgrade path is the only way if a feature has to be changed. +

+See http://www.python.org/peps/pep-0005.html for the proposed +mechanism for creating backwards-incompatibilities. +

+ +Edit this entry / +Log info + +/ Last changed on Mon Apr 1 22:13:47 2002 by +Fred Drake +

+ +


+

2.7. What is the future of Python?

+Please see http://www.python.org/peps/ for proposals of future +activities. One of the PEPs (Python Enhancement Proposals) deals +with the PEP process and PEP format -- see +http://www.python.org/peps/pep-0001.html if you want to +submit a PEP. In http://www.python.org/peps/pep-0042.html there +is a list of wishlists the Python Development team plans to tackle. +

+ +Edit this entry / +Log info + +/ Last changed on Mon Apr 1 22:15:46 2002 by +Fred Drake +

+ +


+

2.8. What was the PSA, anyway?

+The Python Software Activity was +created by a number of Python aficionados who want Python to be more +than the product and responsibility of a single individual. +The PSA was not an independent organization, but lived +under the umbrealla of CNRI. +

+The PSA has been superseded by the Python Software Foundation, +an independent non-profit organization. The PSF's home page +is at http://www.python.org/psf/. +

+Some pages created by the PSA still live at +http://www.python.org/psa/ +

+ +Edit this entry / +Log info + +/ Last changed on Thu Jul 25 18:19:44 2002 by +GvR +

+ +


+

2.9. Deleted

+

+

+ +Edit this entry / +Log info + +/ Last changed on Tue Jan 2 02:51:30 2001 by +Moshe Zadka +

+ +


+

2.10. Deleted

+

+

+ +Edit this entry / +Log info + +/ Last changed on Tue Jan 2 02:52:19 2001 by +Moshe Zadka +

+ +


+

2.11. Is Python Y2K (Year 2000) Compliant?

+As of January, 2001 no major problems have been reported and Y2K +compliance seems to be a non-issue. +

+Since Python is available free of charge, there are no absolute +guarantees. If there are unforeseen problems, liability is the +user's rather than the developers', and there is nobody you can sue for damages. +

+Python does few +date manipulations, and what it does is all based on the Unix +representation for time (even on non-Unix systems) which uses seconds +since 1970 and won't overflow until 2038. +

+ +Edit this entry / +Log info + +/ Last changed on Mon Jan 8 17:19:32 2001 by +Steve Holden +

+ +


+

2.12. Is Python a good language in a class for beginning programmers?

+Yes. This long answer attempts to address any concerns you might +have with teaching Python as a programmer's first language. +(If you want to discuss Python's use in education, then +you may be interested in joining the edu-sig mailinglist. +See http://www.python.org/sigs/edu-sig/ ) +

+It is still common to start students with a procedural +(subset of a) statically typed language such as Pascal, C, or +a subset of C++ or Java. I think that students may be better +served by learning Python as their first language. Python has +a very simple and consistent syntax and a large standard library. +Most importantly, using Python in a beginning programming course +permits students to concentrate on important programming skills, +such as problem decomposition and data type design. +

+With Python, students can be quickly introduced to basic concepts +such as loops and procedures. They can even probably work with +user-defined objects in their very first course. They could +implement a tree structure as nested Python lists, for example. +They could be introduced to objects in their first course if +desired. For a student who has never programmed before, using +a statically typed language seems unnatural. It presents +additional complexity that the student must master and slows +the pace of the course. The students are trying to learn to +think like a computer, decompose problems, design consistent +interfaces, and encapsulate data. While learning to use a +statically typed language is important, it is not necessarily the +best topic to address in the students' first programming course. +

+Many other aspects of Python make it a good first language. +Python has a large standard library (like Java) so that +students can be assigned programming projects very early in the +course that do something. Assignments aren't restricted to the +standard four-function calculator and check balancing programs. +By using the standard library, students can gain the satisfaction +of working on realistic applications as they learn the fundamentals +of programming. Using the standard library also teaches students +about code reuse. +

+Python's interactive interpreter also enables students to +test language features while they're programming. They can keep +a window with the interpreter running while they enter their +programs' source in another window. If they can't remember the +methods for a list, they can do something like this: +

+

+ >>> L = []
+ >>> dir(L)
+ ['append', 'count', 'extend', 'index', 'insert', 'pop', 'remove',
+ 'reverse', 'sort']
+ >>> print L.append.__doc__
+ L.append(object) -- append object to end
+ >>> L.append(1)
+ >>> L
+ [1]
+
+With the interpreter, documentation is never far from the +student as he's programming. +

+There are also good IDEs for Python. Guido van Rossum's IDLE +is a cross-platform IDE for Python that is written in Python +using Tk. There is also a Windows specific IDE called PythonWin. +Emacs users will be happy to know that there is a very good Python +mode for Emacs. All of these programming environments provide +syntax highlighting, auto-indenting, and access to the interactive +interpreter while coding. For more information about IDEs, see XXX. +

+If your department is currently using Pascal because it was +designed to be a teaching language, then you'll be happy to +know that Guido van Rossum designed Python to be simple to +teach to everyone but powerful enough to implement real world +applications. Python makes a good language for first time +programmers because that was one of Python's design goals. +There are papers at http://www.python.org/doc/essays/ on the Python website +by Python's creator explaining his objectives for the language. +One that may interest you is titled "Computer Programming for Everybody" +http://www.python.org/doc/essays/cp4e.html +

+If you're seriously considering Python as a language for your +school, Guido van Rossum may even be willing to correspond with +you about how the language would fit in your curriculum. +See http://www.python.org/doc/FAQ.html#2.2 for examples of +Python's use in the "real world." +

+While Python, its source code, and its IDEs are freely +available, this consideration should not rule +out other languages. There are other free languages (Java, +free C compilers), and many companies are willing to waive some +or all of their fees for student programming tools if it +guarantees that a whole graduating class will know how to +use their tools. That is, if one of the requirements for +the language that will be taught is that it be freely +available, then Python qualifies, but this requirement +does not preclude other languages. +

+While Python jobs may not be as prevalent as C/C++/Java jobs, +teachers should not worry about teaching students critical job +skills in their first course. The skills that win students a +job are those they learn in their senior classes and internships. +Their first programming courses are there to lay a solid +foundation in programming fundamentals. The primary question +in choosing the language for such a course should be which +language permits the students to learn this material without +hindering or limiting them. +

+Another argument for Python is that there are many tasks for +which something like C++ is overkill. That's where languages +like Python, Perl, Tcl, and Visual Basic thrive. It's critical +for students to know something about these languages. (Every +employer for whom I've worked used at least one such language.) +Of the languages listed above, Python probably makes the best +language in a programming curriculum since its syntax is simple, +consistent, and not unlike other languages (C/C++/Java) that +are probably in the curriculum. By starting students with +Python, a department simultaneously lays the foundations for +other programming courses and introduces students to the type +of language that is often used as a "glue" language. As an +added bonus, Python can be used to interface with Microsoft's +COM components (thanks to Mark Hammond). There is also Jython, +a Java implementation of the Python interpreter, that can be +used to connect Java components. +

+If you currently start students with Pascal or C/C++ or Java, +you may be worried they will have trouble learning a statically +typed language after starting with Python. I think that this +fear most often stems from the fact that the teacher started +with a statically typed language, and we tend to like to teach +others in the same way we were taught. In reality, the +transition from Python to one of these other languages is +quite simple. +

+To motivate a statically typed language such as C++, begin the +course by explaining that unlike Python, their first language, +C++ is compiled to a machine dependent executable. Explain +that the point is to make a very fast executable. To permit +the compiler to make optimizations, programmers must help it +by specifying the "types" of variables. By restricting each +variable to a specific type, the compiler can reduce the +book-keeping it has to do to permit dynamic types. The compiler +also has to resolve references at compile time. Thus, the +language gains speed by sacrificing some of Python's dynamic +features. Then again, the C++ compiler provides type safety +and catches many bugs at compile time instead of run time (a +critical consideration for many commercial applications). C++ +is also designed for very large programs where one may want to +guarantee that others don't touch an object's implementation. +C++ provides very strong language features to separate an object's +implementation from its interface. Explain why this separation +is a good thing. +

+The first day of a C++ course could then be a whirlwind introduction +to what C++ requires and provides. The point here is that after +a semester or two of Python, students are hopefully competent +programmers. They know how to handle loops and write procedures. +They've also worked with objects, thought about the benefits of +consistent interfaces, and used the technique of subclassing to +specialize behavior. Thus, a whirlwind introduction to C++ could +show them how objects and subclassing looks in C++. The +potentially difficult concepts of object-oriented design were +taught without the additional obstacles presented by a language +such as C++ or Java. When learning one of these languages, +the students would already understand the "road map." They +understand objects; they would just be learning how objects +fit in a statically typed languages. Language requirements +and compiler errors that seem unnatural to beginning programmers +make sense in this new context. Many students will find it +helpful to be able to write a fast prototype of their algorithms +in Python. Thus, they can test and debug their ideas before +they attempt to write the code in the new language, saving the +effort of working with C++ types for when they've discovered a +working solution for their assignments. When they get annoyed +with the rigidity of types, they'll be happy to learn about +containers and templates to regain some of the lost flexibility +Python afforded them. Students may also gain an appreciation +for the fact that no language is best for every task. They'll +see that C++ is faster, but they'll know that they can gain +flexibility and development speed with a Python when execution +speed isn't critical. +

+If you have any concerns that weren't addressed here, try +posting to the Python newsgroup. Others there have done some +work with using Python as an instructional tool. Good luck. +We'd love to hear about it if you choose Python for your course. +

+ +Edit this entry / +Log info + +/ Last changed on Mon Dec 2 19:32:35 2002 by +Bill Sconce +

+ +


+

3. Building Python and Other Known Bugs

+ +
+

3.1. Is there a test set?

+Sure. You can run it after building with "make test", or you can +run it manually with this command at the Python prompt: +

+

+ import test.autotest
+
+In Python 1.4 or earlier, use +

+

+ import autotest
+
+The test set doesn't test all features of Python, +but it goes a long way to confirm that Python is actually working. +

+NOTE: if "make test" fails, don't just mail the output to the +newsgroup -- this doesn't give enough information to debug the +problem. Instead, find out which test fails, and run that test +manually from an interactive interpreter. For example, if +"make test" reports that test_spam fails, try this interactively: +

+

+ import test.test_spam
+
+This generally produces more verbose output which can be diagnosed +to debug the problem. If you find a bug in Python or the libraries, or in the tests, please report this in the Python bug tracker at SourceForge: +

+http://sourceforge.net/tracker/?func=add&group_id=5470&atid=105470 +

+ +Edit this entry / +Log info + +/ Last changed on Fri Apr 27 10:29:36 2001 by +Fred Drake +

+ +


+

3.2. When running the test set, I get complaints about floating point operations, but when playing with floating point operations I cannot find anything wrong with them.

+The test set makes occasional unwarranted assumptions about the +semantics of C floating point operations. Until someone donates a +better floating point test set, you will have to comment out the +offending floating point tests and execute similar tests manually. +

+ +Edit this entry / +Log info +

+ +


+

3.3. Link errors after rerunning the configure script.

+It is generally necessary to run "make clean" after a configuration +change. +

+ +Edit this entry / +Log info +

+ +


+

3.4. The python interpreter complains about options passed to a script (after the script name).

+You are probably linking with GNU getopt, e.g. through -liberty. +Don't. The reason for the complaint is that GNU getopt, unlike System +V getopt and other getopt implementations, doesn't consider a +non-option to be the end of the option list. A quick (and compatible) +fix for scripts is to add "--" to the interpreter, like this: +

+

+        #! /usr/local/bin/python --
+
+You can also use this interactively: +

+

+        python -- script.py [options]
+
+Note that a working getopt implementation is provided in the Python +distribution (in Python/getopt.c) but not automatically used. +

+ +Edit this entry / +Log info +

+ +


+

3.5. When building on the SGI, make tries to run python to create glmodule.c, but python hasn't been built or installed yet.

+Comment out the line mentioning glmodule.c in Setup and build a +python without gl first; install it or make sure it is in your $PATH, +then edit the Setup file again to turn on the gl module, and make +again. You don't need to do "make clean"; you do need to run "make +Makefile" in the Modules subdirectory (or just run "make" at the +toplevel). +

+ +Edit this entry / +Log info +

+ +


+

3.6. I use VPATH but some targets are built in the source directory.

+On some systems (e.g. Sun), if the target already exists in the +source directory, it is created there instead of in the build +directory. This is usually because you have previously built without +VPATH. Try running "make clobber" in the source directory. +

+ +Edit this entry / +Log info +

+ +


+

3.7. Trouble building or linking with the GNU readline library.

+You can use the GNU readline library to improve the interactive user +interface: this gives you line editing and command history when +calling python interactively. Its sources are distributed with +Python (at least for 2.0). Uncomment the line +

+#readline readline.c -lreadline -ltermcap +

+in Modules/Setup. The configuration option --with-readline +is no longer supported, at least in Python 2.0. Some hints on +building and using the readline library: +On SGI IRIX 5, you may have to add the following +to rldefs.h: +

+

+        #ifndef sigmask
+        #define sigmask(sig) (1L << ((sig)-1))
+        #endif
+
+On some systems, you will have to add #include "rldefs.h" to the +top of several source files, and if you use the VPATH feature, you +will have to add dependencies of the form foo.o: foo.c to the +Makefile for several values of foo. +The readline library requires use of the termcap library. A +known problem with this is that it contains entry points which +cause conflicts with the STDWIN and SGI GL libraries. The STDWIN +conflict can be solved by adding a line saying '#define werase w_erase' to the +stdwin.h file (in the STDWIN distribution, subdirectory H). The +GL conflict has been solved in the Python configure script by a +hack that forces use of the static version of the termcap library. +Check the newsgroup gnu.bash.bug news:gnu.bash.bug for +specific problems with the readline library (I don't read this group +but I've been told that it is the place for readline bugs). +

+ +Edit this entry / +Log info + +/ Last changed on Sat Dec 2 18:23:48 2000 by +Issac Trotts +

+ +


+

3.8. Trouble with socket I/O on older Linux 1.x versions.

+Once you've built Python, use it to run the regen script in the +Lib/plat-linux2 directory. Apparently the files as distributed don't match the system headers on some Linux versions. +

+Note that this FAQ entry only applies to Linux kernel versions 1.x.y; +these are hardly around any more. +

+ +Edit this entry / +Log info + +/ Last changed on Tue Jul 30 20:05:52 2002 by +Jens Kubieziel +

+ +


+

3.9. Trouble with prototypes on Ultrix.

+Ultrix cc seems broken -- use gcc, or edit config.h to #undef +HAVE_PROTOTYPES. +

+ +Edit this entry / +Log info +

+ +


+

3.10. Other trouble building Python on platform X.

+Please submit the details to the SourceForge bug tracker: +

+

+  http://sourceforge.net/tracker/?group_id=5470&atid=105470
+
+and we'll look +into it. Please provide as many details as possible. In particular, +if you don't tell us what type of computer and what operating system +(and version) you are using it will be difficult for us to figure out +what is the matter. If you have compilation output logs, +please use file uploads -- don't paste everything in the message box. +

+In many cases, we won't have access to the same hardware or operating system version, so please, if you have a SourceForge account, log in before filing your report, or if you don't have an account, include an email address at which we can reach you for further questions. Logging in to SourceForge first will also cause SourceForge to send you updates as we act on your report. +

+ +Edit this entry / +Log info + +/ Last changed on Fri Apr 27 10:53:18 2001 by +Fred Drake +

+ +


+

3.11. How to configure dynamic loading on Linux.

+This is now automatic as long as your Linux version uses the ELF +object format (all recent Linuxes do). +

+ +Edit this entry / +Log info +

+ +


+

3.12. I can't get shared modules to work on Linux 2.0 (Slackware96)?

+This is a bug in the Slackware96 release. The fix is simple: Make sure +that there is a link from /lib/libdl.so to /lib/libdl.so.1 so that the +following links are setup: /lib/libdl.so -> /lib/libdl.so.1 +/lib/libdl.so.1 -> /lib/libdl.so.1.7.14 You may have to rerun the +configure script, after rm'ing the config.cache file, before you +attempt to rebuild python after this fix. +

+ +Edit this entry / +Log info + +/ Last changed on Wed May 21 15:45:03 1997 by +GvR +

+ +


+

3.13. Trouble when making modules shared on Linux.

+This happens when you have built Python for static linking and then +enable +
+  *shared*
+
+in the Setup file. Shared library code must be +compiled with "-fpic". If a .o file for the module already exist that +was compiled for static linking, you must remove it or do "make clean" +in the Modules directory. +

+ +Edit this entry / +Log info + +/ Last changed on Fri May 23 13:42:30 1997 by +GvR +

+ +


+

3.14. [deleted]

+[ancient information on threads on linux (when thread support +was not standard) used to be here] +

+ +Edit this entry / +Log info + +/ Last changed on Sun Jun 2 17:27:13 2002 by +Erno Kuusela +

+ +


+

3.15. Errors when linking with a shared library containing C++ code.

+Link the main Python binary with C++. Change the definition of +LINKCC in Modules/Makefile to be your C++ compiler. You may have to +edit config.c slightly to make it compilable with C++. +

+ +Edit this entry / +Log info +

+ +


+

3.16. Deleted

+

+

+ +Edit this entry / +Log info + +/ Last changed on Tue Sep 11 16:02:22 2001 by +GvR +

+ +


+

3.17. Deleted.

+

+

+ +Edit this entry / +Log info + +/ Last changed on Tue Sep 11 15:54:57 2001 by +GvR +

+ +


+

3.18. Compilation or link errors for the _tkinter module

+Most likely, there's a version mismatch between the Tcl/Tk header +files (tcl.h and tk.h) and the Tcl/Tk libraries you are using e.g. +"-ltk8.0" and "-ltcl8.0" arguments for _tkinter in the Setup file). +It is possible to install several versions of the Tcl/Tk libraries, +but there can only be one version of the tcl.h and tk.h header +files. If the library doesn't match the header, you'll get +problems, either when linking the module, or when importing it. +Fortunately, the version number is clearly stated in each file, +so this is easy to find. Reinstalling and using the latest +version usually fixes the problem. +

+(Also note that when compiling unpatched Python 1.5.1 against +Tcl/Tk 7.6/4.2 or older, you get an error on Tcl_Finalize. See +the 1.5.1 patch page at http://www.python.org/1.5/patches-1.5.1/.) +

+ +Edit this entry / +Log info + +/ Last changed on Thu Jun 11 00:49:14 1998 by +Gvr +

+ +


+

3.19. I configured and built Python for Tcl/Tk but "import Tkinter" fails.

+Most likely, you forgot to enable the line in Setup that says +"TKPATH=:$(DESTLIB)/tkinter". +

+ +Edit this entry / +Log info +

+ +


+

3.20. [deleted]

+[ancient information on a gcc+tkinter bug on alpha was here] +

+ +Edit this entry / +Log info + +/ Last changed on Mon Jun 3 16:46:23 2002 by +Erno Kuusela +

+ +


+

3.21. Several common system calls are missing from the posix module.

+Most likely, all test compilations run by the configure script +are failing for some reason or another. Have a look in config.log to +see what could be the reason. A common reason is specifying a +directory to the --with-readline option that doesn't contain the +libreadline.a file. +

+ +Edit this entry / +Log info +

+ +


+

3.22. ImportError: No module named string, on MS Windows.

+Most likely, your PYTHONPATH environment variable should be set to +something like: +

+set PYTHONPATH=c:\python;c:\python\lib;c:\python\scripts +

+(assuming Python was installed in c:\python) +

+ +Edit this entry / +Log info +

+ +


+

3.23. Core dump on SGI when using the gl module.

+There are conflicts between entry points in the termcap and curses +libraries and an entry point in the GL library. There's a hack of a +fix for the termcap library if it's needed for the GNU readline +library, but it doesn't work when you're using curses. Concluding, +you can't build a Python binary containing both the curses and gl +modules. +

+ +Edit this entry / +Log info +

+ +


+

3.24. "Initializer not a constant" while building DLL on MS-Windows

+Static type object initializers in extension modules may cause compiles to +fail with an error message like "initializer not a constant". +Fredrik Lundh <Fredrik.Lundh@image.combitech.se> explains: +

+This shows up when building DLL under MSVC. There's two ways to +address this: either compile the module as C++, or change your code to +something like: +

+

+  statichere PyTypeObject bstreamtype = {
+      PyObject_HEAD_INIT(NULL) /* must be set by init function */
+      0,
+      "bstream",
+      sizeof(bstreamobject),
+
+
+  ...
+
+
+  void
+  initbstream()
+  {
+      /* Patch object type */
+      bstreamtype.ob_type = &PyType_Type;
+      Py_InitModule("bstream", functions);
+      ...
+  }
+
+

+ +Edit this entry / +Log info + +/ Last changed on Sun May 25 14:58:05 1997 by +Aaron Watters +

+ +


+

3.25. Output directed to a pipe or file disappears on Linux.

+Some people have reported that when they run their script +interactively, it runs great, but that when they redirect it +to a pipe or file, no output appears. +

+

+    % python script.py
+    ...some output...
+    % python script.py >file
+    % cat file
+    % # no output
+    % python script.py | cat
+    % # no output
+    %
+
+This was a bug in Linux kernel. It is fixed and should not appear anymore. So most Linux users are not affected by this. +

+If redirection doesn't work on your Linux system, check what shell you are using. Shells like (t)csh doesn't support redirection. +

+ +Edit this entry / +Log info + +/ Last changed on Thu Jan 16 13:38:30 2003 by +Jens Kubieziel +

+ +


+

3.26. [deleted]

+[ancient libc/linux problem was here] +

+ +Edit this entry / +Log info + +/ Last changed on Mon Jun 3 16:48:08 2002 by +Erno Kuusela +

+ +


+

3.27. [deleted]

+[ancient linux + threads + tk problem was described here] +

+ +Edit this entry / +Log info + +/ Last changed on Mon Jun 3 16:49:08 2002 by +Erno Kuusela +

+ +


+

3.28. How can I test if Tkinter is working?

+Try the following: +

+

+  python
+  >>> import _tkinter
+  >>> import Tkinter
+  >>> Tkinter._test()
+
+This should pop up a window with two buttons, +one "Click me" and one "Quit". +

+If the first statement (import _tkinter) fails, your Python +installation probably has not been configured to support Tcl/Tk. +On Unix, if you have installed Tcl/Tk, you have to rebuild Python +after editing the Modules/Setup file to enable the _tkinter module +and the TKPATH environment variable. +

+It is also possible to get complaints about Tcl/Tk version +number mismatches or missing TCL_LIBRARY or TK_LIBRARY +environment variables. These have to do with Tcl/Tk installation +problems. +

+A common problem is to have installed versions of tcl.h and tk.h +that don't match the installed version of the Tcl/Tk libraries; +this usually results in linker errors or (when using dynamic +loading) complaints about missing symbols during loading +the shared library. +

+ +Edit this entry / +Log info + +/ Last changed on Thu Aug 28 17:01:46 1997 by +Guido van Rossum +

+ +


+

3.29. Is there a way to get the interactive mode of the python interpreter to perform function/variable name completion?

+(From a posting by Guido van Rossum) +

+On Unix, if you have enabled the readline module (i.e. if Emacs-style +command line editing and bash-style history works for you), you can +add this by importing the undocumented standard library module +"rlcompleter". When completing a simple identifier, it +completes keywords, built-ins and globals in __main__; when completing +NAME.NAME..., it evaluates (!) the expression up to the last dot and +completes its attributes. +

+This way, you can do "import string", type "string.", hit the +completion key twice, and see the list of names defined by the +string module. +

+Tip: to use the tab key as the completion key, call +

+

+    readline.parse_and_bind("tab: complete")
+
+You can put this in a ~/.pythonrc file, and set the PYTHONSTARTUP +environment variable to ~/.pythonrc. This will cause the completion to be enabled +whenever you run Python interactively. +

+Notes (see the docstring for rlcompleter.py for more information): +

+* The evaluation of the NAME.NAME... form may cause arbitrary +application defined code to be executed if an object with a +__getattr__ hook is found. Since it is the responsibility of the +application (or the user) to enable this feature, I consider this an +acceptable risk. More complicated expressions (e.g. function calls or +indexing operations) are not evaluated. +

+* GNU readline is also used by the built-in functions input() and +raw_input(), and thus these also benefit/suffer from the complete +features. Clearly an interactive application can benefit by +specifying its own completer function and using raw_input() for all +its input. +

+* When stdin is not a tty device, GNU readline is never +used, and this module (and the readline module) are silently inactive. +

+ +Edit this entry / +Log info + +/ Last changed on Fri Jun 12 09:55:24 1998 by +A.M. Kuchling +

+ +


+

3.30. Why is the Python interpreter not built as a shared library?

+(This is a Unix question; on Mac and Windows, it is a shared +library.) +

+It's just a nightmare to get this to work on all different platforms. +Shared library portability is a pain. And yes, I know about GNU libtool +-- but it requires me to use its conventions for filenames etc, and it +would require a complete and utter rewrite of all the makefile and +config tools I'm currently using. +

+In practice, few applications embed Python -- it's much more common to +have Python extensions, which already are shared libraries. Also, +serious embedders often want total control over which Python version +and configuration they use so they wouldn't want to use a standard +shared library anyway. So while the motivation of saving space +when lots of apps embed Python is nice in theory, I +doubt that it will save much in practice. (Hence the low priority I +give to making a shared library.) +

+For Linux systems, the simplest method of producing libpython1.5.so seems to +be (originally from the Minotaur project web page, +http://www.equi4.com/minotaur/minotaur.html): +

+

+  make distclean 
+  ./configure 
+  make OPT="-fpic -O2" 
+  mkdir .extract 
+  (cd .extract; ar xv ../libpython1.5.a) 
+  gcc -shared -o libpython1.5.so .extract/*.o 
+  rm -rf .extract
+
+In Python 2.3 this will be supported by the standard build routine +(at least on Linux) with --enable-shared. Note however that there +is little advantage, and it slows down Python because of the need +for PIC code and the extra cost at startup time to find the library. +

+ +Edit this entry / +Log info + +/ Last changed on Thu May 30 13:36:55 2002 by +GvR +

+ +


+

3.31. Build with GCC on Solaris 2.6 (SunOS 5.6) fails

+If you have upgraded Solaris 2.5 or 2.5.1 to Solaris 2.6, +but you have not upgraded +your GCC installation, the compile may fail, e.g. like this: +

+

+ In file included from /usr/include/sys/stream.h:26,
+                  from /usr/include/netinet/in.h:38,
+                  from /usr/include/netdb.h:96,
+                  from ./socketmodule.c:121:
+ /usr/include/sys/model.h:32: #error "No DATAMODEL_NATIVE specified"
+
+Solution: rebuild GCC for Solaris 2.6. +You might be able to simply re-run fixincludes, but +people have had mixed success with doing that. +

+ +Edit this entry / +Log info + +/ Last changed on Wed Oct 21 11:18:46 1998 by +GvR +

+ +


+

3.32. Running "make clean" seems to leave problematic files that cause subsequent builds to fail.

+Use "make clobber" instead. +

+Use "make clean" to reduce the size of the source/build directory +after you're happy with your build and installation. +If you have already tried to build python and you'd like to start +over, you should use "make clobber". It does a "make clean" and also +removes files such as the partially built Python library from a previous build. +

+ +Edit this entry / +Log info + +/ Last changed on Thu Jun 24 20:39:26 1999 by +TAB +

+ +


+

3.33. Submitting bug reports and patches

+To report a bug or submit a patch, please use the relevant service +from the Python project at SourceForge. +

+Bugs: http://sourceforge.net/tracker/?group_id=5470&atid=105470 +

+Patches: http://sourceforge.net/tracker/?group_id=5470&atid=305470 +

+If you have a SourceForge account, please log in before submitting your bug report; this will make it easier for us to contact you regarding your report in the event we have follow-up questions. It will also enable SourceForge to send you update information as we act on your bug. If you do not have a SourceForge account, please consider leaving your name and email address as part of the report. +

+ +Edit this entry / +Log info + +/ Last changed on Fri Apr 27 10:58:26 2001 by +Fred Drake +

+ +


+

3.34. I can't load shared libraries under Python 1.5.2, Solaris 7, and gcc 2.95.2

+When trying to load shared libraries, you may see errors like: +ImportError: ld.so.1: python: fatal: relocation error: file /usr/local/lib/python1.5/site-packages/Perp/util/du_SweepUtilc.so: +
+ symbol PyExc_RuntimeError: referenced symbol not found
+
+

+There is a problem with the configure script for Python 1.5.2 +under Solaris 7 with gcc 2.95 . configure should set the make variable +LINKFORSHARED=-Xlinker -export-dynamic +

+

+in Modules/Makefile, +

+Manually add this line to the Modules/Makefile. +This builds a Python executable that can load shared library extensions (xxx.so) . +

+ +Edit this entry / +Log info + +/ Last changed on Mon Feb 19 10:37:05 2001 by +GvR +

+ +


+

3.35. In the regression test, test___all__ fails for the profile module. What's wrong?

+If you have been using the profile module, and have properly calibrated a copy of the module as described in the documentation for the profiler: +

+http://www.python.org/doc/current/lib/profile-calibration.html +

+then it is possible that the regression test "test___all__" will fail if you run the regression test manually rather than using "make test" in the Python source directory. This will happen if you have set your PYTHONPATH environment variable to include the directory containing your calibrated profile module. You have probably calibrated the profiler using an older version of the profile module which does not define the __all__ value, added to the module as of Python 2.1. +

+The problem can be fixed by removing the old calibrated version of the profile module and using the latest version to do a fresh calibration. In general, you will need to re-calibrate for each version of Python anyway, since the performance characteristics can change in subtle ways that impact profiling. +

+ +Edit this entry / +Log info + +/ Last changed on Fri Apr 27 10:44:10 2001 by +Fred Drake +

+ +


+

3.36. relocations remain against allocatable but non-writable sections

+This linker error occurs on Solaris if you attempt to build an extension module which incorporates position-dependent (non-PIC) code. A common source of problems is that a static library (.a file), such as libreadline.a or libcrypto.a is linked with the extension module. The error specifically occurs when using gcc as the compiler, but /usr/ccs/bin/ld as the linker. +

+The following solutions and work-arounds are known: +

+1. Rebuild the libraries (libreadline, libcrypto) with -fPIC (-KPIC if using the system compiler). This is recommended; all object files in a shared library should be position-independent. +

+2. Statically link the extension module and its libraries into the Python interpreter, by editing Modules/Setup. +

+3. Use GNU ld instead of /usr/ccs/bin/ld; GNU ld will accept non-PIC code in shared libraries (and mark the section writable) +

+4. Pass -mimpure-text to GCC when linking the module. This will force gcc to not pass -z text to ld; in turn, ld will make all text sections writable. +

+Options 3 and 4 are not recommended, since the ability to share code across processes is lost. +

+ +Edit this entry / +Log info + +/ Last changed on Tue Jan 29 12:05:11 2002 by +Martin v. Lwis +

+ +


+

4. Programming in Python

+ +
+

4.1. Is there a source code level debugger with breakpoints, step, etc.?

+Yes. +

+Module pdb is a rudimentary but adequate console-mode debugger for Python. It is part of the standard Python library, and is documented in the Library Reference Manual. (You can also write your own debugger by using the code for pdb as an example.) +

+The IDLE interactive development environment, which is part of the standard Python distribution (normally available in Tools/idle), includes a graphical debugger. There is documentation for the IDLE debugger at http://www.python.org/idle/doc/idle2.html#Debugger +

+Pythonwin is a Python IDE that includes a GUI debugger based on bdb. The Pythonwin debugger colors breakpoints and has quite a few cool features (including debugging non-Pythonwin programs). A reference can be found at http://www.python.org/ftp/python/pythonwin/pwindex.html +More recent versions of PythonWin are available as a part of the ActivePython distribution (see http://www.activestate.com/Products/ActivePython/index.html). +

+Pydb is a version of the standard Python debugger pdb, modified for use with DDD (Data Display Debugger), a popular graphical debugger front end. Pydb can be found at http://packages.debian.org/unstable/devel/pydb.html +and DDD can be found at http://www.gnu.org/software/ddd/ +

+There are a number of commmercial Python IDEs that include graphical debuggers. They include: +

+

+ * Wing IDE (http://wingide.com/) 
+ * Komodo IDE (http://www.activestate.com/Products/Komodo/)
+
+

+ +Edit this entry / +Log info + +/ Last changed on Tue Jan 28 01:43:41 2003 by +Stephen Ferg +

+ +


+

4.2. Can I create an object class with some methods implemented in C and others in Python (e.g. through inheritance)? (Also phrased as: Can I use a built-in type as base class?)

+In Python 2.2, you can inherit from builtin classes such as int, list, dict, etc. +

+In previous versions of Python, you can easily create a Python class which serves as a wrapper around a built-in object, e.g. (for dictionaries): +

+

+        # A user-defined class behaving almost identical
+        # to a built-in dictionary.
+        class UserDict:
+                def __init__(self): self.data = {}
+                def __repr__(self): return repr(self.data)
+                def __cmp__(self, dict):
+                        if type(dict) == type(self.data):
+                                return cmp(self.data, dict)
+                        else:
+                                return cmp(self.data, dict.data)
+                def __len__(self): return len(self.data)
+                def __getitem__(self, key): return self.data[key]
+                def __setitem__(self, key, item): self.data[key] = item
+                def __delitem__(self, key): del self.data[key]
+                def keys(self): return self.data.keys()
+                def items(self): return self.data.items()
+                def values(self): return self.data.values()
+                def has_key(self, key): return self.data.has_key(key)
+
+A2. See Jim Fulton's ExtensionClass for an example of a mechanism +which allows you to have superclasses which you can inherit from in +Python -- that way you can have some methods from a C superclass (call +it a mixin) and some methods from either a Python superclass or your +subclass. ExtensionClass is distributed as a part of Zope (see +http://www.zope.org), but will be phased out with Zope 3, since +Zope 3 uses Python 2.2 or later which supports direct inheritance +from built-in types. Here's a link to the original paper about +ExtensionClass: +http://debian.acm.ndsu.nodak.edu/doc/python-extclass/ExtensionClass.html +

+A3. The Boost Python Library (BPL, http://www.boost.org/libs/python/doc/index.html) +provides a way of doing this from C++ (i.e. you can inherit from an +extension class written in C++ using the BPL). +

+ +Edit this entry / +Log info + +/ Last changed on Tue May 28 21:09:52 2002 by +GvR +

+ +


+

4.3. Is there a curses/termcap package for Python?

+The standard Python source distribution comes with a curses module in +the Modules/ subdirectory, though it's not compiled by default (note +that this is not available in the Windows distribution -- there is +no curses module for Windows). +

+In Python versions before 2.0 the module only supported plain curses; +you couldn't use ncurses features like colors with it (though it would +link with ncurses). +

+In Python 2.0, the curses module has been greatly extended, starting +from Oliver Andrich's enhanced version, to provide many additional +functions from ncurses and SYSV curses, such as colour, alternative +character set support, pads, and mouse support. This means the +module is no longer compatible with operating systems that only +have BSD curses, but there don't seem to be any currently +maintained OSes that fall into this category. +

+ +Edit this entry / +Log info + +/ Last changed on Sun Jun 23 20:24:06 2002 by +Tim Peters +

+ +


+

4.4. Is there an equivalent to C's onexit() in Python?

+For Python 2.0: The new atexit module provides a register function that +is similar to C's onexit. See the Library Reference for details. For +2.0 you should not assign to sys.exitfunc! +

+For Python 1.5.2: You need to import sys and assign a function to +sys.exitfunc, it will be called when your program exits, is +killed by an unhandled exception, or (on UNIX) receives a +SIGHUP or SIGTERM signal. +

+ +Edit this entry / +Log info + +/ Last changed on Thu Dec 28 12:14:55 2000 by +Bjorn Pettersen +

+ +


+

4.5. [deleted]

+[python used to lack nested scopes, it was explained here] +

+ +Edit this entry / +Log info + +/ Last changed on Thu Mar 21 05:18:22 2002 by +Erno Kuusela +

+ +


+

4.6. How do I iterate over a sequence in reverse order?

+If it is a list, the fastest solution is +

+

+        list.reverse()
+        try:
+                for x in list:
+                        "do something with x"
+        finally:
+                list.reverse()
+
+This has the disadvantage that while you are in the loop, the list +is temporarily reversed. If you don't like this, you can make a copy. +This appears expensive but is actually faster than other solutions: +

+

+        rev = list[:]
+        rev.reverse()
+        for x in rev:
+                <do something with x>
+
+If it's not a list, a more general but slower solution is: +

+

+        for i in range(len(sequence)-1, -1, -1):
+                x = sequence[i]
+                <do something with x>
+
+A more elegant solution, is to define a class which acts as a sequence +and yields the elements in reverse order (solution due to Steve +Majewski): +

+

+        class Rev:
+                def __init__(self, seq):
+                        self.forw = seq
+                def __len__(self):
+                        return len(self.forw)
+                def __getitem__(self, i):
+                        return self.forw[-(i + 1)]
+
+You can now simply write: +

+

+        for x in Rev(list):
+                <do something with x>
+
+Unfortunately, this solution is slowest of all, due to the method +call overhead... +

+ +Edit this entry / +Log info + +/ Last changed on Sun May 25 21:10:50 1997 by +GvR +

+ +


+

4.7. My program is too slow. How do I speed it up?

+That's a tough one, in general. There are many tricks to speed up +Python code; I would consider rewriting parts in C only as a last +resort. One thing to notice is that function and (especially) method +calls are rather expensive; if you have designed a purely OO interface +with lots of tiny functions that don't do much more than get or set an +instance variable or call another method, you may consider using a +more direct way, e.g. directly accessing instance variables. Also see +the standard module "profile" (described in the Library Reference +manual) which makes it possible to find out where +your program is spending most of its time (if you have some patience +-- the profiling itself can slow your program down by an order of +magnitude). +

+Remember that many standard optimization heuristics you +may know from other programming experience may well apply +to Python. For example it may be faster to send output to output +devices using larger writes rather than smaller ones in order to +avoid the overhead of kernel system calls. Thus CGI scripts +that write all output in "one shot" may be notably faster than +those that write lots of small pieces of output. +

+Also, be sure to use "aggregate" operations where appropriate. +For example the "slicing" feature allows programs to chop up +lists and other sequence objects in a single tick of the interpreter +mainloop using highly optimized C implementations. Thus to +get the same effect as +

+

+  L2 = []
+  for i in range[3]:
+       L2.append(L1[i])
+
+it is much shorter and far faster to use +

+

+  L2 = list(L1[:3]) # "list" is redundant if L1 is a list.
+
+Note that the map() function, particularly used with +builtin methods or builtin functions can be a convenient +accelerator. For example to pair the elements of two +lists together: +

+

+  >>> map(None, [1,2,3], [4,5,6])
+  [(1, 4), (2, 5), (3, 6)]
+
+or to compute a number of sines: +

+

+  >>> map( math.sin, (1,2,3,4))
+  [0.841470984808, 0.909297426826, 0.14112000806,   -0.756802495308]
+
+The map operation completes very quickly in such cases. +

+Other examples of aggregate operations include the join and split +methods of string objects. For example if s1..s7 are large (10K+) strings then +"".join([s1,s2,s3,s4,s5,s6,s7]) may be far faster than +the more obvious s1+s2+s3+s4+s5+s6+s7, since the "summation" +will compute many subexpressions, whereas join does all +copying in one pass. For manipulating strings also consider the +regular expression libraries and the "substitution" operations +String % tuple and String % dictionary. Also be sure to use +the list.sort builtin method to do sorting, and see FAQ's 4.51 +and 4.59 for examples of moderately advanced usage -- list.sort beats +other techniques for sorting in all but the most extreme +circumstances. +

+There are many other aggregate operations +available in the standard libraries and in contributed libraries +and extensions. +

+Another common trick is to "push loops into functions or methods." +For example suppose you have a program that runs slowly and you +use the profiler (profile.run) to determine that a Python function ff +is being called lots of times. If you notice that ff +

+

+   def ff(x):
+       ...do something with x computing result...
+       return result
+
+tends to be called in loops like (A) +

+

+   list = map(ff, oldlist)
+
+or (B) +

+

+   for x in sequence:
+       value = ff(x)
+       ...do something with value...
+
+then you can often eliminate function call overhead by rewriting +ff to +

+

+   def ffseq(seq):
+       resultseq = []
+       for x in seq:
+           ...do something with x computing result...
+           resultseq.append(result)
+       return resultseq
+
+and rewrite (A) to +

+

+    list = ffseq(oldlist)
+
+and (B) to +

+

+    for value in ffseq(sequence):
+        ...do something with value...
+
+Other single calls ff(x) translate to ffseq([x])[0] with little +penalty. Of course this technique is not always appropriate +and there are other variants, which you can figure out. +

+You can gain some performance by explicitly storing the results of +a function or method lookup into a local variable. A loop like +

+

+    for key in token:
+        dict[key] = dict.get(key, 0) + 1
+
+resolves dict.get every iteration. If the method isn't going to +change, a faster implementation is +

+

+    dict_get = dict.get  # look up the method once
+    for key in token:
+        dict[key] = dict_get(key, 0) + 1
+
+Default arguments can be used to determine values once, at +compile time instead of at run time. This can only be done for +functions or objects which will not be changed during program +execution, such as replacing +

+

+    def degree_sin(deg):
+        return math.sin(deg * math.pi / 180.0)
+
+with +

+

+    def degree_sin(deg, factor = math.pi/180.0, sin = math.sin):
+        return sin(deg * factor)
+
+Because this trick uses default arguments for terms which should +not be changed, it should only be used when you are not concerned +with presenting a possibly confusing API to your users. +

+

+For an anecdote related to optimization, see +

+

+	http://www.python.org/doc/essays/list2str.html
+
+

+ +Edit this entry / +Log info + +/ Last changed on Mon Jun 3 01:03:54 2002 by +Neal Norwitz +

+ +


+

4.8. When I have imported a module, then edit it, and import it again (into the same Python process), the changes don't seem to take place. What is going on?

+For reasons of efficiency as well as consistency, Python only reads +the module file on the first time a module is imported. (Otherwise a +program consisting of many modules, each of which imports the same +basic module, would read the basic module over and over again.) To +force rereading of a changed module, do this: +

+

+        import modname
+        reload(modname)
+
+Warning: this technique is not 100% fool-proof. In particular, +modules containing statements like +

+

+        from modname import some_objects
+
+will continue to work with the old version of the imported objects. +

+ +Edit this entry / +Log info +

+ +


+

4.9. How do I find the current module name?

+A module can find out its own module name by looking at the +(predefined) global variable __name__. If this has the value +'__main__' you are running as a script. +

+ +Edit this entry / +Log info +

+ +


+

4.10. I have a module in which I want to execute some extra code when it is run as a script. How do I find out whether I am running as a script?

+See the previous question. E.g. if you put the following on the +last line of your module, main() is called only when your module is +running as a script: +

+

+        if __name__ == '__main__': main()
+
+

+ +Edit this entry / +Log info +

+ +


+

4.11. I try to run a program from the Demo directory but it fails with ImportError: No module named ...; what gives?

+This is probably an optional module (written in C!) which hasn't +been configured on your system. This especially happens with modules +like "Tkinter", "stdwin", "gl", "Xt" or "Xm". For Tkinter, STDWIN and +many other modules, see Modules/Setup.in for info on how to add these +modules to your Python, if it is possible at all. Sometimes you will +have to ftp and build another package first (e.g. Tcl and Tk for Tkinter). +Sometimes the module only works on specific platforms (e.g. gl only works +on SGI machines). +

+NOTE: if the complaint is about "Tkinter" (upper case T) and you have +already configured module "tkinter" (lower case t), the solution is +not to rename tkinter to Tkinter or vice versa. There is probably +something wrong with your module search path. Check out the value of +sys.path. +

+For X-related modules (Xt and Xm) you will have to do more work: they +are currently not part of the standard Python distribution. You will +have to ftp the Extensions tar file, i.e. +ftp://ftp.python.org/pub/python/src/X-extension.tar.gz and follow +the instructions there. +

+ +Edit this entry / +Log info + +/ Last changed on Wed Feb 12 21:31:08 2003 by +Jens Kubieziel +

+ +


+

4.12. [deleted]

+[stdwin (long dead windowing library) entry deleted] +

+ +Edit this entry / +Log info + +/ Last changed on Thu Mar 21 08:30:13 2002 by +Erno Kuusela +

+ +


+

4.13. What GUI toolkits exist for Python?

+Depending on what platform(s) you are aiming at, there are several. +

+Currently supported solutions: +

+Cross-platform: +

+Tk: +

+There's a neat object-oriented interface to the Tcl/Tk widget set, +called Tkinter. It is part of the standard Python distribution and +well-supported -- all you need to do is build and install Tcl/Tk and +enable the _tkinter module and the TKPATH definition in Modules/Setup +when building Python. This is probably the easiest to install and +use, and the most complete widget set. It is also very likely that in +the future the standard Python GUI API will be based on or at least +look very much like the Tkinter interface. For more info about Tk, +including pointers to the source, see the Tcl/Tk home page at +http://www.scriptics.com. Tcl/Tk is now fully +portable to the Mac and Windows platforms (NT and 95 only); you need +Python 1.4beta3 or later and Tk 4.1patch1 or later. +

+wxWindows: +

+There's an interface to wxWindows called wxPython. wxWindows is a +portable GUI class library written in C++. It supports GTK, Motif, +MS-Windows and Mac as targets. Ports to other platforms are being +contemplated or have already had some work done on them. wxWindows +preserves the look and feel of the underlying graphics toolkit, and +there is quite a rich widget set and collection of GDI classes. +See the wxWindows page at http://www.wxwindows.org/ for more details. +wxPython is a python extension module that wraps many of the wxWindows +C++ classes, and is quickly gaining popularity amongst Python +developers. You can get wxPython as part of the source or CVS +distribution of wxWindows, or directly from its home page at +http://alldunn.com/wxPython/. +

+Gtk+: +

+PyGtk bindings for the Gtk+ Toolkit by James Henstridge exist; see ftp://ftp.daa.com.au/pub/james/python/. Note that there are two incompatible bindings. If you are using Gtk+ 1.2.x you should get the 0.6.x PyGtk bindings from +

+

+    ftp://ftp.gtk.org/pub/python/v1.2
+
+If you plan to use Gtk+ 2.0 with Python (highly recommended if you are just starting with Gtk), get the most recent distribution from +

+

+    ftp://ftp.gtk.org/pub/python/v2.0
+
+If you are adventurous, you can also check out the source from the Gnome CVS repository. Set your CVS directory to :pserver:anonymous@anoncvs.gnome.org:/cvs/gnome and check the gnome-python module out from the repository. +

+Other: +

+There are also bindings available for the Qt toolkit (PyQt), and for KDE (PyKDE); see http://www.thekompany.com/projects/pykde/. +

+For OpenGL bindings, see http://starship.python.net/~da/PyOpenGL. +

+Platform specific: +

+The Mac port has a rich and ever-growing set of modules that support +the native Mac toolbox calls. See the documentation that comes with +the Mac port. See ftp://ftp.python.org/pub/python/mac. Support +by Jack Jansen jack@cwi.nl. +

+Pythonwin by Mark Hammond (MHammond@skippinet.com.au) +includes an interface to the Microsoft Foundation +Classes and a Python programming environment using it that's written +mostly in Python. See http://www.python.org/windows/. +

+There's an object-oriented GUI based on the Microsoft Foundation +Classes model called WPY, supported by Jim Ahlstrom jim@interet.com. +Programs written in WPY run unchanged and with native look and feel on +Windows NT/95, Windows 3.1 (using win32s), and on Unix (using Tk). +Source and binaries for Windows and Linux are available in +ftp://ftp.python.org/pub/python/wpy/. +

+Obsolete or minority solutions: +

+There's an interface to X11, including the Athena and Motif widget +sets (and a few individual widgets, like Mosaic's HTML widget and +SGI's GL widget) available from +ftp://ftp.python.org/pub/python/src/X-extension.tar.gz. +Support by Sjoerd Mullender sjoerd@cwi.nl. +

+On top of the X11 interface there's the vpApp +toolkit by Per Spilling, now also maintained by Sjoerd Mullender +sjoerd@cwi.nl. See ftp://ftp.cwi.nl/pub/sjoerd/vpApp.tar.gz. +

+For SGI IRIX only, there are unsupported interfaces to the complete +GL (Graphics Library -- low level but very good 3D capabilities) as +well as to FORMS (a buttons-and-sliders-etc package built on top of GL +by Mark Overmars -- ftp'able from +ftp://ftp.cs.ruu.nl/pub/SGI/FORMS/). This is probably also +becoming obsolete, as OpenGL takes over (see above). +

+There's an interface to STDWIN, a platform-independent low-level +windowing interface for Mac and X11. This is totally unsupported and +rapidly becoming obsolete. The STDWIN sources are at +ftp://ftp.cwi.nl/pub/stdwin/. +

+There is an interface to WAFE, a Tcl interface to the X11 +Motif and Athena widget sets. WAFE is at +http://www.wu-wien.ac.at/wafe/wafe.html. +

+ +Edit this entry / +Log info + +/ Last changed on Mon May 13 21:40:39 2002 by +Skip Montanaro +

+ +


+

4.14. Are there any interfaces to database packages in Python?

+Yes! See the Database Topic Guide at +http://www.python.org/topics/database/ for details. +

+ +Edit this entry / +Log info + +/ Last changed on Tue Jan 4 20:12:19 2000 by +Barney Warplug +

+ +


+

4.15. Is it possible to write obfuscated one-liners in Python?

+Yes. See the following three examples, due to Ulf Bartelt: +

+

+        # Primes < 1000
+        print filter(None,map(lambda y:y*reduce(lambda x,y:x*y!=0,
+        map(lambda x,y=y:y%x,range(2,int(pow(y,0.5)+1))),1),range(2,1000)))
+
+
+        # First 10 Fibonacci numbers
+        print map(lambda x,f=lambda x,f:(x<=1) or (f(x-1,f)+f(x-2,f)): f(x,f),
+        range(10))
+
+
+        # Mandelbrot set
+        print (lambda Ru,Ro,Iu,Io,IM,Sx,Sy:reduce(lambda x,y:x+y,map(lambda y,
+        Iu=Iu,Io=Io,Ru=Ru,Ro=Ro,Sy=Sy,L=lambda yc,Iu=Iu,Io=Io,Ru=Ru,Ro=Ro,i=IM,
+        Sx=Sx,Sy=Sy:reduce(lambda x,y:x+y,map(lambda x,xc=Ru,yc=yc,Ru=Ru,Ro=Ro,
+        i=i,Sx=Sx,F=lambda xc,yc,x,y,k,f=lambda xc,yc,x,y,k,f:(k<=0)or (x*x+y*y
+        >=4.0) or 1+f(xc,yc,x*x-y*y+xc,2.0*x*y+yc,k-1,f):f(xc,yc,x,y,k,f):chr(
+        64+F(Ru+x*(Ro-Ru)/Sx,yc,0,0,i)),range(Sx))):L(Iu+y*(Io-Iu)/Sy),range(Sy
+        ))))(-2.1, 0.7, -1.2, 1.2, 30, 80, 24)
+        #    \___ ___/  \___ ___/  |   |   |__ lines on screen
+        #        V          V      |   |______ columns on screen
+        #        |          |      |__________ maximum of "iterations"
+        #        |          |_________________ range on y axis
+        #        |____________________________ range on x axis
+
+Don't try this at home, kids! +

+ +Edit this entry / +Log info + +/ Last changed on Wed May 21 15:48:33 1997 by +GvR +

+ +


+

4.16. Is there an equivalent of C's "?:" ternary operator?

+Not directly. In many cases you can mimic a?b:c with "a and b or +c", but there's a flaw: if b is zero (or empty, or None -- anything +that tests false) then c will be selected instead. In many cases you +can prove by looking at the code that this can't happen (e.g. because +b is a constant or has a type that can never be false), but in general +this can be a problem. +

+Tim Peters (who wishes it was Steve Majewski) suggested the following +solution: (a and [b] or [c])[0]. Because [b] is a singleton list it +is never false, so the wrong path is never taken; then applying [0] to +the whole thing gets the b or c that you really wanted. Ugly, but it +gets you there in the rare cases where it is really inconvenient to +rewrite your code using 'if'. +

+As a last resort it is possible to implement the "?:" operator as a function: +

+

+    def q(cond,on_true,on_false):
+        from inspect import isfunction
+
+
+        if cond:
+            if not isfunction(on_true): return on_true
+            else: return apply(on_true)
+        else:
+            if not isfunction(on_false): return on_false 
+            else: return apply(on_false)
+
+In most cases you'll pass b and c directly: q(a,b,c). To avoid evaluating b +or c when they shouldn't be, encapsulate them +within a lambda function, e.g.: q(a,lambda: b, lambda: c). +

+

+

+It has been asked why Python has no if-then-else expression, +since most language have one; it is a frequently requested feature. +

+There are several possible answers: just as many languages do +just fine without one; it can easily lead to less readable code; +no sufficiently "Pythonic" syntax has been discovered; a search +of the standard library found remarkably few places where using an +if-then-else expression would make the code more understandable. +

+Nevertheless, in an effort to decide once and for all whether +an if-then-else expression should be added to the language, +PEP 308 (http://www.python.org/peps/pep-0308.html) has been +put forward, proposing a specific syntax. The community can +now vote on this issue. +

+ +Edit this entry / +Log info + +/ Last changed on Fri Feb 7 19:41:13 2003 by +David Goodger +

+ +


+

4.17. My class defines __del__ but it is not called when I delete the object.

+There are several possible reasons for this. +

+The del statement does not necessarily call __del__ -- it simply +decrements the object's reference count, and if this reaches zero +__del__ is called. +

+If your data structures contain circular links (e.g. a tree where +each child has a parent pointer and each parent has a list of +children) the reference counts will never go back to zero. You'll +have to define an explicit close() method which removes those +pointers. Please don't ever call __del__ directly -- __del__ should +call close() and close() should make sure that it can be called more +than once for the same object. +

+If the object has ever been a local variable (or argument, which is +really the same thing) to a function that caught an expression in an +except clause, chances are that a reference to the object still exists +in that function's stack frame as contained in the stack trace. +Normally, deleting (better: assigning None to) sys.exc_traceback will +take care of this. If a stack was printed for an unhandled +exception in an interactive interpreter, delete sys.last_traceback +instead. +

+There is code that deletes all objects when the interpreter exits, +but it is not called if your Python has been configured to support +threads (because other threads may still be active). You can define +your own cleanup function using sys.exitfunc (see question 4.4). +

+Finally, if your __del__ method raises an exception, a warning message is printed to sys.stderr. +

+

+Starting with Python 2.0, a garbage collector periodically reclaims the space used by most cycles with no external references. (See the "gc" module documentation for details.) There are, however, pathological cases where it can be expected to fail. Moreover, the garbage collector runs some time after the last reference to your data structure vanishes, so your __del__ method may be called at an inconvenient and random time. This is inconvenient if you're trying to reproduce a problem. Worse, the order in which object's __del__ methods are executed is arbitrary. +

+Another way to avoid cyclical references is to use the "weakref" module, which allows you to point to objects without incrementing their reference count. Tree data structures, for instance, should use weak references for their parent and sibling pointers (if they need them!). +

+Question 6.14 is intended to explain the new garbage collection algorithm. +

+ +Edit this entry / +Log info + +/ Last changed on Mon Jun 10 15:27:28 2002 by +Matthias Urlichs +

+ +


+

4.18. How do I change the shell environment for programs called using os.popen() or os.system()? Changing os.environ doesn't work.

+You must be using either a version of python before 1.4, or on a +(rare) system that doesn't have the putenv() library function. +

+Before Python 1.4, modifying the environment passed to subshells was +left out of the interpreter because there seemed to be no +well-established portable way to do it (in particular, some systems, +have putenv(), others have setenv(), and some have none at all). As +of Python 1.4, almost all Unix systems do have putenv(), and so does +the Win32 API, and thus the os module was modified so that changes to +os.environ are trapped and the corresponding putenv() call is made. +

+ +Edit this entry / +Log info +

+ +


+

4.19. What is a class?

+A class is the particular object type created by executing +a class statement. Class objects are used as templates, to create +instance objects, which embody both the data structure +(attributes) and program routines (methods) specific to a datatype. +

+A class can be based on one or more other classes, called its base +class(es). It then inherits the attributes and methods of its base classes. This allows an object model to be successively refined +by inheritance. +

+The term "classic class" is used to refer to the original +class implementation in Python. One problem with classic +classes is their inability to use the built-in data types +(such as list and dictionary) as base classes. Starting +with Python 2.2 an attempt is in progress to unify user-defined +classes and built-in types. It is now possible to declare classes +that inherit from built-in types. +

+ +Edit this entry / +Log info + +/ Last changed on Mon May 27 01:31:21 2002 by +Steve Holden +

+ +


+

4.20. What is a method?

+A method is a function that you normally call as +x.name(arguments...) for some object x. The term is used for methods +of classes and class instances as well as for methods of built-in +objects. (The latter have a completely different implementation and +only share the way their calls look in Python code.) Methods of +classes (and class instances) are defined as functions inside the +class definition. +

+ +Edit this entry / +Log info +

+ +


+

4.21. What is self?

+Self is merely a conventional name for the first argument of a +method -- i.e. a function defined inside a class definition. A method +defined as meth(self, a, b, c) should be called as x.meth(a, b, c) for +some instance x of the class in which the definition occurs; +the called method will think it is called as meth(x, a, b, c). +

+ +Edit this entry / +Log info +

+ +


+

4.22. What is an unbound method?

+An unbound method is a method defined in a class that is not yet +bound to an instance. You get an unbound method if you ask for a +class attribute that happens to be a function. You get a bound method +if you ask for an instance attribute. A bound method knows which +instance it belongs to and calling it supplies the instance automatically; +an unbound method only knows which class it wants for its first +argument (a derived class is also OK). Calling an unbound method +doesn't "magically" derive the first argument from the context -- you +have to provide it explicitly. +

+Trivia note regarding bound methods: each reference to a bound +method of a particular object creates a bound method object. If you +have two such references (a = inst.meth; b = inst.meth), they will +compare equal (a == b) but are not the same (a is not b). +

+ +Edit this entry / +Log info + +/ Last changed on Wed May 6 18:07:25 1998 by +Clarence Gardner +

+ +


+

4.23. How do I call a method defined in a base class from a derived class that overrides it?

+If your class definition starts with "class Derived(Base): ..." +then you can call method meth defined in Base (or one of Base's base +classes) as Base.meth(self, arguments...). Here, Base.meth is an +unbound method (see previous question). +

+ +Edit this entry / +Log info +

+ +


+

4.24. How do I call a method from a base class without using the name of the base class?

+DON'T DO THIS. REALLY. I MEAN IT. It appears that you could call +self.__class__.__bases__[0].meth(self, arguments...) but this fails when +a doubly-derived method is derived from your class: for its instances, +self.__class__.__bases__[0] is your class, not its base class -- so +(assuming you are doing this from within Derived.meth) you would start +a recursive call. +

+Often when you want to do this you are forgetting that classes +are first class in Python. You can "point to" the class you want +to delegate an operation to either at the instance or at the +subclass level. For example if you want to use a "glorp" +operation of a superclass you can point to the right superclass +to use. +

+

+  class subclass(superclass1, superclass2, superclass3):
+      delegate_glorp = superclass2
+      ...
+      def glorp(self, arg1, arg2):
+            ... subclass specific stuff ...
+            self.delegate_glorp.glorp(self, arg1, arg2)
+       ...
+
+
+  class subsubclass(subclass):
+       delegate_glorp = superclass3
+       ...
+
+Note, however that setting delegate_glorp to subclass in +subsubclass would cause an infinite recursion on subclass.delegate_glorp. Careful! Maybe you are getting too fancy for your own good. Consider simplifying the design (?). +

+ +Edit this entry / +Log info + +/ Last changed on Mon Jul 28 13:58:22 1997 by +aaron watters +

+ +


+

4.25. How can I organize my code to make it easier to change the base class?

+You could define an alias for the base class, assign the real base +class to it before your class definition, and use the alias throughout +your class. Then all you have to change is the value assigned to the +alias. Incidentally, this trick is also handy if you want to decide +dynamically (e.g. depending on availability of resources) which base +class to use. Example: +

+

+        BaseAlias = <real base class>
+        class Derived(BaseAlias):
+                def meth(self):
+                        BaseAlias.meth(self)
+                        ...
+
+

+ +Edit this entry / +Log info + +/ Last changed on Wed May 21 15:49:57 1997 by +GvR +

+ +


+

4.26. How can I find the methods or attributes of an object?

+This depends on the object type. +

+For an instance x of a user-defined class, instance attributes are +found in the dictionary x.__dict__, and methods and attributes defined +by its class are found in x.__class__.__bases__[i].__dict__ (for i in +range(len(x.__class__.__bases__))). You'll have to walk the tree of +base classes to find all class methods and attributes. +

+Many, but not all built-in types define a list of their method names +in x.__methods__, and if they have data attributes, their names may be +found in x.__members__. However this is only a convention. +

+For more information, read the source of the standard (but +undocumented) module newdir. +

+ +Edit this entry / +Log info +

+ +


+

4.27. I can't seem to use os.read() on a pipe created with os.popen().

+os.read() is a low-level function which takes a file descriptor (a +small integer). os.popen() creates a high-level file object -- the +same type used for sys.std{in,out,err} and returned by the builtin +open() function. Thus, to read n bytes from a pipe p created with +os.popen(), you need to use p.read(n). +

+ +Edit this entry / +Log info +

+ +


+

4.28. How can I create a stand-alone binary from a Python script?

+Even though there are Python compilers being developed, +you probably don't need a real compiler, if all you want +is a stand-alone program. There are three solutions to that. +

+One is to use the freeze tool, which is included in the Python +source tree as Tools/freeze. It converts Python byte +code to C arrays. Using a C compiler, you can embed all +your modules into a new program, which is then linked +with the standard Python modules. +

+It works by scanning your source recursively for import statements +(in both forms) and looking for the modules in the standard Python path +as well as in the source directory (for built-in modules). It then +1 the modules written in Python to C code (array initializers +that can be turned into code objects using the marshal module) and +creates a custom-made config file that only contains those built-in +modules which are actually used in the program. It then compiles the +generated C code and links it with the rest of the Python interpreter +to form a self-contained binary which acts exactly like your script. +

+(Hint: the freeze program only works if your script's filename ends in +".py".) +

+There are several utilities which may be helpful. The first is Gordon McMillan's installer at +

+

+    http://www.mcmillan-inc.com/install1.html
+
+which works on Windows, Linux and at least some forms of Unix. +

+Another is Thomas Heller's py2exe (Windows only) at +

+

+    http://starship.python.net/crew/theller/py2exe/
+
+A third is Christian Tismer's SQFREEZE +(http://starship.python.net/crew/pirx/) which appends the byte code +to a specially-prepared Python interpreter, which +will find the byte code in executable. +

+A fourth is Fredrik Lundh's Squeeze +(http://www.pythonware.com/products/python/squeeze/). +

+ +Edit this entry / +Log info + +/ Last changed on Wed Jun 19 14:01:30 2002 by +Gordon McMillan +

+ +


+

4.29. What WWW tools are there for Python?

+See the chapters titled "Internet Protocols and Support" and +"Internet Data Handling" in the Library Reference +Manual. Python is full of good things which will help you build server-side and client-side web systems. +

+A summary of available frameworks is maintained by Paul Boddie at +

+

+    http://thor.prohosting.com/~pboddie/Python/web_modules.html
+
+Cameron Laird maintains a useful set of pages about Python web technologies at +

+

+   http://starbase.neosoft.com/~claird/comp.lang.python/web_python.html/
+
+There was a web browser written in Python, called Grail -- +see http://sourceforge.net/project/grail/. This project has been terminated; http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/grail/grail/README gives more details. +

+ +Edit this entry / +Log info + +/ Last changed on Mon Nov 11 22:48:25 2002 by +GvR +

+ +


+

4.30. How do I run a subprocess with pipes connected to both input and output?

+Use the standard popen2 module. For example: +

+

+	import popen2
+	fromchild, tochild = popen2.popen2("command")
+	tochild.write("input\n")
+	tochild.flush()
+	output = fromchild.readline()
+
+Warning: in general, it is unwise to +do this, because you can easily cause a deadlock where your +process is blocked waiting for output from the child, while the child +is blocked waiting for input from you. This can be caused +because the parent expects the child to output more text than it does, +or it can be caused by data being stuck in stdio buffers due to lack +of flushing. The Python parent can of course explicitly flush the data +it sends to the child before it reads any output, but if the child is +a naive C program it can easily have been written to never explicitly +flush its output, even if it is interactive, since flushing is +normally automatic. +

+Note that a deadlock is also possible if you use popen3 to read +stdout and stderr. If one of the two is too large for the internal +buffer (increasing the buffersize does not help) and you read() +the other one first, there is a deadlock, too. +

+Note on a bug in popen2: unless your program calls wait() +or waitpid(), finished child processes are never removed, +and eventually calls to popen2 will fail because of a limit on +the number of child processes. Calling os.waitpid with the +os.WNOHANG option can prevent this; a good place to insert such +a call would be before calling popen2 again. +

+Another way to produce a deadlock: Call a wait() and there is +still more output from the program than what fits into the +internal buffers. +

+In many cases, all you really need is to run some data through a +command and get the result back. Unless the data is infinite in size, +the easiest (and often the most efficient!) way to do this is to write +it to a temporary file and run the command with that temporary file as +input. The standard module tempfile exports a function mktemp() which +generates unique temporary file names. +

+

+ import tempfile
+ import os
+ class Popen3:
+    """
+    This is a deadlock-save version of popen, that returns
+    an object with errorlevel, out (a string) and err (a string).
+    (capturestderr may not work under windows.)
+    Example: print Popen3('grep spam','\n\nhere spam\n\n').out
+    """
+    def __init__(self,command,input=None,capturestderr=None):
+        outfile=tempfile.mktemp()
+        command="( %s ) > %s" % (command,outfile)
+        if input:
+            infile=tempfile.mktemp()
+            open(infile,"w").write(input)
+            command=command+" <"+infile
+        if capturestderr:
+            errfile=tempfile.mktemp()
+            command=command+" 2>"+errfile
+        self.errorlevel=os.system(command) >> 8
+        self.out=open(outfile,"r").read()
+        os.remove(outfile)
+        if input:
+            os.remove(infile)
+        if capturestderr:
+            self.err=open(errfile,"r").read()
+            os.remove(errfile)
+
+Note that many interactive programs (e.g. vi) don't work well with +pipes substituted for standard input and output. You will have to use +pseudo ttys ("ptys") instead of pipes. There is some undocumented +code to use these in the library module pty.py -- I'm afraid you're on +your own here. +

+A different answer is a Python interface to Don Libes' "expect" +library. A Python extension that interfaces to expect is called "expy" +and available from +http://expectpy.sourceforge.net/. +

+A pure Python solution that works like expect is pexpect of Noah Spurrier. +A beta version is available from +http://pexpect.sourceforge.net/ +

+ +Edit this entry / +Log info + +/ Last changed on Tue Sep 3 16:31:31 2002 by +Tobias Polzin +

+ +


+

4.31. How do I call a function if I have the arguments in a tuple?

+Use the built-in function apply(). For instance, +

+

+    func(1, 2, 3)
+
+is equivalent to +

+

+    args = (1, 2, 3)
+    apply(func, args)
+
+Note that func(args) is not the same -- it calls func() with exactly +one argument, the tuple args, instead of three arguments, the integers +1, 2 and 3. +

+In Python 2.0, you can also use extended call syntax: +

+f(*args) is equivalent to apply(f, args) +

+ +Edit this entry / +Log info + +/ Last changed on Tue Jan 2 03:42:50 2001 by +Moshe Zadka +

+ +


+

4.32. How do I enable font-lock-mode for Python in Emacs?

+If you are using XEmacs 19.14 or later, any XEmacs 20, FSF Emacs 19.34 +or any Emacs 20, font-lock should work automatically for you if you +are using the latest python-mode.el. +

+If you are using an older version of XEmacs or Emacs you will need +to put this in your .emacs file: +

+

+        (defun my-python-mode-hook ()
+          (setq font-lock-keywords python-font-lock-keywords)
+          (font-lock-mode 1))
+        (add-hook 'python-mode-hook 'my-python-mode-hook)
+
+

+ +Edit this entry / +Log info + +/ Last changed on Mon Apr 6 16:18:46 1998 by +Barry Warsaw +

+ +


+

4.33. Is there a scanf() or sscanf() equivalent?

+Not as such. +

+For simple input parsing, the easiest approach is usually to split +the line into whitespace-delimited words using string.split(), and to +convert decimal strings to numeric values using int(), +long() or float(). (Python's int() is 32-bit and its +long() is arbitrary precision.) string.split supports an optional +"sep" parameter which is useful if the line uses something other +than whitespace as a delimiter. +

+For more complicated input parsing, regular expressions (see module re) +are better suited and more powerful than C's sscanf(). +

+There's a contributed module that emulates sscanf(), by Steve Clift; +see contrib/Misc/sscanfmodule.c of the ftp site: +

+

+    http://www.python.org/ftp/python/contrib-09-Dec-1999/Misc/
+
+

+ +Edit this entry / +Log info + +/ Last changed on Mon Jun 3 01:07:51 2002 by +Neal Norwitz +

+ +


+

4.34. Can I have Tk events handled while waiting for I/O?

+Yes, and you don't even need threads! But you'll have to +restructure your I/O code a bit. Tk has the equivalent of Xt's +XtAddInput() call, which allows you to register a callback function +which will be called from the Tk mainloop when I/O is possible on a +file descriptor. Here's what you need: +

+

+        from Tkinter import tkinter
+        tkinter.createfilehandler(file, mask, callback)
+
+The file may be a Python file or socket object (actually, anything +with a fileno() method), or an integer file descriptor. The mask is +one of the constants tkinter.READABLE or tkinter.WRITABLE. The +callback is called as follows: +

+

+        callback(file, mask)
+
+You must unregister the callback when you're done, using +

+

+        tkinter.deletefilehandler(file)
+
+Note: since you don't know *how many bytes* are available for reading, +you can't use the Python file object's read or readline methods, since +these will insist on reading a predefined number of bytes. For +sockets, the recv() or recvfrom() methods will work fine; for other +files, use os.read(file.fileno(), maxbytecount). +

+ +Edit this entry / +Log info +

+ +


+

4.35. How do I write a function with output parameters (call by reference)?

+[Mark Lutz] The thing to remember is that arguments are passed by +assignment in Python. Since assignment just creates references to +objects, there's no alias between an argument name in the caller and +callee, and so no call-by-reference per se. But you can simulate it +in a number of ways: +

+1) By using global variables; but you probably shouldn't :-) +

+2) By passing a mutable (changeable in-place) object: +

+

+      def func1(a):
+          a[0] = 'new-value'     # 'a' references a mutable list
+          a[1] = a[1] + 1        # changes a shared object
+
+
+      args = ['old-value', 99]
+      func1(args)
+      print args[0], args[1]     # output: new-value 100
+
+3) By returning a tuple, holding the final values of arguments: +

+

+      def func2(a, b):
+          a = 'new-value'        # a and b are local names
+          b = b + 1              # assigned to new objects
+          return a, b            # return new values
+
+
+      x, y = 'old-value', 99
+      x, y = func2(x, y)
+      print x, y                 # output: new-value 100
+
+4) And other ideas that fall-out from Python's object model. For instance, it might be clearer to pass in a mutable dictionary: +

+

+      def func3(args):
+          args['a'] = 'new-value'     # args is a mutable dictionary
+          args['b'] = args['b'] + 1   # change it in-place
+
+
+      args = {'a':' old-value', 'b': 99}
+      func3(args)
+      print args['a'], args['b']
+
+5) Or bundle-up values in a class instance: +

+

+      class callByRef:
+          def __init__(self, **args):
+              for (key, value) in args.items():
+                  setattr(self, key, value)
+
+
+      def func4(args):
+          args.a = 'new-value'        # args is a mutable callByRef
+          args.b = args.b + 1         # change object in-place
+
+
+      args = callByRef(a='old-value', b=99)
+      func4(args)
+      print args.a, args.b
+
+
+   But there's probably no good reason to get this complicated :-).
+
+[Python's author favors solution 3 in most cases.] +

+ +Edit this entry / +Log info + +/ Last changed on Sun Jun 8 23:49:46 1997 by +David Ascher +

+ +


+

4.36. Please explain the rules for local and global variables in Python.

+[Ken Manheimer] In Python, procedure variables are implicitly +global, unless they are assigned anywhere within the block. +In that case +they are implicitly local, and you need to explicitly declare them as +'global'. +

+Though a bit surprising at first, a moment's consideration explains +this. On one hand, requirement of 'global' for assigned vars provides +a bar against unintended side-effects. On the other hand, if global +were required for all global references, you'd be using global all the +time. Eg, you'd have to declare as global every reference to a +builtin function, or to a component of an imported module. This +clutter would defeat the usefulness of the 'global' declaration for +identifying side-effects. +

+ +Edit this entry / +Log info + +/ Last changed on Fri Aug 28 09:53:27 1998 by +GvR +

+ +


+

4.37. How can I have modules that mutually import each other?

+Suppose you have the following modules: +

+foo.py: +

+

+	from bar import bar_var
+	foo_var=1
+
+bar.py: +

+

+	from foo import foo_var
+	bar_var=2
+
+The problem is that the above is processed by the interpreter thus: +

+

+	main imports foo
+	Empty globals for foo are created
+	foo is compiled and starts executing
+	foo imports bar
+	Empty globals for bar are created
+	bar is compiled and starts executing
+	bar imports foo (which is a no-op since there already is a module named foo)
+	bar.foo_var = foo.foo_var
+	...
+
+The last step fails, because Python isn't done with interpreting foo yet and the global symbol dict for foo is still empty. +

+The same thing happens when you use "import foo", and then try to access "foo.one" in global code. +

+

+There are (at least) three possible workarounds for this problem. +

+Guido van Rossum recommends to avoid all uses of "from <module> import ..." (so everything from an imported module is referenced as <module>.<name>) and to place all code inside functions. Initializations of global variables and class variables should use constants or built-in functions only. +

+

+Jim Roskind suggests the following order in each module: +

+

+ exports (globals, functions, and classes that don't need imported base classes)
+ import statements
+ active code (including globals that are initialized from imported values).
+
+Python's author doesn't like this approach much because the imports +appear in a strange place, but has to admit that it works. +

+

+

+Matthias Urlichs recommends to restructure your code so that the recursive import is not necessary in the first place. +

+

+These solutions are not mutually exclusive. +

+ +Edit this entry / +Log info + +/ Last changed on Mon Jun 3 06:52:51 2002 by +Matthias Urlichs +

+ +


+

4.38. How do I copy an object in Python?

+Try copy.copy() or copy.deepcopy() for the general case. Not all objects can be copied, but most can. +

+Dictionaries have a copy method. Sequences can be copied by slicing: +

+ new_l = l[:]
+
+

+ +Edit this entry / +Log info + +/ Last changed on Thu Mar 21 05:40:26 2002 by +Erno Kuusela +

+ +


+

4.39. How to implement persistent objects in Python? (Persistent == automatically saved to and restored from disk.)

+The library module "pickle" now solves this in a very general way +(though you still can't store things like open files, sockets or +windows), and the library module "shelve" uses pickle and (g)dbm to +create persistent mappings containing arbitrary Python objects. +For possibly better performance also look for the latest version +of the relatively recent cPickle module. +

+A more awkward way of doing things is to use pickle's little sister, +marshal. The marshal module provides very fast ways to store +noncircular basic Python types to files and strings, and back again. +Although marshal does not do fancy things like store instances or +handle shared references properly, it does run extremely fast. For +example loading a half megabyte of data may take less than a +third of a second (on some machines). This often beats doing +something more complex and general such as using gdbm with +pickle/shelve. +

+ +Edit this entry / +Log info + +/ Last changed on Sun Jun 8 22:59:00 1997 by +David Ascher +

+ +


+

4.40. I try to use __spam and I get an error about _SomeClassName__spam.

+Variables with double leading underscore are "mangled" to provide a +simple but effective way to define class private variables. See the +chapter "New in Release 1.4" in the Python Tutorial. +

+ +Edit this entry / +Log info +

+ +


+

4.41. How do I delete a file? And other file questions.

+Use os.remove(filename) or os.unlink(filename); for documentation, +see the posix section of the library manual. They are the same, +unlink() is simply the Unix name for this function. In earlier +versions of Python, only os.unlink() was available. +

+To remove a directory, use os.rmdir(); use os.mkdir() to create one. +

+To rename a file, use os.rename(). +

+To truncate a file, open it using f = open(filename, "r+"), and use +f.truncate(offset); offset defaults to the current seek position. +(The "r+" mode opens the file for reading and writing.) +There's also os.ftruncate(fd, offset) for files opened with os.open() +-- for advanced Unix hacks only. +

+The shutil module also contains a number of functions to work on files +including copyfile, copytree, and rmtree amongst others. +

+ +Edit this entry / +Log info + +/ Last changed on Thu Dec 28 12:30:01 2000 by +Bjorn Pettersen +

+ +


+

4.42. How to modify urllib or httplib to support HTTP/1.1?

+Recent versions of Python (2.0 and onwards) support HTTP/1.1 natively. +

+ +Edit this entry / +Log info + +/ Last changed on Tue Jan 2 02:56:56 2001 by +Moshe Zadka +

+ +


+

4.43. Unexplicable syntax errors in compile() or exec.

+When a statement suite (as opposed to an expression) is compiled by +compile(), exec or execfile(), it must end in a newline. In some +cases, when the source ends in an indented block it appears that at +least two newlines are required. +

+ +Edit this entry / +Log info +

+ +


+

4.44. How do I convert a string to a number?

+For integers, use the built-in int() function, e.g. int('144') == 144. Similarly, long() converts from string to long integer, e.g. long('144') == 144L; and float() to floating-point, e.g. float('144') == 144.0. +

+Note that these are restricted to decimal interpretation, so +that int('0144') == 144 and int('0x144') raises ValueError. For Python +2.0 int takes the base to convert from as a second optional argument, so +int('0x144', 16) == 324. +

+For greater flexibility, or before Python 1.5, import the module +string and use the string.atoi() function for integers, +string.atol() for long integers, or string.atof() for +floating-point. E.g., +string.atoi('100', 16) == string.atoi('0x100', 0) == 256. +See the library reference manual section for the string module for +more details. +

+While you could use the built-in function eval() instead of +any of those, this is not recommended, because someone could pass you +a Python expression that might have unwanted side effects (like +reformatting your disk). It also has the effect of interpreting numbers +as Python expressions, so that e.g. eval('09') gives a syntax error +since Python regards numbers starting with '0' as octal (base 8). +

+ +Edit this entry / +Log info + +/ Last changed on Thu Dec 28 12:37:34 2000 by +Bjorn Pettersen +

+ +


+

4.45. How do I convert a number to a string?

+To convert, e.g., the number 144 to the string '144', use the +built-in function repr() or the backquote notation (these are +equivalent). If you want a hexadecimal or octal representation, use +the built-in functions hex() or oct(), respectively. For fancy +formatting, use the % operator on strings, just like C printf formats, +e.g. "%04d" % 144 yields '0144' and "%.3f" % (1/3.0) yields '0.333'. +See the library reference manual for details. +

+ +Edit this entry / +Log info +

+ +


+

4.46. How do I copy a file?

+There's the shutil module which contains a copyfile() +function that implements a copy loop; +it isn't good enough for the Macintosh, though: +it doesn't copy the resource fork and Finder info. +

+ +Edit this entry / +Log info + +/ Last changed on Tue Jan 2 02:59:40 2001 by +Moshe Zadka +

+ +


+

4.47. How do I check if an object is an instance of a given class or of a subclass of it?

+If you are developing the classes from scratch it might be better to +program in a more proper object-oriented style -- instead of doing a different +thing based on class membership, why not use a method and define the +method differently in different classes? +

+However, there are some legitimate situations +where you need to test for class membership. +

+In Python 1.5, you can use the built-in function isinstance(obj, cls). +

+The following approaches can be used with earlier Python versions: +

+An unobvious method is to raise the object +as an exception and to try to catch the exception with the class you're +testing for: +

+

+	def is_instance_of(the_instance, the_class):
+	    try:
+		raise the_instance
+	    except the_class:
+		return 1
+	    except:
+		return 0
+
+This technique can be used to distinguish "subclassness" +from a collection of classes as well +

+

+                try:
+                              raise the_instance
+                except Audible:
+                              the_instance.play(largo)
+                except Visual:
+                              the_instance.display(gaudy)
+                except Olfactory:
+                              sniff(the_instance)
+                except:
+                              raise ValueError, "dunno what to do with this!"
+
+This uses the fact that exception catching tests for class or subclass +membership. +

+A different approach is to test for the presence of a class attribute that +is presumably unique for the given class. For instance: +

+

+	class MyClass:
+	    ThisIsMyClass = 1
+	    ...
+
+
+	def is_a_MyClass(the_instance):
+	    return hasattr(the_instance, 'ThisIsMyClass')
+
+This version is easier to inline, and probably faster (inlined it +is definitely faster). The disadvantage is that someone else could cheat: +

+

+	class IntruderClass:
+	    ThisIsMyClass = 1    # Masquerade as MyClass
+	    ...
+
+but this may be seen as a feature (anyway, there are plenty of other ways +to cheat in Python). Another disadvantage is that the class must be +prepared for the membership test. If you do not "control the +source code" for the class it may not be advisable to modify the +class to support testability. +

+ +Edit this entry / +Log info + +/ Last changed on Fri Jan 2 15:16:04 1998 by +GvR +

+ +


+

4.48. What is delegation?

+Delegation refers to an object oriented technique Python programmers +may implement with particular ease. Consider the following: +

+

+  from string import upper
+
+
+  class UpperOut:
+        def __init__(self, outfile):
+              self.__outfile = outfile
+        def write(self, str):
+              self.__outfile.write( upper(str) )
+        def __getattr__(self, name):
+              return getattr(self.__outfile, name)
+
+Here the UpperOut class redefines the write method +to convert the argument string to upper case before +calling the underlying self.__outfile.write method, but +all other methods are delegated to the underlying +self.__outfile object. The delegation is accomplished +via the "magic" __getattr__ method. Please see the +language reference for more information on the use +of this method. +

+Note that for more general cases delegation can +get trickier. Particularly when attributes must be set +as well as gotten the class must define a __settattr__ +method too, and it must do so carefully. +

+The basic implementation of __setattr__ is roughly +equivalent to the following: +

+

+   class X:
+        ...
+        def __setattr__(self, name, value):
+             self.__dict__[name] = value
+        ...
+
+Most __setattr__ implementations must modify +self.__dict__ to store local state for self without +causing an infinite recursion. +

+ +Edit this entry / +Log info + +/ Last changed on Wed Aug 13 07:11:24 1997 by +aaron watters +

+ +


+

4.49. How do I test a Python program or component.

+We presume for the purposes of this question you are interested +in standalone testing, rather than testing your components inside +a testing framework. The best-known testing framework for Python +is the PyUnit module, maintained at +

+

+    http://pyunit.sourceforge.net/
+
+For standalone testing, it helps to write the program so that +it may be easily tested by using good modular design. +In particular your program +should have almost all functionality encapsulated in either functions +or class methods -- and this sometimes has the surprising and +delightful effect of making the program run faster (because +local variable accesses are faster than global accesses). +Furthermore the program should avoid depending on mutating +global variables, since this makes testing much more difficult to do. +

+The "global main logic" of your program may be as simple +as +

+

+  if __name__=="__main__":
+       main_logic()
+
+at the bottom of the main module of your program. +

+Once your program is organized as a tractable collection +of functions and class behaviours you should write test +functions that exercise the behaviours. A test suite +can be associated with each module which automates +a sequence of tests. This sounds like a lot of work, but +since Python is so terse and flexible it's surprisingly easy. +You can make coding much more pleasant and fun by +writing your test functions in parallel with the "production +code", since this makes it easy to find bugs and even +design flaws earlier. +

+"Support modules" that are not intended to be the main +module of a program may include a "test script interpretation" +which invokes a self test of the module. +

+

+   if __name__ == "__main__":
+      self_test()
+
+Even programs that interact with complex external +interfaces may be tested when the external interfaces are +unavailable by using "fake" interfaces implemented in +Python. For an example of a "fake" interface, the following +class defines (part of) a "fake" file interface: +

+

+ import string
+ testdata = "just a random sequence of characters"
+
+
+ class FakeInputFile:
+   data = testdata
+   position = 0
+   closed = 0
+
+
+   def read(self, n=None):
+       self.testclosed()
+       p = self.position
+       if n is None:
+          result= self.data[p:]
+       else:
+          result= self.data[p: p+n]
+       self.position = p + len(result)
+       return result
+
+
+   def seek(self, n, m=0):
+       self.testclosed()
+       last = len(self.data)
+       p = self.position
+       if m==0: 
+          final=n
+       elif m==1:
+          final=n+p
+       elif m==2:
+          final=len(self.data)+n
+       else:
+          raise ValueError, "bad m"
+       if final<0:
+          raise IOError, "negative seek"
+       self.position = final
+
+
+   def isatty(self):
+       return 0
+
+
+   def tell(self):
+       return self.position
+
+
+   def close(self):
+       self.closed = 1
+
+
+   def testclosed(self):
+       if self.closed:
+          raise IOError, "file closed"
+
+Try f=FakeInputFile() and test out its operations. +

+ +Edit this entry / +Log info + +/ Last changed on Mon Jun 3 01:12:10 2002 by +Neal Norwitz +

+ +


+

4.50. My multidimensional list (array) is broken! What gives?

+You probably tried to make a multidimensional array like this. +

+

+   A = [[None] * 2] * 3
+
+This makes a list containing 3 references to the same list of length +two. Changes to one row will show in all rows, which is probably not +what you want. The following works much better: +

+

+   A = [None]*3
+   for i in range(3):
+        A[i] = [None] * 2
+
+This generates a list containing 3 different lists of length two. +

+If you feel weird, you can also do it in the following way: +

+

+   w, h = 2, 3
+   A = map(lambda i,w=w: [None] * w, range(h))
+
+For Python 2.0 the above can be spelled using a list comprehension: +

+

+   w,h = 2,3
+   A = [ [None]*w for i in range(h) ]
+
+

+ +Edit this entry / +Log info + +/ Last changed on Thu Dec 28 12:18:35 2000 by +Bjorn Pettersen +

+ +


+

4.51. I want to do a complicated sort: can you do a Schwartzian Transform in Python?

+Yes, and in Python you only have to write it once: +

+

+ def st(List, Metric):
+     def pairing(element, M = Metric):
+           return (M(element), element)
+     paired = map(pairing, List)
+     paired.sort()
+     return map(stripit, paired)
+
+
+ def stripit(pair):
+     return pair[1]
+
+This technique, attributed to Randal Schwartz, sorts the elements +of a list by a metric which maps each element to its "sort value". +For example, if L is a list of string then +

+

+   import string
+   Usorted = st(L, string.upper)
+
+
+   def intfield(s):
+         return string.atoi( string.strip(s[10:15] ) )
+
+
+   Isorted = st(L, intfield)
+
+Usorted gives the elements of L sorted as if they were upper +case, and Isorted gives the elements of L sorted by the integer +values that appear in the string slices starting at position 10 +and ending at position 15. In Python 2.0 this can be done more +naturally with list comprehensions: +

+

+  tmp1 = [ (x.upper(), x) for x in L ] # Schwartzian transform
+  tmp1.sort()
+  Usorted = [ x[1] for x in tmp1 ]
+
+
+  tmp2 = [ (int(s[10:15]), s) for s in L ] # Schwartzian transform
+  tmp2.sort()
+  Isorted = [ x[1] for x in tmp2 ]
+
+

+Note that Isorted may also be computed by +

+

+   def Icmp(s1, s2):
+         return cmp( intfield(s1), intfield(s2) )
+
+
+   Isorted = L[:]
+   Isorted.sort(Icmp)
+
+but since this method computes intfield many times for each +element of L, it is slower than the Schwartzian Transform. +

+ +Edit this entry / +Log info + +/ Last changed on Sat Jun 1 19:18:46 2002 by +Neal Norwitz +

+ +


+

4.52. How to convert between tuples and lists?

+The function tuple(seq) converts any sequence into a tuple with +the same items in the same order. +For example, tuple([1, 2, 3]) yields (1, 2, 3) and tuple('abc') +yields ('a', 'b', 'c'). If the argument is +a tuple, it does not make a copy but returns the same object, so +it is cheap to call tuple() when you aren't sure that an object +is already a tuple. +

+The function list(seq) converts any sequence into a list with +the same items in the same order. +For example, list((1, 2, 3)) yields [1, 2, 3] and list('abc') +yields ['a', 'b', 'c']. If the argument is a list, +it makes a copy just like seq[:] would. +

+ +Edit this entry / +Log info + +/ Last changed on Sun Jun 14 14:18:53 1998 by +Tim Peters +

+ +


+

4.53. Files retrieved with urllib contain leading garbage that looks like email headers.

+Extremely old versions of Python supplied libraries which +did not support HTTP/1.1; the vanilla httplib in Python 1.4 +only recognized HTTP/1.0. In Python 2.0 full HTTP/1.1 support is included. +

+ +Edit this entry / +Log info + +/ Last changed on Mon Jan 8 17:26:18 2001 by +Steve Holden +

+ +


+

4.54. How do I get a list of all instances of a given class?

+Python does not keep track of all instances of a class (or of a +built-in type). +

+You can program the class's constructor to keep track of all +instances, but unless you're very clever, this has the disadvantage +that the instances never get deleted,because your list of all +instances keeps a reference to them. +

+(The trick is to regularly inspect the reference counts of the +instances you've retained, and if the reference count is below a +certain level, remove it from the list. Determining that level is +tricky -- it's definitely larger than 1.) +

+ +Edit this entry / +Log info + +/ Last changed on Tue May 27 23:52:16 1997 by +GvR +

+ +


+

4.55. A regular expression fails with regex.error: match failure.

+This is usually caused by too much backtracking; the regular +expression engine has a fixed size stack which holds at most 4000 +backtrack points. Every character matched by e.g. ".*" accounts for a +backtrack point, so even a simple search like +

+

+  regex.match('.*x',"x"*5000)
+
+will fail. +

+This is fixed in the re module introduced with +Python 1.5; consult the Library Reference section on re for more information. +

+ +Edit this entry / +Log info + +/ Last changed on Thu Jul 30 12:35:49 1998 by +A.M. Kuchling +

+ +


+

4.56. I can't get signal handlers to work.

+The most common problem is that the signal handler is declared +with the wrong argument list. It is called as +

+

+	handler(signum, frame)
+
+so it should be declared with two arguments: +

+

+	def handler(signum, frame):
+		...
+
+

+ +Edit this entry / +Log info + +/ Last changed on Wed May 28 09:29:08 1997 by +GvR +

+ +


+

4.57. I can't use a global variable in a function? Help!

+Did you do something like this? +

+

+   x = 1 # make a global
+
+
+   def f():
+         print x # try to print the global
+         ...
+         for j in range(100):
+              if q>3:
+                 x=4
+
+Any variable assigned in a function is local to that function. +unless it is specifically declared global. Since a value is bound +to x as the last statement of the function body, the compiler +assumes that x is local. Consequently the "print x" +attempts to print an uninitialized local variable and will +trigger a NameError. +

+In such cases the solution is to insert an explicit global +declaration at the start of the function, making it +

+

+

+   def f():
+         global x
+         print x # try to print the global
+         ...
+         for j in range(100):
+              if q>3:
+                 x=4
+
+

+In this case, all references to x are interpreted as references +to the x from the module namespace. +

+ +Edit this entry / +Log info + +/ Last changed on Mon Feb 12 15:52:12 2001 by +Steve Holden +

+ +


+

4.58. What's a negative index? Why doesn't list.insert() use them?

+Python sequences are indexed with positive numbers and +negative numbers. For positive numbers 0 is the first index +1 is the second index and so forth. For negative indices -1 +is the last index and -2 is the pentultimate (next to last) index +and so forth. Think of seq[-n] as the same as seq[len(seq)-n]. +

+Using negative indices can be very convenient. For example +if the string Line ends in a newline then Line[:-1] is all of Line except +the newline. +

+Sadly the list builtin method L.insert does not observe negative +indices. This feature could be considered a mistake but since +existing programs depend on this feature it may stay around +forever. L.insert for negative indices inserts at the start of the +list. To get "proper" negative index behaviour use L[n:n] = [x] +in place of the insert method. +

+ +Edit this entry / +Log info + +/ Last changed on Wed Aug 13 07:03:18 1997 by +aaron watters +

+ +


+

4.59. How can I sort one list by values from another list?

+You can sort lists of tuples. +

+

+  >>> list1 = ["what", "I'm", "sorting", "by"]
+  >>> list2 = ["something", "else", "to", "sort"]
+  >>> pairs = map(None, list1, list2)
+  >>> pairs
+  [('what', 'something'), ("I'm", 'else'), ('sorting', 'to'), ('by', 'sort')]
+  >>> pairs.sort()
+  >>> pairs
+  [("I'm", 'else'), ('by', 'sort'), ('sorting', 'to'), ('what', 'something')]
+  >>> result = pairs[:]
+  >>> for i in xrange(len(result)): result[i] = result[i][1]
+  ...
+  >>> result
+  ['else', 'sort', 'to', 'something']
+
+And if you didn't understand the question, please see the +example above ;c). Note that "I'm" sorts before "by" because +uppercase "I" comes before lowercase "b" in the ascii order. +Also see 4.51. +

+In Python 2.0 this can be done like: +

+

+ >>> list1 = ["what", "I'm", "sorting", "by"]
+ >>> list2 = ["something", "else", "to", "sort"]
+ >>> pairs = zip(list1, list2)
+ >>> pairs
+ [('what', 'something'), ("I'm", 'else'), ('sorting', 'to'), ('by', 'sort')]
+ >>> pairs.sort()
+ >>> result = [ x[1] for x in pairs ]
+ >>> result
+ ['else', 'sort', 'to', 'something']
+
+[Followup] +

+Someone asked, why not this for the last steps: +

+

+  result = []
+  for p in pairs: result.append(p[1])
+
+This is much more legible. However, a quick test shows that +it is almost twice as slow for long lists. Why? First of all, +the append() operation has to reallocate memory, and while it +uses some tricks to avoid doing that each time, it still has +to do it occasionally, and apparently that costs quite a bit. +Second, the expression "result.append" requires an extra +attribute lookup. The attribute lookup could be done away +with by rewriting as follows: +

+

+  result = []
+  append = result.append
+  for p in pairs: append(p[1])
+
+which gains back some speed, but is still considerably slower +than the original solution, and hardly less convoluted. +

+ +Edit this entry / +Log info + +/ Last changed on Thu Dec 28 12:56:35 2000 by +Bjorn Pettersen +

+ +


+

4.60. Why doesn't dir() work on builtin types like files and lists?

+It does starting with Python 1.5. +

+Using 1.4, you can find out which methods a given object supports +by looking at its __methods__ attribute: +

+

+    >>> List = []
+    >>> List.__methods__
+    ['append', 'count', 'index', 'insert', 'remove', 'reverse', 'sort']
+
+

+ +Edit this entry / +Log info + +/ Last changed on Thu Sep 16 14:56:42 1999 by +Skip Montanaro +

+ +


+

4.61. How can I mimic CGI form submission (METHOD=POST)?

+I would like to retrieve web pages that are the result of POSTing a +form. Is there existing code that would let me do this easily? +

+Yes. Here's a simple example that uses httplib. +

+

+    #!/usr/local/bin/python
+
+
+    import httplib, sys, time
+
+
+    ### build the query string
+    qs = "First=Josephine&MI=Q&Last=Public"
+
+
+    ### connect and send the server a path
+    httpobj = httplib.HTTP('www.some-server.out-there', 80)
+    httpobj.putrequest('POST', '/cgi-bin/some-cgi-script')
+    ### now generate the rest of the HTTP headers...
+    httpobj.putheader('Accept', '*/*')
+    httpobj.putheader('Connection', 'Keep-Alive')
+    httpobj.putheader('Content-type', 'application/x-www-form-urlencoded')
+    httpobj.putheader('Content-length', '%d' % len(qs))
+    httpobj.endheaders()
+    httpobj.send(qs)
+    ### find out what the server said in response...
+    reply, msg, hdrs = httpobj.getreply()
+    if reply != 200:
+	sys.stdout.write(httpobj.getfile().read())
+
+Note that in general for "url encoded posts" (the default) query strings must be "quoted" to, for example, change equals signs and spaces to an encoded form when they occur in name or value. Use urllib.quote to perform this quoting. For example to send name="Guy Steele, Jr.": +

+

+   >>> from urllib import quote
+   >>> x = quote("Guy Steele, Jr.")
+   >>> x
+   'Guy%20Steele,%20Jr.'
+   >>> query_string = "name="+x
+   >>> query_string
+   'name=Guy%20Steele,%20Jr.'
+
+

+ +Edit this entry / +Log info + +/ Last changed on Mon Jun 21 03:47:07 1999 by +TAB +

+ +


+

4.62. If my program crashes with a bsddb (or anydbm) database open, it gets corrupted. How come?

+Databases opened for write access with the bsddb module (and often by +the anydbm module, since it will preferentially use bsddb) must +explicitly be closed using the close method of the database. The +underlying libdb package caches database contents which need to be +converted to on-disk form and written, unlike regular open files which +already have the on-disk bits in the kernel's write buffer, where they +can just be dumped by the kernel with the program exits. +

+If you have initialized a new bsddb database but not written anything to +it before the program crashes, you will often wind up with a zero-length +file and encounter an exception the next time the file is opened. +

+ +Edit this entry / +Log info + +/ Last changed on Mon Jun 3 01:15:01 2002 by +Neal Norwitz +

+ +


+

4.63. How do I make a Python script executable on Unix?

+You need to do two things: the script file's mode must be executable +(include the 'x' bit), and the first line must begin with #! +followed by the pathname for the Python interpreter. +

+The first is done by executing 'chmod +x scriptfile' or perhaps +'chmod 755 scriptfile'. +

+The second can be done in a number of way. The most straightforward +way is to write +

+

+  #!/usr/local/bin/python
+
+as the very first line of your file - or whatever the pathname is +where the python interpreter is installed on your platform. +

+If you would like the script to be independent of where the python +interpreter lives, you can use the "env" program. On almost all +platforms, the following will work, assuming the python interpreter +is in a directory on the user's $PATH: +

+

+  #! /usr/bin/env python
+
+Note -- *don't* do this for CGI scripts. The $PATH variable for +CGI scripts is often very minimal, so you need to use the actual +absolute pathname of the interpreter. +

+Occasionally, a user's environment is so full that the /usr/bin/env +program fails; or there's no env program at all. +In that case, you can try the following hack (due to Alex Rezinsky): +

+

+  #! /bin/sh
+  """:"
+  exec python $0 ${1+"$@"}
+  """
+
+The disadvantage is that this defines the script's __doc__ string. +However, you can fix that by adding +

+

+  __doc__ = """...Whatever..."""
+
+

+ +Edit this entry / +Log info + +/ Last changed on Mon Jan 15 09:19:16 2001 by +Neal Norwitz +

+ +


+

4.64. How do you remove duplicates from a list?

+See the Python Cookbook for a long discussion of many cool ways: +

+

+    http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/52560
+
+Generally, if you don't mind reordering the List +

+

+   if List:
+      List.sort()
+      last = List[-1]
+      for i in range(len(List)-2, -1, -1):
+          if last==List[i]: del List[i]
+          else: last=List[i]
+
+If all elements of the list may be used as +dictionary keys (ie, they are all hashable) +this is often faster +

+

+   d = {}
+   for x in List: d[x]=x
+   List = d.values()
+
+Also, for extremely large lists you might +consider more optimal alternatives to the first one. +The second one is pretty good whenever it can +be used. +

+ +Edit this entry / +Log info + +/ Last changed on Fri May 24 21:56:33 2002 by +Tim Peters +

+ +


+

4.65. Are there any known year 2000 problems in Python?

+I am not aware of year 2000 deficiencies in Python 1.5. Python does +very few date calculations and for what it does, it relies on the C +library functions. Python generally represent times either as seconds +since 1970 or as a tuple (year, month, day, ...) where the year is +expressed with four digits, which makes Y2K bugs unlikely. So as long +as your C library is okay, Python should be okay. Of course, I cannot +vouch for your Python code! +

+Given the nature of freely available software, I have to add that this statement is not +legally binding. The Python copyright notice contains the following +disclaimer: +

+

+  STICHTING MATHEMATISCH CENTRUM AND CNRI DISCLAIM ALL WARRANTIES WITH
+  REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF
+  MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH
+  CENTRUM OR CNRI BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL
+  DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
+  PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
+  TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
+  PERFORMANCE OF THIS SOFTWARE.
+
+The good news is that if you encounter a problem, you have full +source available to track it down and fix it! +

+ +Edit this entry / +Log info + +/ Last changed on Fri Apr 10 14:59:31 1998 by +GvR +

+ +


+

4.66. I want a version of map that applies a method to a sequence of objects! Help!

+Get fancy! +

+

+  def method_map(objects, method, arguments):
+       """method_map([a,b], "flog", (1,2)) gives [a.flog(1,2), b.flog(1,2)]"""
+       nobjects = len(objects)
+       methods = map(getattr, objects, [method]*nobjects)
+       return map(apply, methods, [arguments]*nobjects)
+
+It's generally a good idea to get to know the mysteries of map and apply +and getattr and the other dynamic features of Python. +

+ +Edit this entry / +Log info + +/ Last changed on Mon Jan 5 14:21:14 1998 by +Aaron Watters +

+ +


+

4.67. How do I generate random numbers in Python?

+The standard library module "random" implements a random number +generator. Usage is simple: +

+

+    import random
+
+
+    random.random()
+
+This returns a random floating point number in the range [0, 1). +

+There are also many other specialized generators in this module, such +as +

+

+    randrange(a, b) chooses an integer in the range [a, b)
+    uniform(a, b) chooses a floating point number in the range [a, b)
+    normalvariate(mean, sdev) sample from normal (Gaussian) distribution
+
+Some higher-level functions operate on sequences directly, such as +

+

+    choice(S) chooses random element from a given sequence
+    shuffle(L) shuffles a list in-place, i.e. permutes it randomly
+
+There's also a class, Random, which you can instantiate +to create independent multiple random number generators. +

+All this is documented in the library reference manual. Note that +the module "whrandom" is obsolete. +

+ +Edit this entry / +Log info + +/ Last changed on Mon Jun 3 01:16:51 2002 by +Neal Norwitz +

+ +


+

4.68. How do I access the serial (RS232) port?

+There's a Windows serial communication module (for communication +over RS 232 serial ports) at +

+

+  ftp://ftp.python.org/pub/python/contrib/sio-151.zip
+  http://www.python.org/ftp/python/contrib/sio-151.zip
+
+For DOS, try Hans Nowak's Python-DX, which supports this, at: +

+

+  http://www.cuci.nl/~hnowak/
+
+For Unix, see a usenet post by Mitch Chapman: +

+

+  http://groups.google.com/groups?selm=34A04430.CF9@ohioee.com
+
+For Win32, POSIX(Linux, BSD, *), Jython, Chris': +

+

+  http://pyserial.sourceforge.net
+
+

+ +Edit this entry / +Log info + +/ Last changed on Tue Jul 2 21:11:07 2002 by +Chris Liechti +

+ +


+

4.69. Images on Tk-Buttons don't work in Py15?

+They do work, but you must keep your own reference to the image +object now. More verbosely, you must make sure that, say, a global +variable or a class attribute refers to the object. +

+Quoting Fredrik Lundh from the mailinglist: +

+

+  Well, the Tk button widget keeps a reference to the internal
+  photoimage object, but Tkinter does not.  So when the last
+  Python reference goes away, Tkinter tells Tk to release the
+  photoimage.  But since the image is in use by a widget, Tk
+  doesn't destroy it.  Not completely.  It just blanks the image,
+  making it completely transparent...
+
+
+  And yes, there was a bug in the keyword argument handling
+  in 1.4 that kept an extra reference around in some cases.  And
+  when Guido fixed that bug in 1.5, he broke quite a few Tkinter
+  programs...
+
+

+ +Edit this entry / +Log info + +/ Last changed on Tue Feb 3 11:31:03 1998 by +Case Roole +

+ +


+

4.70. Where is the math.py (socket.py, regex.py, etc.) source file?

+If you can't find a source file for a module it may be a builtin +or dynamically loaded module implemented in C, C++ or other +compiled language. In this case you may not have the source +file or it may be something like mathmodule.c, somewhere in +a C source directory (not on the Python Path). +

+Fredrik Lundh (fredrik@pythonware.com) explains (on the python-list): +

+There are (at least) three kinds of modules in Python: +1) modules written in Python (.py); +2) modules written in C and dynamically loaded (.dll, .pyd, .so, .sl, etc); +3) modules written in C and linked with the interpreter; to get a list +of these, type: +

+

+    import sys
+    print sys.builtin_module_names
+
+

+ +Edit this entry / +Log info + +/ Last changed on Tue Feb 3 13:55:33 1998 by +Aaron Watters +

+ +


+

4.71. How do I send mail from a Python script?

+The standard library module smtplib does this. +Here's a very simple interactive mail +sender that uses it. This method will work on any host that +supports an SMTP listener. +

+

+    import sys, smtplib
+
+
+    fromaddr = raw_input("From: ")
+    toaddrs  = raw_input("To: ").split(',')
+    print "Enter message, end with ^D:"
+    msg = ''
+    while 1:
+        line = sys.stdin.readline()
+        if not line:
+            break
+        msg = msg + line
+
+
+    # The actual mail send
+    server = smtplib.SMTP('localhost')
+    server.sendmail(fromaddr, toaddrs, msg)
+    server.quit()
+
+If the local host doesn't have an SMTP listener, you need to find one. The simple method is to ask the user. Alternately, you can use the DNS system to find the mail gateway(s) responsible for the source address. +

+A Unix-only alternative uses sendmail. The location of the +sendmail program varies between systems; sometimes it is +/usr/lib/sendmail, sometime /usr/sbin/sendmail. The sendmail manual +page will help you out. Here's some sample code: +

+

+  SENDMAIL = "/usr/sbin/sendmail" # sendmail location
+  import os
+  p = os.popen("%s -t -i" % SENDMAIL, "w")
+  p.write("To: cary@ratatosk.org\n")
+  p.write("Subject: test\n")
+  p.write("\n") # blank line separating headers from body
+  p.write("Some text\n")
+  p.write("some more text\n")
+  sts = p.close()
+  if sts != 0:
+      print "Sendmail exit status", sts
+
+

+ +Edit this entry / +Log info + +/ Last changed on Mon Jun 3 07:05:12 2002 by +Matthias Urlichs +

+ +


+

4.72. How do I avoid blocking in connect() of a socket?

+The select module is widely known to help with asynchronous +I/O on sockets once they are connected. However, it is less +than common knowledge how to avoid blocking on the initial +connect() call. Jeremy Hylton has the following advice (slightly +edited): +

+To prevent the TCP connect from blocking, you can set the socket to +non-blocking mode. Then when you do the connect(), you will either +connect immediately (unlikely) or get an exception that contains the +errno. errno.EINPROGRESS indicates that the connection is in +progress, but hasn't finished yet. Different OSes will return +different errnos, so you're going to have to check. I can tell you +that different versions of Solaris return different errno values. +

+In Python 1.5 and later, you can use connect_ex() to avoid +creating an exception. It will just return the errno value. +

+To poll, you can call connect_ex() again later -- 0 or errno.EISCONN +indicate that you're connected -- or you can pass this socket to +select (checking to see if it is writeable). +

+ +Edit this entry / +Log info + +/ Last changed on Tue Feb 24 21:30:45 1998 by +GvR +

+ +


+

4.73. How do I specify hexadecimal and octal integers?

+To specify an octal digit, precede the octal value with a zero. For example, +to set the variable "a" to the octal value "10" (8 in decimal), type: +

+

+    >>> a = 010
+
+To verify that this works, you can type "a" and hit enter while in the +interpreter, which will cause Python to spit out the current value of "a" +in decimal: +

+

+    >>> a
+    8
+
+Hexadecimal is just as easy. Simply precede the hexadecimal number with a +zero, and then a lower or uppercase "x". Hexadecimal digits can be specified +in lower or uppercase. For example, in the Python interpreter: +

+

+    >>> a = 0xa5
+    >>> a
+    165
+    >>> b = 0XB2
+    >>> b
+    178
+
+

+ +Edit this entry / +Log info + +/ Last changed on Tue Mar 3 12:53:16 1998 by +GvR +

+ +


+

4.74. How to get a single keypress at a time?

+For Windows, see question 8.2. Here is an answer for Unix (see also 4.94). +

+There are several solutions; some involve using curses, which is a +pretty big thing to learn. Here's a solution without curses, due +to Andrew Kuchling (adapted from code to do a PGP-style +randomness pool): +

+

+        import termios, sys, os
+        fd = sys.stdin.fileno()
+        old = termios.tcgetattr(fd)
+        new = termios.tcgetattr(fd)
+        new[3] = new[3] & ~termios.ICANON & ~termios.ECHO
+        new[6][termios.VMIN] = 1
+        new[6][termios.VTIME] = 0
+        termios.tcsetattr(fd, termios.TCSANOW, new)
+        s = ''    # We'll save the characters typed and add them to the pool.
+        try:
+            while 1:
+                c = os.read(fd, 1)
+                print "Got character", `c`
+                s = s+c
+        finally:
+            termios.tcsetattr(fd, termios.TCSAFLUSH, old)
+
+You need the termios module for any of this to work, and I've only +tried it on Linux, though it should work elsewhere. It turns off +stdin's echoing and disables canonical mode, and then reads a +character at a time from stdin, noting the time after each keystroke. +

+ +Edit this entry / +Log info + +/ Last changed on Thu Oct 24 00:36:56 2002 by +chris +

+ +


+

4.75. How can I overload constructors (or methods) in Python?

+(This actually applies to all methods, but somehow the question +usually comes up first in the context of constructors.) +

+Where in C++ you'd write +

+

+    class C {
+        C() { cout << "No arguments\n"; }
+        C(int i) { cout << "Argument is " << i << "\n"; }
+    }
+
+in Python you have to write a single constructor that catches all +cases using default arguments. For example: +

+

+    class C:
+        def __init__(self, i=None):
+            if i is None:
+                print "No arguments"
+            else:
+                print "Argument is", i
+
+This is not entirely equivalent, but close enough in practice. +

+You could also try a variable-length argument list, e.g. +

+

+        def __init__(self, *args):
+            ....
+
+The same approach works for all method definitions. +

+ +Edit this entry / +Log info + +/ Last changed on Mon Apr 20 11:55:55 1998 by +GvR +

+ +


+

4.76. How do I pass keyword arguments from one method to another?

+Use apply. For example: +

+

+    class Account:
+        def __init__(self, **kw):
+            self.accountType = kw.get('accountType')
+            self.balance = kw.get('balance')
+
+
+    class CheckingAccount(Account):
+        def __init__(self, **kw):
+            kw['accountType'] = 'checking'
+            apply(Account.__init__, (self,), kw)
+
+
+    myAccount = CheckingAccount(balance=100.00)
+
+In Python 2.0 you can call it directly using the new ** syntax: +

+

+    class CheckingAccount(Account):
+        def __init__(self, **kw):
+            kw['accountType'] = 'checking'
+            Account.__init__(self, **kw)
+
+or more generally: +

+

+ >>> def f(x, *y, **z):
+ ...  print x,y,z
+ ...
+ >>> Y = [1,2,3]
+ >>> Z = {'foo':3,'bar':None}
+ >>> f('hello', *Y, **Z)
+ hello (1, 2, 3) {'foo': 3, 'bar': None}
+
+

+ +Edit this entry / +Log info + +/ Last changed on Thu Dec 28 13:04:01 2000 by +Bjorn Pettersen +

+ +


+

4.77. What module should I use to help with generating HTML?

+Check out HTMLgen written by Robin Friedrich. It's a class library +of objects corresponding to all the HTML 3.2 markup tags. It's used +when you are writing in Python and wish to synthesize HTML pages for +generating a web or for CGI forms, etc. +

+It can be found in the FTP contrib area on python.org or on the +Starship. Use the search engines there to locate the latest version. +

+It might also be useful to consider DocumentTemplate, which offers clear +separation between Python code and HTML code. DocumentTemplate is part +of the Bobo objects publishing system (http:/www.digicool.com/releases) +but can be used independantly of course! +

+ +Edit this entry / +Log info + +/ Last changed on Fri Aug 28 09:54:58 1998 by +GvR +

+ +


+

4.78. How do I create documentation from doc strings?

+Use gendoc, by Daniel Larson. See +

+http://starship.python.net/crew/danilo/ +

+It can create HTML from the doc strings in your Python source code. +

+ +Edit this entry / +Log info + +/ Last changed on Mon Oct 7 17:15:51 2002 by +Phil Rittenhouse +

+ +


+

4.79. How do I read (or write) binary data?

+For complex data formats, it's best to use +use the struct module. It's documented in the library reference. +It allows you to take a string read from a file containing binary +data (usually numbers) and convert it to Python objects; and vice +versa. +

+For example, the following code reads two 2-byte integers +and one 4-byte integer in big-endian format from a file: +

+

+  import struct
+
+
+  f = open(filename, "rb")  # Open in binary mode for portability
+  s = f.read(8)
+  x, y, z = struct.unpack(">hhl", s)
+
+The '>' in the format string forces bin-endian data; the letter +'h' reads one "short integer" (2 bytes), and 'l' reads one +"long integer" (4 bytes) from the string. +

+For data that is more regular (e.g. a homogeneous list of ints or +floats), you can also use the array module, also documented +in the library reference. +

+ +Edit this entry / +Log info + +/ Last changed on Wed Oct 7 09:16:45 1998 by +GvR +

+ +


+

4.80. I can't get key bindings to work in Tkinter

+An oft-heard complaint is that event handlers bound to events +with the bind() method don't get handled even when the appropriate +key is pressed. +

+The most common cause is that the widget to which the binding applies +doesn't have "keyboard focus". Check out the Tk documentation +for the focus command. Usually a widget is given the keyboard +focus by clicking in it (but not for labels; see the taketocus +option). +

+ +Edit this entry / +Log info + +/ Last changed on Fri Jun 12 09:37:33 1998 by +GvR +

+ +


+

4.81. "import crypt" fails

+[Unix] +

+Starting with Python 1.5, the crypt module is disabled by default. +In order to enable it, you must go into the Python source tree and +edit the file Modules/Setup to enable it (remove a '#' sign in +front of the line starting with '#crypt'). Then rebuild. +You may also have to add the string '-lcrypt' to that same line. +

+ +Edit this entry / +Log info + +/ Last changed on Wed Aug 5 08:57:09 1998 by +GvR +

+ +


+

4.82. Are there coding standards or a style guide for Python programs?

+Yes, Guido has written the "Python Style Guide". See +http://www.python.org/doc/essays/styleguide.html +

+ +Edit this entry / +Log info + +/ Last changed on Tue Sep 29 09:50:27 1998 by +Joseph VanAndel +

+ +


+

4.83. How do I freeze Tkinter applications?

+Freeze is a tool to create stand-alone applications (see 4.28). +

+When freezing Tkinter applications, the applications will not be +truly stand-alone, as the application will still need the tcl and +tk libraries. +

+One solution is to ship the application with the tcl and tk libraries, +and point to them at run-time using the TCL_LIBRARY and TK_LIBRARY +environment variables. +

+To get truly stand-alone applications, the Tcl scripts that form +the library have to be integrated into the application as well. One +tool supporting that is SAM (stand-alone modules), which is part +of the Tix distribution (http://tix.mne.com). Build Tix with SAM +enabled, perform the appropriate call to Tclsam_init etc inside +Python's Modules/tkappinit.c, and link with libtclsam +and libtksam (you might include the Tix libraries as well). +

+ +Edit this entry / +Log info + +/ Last changed on Wed Jan 20 17:35:01 1999 by +Martin v. Lwis +

+ +


+

4.84. How do I create static class data and static class methods?

+[Tim Peters, tim_one@email.msn.com] +

+Static data (in the sense of C++ or Java) is easy; static methods (again in the sense of C++ or Java) are not supported directly. +

+STATIC DATA +

+For example, +

+

+    class C:
+        count = 0   # number of times C.__init__ called
+
+
+        def __init__(self):
+            C.count = C.count + 1
+
+
+        def getcount(self):
+            return C.count  # or return self.count
+
+c.count also refers to C.count for any c such that isinstance(c, C) holds, unless overridden by c itself or by some class on the base-class search path from c.__class__ back to C. +

+Caution: within a method of C, +

+

+    self.count = 42
+
+creates a new and unrelated instance vrbl named "count" in self's own dict. So rebinding of a class-static data name needs the +

+

+    C.count = 314
+
+form whether inside a method or not. +

+

+STATIC METHODS +

+Static methods (as opposed to static data) are unnatural in Python, because +

+

+    C.getcount
+
+returns an unbound method object, which can't be invoked without supplying an instance of C as the first argument. +

+The intended way to get the effect of a static method is via a module-level function: +

+

+    def getcount():
+        return C.count
+
+If your code is structured so as to define one class (or tightly related class hierarchy) per module, this supplies the desired encapsulation. +

+Several tortured schemes for faking static methods can be found by searching DejaNews. Most people feel such cures are worse than the disease. Perhaps the least obnoxious is due to Pekka Pessi (mailto:ppessi@hut.fi): +

+

+    # helper class to disguise function objects
+    class _static:
+        def __init__(self, f):
+            self.__call__ = f
+
+
+    class C:
+        count = 0
+
+
+        def __init__(self):
+            C.count = C.count + 1
+
+
+        def getcount():
+            return C.count
+        getcount = _static(getcount)
+
+
+        def sum(x, y):
+            return x + y
+        sum = _static(sum)
+
+
+    C(); C()
+    c = C()
+    print C.getcount()  # prints 3
+    print c.getcount()  # prints 3
+    print C.sum(27, 15) # prints 42
+
+

+ +Edit this entry / +Log info + +/ Last changed on Thu Jan 21 21:35:38 1999 by +Tim Peters +

+ +


+

4.85. __import__('x.y.z') returns <module 'x'>; how do I get z?

+Try +

+

+   __import__('x.y.z').y.z
+
+For more realistic situations, you may have to do something like +

+

+   m = __import__(s)
+   for i in string.split(s, ".")[1:]:
+       m = getattr(m, i)
+
+

+ +Edit this entry / +Log info + +/ Last changed on Thu Jan 28 11:01:43 1999 by +GvR +

+ +


+

4.86. Basic thread wisdom

+Please note that there is no way to take advantage of +multiprocessor hardware using the Python thread model. The interpreter +uses a global interpreter lock (GIL), +which does not allow multiple threads to be concurrently active. +

+If you write a simple test program like this: +

+

+  import thread
+  def run(name, n):
+      for i in range(n): print name, i
+  for i in range(10):
+      thread.start_new(run, (i, 100))
+
+none of the threads seem to run! The reason is that as soon as +the main thread exits, all threads are killed. +

+A simple fix is to add a sleep to the end of the program, +sufficiently long for all threads to finish: +

+

+  import thread, time
+  def run(name, n):
+      for i in range(n): print name, i
+  for i in range(10):
+      thread.start_new(run, (i, 100))
+  time.sleep(10) # <----------------------------!
+
+But now (on many platforms) the threads don't run in parallel, +but appear to run sequentially, one at a time! The reason is +that the OS thread scheduler doesn't start a new thread until +the previous thread is blocked. +

+A simple fix is to add a tiny sleep to the start of the run +function: +

+

+  import thread, time
+  def run(name, n):
+      time.sleep(0.001) # <---------------------!
+      for i in range(n): print name, i
+  for i in range(10):
+      thread.start_new(run, (i, 100))
+  time.sleep(10)
+
+Some more hints: +

+Instead of using a time.sleep() call at the end, it's +better to use some kind of semaphore mechanism. One idea is to +use a the Queue module to create a queue object, let each thread +append a token to the queue when it finishes, and let the main +thread read as many tokens from the queue as there are threads. +

+Use the threading module instead of the thread module. It's part +of Python since version 1.5.1. It takes care of all these details, +and has many other nice features too! +

+ +Edit this entry / +Log info + +/ Last changed on Fri Feb 7 16:21:55 2003 by +GvR +

+ +


+

4.87. Why doesn't closing sys.stdout (stdin, stderr) really close it?

+Python file objects are a high-level layer of abstraction on top of C streams, which in turn are a medium-level layer of abstraction on top of (among other things) low-level C file descriptors. +

+For most file objects f you create in Python via the builtin "open" function, f.close() marks the Python file object as being closed from Python's point of view, and also arranges to close the underlying C stream. This happens automatically too, in f's destructor, when f becomes garbage. +

+But stdin, stdout and stderr are treated specially by Python, because of the special status also given to them by C: doing +

+

+    sys.stdout.close() # ditto for stdin and stderr
+
+marks the Python-level file object as being closed, but does not close the associated C stream (provided sys.stdout is still bound to its default value, which is the stream C also calls "stdout"). +

+To close the underlying C stream for one of these three, you should first be sure that's what you really want to do (e.g., you may confuse the heck out of extension modules trying to do I/O). If it is, use os.close: +

+

+    os.close(0)   # close C's stdin stream
+    os.close(1)   # close C's stdout stream
+    os.close(2)   # close C's stderr stream
+
+

+ +Edit this entry / +Log info + +/ Last changed on Sat Apr 17 02:22:35 1999 by +Tim Peters +

+ +


+

4.88. What kinds of global value mutation are thread-safe?

+[adapted from c.l.py responses by Gordon McMillan & GvR] +

+A global interpreter lock (GIL) is used internally to ensure that only one thread runs in the Python VM at a time. In general, Python offers to switch among threads only between bytecode instructions (how frequently it offers to switch can be set via sys.setcheckinterval). Each bytecode instruction-- and all the C implementation code reached from it --is therefore atomic. +

+In theory, this means an exact accounting requires an exact understanding of the PVM bytecode implementation. In practice, it means that operations on shared vrbls of builtin data types (ints, lists, dicts, etc) that "look atomic" really are. +

+For example, these are atomic (L, L1, L2 are lists, D, D1, D2 are dicts, x, y +are objects, i, j are ints): +

+

+    L.append(x)
+    L1.extend(L2)
+    x = L[i]
+    x = L.pop()
+    L1[i:j] = L2
+    L.sort()
+    x = y
+    x.field = y
+    D[x] = y
+    D1.update(D2)
+    D.keys()
+
+These aren't: +

+

+    i = i+1
+    L.append(L[-1])
+    L[i] = L[j]
+    D[x] = D[x] + 1
+
+Note: operations that replace other objects may invoke those other objects' __del__ method when their reference count reaches zero, and that can affect things. This is especially true for the mass updates to dictionaries and lists. When in doubt, use a mutex! +

+ +Edit this entry / +Log info + +/ Last changed on Fri Feb 7 16:21:03 2003 by +GvR +

+ +


+

4.89. How do I modify a string in place?

+Strings are immutable (see question 6.2) so you cannot modify a string +directly. If you need an object with this ability, try converting the +string to a list or take a look at the array module. +

+

+    >>> s = "Hello, world"
+    >>> a = list(s)
+    >>> print a
+    ['H', 'e', 'l', 'l', 'o', ',', ' ', 'w', 'o', 'r', 'l', 'd']
+    >>> a[7:] = list("there!")
+    >>> import string
+    >>> print string.join(a, '')
+    'Hello, there!'
+
+
+    >>> import array
+    >>> a = array.array('c', s)
+    >>> print a
+    array('c', 'Hello, world')
+    >>> a[0] = 'y' ; print a
+    array('c', 'yello world')
+    >>> a.tostring()
+    'yello, world'
+
+

+ +Edit this entry / +Log info + +/ Last changed on Tue May 18 01:22:47 1999 by +Andrew Dalke +

+ +


+

4.90. How to pass on keyword/optional parameters/arguments

+Q: How can I pass on optional or keyword parameters from one function to another? +

+

+	def f1(a, *b, **c):
+		...
+
+A: In Python 2.0 and above: +

+

+	def f2(x, *y, **z):
+		...
+		z['width']='14.3c'
+		...
+		f1(x, *y, **z)
+
+
+   Note: y can be any sequence (e.g., list or tuple) and z must be a dict.
+
+

+A: For versions prior to 2.0, use 'apply', like: +

+

+	def f2(x, *y, **z):
+		...
+		z['width']='14.3c'
+		...
+		apply(f1, (x,)+y, z)
+
+

+ +Edit this entry / +Log info + +/ Last changed on Mon Jun 3 07:20:56 2002 by +Matthias Urlichs +

+ +


+

4.91. How can I get a dictionary to display its keys in a consistent order?

+In general, dictionaries store their keys in an unpredictable order, +so the display order of a dictionary's elements will be similarly +unpredictable. +(See +Question 6.12 +to understand why this is so.) +

+This can be frustrating if you want to save a printable version to a +file, make some changes and then compare it with some other printed +dictionary. If you have such needs you can subclass UserDict.UserDict +to create a SortedDict class that prints itself in a predictable order. +Here's one simpleminded implementation of such a class: +

+

+  import UserDict, string
+
+
+  class SortedDict(UserDict.UserDict):
+    def __repr__(self):
+      result = []
+      append = result.append
+      keys = self.data.keys()
+      keys.sort()
+      for k in keys:
+        append("%s: %s" % (`k`, `self.data[k]`))
+      return "{%s}" % string.join(result, ", ")
+
+
+    ___str__ = __repr__
+
+

+This will work for many common situations you might encounter, though +it's far from a perfect solution. (It won't have any effect on the +pprint module and does not transparently handle values that are or +contain dictionaries. +

+ +Edit this entry / +Log info + +/ Last changed on Thu Sep 16 17:31:06 1999 by +Skip Montanaro +

+ +


+

4.92. Is there a Python tutorial?

+Yes. See question 1.20 at +http://www.python.org/doc/FAQ.html#1.20 +

+ +Edit this entry / +Log info + +/ Last changed on Sat Dec 4 16:04:00 1999 by +TAB +

+ +


+

4.93. Deleted

+See 4.28 +

+ +Edit this entry / +Log info + +/ Last changed on Tue May 28 20:40:37 2002 by +GvR +

+ +


+

4.94. How do I get a single keypress without blocking?

+There are several solutions; some involve using curses, which is a +pretty big thing to learn. Here's a solution without curses. (see also 4.74, for Windows, see question 8.2) +

+

+  import termios, fcntl, sys, os
+  fd = sys.stdin.fileno()
+
+
+  oldterm = termios.tcgetattr(fd)
+  newattr = termios.tcgetattr(fd)
+  newattr[3] = newattr[3] & ~termios.ICANON & ~termios.ECHO
+  termios.tcsetattr(fd, termios.TCSANOW, newattr)
+
+
+  oldflags = fcntl.fcntl(fd, fcntl.F_GETFL)
+  fcntl.fcntl(fd, fcntl.F_SETFL, oldflags | os.O_NONBLOCK)
+
+
+  try:
+      while 1:
+          try:
+              c = sys.stdin.read(1)
+              print "Got character", `c`
+          except IOError: pass
+  finally:
+      termios.tcsetattr(fd, termios.TCSAFLUSH, oldterm)
+      fcntl.fcntl(fd, fcntl.F_SETFL, oldflags)
+
+

+You need the termios and the fcntl module for any of this to work, +and I've only tried it on Linux, though it should work elsewhere. +

+In this code, characters are read and printed one at a time. +

+termios.tcsetattr() turns off stdin's echoing and disables canonical +mode. fcntl.fnctl() is used to obtain stdin's file descriptor flags +and modify them for non-blocking mode. Since reading stdin when it is +empty results in an IOError, this error is caught and ignored. +

+ +Edit this entry / +Log info + +/ Last changed on Thu Oct 24 00:39:06 2002 by +chris +

+ +


+

4.95. Is there an equivalent to Perl chomp()? (Remove trailing newline from string)

+There are two partial substitutes. If you want to remove all trailing +whitespace, use the method string.rstrip(). Otherwise, if there is only +one line in the string, use string.splitlines()[0]. +

+

+ -----------------------------------------------------------------------
+
+
+ rstrip() is too greedy, it strips all trailing white spaces.
+ splitlines() takes ControlM as line boundary.
+ Consider these strings as input:
+   "python python    \r\n"
+   "python\rpython\r\n"
+   "python python   \r\r\r\n"
+ The results from rstrip()/splitlines() are perhaps not what we want.
+
+
+ It seems re can perform this task.
+
+

+

+ #!/usr/bin/python 
+ # requires python2                                                             
+
+
+ import re, os, StringIO
+
+
+ lines=StringIO.StringIO(
+   "The Python Programming Language\r\n"
+   "The Python Programming Language \r \r \r\r\n"
+   "The\rProgramming\rLanguage\r\n"
+   "The\rProgramming\rLanguage\r\r\r\r\n"
+   "The\r\rProgramming\r\rLanguage\r\r\r\r\n"
+ )
+
+
+ ln=re.compile("(?:[\r]?\n|\r)$") # dos:\r\n, unix:\n, mac:\r, others: unknown
+ # os.linesep does not work if someone ftps(in binary mode) a dos/mac text file
+ # to your unix box
+ #ln=re.compile(os.linesep + "$")
+
+
+ while 1:
+   s=lines.readline()
+   if not s: break
+   print "1.(%s)" % `s.rstrip()`
+   print "2.(%s)" % `ln.sub( "", s, 1)`
+   print "3.(%s)" % `s.splitlines()[0]`
+   print "4.(%s)" % `s.splitlines()`
+   print
+
+
+ lines.close()
+
+

+ +Edit this entry / +Log info + +/ Last changed on Wed Aug 8 09:51:34 2001 by +Crystal +

+ +


+

4.96. Why is join() a string method when I'm really joining the elements of a (list, tuple, sequence)?

+Strings became much more like other standard types starting in release 1.6, when methods were added which give the same functionality that has always been available using the functions of the string module. These new methods have been widely accepted, but the one which appears to make (some) programmers feel uncomfortable is: +

+

+    ", ".join(['1', '2', '4', '8', '16'])
+
+which gives the result +

+

+    "1, 2, 4, 8, 16"
+
+There are two usual arguments against this usage. +

+The first runs along the lines of: "It looks really ugly using a method of a string literal (string constant)", to which the answer is that it might, but a string literal is just a fixed value. If the methods are to be allowed on names bound to strings there is no logical reason to make them unavailable on literals. Get over it! +

+The second objection is typically cast as: "I am really telling a sequence to join its members together with a string constant". Sadly, you aren't. For some reason there seems to be much less difficulty with having split() as a string method, since in that case it is easy to see that +

+

+    "1, 2, 4, 8, 16".split(", ")
+
+is an instruction to a string literal to return the substrings delimited by the given separator (or, by default, arbitrary runs of white space). In this case a Unicode string returns a list of Unicode strings, an ASCII string returns a list of ASCII strings, and everyone is happy. +

+join() is a string method because in using it you are telling the separator string to iterate over an arbitrary sequence, forming string representations of each of the elements, and inserting itself between the elements' representations. This method can be used with any argument which obeys the rules for sequence objects, inluding any new classes you might define yourself. +

+Because this is a string method it can work for Unicode strings as well as plain ASCII strings. If join() were a method of the sequence types then the sequence types would have to decide which type of string to return depending on the type of the separator. +

+If none of these arguments persuade you, then for the moment you can continue to use the join() function from the string module, which allows you to write +

+

+    string.join(['1', '2', '4', '8', '16'], ", ")
+
+You will just have to try and forget that the string module actually uses the syntax you are compaining about to implement the syntax you prefer! +

+ +Edit this entry / +Log info + +/ Last changed on Fri Aug 2 15:51:58 2002 by +Steve Holden +

+ +


+

4.97. How can my code discover the name of an object?

+Generally speaking, it can't, because objects don't really have names. The assignment statement does not store the assigned value in the name but a reference to it. Essentially, assignment creates a binding of a name to a value. The same is true of def and class statements, but in that case the value is a callable. Consider the following code: +

+

+    class A:
+        pass
+
+
+    B = A
+
+
+    a = B()
+    b = a
+    print b
+    <__main__.A instance at 016D07CC>
+    print a
+    <__main__.A instance at 016D07CC>
+
+

+Arguably the class has a name: even though it is bound to two names and invoked through the name B the created instance is still reported as an instance of class A. However, it is impossible to say whether the instance's name is a or b, since both names are bound to the same value. +

+Generally speaking it should not be necessary for your code to "know the names" of particular values. Unless you are deliberately writing introspective programs, this is usually an indication that a change of approach might be beneficial. +

+ +Edit this entry / +Log info + +/ Last changed on Thu Mar 8 03:53:39 2001 by +Steve Holden +

+ +


+

4.98. Why are floating point calculations so inaccurate?

+The development version of the Python Tutorial now contains an Appendix with more info: +
+    http://www.python.org/doc/current/tut/node14.html
+
+People are often very surprised by results like this: +

+

+ >>> 1.2-1.0
+ 0.199999999999999996
+
+And think it is a bug in Python. It's not. It's a problem caused by +the internal representation of a floating point number. A floating point +number is stored as a fixed number of binary digits. +

+In decimal math, there are many numbers that can't be represented +with a fixed number of decimal digits, i.e. +1/3 = 0.3333333333....... +

+In the binary case, 1/2 = 0.1, 1/4 = 0.01, 1/8 = 0.001, etc. There are +a lot of numbers that can't be represented. The digits are cut off at +some point. +

+Since Python 1.6, a floating point's repr() function prints as many +digits are necessary to make eval(repr(f)) == f true for any float f. +The str() function prints the more sensible number that was probably +intended: +

+

+ >>> 0.2
+ 0.20000000000000001
+ >>> print 0.2
+ 0.2
+
+Again, this has nothing to do with Python, but with the way the +underlying C platform handles floating points, and ultimately with +the inaccuracy you'll always have when writing down numbers of fixed +number of digit strings. +

+One of the consequences of this is that it is dangerous to compare +the result of some computation to a float with == ! +Tiny inaccuracies may mean that == fails. +

+Instead try something like this: +

+

+ epsilon = 0.0000000000001 # Tiny allowed error
+ expected_result = 0.4
+
+
+ if expected_result-epsilon <= computation() <= expected_result+epsilon:
+    ...
+
+

+ +Edit this entry / +Log info + +/ Last changed on Mon Apr 1 22:18:47 2002 by +Fred Drake +

+ +


+

4.99. I tried to open Berkeley DB file, but bsddb produces bsddb.error: (22, 'Invalid argument'). Help! How can I restore my data?

+Don't panic! Your data are probably intact. The most frequent cause +for the error is that you tried to open an earlier Berkeley DB file +with a later version of the Berkeley DB library. +

+Many Linux systems now have all three versions of Berkeley DB +available. If you are migrating from version 1 to a newer version use +db_dump185 to dump a plain text version of the database. +If you are migrating from version 2 to version 3 use db2_dump to create +a plain text version of the database. In either case, use db_load to +create a new native database for the latest version installed on your +computer. If you have version 3 of Berkeley DB installed, you should +be able to use db2_load to create a native version 2 database. +

+You should probably move away from Berkeley DB version 1 files because +the hash file code contains known bugs that can corrupt your data. +

+ +Edit this entry / +Log info + +/ Last changed on Wed Aug 29 16:04:29 2001 by +Skip Montanaro +

+ +


+

4.100. What are the "best practices" for using import in a module?

+First, the standard modules are great. Use them! The standard Python library is large and varied. Using modules can save you time and effort and will reduce maintainenance cost of your code. (Other programs are dedicated to supporting and fixing bugs in the standard Python modules. Coworkers may also be familiar with themodules that you use, reducing the amount of time it takes them to understand your code.) +

+The rest of this answer is largely a matter of personal preference, but here's what some newsgroup posters said (thanks to all who responded) +

+In general, don't use +

+ from modulename import *
+
+Doing so clutters the importer's namespace. Some avoid this idiom even with the few modules that were designed to be imported in this manner. (Modules designed in this manner include Tkinter, thread, and wxPython.) +

+Import modules at the top of a file, one module per line. Doing so makes it clear what other modules your code requires and avoids questions of whether the module name is in scope. Using one import per line makes it easy to add and delete module imports. +

+Move imports into a local scope (such as at the top of a function definition) if there are a lot of imports, and you're trying to avoid the cost (lots of initialization time) of many imports. This technique is especially helpful if many of the imports are unnecessary depending on how the program executes. You may also want to move imports into a function if the modules are only ever used in that function. Note that loading a module the first time may be expensive (because of the one time initialization of the module) but that loading a module multiple times is virtually free (a couple of dictionary lookups). Even if the module name has gone out of scope, the module is probably available in sys.modules. Thus, there isn't really anything wrong with putting no imports at the module level (if they aren't needed) and putting all of the imports at the function level. +

+It is sometimes necessary to move imports to a function or class to avoid problems with circular imports. Gordon says: +

+ Circular imports are fine where both modules use the "import <module>"
+ form of import. They fail when the 2nd module wants to grab a name
+ out of the first ("from module import name") and the import is at
+ the top level. That's because names in the 1st are not yet available,
+ (the first module is busy importing the 2nd).  
+
+In this case, if the 2nd module is only used in one function, then the import can easily be moved into that function. By the time the import is called, the first module will have finished initializing, and the second module can do its import. +

+It may also be necessary to move imports out of the top level of code +if some of the modules are platform-specific. In that case, it may not even be possible to import all of the modules at the top of the file. In this case, importing the correct modules in the corresponding platform-specific code is a good option. +

+If only instances of a specific class uses a module, then it is reasonable to import the module in the class's __init__ method and then assign the module to an instance variable so that the module is always available (via that instance variable) during the life of the object. Note that to delay an import until the class is instantiated, the import must be inside a method. Putting the import inside the class but outside of any method still causes the import to occur when the module is initialized. +

+ +Edit this entry / +Log info + +/ Last changed on Sat Aug 4 04:44:47 2001 by +TAB +

+ +


+

4.101. Is there a tool to help find bugs or perform static analysis?

+Yes. PyChecker is a static analysis tool for finding bugs +in Python source code as well as warning about code complexity +and style. +

+You can get PyChecker from: http://pychecker.sf.net. +

+ +Edit this entry / +Log info + +/ Last changed on Fri Aug 10 15:42:11 2001 by +Neal +

+ +


+

4.102. UnicodeError: ASCII [decoding,encoding] error: ordinal not in range(128)

+This error indicates that your Python installation can handle +only 7-bit ASCII strings. There are a couple ways to fix or +workaround the problem. +

+If your programs must handle data in arbitary character set encodings, the environment the application runs in will generally identify the encoding of the data it is handing you. You need to convert the input to Unicode data using that encoding. For instance, a program that handles email or web input will typically find character set encoding information in Content-Type headers. This can then be used to properly convert input data to Unicode. Assuming the string referred to by "value" is encoded as UTF-8: +

+

+    value = unicode(value, "utf-8")
+
+will return a Unicode object. If the data is not correctly encoded as UTF-8, the above call will raise a UnicodeError. +

+If you only want strings coverted to Unicode which have non-ASCII data, you can try converting them first assuming an ASCII encoding, and then generate Unicode objects if that fails: +

+

+    try:
+        x = unicode(value, "ascii")
+    except UnicodeError:
+        value = unicode(value, "utf-8")
+    else:
+        # value was valid ASCII data
+        pass
+
+

+If you normally use a character set encoding other than US-ASCII and only need to handle data in that encoding, the simplest way to fix the problem may be simply to set the encoding in sitecustomize.py. The following code is just a modified version of the encoding setup code from site.py with the relevant lines uncommented. +

+

+    # Set the string encoding used by the Unicode implementation.
+    # The default is 'ascii'
+    encoding = "ascii" # <= CHANGE THIS if you wish
+
+
+    # Enable to support locale aware default string encodings.
+    import locale
+    loc = locale.getdefaultlocale()
+    if loc[1]:
+        encoding = loc[1]
+    if encoding != "ascii":
+        import sys
+        sys.setdefaultencoding(encoding)
+
+

+Also note that on Windows, there is an encoding known as "mbcs", which uses an encoding specific to your current locale. In many cases, and particularly when working with COM, this may be an appropriate default encoding to use. +

+ +Edit this entry / +Log info + +/ Last changed on Sat Apr 13 04:45:41 2002 by +Skip Montanaro +

+ +


+

4.103. Using strings to call functions/methods

+There are various techniques: +

+* Use a dictionary pre-loaded with strings and functions. The primary +advantage of this technique is that the strings do not need to match the +names of the functions. This is also the primary technique used to +emulate a case construct: +

+

+    def a():
+        pass
+
+
+    def b():
+        pass
+
+
+    dispatch = {'go': a, 'stop': b}  # Note lack of parens for funcs
+
+
+    dispatch[get_input()]()  # Note trailing parens to call function
+
+* Use the built-in function getattr(): +

+

+    import foo
+    getattr(foo, 'bar')()
+
+Note that getattr() works on any object, including classes, class +instances, modules, and so on. +

+This is used in several places in the standard library, like +this: +

+

+    class Foo:
+        def do_foo(self):
+            ...
+
+
+        def do_bar(self):
+            ...
+
+
+     f = getattr(foo_instance, 'do_' + opname)
+     f()
+
+

+* Use locals() or eval() to resolve the function name: +

+def myFunc(): +

+    print "hello"
+
+fname = "myFunc" +

+f = locals()[fname] +f() +

+f = eval(fname) +f() +

+Note: Using eval() can be dangerous. If you don't have absolute control +over the contents of the string, all sorts of things could happen... +

+ +Edit this entry / +Log info + +/ Last changed on Thu Mar 21 08:14:58 2002 by +Erno Kuusela +

+ +


+

4.104. How fast are exceptions?

+A try/except block is extremely efficient. Actually executing an +exception is expensive. In older versions of Python (prior to 2.0), it +was common to code this idiom: +

+

+    try:
+        value = dict[key]
+    except KeyError:
+        dict[key] = getvalue(key)
+        value = dict[key]
+
+This idiom only made sense when you expected the dict to have the key +95% of the time or more; other times, you coded it like this: +

+

+    if dict.has_key(key):
+        value = dict[key]
+    else:
+        dict[key] = getvalue(key)
+        value = dict[key]
+
+In Python 2.0 and higher, of course, you can code this as +

+

+    value = dict.setdefault(key, getvalue(key))
+
+However this evaluates getvalue(key) always, regardless of whether it's needed or not. So if it's slow or has a side effect you should use one of the above variants. +

+ +Edit this entry / +Log info + +/ Last changed on Mon Dec 9 10:12:30 2002 by +Yeti +

+ +


+

4.105. Sharing global variables across modules

+The canonical way to share information across modules within a single +program is to create a special module (often called config or cfg). +Just import the config module in all modules of your application; the +module then becomes available as a global name. Because there is only +one instance of each module, any changes made to the module object get +reflected everywhere. For example: +

+config.py: +

+

+    pass
+
+mod.py: +

+

+    import config
+    config.x = 1
+
+main.py: +

+

+    import config
+    import mod
+    print config.x
+
+Note that using a module is also the basis for implementing the +Singleton design pattern, for the same reason. +

+ +Edit this entry / +Log info + +/ Last changed on Tue Apr 23 23:07:19 2002 by +Aahz +

+ +


+

4.106. Why is cPickle so slow?

+Use the binary option. We'd like to make that the default, but it would +break backward compatibility: +

+

+    largeString = 'z' * (100 * 1024)
+    myPickle = cPickle.dumps(largeString, 1)
+
+

+ +Edit this entry / +Log info + +/ Last changed on Thu Aug 22 19:54:25 2002 by +Aahz +

+ +


+

4.107. When importing module XXX, why do I get "undefined symbol: PyUnicodeUCS2_..." ?

+You are using a version of Python that uses a 4-byte representation for +Unicode characters, but the extension module you are importing (possibly +indirectly) was compiled using a Python that uses a 2-byte representation +for Unicode characters (the default). +

+If instead the name of the undefined symbol starts with PyUnicodeUCS4_, +the problem is the same by the relationship is reversed: Python was +built using 2-byte Unicode characters, and the extension module was +compiled using a Python with 4-byte Unicode characters. +

+This can easily occur when using pre-built extension packages. RedHat +Linux 7.x, in particular, provides a "python2" binary that is compiled +with 4-byte Unicode. This only causes the link failure if the extension +uses any of the PyUnicode_*() functions. It is also a problem if if an +extension uses any of the Unicode-related format specifiers for +Py_BuildValue (or similar) or parameter-specifications for +PyArg_ParseTuple(). +

+You can check the size of the Unicode character a Python interpreter is +using by checking the value of sys.maxunicode: +

+

+  >>> import sys
+  >>> if sys.maxunicode > 65535:
+  ...     print 'UCS4 build'
+  ... else:
+  ...     print 'UCS2 build'
+
+The only way to solve this problem is to use extension modules compiled +with a Python binary built using the same size for Unicode characters. +

+ +Edit this entry / +Log info + +/ Last changed on Tue Aug 27 15:00:17 2002 by +Fred Drake +

+ +


+

4.108. How do I create a .pyc file?

+QUESTION: +

+I have a module and I wish to generate a .pyc file. +How do I do it? Everything I read says that generation of a .pyc file is +"automatic", but I'm not getting anywhere. +

+

+ANSWER: +

+When a module is imported for the first time (or when the source is more +recent than the current compiled file) a .pyc file containing the compiled code should be created in the +same directory as the .py file. +

+One reason that a .pyc file may not be created is permissions problems with the directory. This can happen, for example, if you develop as one user but run as another, such as if you are testing with a web server. +

+However, in most cases, that's not the problem. +

+Creation of a .pyc file is "automatic" if you are importing a module and Python has the +ability (permissions, free space, etc...) to write the compiled module +back to the directory. But note that running Python on a top level script is not considered an +import and so no .pyc will be created automatically. For example, if you have a top-level module abc.py that imports another module xyz.py, when you run abc, xyz.pyc will be created since xyz is imported, but no abc.pyc file will be created since abc isn't imported. +

+If you need to create abc.pyc -- that is, to create a .pyc file for a +module that is not imported -- you can. (Look up +the py_compile and compileall modules in the Library Reference.) +

+You can manually compile any module using the "py_compile" module. One +way is to use the compile() function in that module interactively: +

+

+    >>> import py_compile
+    >>> py_compile.compile('abc.py')
+
+This will write the .pyc to the same location as abc.py (or you +can override that with the optional parameter cfile). +

+You can also automatically compile all files in a directory or +directories using the "compileall" module, which can also be run +straight from the command line. +

+You can do it from the shell (or DOS) prompt by entering: +

+       python compile.py abc.py
+
+or +
+       python compile.py *
+
+Or you can write a script to do it on a list of filenames that you enter. +

+

+     import sys
+     from py_compile import compile
+
+
+     if len(sys.argv) <= 1:
+        sys.exit(1)
+
+
+     for file in sys.argv[1:]:
+        compile(file)
+
+ACKNOWLEDGMENTS: +

+Steve Holden, David Bolen, Rich Somerfield, Oleg Broytmann, Steve Ferg +

+ +Edit this entry / +Log info + +/ Last changed on Wed Feb 12 15:58:25 2003 by +Stephen Ferg +

+ +


+

5. Extending Python

+ +
+

5.1. Can I create my own functions in C?

+Yes, you can create built-in modules containing functions, +variables, exceptions and even new types in C. This is explained in +the document "Extending and Embedding the Python Interpreter" (http://www.python.org/doc/current/ext/ext.html). Also read the chapter +on dynamic loading. +

+There's more information on this in each of the Python books: +Programming Python, Internet Programming with Python, and Das Python-Buch +(in German). +

+ +Edit this entry / +Log info + +/ Last changed on Mon Dec 10 05:18:57 2001 by +Fred L. Drake, Jr. +

+ +


+

5.2. Can I create my own functions in C++?

+Yes, using the C-compatibility features found in C++. Basically +you place extern "C" { ... } around the Python include files and put +extern "C" before each function that is going to be called by the +Python interpreter. Global or static C++ objects with constructors +are probably not a good idea. +

+ +Edit this entry / +Log info +

+ +


+

5.3. How can I execute arbitrary Python statements from C?

+The highest-level function to do this is PyRun_SimpleString() which takes +a single string argument which is executed in the context of module +__main__ and returns 0 for success and -1 when an exception occurred +(including SyntaxError). If you want more control, use PyRun_String(); +see the source for PyRun_SimpleString() in Python/pythonrun.c. +

+ +Edit this entry / +Log info + +/ Last changed on Fri May 23 20:08:14 1997 by +Bill Tutt +

+ +


+

5.4. How can I evaluate an arbitrary Python expression from C?

+Call the function PyRun_String() from the previous question with the +start symbol eval_input (Py_eval_input starting with 1.5a1); it +parses an expression, evaluates it and returns its value. +

+ +Edit this entry / +Log info + +/ Last changed on Wed May 21 22:23:18 1997 by +David Ascher +

+ +


+

5.5. How do I extract C values from a Python object?

+That depends on the object's type. If it's a tuple, +PyTupleSize(o) returns its length and PyTuple_GetItem(o, i) +returns its i'th item; similar for lists with PyListSize(o) +and PyList_GetItem(o, i). For strings, PyString_Size(o) returns +its length and PyString_AsString(o) a pointer to its value +(note that Python strings may contain null bytes so strlen() +is not safe). To test which type an object is, first make sure +it isn't NULL, and then use PyString_Check(o), PyTuple_Check(o), +PyList_Check(o), etc. +

+There is also a high-level API to Python objects which is +provided by the so-called 'abstract' interface -- read +Include/abstract.h for further details. It allows for example +interfacing with any kind of Python sequence (e.g. lists and tuples) +using calls like PySequence_Length(), PySequence_GetItem(), etc.) +as well as many other useful protocols. +

+ +Edit this entry / +Log info + +/ Last changed on Wed May 21 22:34:20 1997 by +David Ascher +

+ +


+

5.6. How do I use Py_BuildValue() to create a tuple of arbitrary length?

+You can't. Use t = PyTuple_New(n) instead, and fill it with +objects using PyTuple_SetItem(t, i, o) -- note that this "eats" a +reference count of o. Similar for lists with PyList_New(n) and +PyList_SetItem(l, i, o). Note that you must set all the tuple items to +some value before you pass the tuple to Python code -- +PyTuple_New(n) initializes them to NULL, which isn't a valid Python +value. +

+ +Edit this entry / +Log info + +/ Last changed on Thu Jul 31 18:15:29 1997 by +Guido van Rossum +

+ +


+

5.7. How do I call an object's method from C?

+The PyObject_CallMethod() function can be used to call an arbitrary +method of an object. The parameters are the object, the name of the +method to call, a format string like that used with Py_BuildValue(), and the argument values: +

+

+    PyObject *
+    PyObject_CallMethod(PyObject *object, char *method_name,
+                        char *arg_format, ...);
+
+This works for any object that has methods -- whether built-in or +user-defined. You are responsible for eventually DECREF'ing the +return value. +

+To call, e.g., a file object's "seek" method with arguments 10, 0 +(assuming the file object pointer is "f"): +

+

+        res = PyObject_CallMethod(f, "seek", "(ii)", 10, 0);
+        if (res == NULL) {
+                ... an exception occurred ...
+        }
+        else {
+                Py_DECREF(res);
+        }
+
+Note that since PyObject_CallObject() always wants a tuple for the +argument list, to call a function without arguments, pass "()" for the +format, and to call a function with one argument, surround the argument +in parentheses, e.g. "(i)". +

+ +Edit this entry / +Log info + +/ Last changed on Thu Jun 6 16:15:46 2002 by +Neal Norwitz +

+ +


+

5.8. How do I catch the output from PyErr_Print() (or anything that prints to stdout/stderr)?

+(Due to Mark Hammond): +

+In Python code, define an object that supports the "write()" method. +Redirect sys.stdout and sys.stderr to this object. +Call print_error, or just allow the standard traceback mechanism to +work. Then, the output will go wherever your write() method sends it. +

+The easiest way to do this is to use the StringIO class in the standard +library. +

+Sample code and use for catching stdout: +

+	>>> class StdoutCatcher:
+	...  def __init__(self):
+	...   self.data = ''
+	...  def write(self, stuff):
+	...   self.data = self.data + stuff
+	...  
+	>>> import sys
+	>>> sys.stdout = StdoutCatcher()
+	>>> print 'foo'
+	>>> print 'hello world!'
+	>>> sys.stderr.write(sys.stdout.data)
+	foo
+	hello world!
+
+

+ +Edit this entry / +Log info + +/ Last changed on Wed Dec 16 18:34:25 1998 by +Richard Jones +

+ +


+

5.9. How do I access a module written in Python from C?

+You can get a pointer to the module object as follows: +

+

+        module = PyImport_ImportModule("<modulename>");
+
+If the module hasn't been imported yet (i.e. it is not yet present in +sys.modules), this initializes the module; otherwise it simply returns +the value of sys.modules["<modulename>"]. Note that it doesn't enter +the module into any namespace -- it only ensures it has been +initialized and is stored in sys.modules. +

+You can then access the module's attributes (i.e. any name defined in +the module) as follows: +

+

+        attr = PyObject_GetAttrString(module, "<attrname>");
+
+Calling PyObject_SetAttrString(), to assign to variables in the module, also works. +

+ +Edit this entry / +Log info + +/ Last changed on Wed May 21 22:56:40 1997 by +david ascher +

+ +


+

5.10. How do I interface to C++ objects from Python?

+Depending on your requirements, there are many approaches. To do +this manually, begin by reading the "Extending and Embedding" document +(Doc/ext.tex, see also http://www.python.org/doc/). Realize +that for the Python run-time system, there isn't a whole lot of +difference between C and C++ -- so the strategy to build a new Python +type around a C structure (pointer) type will also work for C++ +objects. +

+A useful automated approach (which also works for C) is SWIG: +http://www.swig.org/. +

+ +Edit this entry / +Log info + +/ Last changed on Fri Oct 15 05:14:01 1999 by +Sjoerd Mullender +

+ +


+

5.11. mSQLmodule (or other old module) won't build with Python 1.5 (or later)

+Since python-1.4 "Python.h" will have the file includes needed in an +extension module. +Backward compatibility is dropped after version 1.4 and therefore +mSQLmodule.c will not build as "allobjects.h" cannot be found. +The following change in mSQLmodule.c is harmless when building it with +1.4 and necessary when doing so for later python versions: +

+Remove lines: +

+

+	#include "allobjects.h"
+	#include "modsupport.h"
+
+And insert instead: +

+

+	#include "Python.h"
+
+You may also need to add +

+

+                #include "rename2.h"
+
+if the module uses "old names". +

+This may happen with other ancient python modules as well, +and the same fix applies. +

+ +Edit this entry / +Log info + +/ Last changed on Sun Dec 21 02:03:35 1997 by +GvR +

+ +


+

5.12. I added a module using the Setup file and the make fails! Huh?

+Setup must end in a newline, if there is no newline there it gets +very sad. Aside from this possibility, maybe you have other +non-Python-specific linkage problems. +

+ +Edit this entry / +Log info + +/ Last changed on Tue Jun 24 15:54:01 1997 by +aaron watters +

+ +


+

5.13. I want to compile a Python module on my Red Hat Linux system, but some files are missing.

+Red Hat's RPM for Python doesn't include the +/usr/lib/python1.x/config/ directory, which contains various files required +for compiling Python extensions. +Install the python-devel RPM to get the necessary files. +

+ +Edit this entry / +Log info + +/ Last changed on Tue Jan 26 13:44:04 1999 by +A.M. Kuchling +

+ +


+

5.14. What does "SystemError: _PyImport_FixupExtension: module yourmodule not loaded" mean?

+This means that you have created an extension module named "yourmodule", but your module init function does not initialize with that name. +

+Every module init function will have a line similar to: +

+

+  module = Py_InitModule("yourmodule", yourmodule_functions);
+
+If the string passed to this function is not the same name as your extenion module, the SystemError will be raised. +

+ +Edit this entry / +Log info + +/ Last changed on Thu Mar 25 07:16:08 1999 by +Mark Hammond +

+ +


+

5.15. How to tell "incomplete input" from "invalid input"?

+Sometimes you want to emulate the Python interactive interpreter's +behavior, where it gives you a continuation prompt when the input +is incomplete (e.g. you typed the start of an "if" statement +or you didn't close your parentheses or triple string quotes), +but it gives you a syntax error message immediately when the input +is invalid. +

+In Python you can use the codeop module, which approximates the +parser's behavior sufficiently. IDLE uses this, for example. +

+The easiest way to do it in C is to call PyRun_InteractiveLoop() +(in a separate thread maybe) and let the Python interpreter handle +the input for you. You can also set the PyOS_ReadlineFunctionPointer +to point at your custom input function. See Modules/readline.c and +Parser/myreadline.c for more hints. +

+However sometimes you have to run the embedded Python interpreter +in the same thread as your rest application and you can't allow the +PyRun_InteractiveLoop() to stop while waiting for user input. +The one solution then is to call PyParser_ParseString() +and test for e.error equal to E_EOF (then the input is incomplete). +Sample code fragment, untested, inspired by code from Alex Farber: +

+

+  #include <Python.h>
+  #include <node.h>
+  #include <errcode.h>
+  #include <grammar.h>
+  #include <parsetok.h>
+  #include <compile.h>
+
+
+  int testcomplete(char *code)
+    /* code should end in \n */
+    /* return -1 for error, 0 for incomplete, 1 for complete */
+  {
+    node *n;
+    perrdetail e;
+
+
+    n = PyParser_ParseString(code, &_PyParser_Grammar,
+                             Py_file_input, &e);
+    if (n == NULL) {
+      if (e.error == E_EOF) 
+        return 0;
+      return -1;
+    }
+
+
+    PyNode_Free(n);
+    return 1;
+  }
+
+Another solution is trying to compile the received string with +Py_CompileString(). If it compiles fine - try to execute the returned +code object by calling PyEval_EvalCode(). Otherwise save the input for +later. If the compilation fails, find out if it's an error or just +more input is required - by extracting the message string from the +exception tuple and comparing it to the "unexpected EOF while parsing". +Here is a complete example using the GNU readline library (you may +want to ignore SIGINT while calling readline()): +

+

+  #include <stdio.h>
+  #include <readline.h>
+
+
+  #include <Python.h>
+  #include <object.h>
+  #include <compile.h>
+  #include <eval.h>
+
+
+  int main (int argc, char* argv[])
+  {
+    int i, j, done = 0;                          /* lengths of line, code */
+    char ps1[] = ">>> ";
+    char ps2[] = "... ";
+    char *prompt = ps1;
+    char *msg, *line, *code = NULL;
+    PyObject *src, *glb, *loc;
+    PyObject *exc, *val, *trb, *obj, *dum;
+
+
+    Py_Initialize ();
+    loc = PyDict_New ();
+    glb = PyDict_New ();
+    PyDict_SetItemString (glb, "__builtins__", PyEval_GetBuiltins ());
+
+
+    while (!done)
+    {
+      line = readline (prompt);
+
+
+      if (NULL == line)                          /* CTRL-D pressed */
+      {
+        done = 1;
+      }
+      else
+      {
+        i = strlen (line);
+
+
+        if (i > 0)
+          add_history (line);                    /* save non-empty lines */
+
+
+        if (NULL == code)                        /* nothing in code yet */
+          j = 0;
+        else
+          j = strlen (code);
+
+
+        code = realloc (code, i + j + 2);
+        if (NULL == code)                        /* out of memory */
+          exit (1);
+
+
+        if (0 == j)                              /* code was empty, so */
+          code[0] = '\0';                        /* keep strncat happy */
+
+
+        strncat (code, line, i);                 /* append line to code */
+        code[i + j] = '\n';                      /* append '\n' to code */
+        code[i + j + 1] = '\0';
+
+
+        src = Py_CompileString (code, "<stdin>", Py_single_input);       
+
+
+        if (NULL != src)                         /* compiled just fine - */
+        {
+          if (ps1  == prompt ||                  /* ">>> " or */
+              '\n' == code[i + j - 1])           /* "... " and double '\n' */
+          {                                               /* so execute it */
+            dum = PyEval_EvalCode ((PyCodeObject *)src, glb, loc);
+            Py_XDECREF (dum);
+            Py_XDECREF (src);
+            free (code);
+            code = NULL;
+            if (PyErr_Occurred ())
+              PyErr_Print ();
+            prompt = ps1;
+          }
+        }                                        /* syntax error or E_EOF? */
+        else if (PyErr_ExceptionMatches (PyExc_SyntaxError))           
+        {
+          PyErr_Fetch (&exc, &val, &trb);        /* clears exception! */
+
+
+          if (PyArg_ParseTuple (val, "sO", &msg, &obj) &&
+              !strcmp (msg, "unexpected EOF while parsing")) /* E_EOF */
+          {
+            Py_XDECREF (exc);
+            Py_XDECREF (val);
+            Py_XDECREF (trb);
+            prompt = ps2;
+          }
+          else                                   /* some other syntax error */
+          {
+            PyErr_Restore (exc, val, trb);
+            PyErr_Print ();
+            free (code);
+            code = NULL;
+            prompt = ps1;
+          }
+        }
+        else                                     /* some non-syntax error */
+        {
+          PyErr_Print ();
+          free (code);
+          code = NULL;
+          prompt = ps1;
+        }
+
+
+        free (line);
+      }
+    }
+
+
+    Py_XDECREF(glb);
+    Py_XDECREF(loc);
+    Py_Finalize();
+    exit(0);
+  }
+
+

+ +Edit this entry / +Log info + +/ Last changed on Wed Mar 15 09:47:24 2000 by +Alex Farber +

+ +


+

5.16. How do I debug an extension?

+When using gdb with dynamically loaded extensions, you can't set a +breakpoint in your extension until your extension is loaded. +

+In your .gdbinit file (or interactively), add the command +

+br _PyImport_LoadDynamicModule +

+

+$ gdb /local/bin/python +

+gdb) run myscript.py +

+gdb) continue # repeat until your extension is loaded +

+gdb) finish # so that your extension is loaded +

+gdb) br myfunction.c:50 +

+gdb) continue +

+ +Edit this entry / +Log info + +/ Last changed on Fri Oct 20 11:10:32 2000 by +Joe VanAndel +

+ +


+

5.17. How do I find undefined Linux g++ symbols, __builtin_new or __pure_virtural

+To dynamically load g++ extension modules, you must recompile python, relink python using g++ (change LINKCC in the python Modules Makefile), and link your extension module using g++ (e.g., "g++ -shared -o mymodule.so mymodule.o"). +

+ +Edit this entry / +Log info + +/ Last changed on Sun Jan 14 18:03:51 2001 by +douglas orr +

+ +


+

5.18. How do I define and create objects corresponding to built-in/extension types

+Usually you would like to be able to inherit from a Python type when +you ask this question. The bottom line for Python 2.2 is: types and classes are miscible. You build instances by calling classes, and you can build subclasses to your heart's desire. +

+You need to be careful when instantiating immutable types like integers or strings. See http://www.amk.ca/python/2.2/, section 2, for details. +

+Prior to version 2.2, Python (like Java) insisted that there are first-class and second-class objects (the former are types, the latter classes), and never the twain shall meet. +

+The library has, however, done a good job of providing class wrappers for the more commonly desired objects (see UserDict, UserList and UserString for examples), and more are always welcome if you happen to be in the mood to write code. These wrappers still exist in Python 2.2. +

+ +Edit this entry / +Log info + +/ Last changed on Mon Jun 10 15:14:07 2002 by +Matthias Urlichs +

+ +


+

6. Python's design

+ +
+

6.1. Why isn't there a switch or case statement in Python?

+You can do this easily enough with a sequence of +if... elif... elif... else. There have been some proposals for switch +statement syntax, but there is no consensus (yet) on whether and how +to do range tests. +

+ +Edit this entry / +Log info +

+ +


+

6.2. Why does Python use indentation for grouping of statements?

+Basically I believe that using indentation for grouping is +extremely elegant and contributes a lot to the clarity of the average +Python program. Most people learn to love this feature after a while. +Some arguments for it: +

+Since there are no begin/end brackets there cannot be a disagreement +between grouping perceived by the parser and the human reader. I +remember long ago seeing a C fragment like this: +

+

+        if (x <= y)
+                x++;
+                y--;
+        z++;
+
+and staring a long time at it wondering why y was being decremented +even for x > y... (And I wasn't a C newbie then either.) +

+Since there are no begin/end brackets, Python is much less prone to +coding-style conflicts. In C there are loads of different ways to +place the braces (including the choice whether to place braces around +single statements in certain cases, for consistency). If you're used +to reading (and writing) code that uses one style, you will feel at +least slightly uneasy when reading (or being required to write) +another style. +Many coding styles place begin/end brackets on a line by themself. +This makes programs considerably longer and wastes valuable screen +space, making it harder to get a good overview over a program. +Ideally, a function should fit on one basic tty screen (say, 20 +lines). 20 lines of Python are worth a LOT more than 20 lines of C. +This is not solely due to the lack of begin/end brackets (the lack of +declarations also helps, and the powerful operations of course), but +it certainly helps! +

+ +Edit this entry / +Log info + +/ Last changed on Wed May 21 16:00:15 1997 by +GvR +

+ +


+

6.3. Why are Python strings immutable?

+There are two advantages. One is performance: knowing that a +string is immutable makes it easy to lay it out at construction time +-- fixed and unchanging storage requirements. (This is also one of +the reasons for the distinction between tuples and lists.) The +other is that strings in Python are considered as "elemental" as +numbers. No amount of activity will change the value 8 to anything +else, and in Python, no amount of activity will change the string +"eight" to anything else. (Adapted from Jim Roskind) +

+ +Edit this entry / +Log info +

+ +


+

6.4. Delete

+

+

+ +Edit this entry / +Log info + +/ Last changed on Tue Jan 2 03:05:25 2001 by +Moshe Zadka +

+ +


+

6.5. Why does Python use methods for some functionality (e.g. list.index()) but functions for other (e.g. len(list))?

+The major reason is history. Functions were used for those +operations that were generic for a group of types and which +were intended to work even for objects that didn't have +methods at all (e.g. numbers before type/class unification +began, or tuples). +

+It is also convenient to have a function that can readily be applied +to an amorphous collection of objects when you use the functional features of Python (map(), apply() et al). +

+In fact, implementing len(), max(), min() as a built-in function is +actually less code than implementing them as methods for each type. +One can quibble about individual cases but it's a part of Python, +and it's too late to change such things fundamentally now. The +functions have to remain to avoid massive code breakage. +

+Note that for string operations Python has moved from external functions +(the string module) to methods. However, len() is still a function. +

+ +Edit this entry / +Log info + +/ Last changed on Thu May 30 14:08:58 2002 by +Steve Holden +

+ +


+

6.6. Why can't I derive a class from built-in types (e.g. lists or files)?

+As of Python 2.2, you can derive from built-in types. For previous versions, the answer is: +

+This is caused by the relatively late addition of (user-defined) +classes to the language -- the implementation framework doesn't easily +allow it. See the answer to question 4.2 for a work-around. This +may be fixed in the (distant) future. +

+ +Edit this entry / +Log info + +/ Last changed on Thu May 23 02:53:22 2002 by +Neal Norwitz +

+ +


+

6.7. Why must 'self' be declared and used explicitly in method definitions and calls?

+So, is your current programming language C++ or Java? :-) +When classes were added to Python, this was (again) the simplest way of +implementing methods without too many changes to the interpreter. The +idea was borrowed from Modula-3. It turns out to be very useful, for +a variety of reasons. +

+First, it makes it more obvious that you are using a method or +instance attribute instead of a local variable. Reading "self.x" or +"self.meth()" makes it absolutely clear that an instance variable or +method is used even if you don't know the class definition by heart. +In C++, you can sort of tell by the lack of a local variable +declaration (assuming globals are rare or easily recognizable) -- but +in Python, there are no local variable declarations, so you'd have to +look up the class definition to be sure. +

+Second, it means that no special syntax is necessary if you want to +explicitly reference or call the method from a particular class. In +C++, if you want to use a method from base class that is overridden in +a derived class, you have to use the :: operator -- in Python you can +write baseclass.methodname(self, <argument list>). This is +particularly useful for __init__() methods, and in general in cases +where a derived class method wants to extend the base class method of +the same name and thus has to call the base class method somehow. +

+Lastly, for instance variables, it solves a syntactic problem with +assignment: since local variables in Python are (by definition!) those +variables to which a value assigned in a function body (and that +aren't explicitly declared global), there has to be some way to tell +the interpreter that an assignment was meant to assign to an instance +variable instead of to a local variable, and it should preferably be +syntactic (for efficiency reasons). C++ does this through +declarations, but Python doesn't have declarations and it would be a +pity having to introduce them just for this purpose. Using the +explicit "self.var" solves this nicely. Similarly, for using instance +variables, having to write "self.var" means that references to +unqualified names inside a method don't have to search the instance's +directories. +

+ +Edit this entry / +Log info + +/ Last changed on Fri Jan 12 08:01:50 2001 by +Steve Holden +

+ +


+

6.8. Can't you emulate threads in the interpreter instead of relying on an OS-specific thread implementation?

+Answer 1: Unfortunately, the interpreter pushes at least one C stack +frame for each Python stack frame. Also, extensions can call back into +Python at almost random moments. Therefore a complete threads +implementation requires thread support for C. +

+Answer 2: Fortunately, there is Stackless Python, which has a completely redesigned interpreter loop that avoids the C stack. It's still experimental but looks very promising. Although it is binary compatible with standard Python, it's still unclear whether Stackless will make it into the core -- maybe it's just too revolutionary. Stackless Python currently lives here: http://www.stackless.com. A microthread implementation that uses it can be found here: http://world.std.com/~wware/uthread.html. +

+ +Edit this entry / +Log info + +/ Last changed on Sat Apr 15 08:18:16 2000 by +Just van Rossum +

+ +


+

6.9. Why can't lambda forms contain statements?

+Python lambda forms cannot contain statements because Python's +syntactic framework can't handle statements nested inside expressions. +

+However, in Python, this is not a serious problem. Unlike lambda +forms in other languages, where they add functionality, Python lambdas +are only a shorthand notation if you're too lazy to define a function. +

+Functions are already first class objects in Python, and can be +declared in a local scope. Therefore the only advantage of using a +lambda form instead of a locally-defined function is that you don't need to invent a name for the function -- but that's just a local variable to which the function object (which is exactly the same type of object that a lambda form yields) is assigned! +

+ +Edit this entry / +Log info + +/ Last changed on Sun Jun 14 14:15:17 1998 by +Tim Peters +

+ +


+

6.10. [deleted]

+[lambda vs non-nested scopes used to be here] +

+ +Edit this entry / +Log info + +/ Last changed on Thu Mar 21 05:20:56 2002 by +Erno Kuusela +

+ +


+

6.11. [deleted]

+[recursive functions vs non-nested scopes used to be here] +

+ +Edit this entry / +Log info + +/ Last changed on Thu Mar 21 05:22:04 2002 by +Erno Kuusela +

+ +


+

6.12. Why is there no more efficient way of iterating over a dictionary than first constructing the list of keys()?

+As of Python 2.2, you can now iterate over a dictionary directly, +using the new implied dictionary iterator: +

+

+    for k in d: ...
+
+There are also methods returning iterators over the values and items: +

+

+    for k in d.iterkeys(): # same as above
+    for v in d.itervalues(): # iterate over values
+    for k, v in d.iteritems(): # iterate over items
+
+All these require that you do not modify the dictionary during the loop. +

+For previous Python versions, the following defense should do: +

+Have you tried it? I bet it's fast enough for your purposes! In +most cases such a list takes only a few percent of the space occupied +by the dictionary. Apart from the fixed header, +the list needs only 4 bytes (the size of a pointer) per +key. A dictionary uses 12 bytes per key plus between 30 and 70 +percent hash table overhead, plus the space for the keys and values. +By necessity, all keys are distinct objects, and a string object (the most +common key type) costs at least 20 bytes plus the length of the +string. Add to that the values contained in the dictionary, and you +see that 4 bytes more per item really isn't that much more memory... +

+A call to dict.keys() makes one fast scan over the dictionary +(internally, the iteration function does exist) copying the pointers +to the key objects into a pre-allocated list object of the right size. +The iteration time isn't lost (since you'll have to iterate anyway -- +unless in the majority of cases your loop terminates very prematurely +(which I doubt since you're getting the keys in random order). +

+I don't expose the dictionary iteration operation to Python +programmers because the dictionary shouldn't be modified during the +entire iteration -- if it is, there's a small chance that the +dictionary is reorganized because the hash table becomes too full, and +then the iteration may miss some items and see others twice. Exactly +because this only occurs rarely, it would lead to hidden bugs in +programs: it's easy never to have it happen during test runs if you +only insert or delete a few items per iteration -- but your users will +surely hit upon it sooner or later. +

+ +Edit this entry / +Log info + +/ Last changed on Fri May 24 21:24:08 2002 by +GvR +

+ +


+

6.13. Can Python be compiled to machine code, C or some other language?

+Not easily. Python's high level data types, dynamic typing of +objects and run-time invocation of the interpreter (using eval() or +exec) together mean that a "compiled" Python program would probably +consist mostly of calls into the Python run-time system, even for +seemingly simple operations like "x+1". +

+Several projects described in the Python newsgroup or at past +Python conferences have shown that this approach is feasible, +although the speedups reached so far are only modest (e.g. 2x). +JPython uses the same strategy for compiling to Java bytecode. +(Jim Hugunin has demonstrated that in combination with whole-program +analysis, speedups of 1000x are feasible for small demo programs. +See the website for the 1997 Python conference.) +

+Internally, Python source code is always translated into a "virtual +machine code" or "byte code" representation before it is interpreted +(by the "Python virtual machine" or "bytecode interpreter"). In order +to avoid the overhead of parsing and translating modules that rarely +change over and over again, this byte code is written on a file whose +name ends in ".pyc" whenever a module is parsed (from a file whose +name ends in ".py"). When the corresponding .py file is changed, it +is parsed and translated again and the .pyc file is rewritten. +

+There is no performance difference once the .pyc file has been loaded +(the bytecode read from the .pyc file is exactly the same as the bytecode +created by direct translation). The only difference is that loading +code from a .pyc file is faster than parsing and translating a .py +file, so the presence of precompiled .pyc files will generally improve +start-up time of Python scripts. If desired, the Lib/compileall.py +module/script can be used to force creation of valid .pyc files for a +given set of modules. +

+Note that the main script executed by Python, even if its filename +ends in .py, is not compiled to a .pyc file. It is compiled to +bytecode, but the bytecode is not saved to a file. +

+If you are looking for a way to translate Python programs in order to +distribute them in binary form, without the need to distribute the +interpreter and library as well, have a look at the freeze.py script +in the Tools/freeze directory. This creates a single binary file +incorporating your program, the Python interpreter, and those parts of +the Python library that are needed by your program. Of course, the +resulting binary will only run on the same type of platform as that +used to create it. +

+Newsflash: there are now several programs that do this, to some extent. +Look for Psyco, Pyrex, PyInline, Py2Cmod, and Weave. +

+ +Edit this entry / +Log info + +/ Last changed on Fri May 24 21:26:19 2002 by +GvR +

+ +


+

6.14. How does Python manage memory?

+The details of Python memory management depend on the implementation. +The standard Python implementation (the C implementation) uses reference +counting and another mechanism to collect reference cycles. +

+Jython relies on the Java runtime; so it uses +the JVM's garbage collector. This difference can cause some subtle +porting problems if your Python code depends on the behavior of +the reference counting implementation. +

+The reference cycle collector was added in CPython 2.0. It +periodically executes a cycle detection algorithm which looks for inaccessible cycles and deletes the objects involved. A new gc module provides functions to perform a garbage collection, obtain debugging statistics, and tuning the collector's parameters. +

+The detection of cycles can be disabled when Python is compiled, if you can't afford even a tiny speed penalty or suspect that the cycle collection is buggy, by specifying the "--without-cycle-gc" switch when running the configure script. +

+Sometimes objects get stuck in "tracebacks" temporarily and hence are not deallocated when you might expect. Clear the tracebacks via +

+

+       import sys
+       sys.exc_traceback = sys.last_traceback = None
+
+Tracebacks are used for reporting errors and implementing debuggers and related things. They contain a portion of the program state extracted during the handling of an exception (usually the most recent exception). +

+In the absence of circularities and modulo tracebacks, Python programs need not explicitly manage memory. +

+Why python doesn't use a more traditional garbage collection +scheme? For one thing, unless this were +added to C as a standard feature, it's a portability pain in the ass. +And yes, I know about the Xerox library. It has bits of assembler +code for most common platforms. Not for all. And although it is +mostly transparent, it isn't completely transparent (when I once +linked Python with it, it dumped core). +

+Traditional GC also becomes a problem when Python gets embedded into +other applications. While in a stand-alone Python it may be fine to +replace the standard malloc() and free() with versions provided by the +GC library, an application embedding Python may want to have its own +substitute for malloc() and free(), and may not want Python's. Right +now, Python works with anything that implements malloc() and free() +properly. +

+In Jython, the following code (which is +fine in C Python) will probably run out of file descriptors long before +it runs out of memory: +

+

+        for file in <very long list of files>:
+                f = open(file)
+                c = f.read(1)
+
+Using the current reference counting and destructor scheme, each new +assignment to f closes the previous file. Using GC, this is not +guaranteed. Sure, you can think of ways to fix this. But it's not +off-the-shelf technology. If you want to write code that will +work with any Python implementation, you should explicitly close +the file; this will work regardless of GC: +

+

+       for file in <very long list of files>:
+                f = open(file)
+                c = f.read(1)
+                f.close()
+
+

+ +Edit this entry / +Log info + +/ Last changed on Thu Mar 21 05:35:38 2002 by +Erno Kuusela +

+ +


+

6.15. Why are there separate tuple and list data types?

+This is done so that tuples can be immutable while lists are mutable. +

+Immutable tuples are useful in situations where you need to pass a few +items to a function and don't want the function to modify the tuple; +for example, +

+

+	point1 = (120, 140)
+	point2 = (200, 300)
+	record(point1, point2)
+	draw(point1, point2)
+
+You don't want to have to think about what would happen if record() +changed the coordinates -- it can't, because the tuples are immutable. +

+On the other hand, when creating large lists dynamically, it is +absolutely crucial that they are mutable -- adding elements to a tuple +one by one requires using the concatenation operator, which makes it +quadratic in time. +

+As a general guideline, use tuples like you would use structs in C or +records in Pascal, use lists like (variable length) arrays. +

+ +Edit this entry / +Log info + +/ Last changed on Fri May 23 15:26:03 1997 by +GvR +

+ +


+

6.16. How are lists implemented?

+Despite what a Lisper might think, Python's lists are really +variable-length arrays. The implementation uses a contiguous +array of references to other objects, and keeps a pointer +to this array (as well as its length) in a list head structure. +

+This makes indexing a list (a[i]) an operation whose cost is +independent of the size of the list or the value of the index. +

+When items are appended or inserted, the array of references is resized. +Some cleverness is applied to improve the performance of appending +items repeatedly; when the array must be grown, some extra space +is allocated so the next few times don't require an actual resize. +

+ +Edit this entry / +Log info + +/ Last changed on Fri May 23 15:32:24 1997 by +GvR +

+ +


+

6.17. How are dictionaries implemented?

+Python's dictionaries are implemented as resizable hash tables. +

+Compared to B-trees, this gives better performance for lookup +(the most common operation by far) under most circumstances, +and the implementation is simpler. +

+ +Edit this entry / +Log info + +/ Last changed on Fri May 23 23:51:14 1997 by +Vladimir Marangozov +

+ +


+

6.18. Why must dictionary keys be immutable?

+The hash table implementation of dictionaries uses a hash value +calculated from the key value to find the key. If the key were +a mutable object, its value could change, and thus its hash could +change. But since whoever changes the key object can't tell that +is incorporated in a dictionary, it can't move the entry around in +the dictionary. Then, when you try to look up the same object +in the dictionary, it won't be found, since its hash value is different; +and if you try to look up the old value, it won't be found either, +since the value of the object found in that hash bin differs. +

+If you think you need to have a dictionary indexed with a list, +try to use a tuple instead. The function tuple(l) creates a tuple +with the same entries as the list l. +

+Some unacceptable solutions that have been proposed: +

+- Hash lists by their address (object ID). This doesn't work because +if you construct a new list with the same value it won't be found; +e.g., +

+

+  d = {[1,2]: '12'}
+  print d[[1,2]]
+
+will raise a KeyError exception because the id of the [1,2] used +in the second line differs from that in the first line. +In other words, dictionary keys should be compared using '==', not using 'is'. +

+- Make a copy when using a list as a key. This doesn't work because +the list (being a mutable object) could contain a reference to itself, +and then the copying code would run into an infinite loop. +

+- Allow lists as keys but tell the user not to modify them. This would +allow a class of hard-to-track bugs in programs that I'd rather not see; +it invalidates an important invariant of dictionaries (every value in +d.keys() is usable as a key of the dictionary). +

+- Mark lists as read-only once they are used as a dictionary key. +The problem is that it's not just the top-level object that could change +its value; you could use a tuple containing a list as a key. Entering +anything as a key into a dictionary would require marking all objects +reachable from there as read-only -- and again, self-referential objects +could cause an infinite loop again (and again and again). +

+There is a trick to get around this if you need to, but +use it at your own risk: You +can wrap a mutable structure inside a class instance which +has both a __cmp__ and a __hash__ method. +

+

+   class listwrapper:
+        def __init__(self, the_list):
+              self.the_list = the_list
+        def __cmp__(self, other):
+              return self.the_list == other.the_list
+        def __hash__(self):
+              l = self.the_list
+              result = 98767 - len(l)*555
+              for i in range(len(l)):
+                   try:
+                        result = result + (hash(l[i]) % 9999999) * 1001 + i
+                   except:
+                        result = (result % 7777777) + i * 333
+              return result
+
+Note that the hash computation is complicated by the +possibility that some members of the list may be unhashable +and also by the possibility of arithmetic overflow. +

+You must make +sure that the hash value for all such wrapper objects that reside in a +dictionary (or other hash based structure), remain fixed while +the object is in the dictionary (or other structure). +

+Furthermore it must always be the case that if +o1 == o2 (ie o1.__cmp__(o2)==0) then hash(o1)==hash(o2) +(ie, o1.__hash__() == o2.__hash__()), regardless of whether +the object is in a dictionary or not. +If you fail to meet these restrictions dictionaries and other +hash based structures may misbehave! +

+In the case of listwrapper above whenever the wrapper +object is in a dictionary the wrapped list must not change +to avoid anomalies. Don't do this unless you are prepared +to think hard about the requirements and the consequences +of not meeting them correctly. You've been warned! +

+ +Edit this entry / +Log info + +/ Last changed on Thu Jul 10 10:08:40 1997 by +aaron watters +

+ +


+

6.19. How the heck do you make an array in Python?

+["this", 1, "is", "an", "array"] +

+Lists are arrays in the C or Pascal sense of the word (see question +6.16). The array module also provides methods for creating arrays +of fixed types with compact representations (but they are slower to +index than lists). Also note that the Numerics extensions and others +define array-like structures with various characteristics as well. +

+To get Lisp-like lists, emulate cons cells +

+

+    lisp_list = ("like",  ("this",  ("example", None) ) )
+
+using tuples (or lists, if you want mutability). Here the analogue +of lisp car is lisp_list[0] and the analogue of cdr is lisp_list[1]. +Only do this if you're sure you really need to (it's usually a lot +slower than using Python lists). +

+Think of Python lists as mutable heterogeneous arrays of +Python objects (say that 10 times fast :) ). +

+ +Edit this entry / +Log info + +/ Last changed on Wed Aug 13 07:08:27 1997 by +aaron watters +

+ +


+

6.20. Why doesn't list.sort() return the sorted list?

+In situations where performance matters, making a copy of the list +just to sort it would be wasteful. Therefore, list.sort() sorts +the list in place. In order to remind you of that fact, it does +not return the sorted list. This way, you won't be fooled into +accidentally overwriting a list when you need a sorted copy but also +need to keep the unsorted version around. +

+As a result, here's the idiom to iterate over the keys of a dictionary +in sorted order: +

+

+	keys = dict.keys()
+	keys.sort()
+	for key in keys:
+		...do whatever with dict[key]...
+
+

+ +Edit this entry / +Log info + +/ Last changed on Thu Dec 2 17:01:52 1999 by +Fred L. Drake, Jr. +

+ +


+

6.21. How do you specify and enforce an interface spec in Python?

+An interfaces specification for a module as provided +by languages such as C++ and java describes the prototypes +for the methods and functions of the module. Many feel +that compile time enforcement of interface specifications +help aid in the construction of large programs. Python +does not support interface specifications directly, but many +of their advantages can be obtained by an appropriate +test discipline for components, which can often be very +easily accomplished in Python. There is also a tool, PyChecker, +which can be used to find problems due to subclassing. +

+A good test suite for a module can at +once provide a regression test and serve as a module interface +specification (even better since it also gives example usage). Look to +many of the standard libraries which often have a "script +interpretation" which provides a simple "self test." Even +modules which use complex external interfaces can often +be tested in isolation using trivial "stub" emulations of the +external interface. +

+An appropriate testing discipline (if enforced) can help +build large complex applications in Python as well as having interface +specifications would do (or better). Of course Python allows you +to get sloppy and not do it. Also you might want to design +your code with an eye to make it easily tested. +

+ +Edit this entry / +Log info + +/ Last changed on Thu May 23 03:05:29 2002 by +Neal Norwitz +

+ +


+

6.22. Why do all classes have the same type? Why do instances all have the same type?

+The Pythonic use of the word "type" is quite different from +common usage in much of the rest of the programming language +world. A "type" in Python is a description for an object's operations +as implemented in C. All classes have the same operations +implemented in C which sometimes "call back" to differing program +fragments implemented in Python, and hence all classes have the +same type. Similarly at the C level all class instances have the +same C implementation, and hence all instances have the same +type. +

+Remember that in Python usage "type" refers to a C implementation +of an object. To distinguish among instances of different classes +use Instance.__class__, and also look to 4.47. Sorry for the +terminological confusion, but at this point in Python's development +nothing can be done! +

+ +Edit this entry / +Log info + +/ Last changed on Tue Jul 1 12:35:47 1997 by +aaron watters +

+ +


+

6.23. Why isn't all memory freed when Python exits?

+Objects referenced from Python module global name spaces are +not always deallocated when Python exits. +

+This may happen if there are circular references (see question +4.17). There are also certain bits of memory that are allocated +by the C library that are impossible to free (e.g. a tool +like Purify will complain about these). +

+But in general, Python 1.5 and beyond +(in contrast with earlier versions) is quite agressive about +cleaning up memory on exit. +

+If you want to force Python to delete certain things on deallocation +use the sys.exitfunc hook to force those deletions. For example +if you are debugging an extension module using a memory analysis +tool and you wish to make Python deallocate almost everything +you might use an exitfunc like this one: +

+

+  import sys
+
+
+  def my_exitfunc():
+       print "cleaning up"
+       import sys
+       # do order dependant deletions here
+       ...
+       # now delete everything else in arbitrary order
+       for x in sys.modules.values():
+            d = x.__dict__
+            for name in d.keys():
+                 del d[name]
+
+
+  sys.exitfunc = my_exitfunc
+
+Other exitfuncs can be less drastic, of course. +

+(In fact, this one just does what Python now already does itself; +but the example of using sys.exitfunc to force cleanups is still +useful.) +

+ +Edit this entry / +Log info + +/ Last changed on Tue Sep 29 09:46:26 1998 by +GvR +

+ +


+

6.24. Why no class methods or mutable class variables?

+The notation +

+

+    instance.attribute(arg1, arg2)
+
+usually translates to the equivalent of +

+

+    Class.attribute(instance, arg1, arg2)
+
+where Class is a (super)class of instance. Similarly +

+

+    instance.attribute = value
+
+sets an attribute of an instance (overriding any attribute of a class +that instance inherits). +

+Sometimes programmers want to have +different behaviours -- they want a method which does not bind +to the instance and a class attribute which changes in place. +Python does not preclude these behaviours, but you have to +adopt a convention to implement them. One way to accomplish +this is to use "list wrappers" and global functions. +

+

+   def C_hello():
+         print "hello"
+
+
+   class C:
+        hello = [C_hello]
+        counter = [0]
+
+
+    I = C()
+
+Here I.hello[0]() acts very much like a "class method" and +I.counter[0] = 2 alters C.counter (and doesn't override it). +If you don't understand why you'd ever want to do this, that's +because you are pure of mind, and you probably never will +want to do it! This is dangerous trickery, not recommended +when avoidable. (Inspired by Tim Peter's discussion.) +

+In Python 2.2, you can do this using the new built-in operations +classmethod and staticmethod. +See http://www.python.org/2.2/descrintro.html#staticmethods +

+ +Edit this entry / +Log info + +/ Last changed on Tue Sep 11 15:59:37 2001 by +GvR +

+ +


+

6.25. Why are default values sometimes shared between objects?

+It is often expected that a function CALL creates new objects for default +values. This is not what happens. Default values are created when the +function is DEFINED, that is, there is only one such object that all +functions refer to. If that object is changed, subsequent calls to the +function will refer to this changed object. By definition, immutable objects +(like numbers, strings, tuples, None) are safe from change. Changes to mutable +objects (like dictionaries, lists, class instances) is what causes the +confusion. +

+Because of this feature it is good programming practice not to use mutable +objects as default values, but to introduce them in the function. +Don't write: +

+

+	def foo(dict={}):  # XXX shared reference to one dict for all calls
+	    ...
+
+but: +
+	def foo(dict=None):
+		if dict is None:
+			dict = {} # create a new dict for local namespace
+
+See page 182 of "Internet Programming with Python" for one discussion +of this feature. Or see the top of page 144 or bottom of page 277 in +"Programming Python" for another discussion. +

+ +Edit this entry / +Log info + +/ Last changed on Sat Aug 16 07:03:35 1997 by +Case Roole +

+ +


+

6.26. Why no goto?

+Actually, you can use exceptions to provide a "structured goto" +that even works across function calls. Many feel that exceptions +can conveniently emulate all reasonable uses of the "go" or "goto" +constructs of C, Fortran, and other languages. For example: +

+

+   class label: pass # declare a label
+   try:
+        ...
+        if (condition): raise label() # goto label
+        ...
+   except label: # where to goto
+        pass
+   ...
+
+This doesn't allow you to jump into the middle of a loop, but +that's usually considered an abuse of goto anyway. Use sparingly. +

+ +Edit this entry / +Log info + +/ Last changed on Wed Sep 10 07:16:44 1997 by +aaron watters +

+ +


+

6.27. How do you make a higher order function in Python?

+You have two choices: you can use default arguments and override +them or you can use "callable objects." For example suppose you +wanted to define linear(a,b) which returns a function f where f(x) +computes the value a*x+b. Using default arguments: +

+

+     def linear(a,b):
+         def result(x, a=a, b=b):
+             return a*x + b
+         return result
+
+Or using callable objects: +

+

+     class linear:
+        def __init__(self, a, b):
+            self.a, self.b = a,b
+        def __call__(self, x):
+            return self.a * x + self.b
+
+In both cases: +

+

+     taxes = linear(0.3,2)
+
+gives a callable object where taxes(10e6) == 0.3 * 10e6 + 2. +

+The defaults strategy has the disadvantage that the default arguments +could be accidentally or maliciously overridden. The callable objects +approach has the disadvantage that it is a bit slower and a bit +longer. Note however that a collection of callables can share +their signature via inheritance. EG +

+

+      class exponential(linear):
+         # __init__ inherited
+         def __call__(self, x):
+             return self.a * (x ** self.b)
+
+On comp.lang.python, zenin@bawdycaste.org points out that +an object can encapsulate state for several methods in order +to emulate the "closure" concept from functional programming +languages, for example: +

+

+    class counter:
+        value = 0
+        def set(self, x): self.value = x
+        def up(self): self.value=self.value+1
+        def down(self): self.value=self.value-1
+
+
+    count = counter()
+    inc, dec, reset = count.up, count.down, count.set
+
+Here inc, dec and reset act like "functions which share the +same closure containing the variable count.value" (if you +like that way of thinking). +

+ +Edit this entry / +Log info + +/ Last changed on Fri Sep 25 08:38:35 1998 by +Aaron Watters +

+ +


+

6.28. Why do I get a SyntaxError for a 'continue' inside a 'try'?

+This is an implementation limitation, +caused by the extremely simple-minded +way Python generates bytecode. The try block pushes something on the +"block stack" which the continue would have to pop off again. The +current code generator doesn't have the data structures around so that +'continue' can generate the right code. +

+Note that JPython doesn't have this restriction! +

+ +Edit this entry / +Log info + +/ Last changed on Fri May 22 15:01:07 1998 by +GvR +

+ +


+

6.29. Why can't raw strings (r-strings) end with a backslash?

+More precisely, they can't end with an odd number of backslashes: +the unpaired backslash at the end escapes the closing quote character, +leaving an unterminated string. +

+Raw strings were designed to ease creating input for processors (chiefly +regular expression engines) that want to do their own backslash escape processing. Such processors consider an unmatched trailing backslash to be an error anyway, so raw strings disallow that. In return, they allow you to pass on the string quote character by escaping it with a backslash. These rules work well when r-strings are used for their intended purpose. +

+If you're trying to build Windows pathnames, note that all Windows system calls accept forward slashes too: +

+

+    f = open("/mydir/file.txt") # works fine!
+
+If you're trying to build a pathname for a DOS command, try e.g. one of +

+

+    dir = r"\this\is\my\dos\dir" "\\"
+    dir = r"\this\is\my\dos\dir\ "[:-1]
+    dir = "\\this\\is\\my\\dos\\dir\\"
+
+

+ +Edit this entry / +Log info + +/ Last changed on Mon Jul 13 20:50:20 1998 by +Tim Peters +

+ +


+

6.30. Why can't I use an assignment in an expression?

+Many people used to C or Perl complain that they want to be able to +use e.g. this C idiom: +

+

+    while (line = readline(f)) {
+        ...do something with line...
+    }
+
+where in Python you're forced to write this: +

+

+    while 1:
+        line = f.readline()
+        if not line:
+            break
+        ...do something with line...
+
+This issue comes up in the Python newsgroup with alarming frequency +-- search Deja News for past messages about assignment expression. +The reason for not allowing assignment in Python expressions +is a common, hard-to-find bug in those other languages, +caused by this construct: +

+

+    if (x = 0) {
+        ...error handling...
+    }
+    else {
+        ...code that only works for nonzero x...
+    }
+
+Many alternatives have been proposed. Most are hacks that save some +typing but use arbitrary or cryptic syntax or keywords, +and fail the simple criterion that I use for language change proposals: +it should intuitively suggest the proper meaning to a human reader +who has not yet been introduced with the construct. +

+The earliest time something can be done about this will be with +Python 2.0 -- if it is decided that it is worth fixing. +An interesting phenomenon is that most experienced Python programmers +recognize the "while 1" idiom and don't seem to be missing the +assignment in expression construct much; it's only the newcomers +who express a strong desire to add this to the language. +

+One fairly elegant solution would be to introduce a new operator +for assignment in expressions spelled ":=" -- this avoids the "=" +instead of "==" problem. It would have the same precedence +as comparison operators but the parser would flag combination with +other comparisons (without disambiguating parentheses) as an error. +

+Finally -- there's an alternative way of spelling this that seems +attractive but is generally less robust than the "while 1" solution: +

+

+    line = f.readline()
+    while line:
+        ...do something with line...
+        line = f.readline()
+
+The problem with this is that if you change your mind about exactly +how you get the next line (e.g. you want to change it into +sys.stdin.readline()) you have to remember to change two places +in your program -- the second one hidden at the bottom of the loop. +

+ +Edit this entry / +Log info + +/ Last changed on Tue May 18 00:57:41 1999 by +Andrew Dalke +

+ +


+

6.31. Why doesn't Python have a "with" statement like some other languages?

+Basically, because such a construct would be terribly ambiguous. Thanks to Carlos Ribeiro for the following remarks: +

+Some languages, such as Object Pascal, Delphi, and C++, use static types. So it is possible to know, in an unambiguous way, what member is being assigned in a "with" clause. This is the main point - the compiler always knows the scope of every variable at compile time. +

+Python uses dynamic types. It is impossible to know in advance which +attribute will be referenced at runtime. Member attributes may be added or removed from objects on the fly. This would make it impossible to know, from a simple reading, what attribute is being referenced - a local one, a global one, or a member attribute. +

+For instance, take the following snippet (it is incomplete btw, just to +give you the idea): +

+

+   def with_is_broken(a):
+      with a:
+         print x
+
+The snippet assumes that "a" must have a member attribute called "x". +However, there is nothing in Python that guarantees that. What should +happen if "a" is, let us say, an integer? And if I have a global variable named "x", will it end up being used inside the with block? As you see, the dynamic nature of Python makes such choices much harder. +

+The primary benefit of "with" and similar language features (reduction of code volume) can, however, easily be achieved in Python by assignment. Instead of: +

+

+    function(args).dict[index][index].a = 21
+    function(args).dict[index][index].b = 42
+    function(args).dict[index][index].c = 63
+
+would become: +

+

+    ref = function(args).dict[index][index]
+    ref.a = 21
+    ref.b = 42
+    ref.c = 63
+
+This also has the happy side-effect of increasing execution speed, since name bindings are resolved at run-time in Python, and the second method only needs to perform the resolution once. If the referenced object does not have a, b and c attributes, of course, the end result is still a run-time exception. +

+ +Edit this entry / +Log info + +/ Last changed on Fri Jan 11 14:32:58 2002 by +Steve Holden +

+ +


+

6.32. Why are colons required for if/while/def/class?

+The colon is required primarily to enhance readability (one of the +results of the experimental ABC language). Consider this: +

+

+    if a==b
+        print a
+
+versus +

+

+    if a==b:
+        print a
+
+Notice how the second one is slightly easier to read. Notice further how +a colon sets off the example in the second line of this FAQ answer; it's +a standard usage in English. Finally, the colon makes it easier for +editors with syntax highlighting. +

+ +Edit this entry / +Log info + +/ Last changed on Mon Jun 3 07:22:57 2002 by +Matthias Urlichs +

+ +


+

6.33. Can't we get rid of the Global Interpreter Lock?

+The Global Interpreter Lock (GIL) is often seen as a hindrance to +Python's deployment on high-end multiprocessor server machines, +because a multi-threaded Python program effectively only uses +one CPU, due to the insistence that (almost) all Python code +can only run while the GIL is held. +

+Back in the days of Python 1.5, Greg Stein actually implemented +a comprehensive patch set ("free threading") +that removed the GIL, replacing it with +fine-grained locking. Unfortunately, even on Windows (where locks +are very efficient) this ran ordinary Python code about twice as +slow as the interpreter using the GIL. On Linux the performance +loss was even worse (pthread locks aren't as efficient). +

+Since then, the idea of getting rid of the GIL has occasionally +come up but nobody has found a way to deal with the expected slowdown; +Greg's free threading patch set has not been kept up-to-date for +later Python versions. +

+This doesn't mean that you can't make good use of Python on +multi-CPU machines! You just have to be creative with dividing +the work up between multiple processes rather than multiple +threads. +

+

+It has been suggested that the GIL should be a per-interpreter-state +lock rather than truly global; interpreters then wouldn't be able +to share objects. Unfortunately, this isn't likely to happen either. +

+It would be a tremendous amount of work, because many object +implementations currently have global state. E.g. small ints and +small strings are cached; these caches would have to be moved to the +interpreter state. Other object types have their own free list; these +free lists would have to be moved to the interpreter state. And so +on. +

+And I doubt that it can even be done in finite time, because the same +problem exists for 3rd party extensions. It is likely that 3rd party +extensions are being written at a faster rate than you can convert +them to store all their global state in the interpreter state. +

+And finally, once you have multiple interpreters not sharing any +state, what have you gained over running each interpreter +in a separate process? +

+ +Edit this entry / +Log info + +/ Last changed on Fri Feb 7 16:34:01 2003 by +GvR +

+ +


+

7. Using Python on non-UNIX platforms

+ +
+

7.1. Is there a Mac version of Python?

+Yes, it is maintained by Jack Jansen. See Jack's MacPython Page: +

+

+  http://www.cwi.nl/~jack/macpython.html
+
+

+ +Edit this entry / +Log info + +/ Last changed on Fri May 4 09:33:42 2001 by +GvR +

+ +


+

7.2. Are there DOS and Windows versions of Python?

+Yes. The core windows binaries are available from http://www.python.org/windows/. There is a plethora of Windows extensions available, including a large number of not-always-compatible GUI toolkits. The core binaries include the standard Tkinter GUI extension. +

+Most windows extensions can be found (or referenced) at http://www.python.org/windows/ +

+Windows 3.1/DOS support seems to have dropped off recently. You may need to settle for an old version of Python one these platforms. One such port is WPY +

+WPY: Ports to DOS, Windows 3.1(1), Windows 95, Windows NT and OS/2. +Also contains a GUI package that offers portability between Windows +(not DOS) and Unix, and native look and feel on both. +ftp://ftp.python.org/pub/python/wpy/. +

+ +Edit this entry / +Log info + +/ Last changed on Tue Jun 2 20:21:57 1998 by +Mark Hammond +

+ +


+

7.3. Is there an OS/2 version of Python?

+Yes, see http://www.python.org/download/download_os2.html. +

+ +Edit this entry / +Log info + +/ Last changed on Tue Sep 7 11:33:16 1999 by +GvR +

+ +


+

7.4. Is there a VMS version of Python?

+Jean-Franois Pironne has ported 2.1.3 to OpenVMS. It can be found at +<http://vmspython.dyndns.org/>. +

+ +Edit this entry / +Log info + +/ Last changed on Thu Sep 19 15:40:38 2002 by +Skip Montanaro +

+ +


+

7.5. What about IBM mainframes, or other non-UNIX platforms?

+I haven't heard about these, except I remember hearing about an +OS/9 port and a port to Vxworks (both operating systems for embedded +systems). If you're interested in any of this, go directly to the +newsgroup and ask there, you may find exactly what you need. For +example, a port to MPE/iX 5.0 on HP3000 computers was just announced, +see http://www.allegro.com/software/. +

+On the IBM mainframe side, for Z/OS there's a port of python 1.4 that goes with their open-unix package, formely OpenEdition MVS, (http://www-1.ibm.com/servers/eserver/zseries/zos/unix/python.html). On a side note, there's also a java vm ported - so, in theory, jython could run too. +

+ +Edit this entry / +Log info + +/ Last changed on Mon Nov 18 03:18:39 2002 by +Bruno Jessen +

+ +


+

7.6. Where are the source or Makefiles for the non-UNIX versions?

+The standard sources can (almost) be used. Additional sources can +be found in the platform-specific subdirectories of the distribution. +

+ +Edit this entry / +Log info +

+ +


+

7.7. What is the status and support for the non-UNIX versions?

+I don't have access to most of these platforms, so in general I am +dependent on material submitted by volunteers. However I strive to +integrate all changes needed to get it to compile on a particular +platform back into the standard sources, so porting of the next +version to the various non-UNIX platforms should be easy. +(Note that Linux is classified as a UNIX platform here. :-) +

+Some specific platforms: +

+Windows: all versions (95, 98, ME, NT, 2000, XP) are supported, +all python.org releases come with a Windows installer. +

+MacOS: Jack Jansen does an admirable job of keeping the Mac version +up to date (both MacOS X and older versions); +see http://www.cwi.nl/~jack/macpython.html +

+For all supported platforms, see http://www.python.org/download/ +(follow the link to "Other platforms" for less common platforms) +

+ +Edit this entry / +Log info + +/ Last changed on Fri May 24 21:34:24 2002 by +GvR +

+ +


+

7.8. I have a PC version but it appears to be only a binary. Where's the library?

+If you are running any version of Windows, then you have the wrong distribution. The FAQ lists current Windows versions. Notably, Pythonwin and wpy provide fully functional installations. +

+But if you are sure you have the only distribution with a hope of working on +your system, then... +

+You still need to copy the files from the distribution directory +"python/Lib" to your system. If you don't have the full distribution, +you can get the file lib<version>.tar.gz from most ftp sites carrying +Python; this is a subset of the distribution containing just those +files, e.g. ftp://ftp.python.org/pub/python/src/lib1.4.tar.gz. +

+Once you have installed the library, you need to point sys.path to it. +Assuming the library is in C:\misc\python\lib, the following commands +will point your Python interpreter to it (note the doubled backslashes +-- you can also use single forward slashes instead): +

+

+        >>> import sys
+        >>> sys.path.insert(0, 'C:\\misc\\python\\lib')
+        >>>
+
+For a more permanent effect, set the environment variable PYTHONPATH, +as follows (talking to a DOS prompt): +

+

+        C> SET PYTHONPATH=C:\misc\python\lib
+
+

+ +Edit this entry / +Log info + +/ Last changed on Fri May 23 16:28:27 1997 by +Ken Manheimer +

+ +


+

7.9. Where's the documentation for the Mac or PC version?

+The documentation for the Unix version also applies to the Mac and +PC versions. Where applicable, differences are indicated in the text. +

+ +Edit this entry / +Log info +

+ +


+

7.10. How do I create a Python program file on the Mac or PC?

+Use an external editor. On the Mac, BBEdit seems to be a popular +no-frills text editor. I work like this: start the interpreter; edit +a module file using BBedit; import and test it in the interpreter; +edit again in BBedit; then use the built-in function reload() to +re-read the imported module; etc. In the 1.4 distribution +you will find a BBEdit extension that makes life a little easier: +it can tell the interpreter to execute the current window. +See :Mac:Tools:BBPy:README. +

+Regarding the same question for the PC, Kurt Wm. Hemr writes: "While +anyone with a pulse could certainly figure out how to do the same on +MS-Windows, I would recommend the NotGNU Emacs clone for MS-Windows. +Not only can you easily resave and "reload()" from Python after making +changes, but since WinNot auto-copies to the clipboard any text you +select, you can simply select the entire procedure (function) which +you changed in WinNot, switch to QWPython, and shift-ins to reenter +the changed program unit." +

+If you're using Windows95 or Windows NT, you should also know about +PythonWin, which provides a GUI framework, with an mouse-driven +editor, an object browser, and a GUI-based debugger. See +

+       http://www.python.org/ftp/python/pythonwin/
+
+for details. +

+ +Edit this entry / +Log info + +/ Last changed on Sun May 25 10:04:25 1997 by +GvR +

+ +


+

7.11. How can I use Tkinter on Windows 95/NT?

+Starting from Python 1.5, it's very easy -- just download and install +Python and Tcl/Tk and you're in business. See +

+

+  http://www.python.org/download/download_windows.html
+
+One warning: don't attempt to use Tkinter from PythonWin +(Mark Hammond's IDE). Use it from the command line interface +(python.exe) or the windowless interpreter (pythonw.exe). +

+ +Edit this entry / +Log info + +/ Last changed on Fri Jun 12 09:32:48 1998 by +GvR +

+ +


+

7.12. cgi.py (or other CGI programming) doesn't work sometimes on NT or win95!

+Be sure you have the latest python.exe, that you are using +python.exe rather than a GUI version of python and that you +have configured the server to execute +

+

+     "...\python.exe -u ..."
+
+for the cgi execution. The -u (unbuffered) option on NT and +win95 prevents the interpreter from altering newlines in the +standard input and output. Without it post/multipart requests +will seem to have the wrong length and binary (eg, GIF) +responses may get garbled (resulting in, eg, a "broken image"). +

+ +Edit this entry / +Log info + +/ Last changed on Wed Jul 30 10:48:02 1997 by +aaron watters +

+ +


+

7.13. Why doesn't os.popen() work in PythonWin on NT?

+The reason that os.popen() doesn't work from within PythonWin is due to a bug in Microsoft's C Runtime Library (CRT). The CRT assumes you have a Win32 console attached to the process. +

+You should use the win32pipe module's popen() instead which doesn't depend on having an attached Win32 console. +

+Example: +

+ import win32pipe
+ f = win32pipe.popen('dir /c c:\\')
+ print f.readlines()
+ f.close()
+
+

+ +Edit this entry / +Log info + +/ Last changed on Thu Jul 31 15:34:09 1997 by +Bill Tutt +

+ +


+

7.14. How do I use different functionality on different platforms with the same program?

+Remember that Python is extremely dynamic and that you +can use this dynamism to configure a program at run-time to +use available functionality on different platforms. For example +you can test the sys.platform and import different modules based +on its value. +

+

+   import sys
+   if sys.platform == "win32":
+      import win32pipe
+      popen = win32pipe.popen
+   else:
+      import os
+      popen = os.popen
+
+(See FAQ 7.13 for an explanation of why you might want to +do something like this.) Also you can try to import a module +and use a fallback if the import fails: +

+

+    try:
+         import really_fast_implementation
+         choice = really_fast_implementation
+    except ImportError:
+         import slower_implementation
+         choice = slower_implementation
+
+

+ +Edit this entry / +Log info + +/ Last changed on Wed Aug 13 07:39:06 1997 by +aaron watters +

+ +


+

7.15. Is there an Amiga version of Python?

+Yes. See the AmigaPython homepage at http://www.bigfoot.com/~irmen/python.html. +

+ +Edit this entry / +Log info + +/ Last changed on Mon Dec 14 06:53:32 1998 by +Irmen de Jong +

+ +


+

7.16. Why doesn't os.popen()/win32pipe.popen() work on Win9x?

+There is a bug in Win9x that prevents os.popen/win32pipe.popen* from working. The good news is there is a way to work around this problem. +The Microsoft Knowledge Base article that you need to lookup is: Q150956. You will find links to the knowledge base at: +http://www.microsoft.com/kb. +

+ +Edit this entry / +Log info + +/ Last changed on Fri Jun 25 10:45:38 1999 by +Bill Tutt +

+ +


+

8. Python on Windows

+ +
+

8.1. Using Python for CGI on Microsoft Windows

+** Setting up the Microsoft IIS Server/Peer Server +

+On the Microsoft IIS +server or on the Win95 MS Personal Web Server +you set up python in the same way that you +would set up any other scripting engine. +

+Run regedt32 and go to: +

+HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap +

+and enter the following line (making any specific changes that your system may need) +

+.py :REG_SZ: c:\<path to python>\python.exe -u %s %s +

+This line will allow you to call your script with a simple reference like: +http://yourserver/scripts/yourscript.py +provided "scripts" is an "executable" directory for your server (which +it usually is by default). +The "-u" flag specifies unbuffered and binary mode for stdin - needed when working with binary data +

+In addition, it is recommended by people who would know that using ".py" may +not be a good idea for the file extensions when used in this context +(you might want to reserve *.py for support modules and use *.cgi or *.cgp +for "main program" scripts). +However, that issue is beyond this Windows FAQ entry. +

+

+** Apache configuration +

+In the Apache configuration file httpd.conf, add the following line at +the end of the file: +

+ScriptInterpreterSource Registry +

+Then, give your Python CGI-scripts the extension .py and put them in the cgi-bin directory. +

+

+** Netscape Servers: +Information on this topic exists at: +http://home.netscape.com/comprod/server_central/support/fasttrack_man/programs.htm#1010870 +

+ +Edit this entry / +Log info + +/ Last changed on Wed Mar 27 12:25:54 2002 by +Gerhard Hring +

+ +


+

8.2. How to check for a keypress without blocking?

+Use the msvcrt module. This is a standard Windows-specific extensions +in Python 1.5 and beyond. It defines a function kbhit() which checks +whether a keyboard hit is present; also getch() which gets one +character without echo. Plus a few other goodies. +

+(Search for "keypress" to find an answer for Unix as well.) +

+ +Edit this entry / +Log info + +/ Last changed on Mon Mar 30 16:21:46 1998 by +GvR +

+ +


+

8.3. $PYTHONPATH

+In MS-DOS derived environments, a unix variable such as $PYTHONPATH is +set as PYTHONPATH, without the dollar sign. PYTHONPATH is useful for +specifying the location of library files. +

+ +Edit this entry / +Log info + +/ Last changed on Thu Jun 11 00:41:26 1998 by +Gvr +

+ +


+

8.4. dedent syntax errors

+The FAQ does not recommend using tabs, and Guido's Python Style Guide recommends 4 spaces for distributed Python code; this is also the Emacs python-mode default; see +

+

+    http://www.python.org/doc/essays/styleguide.html
+
+Under any editor mixing tabs and spaces is a bad idea. MSVC is no different in this respect, and is easily configured to use spaces: Take Tools -> Options -> Tabs, and for file type "Default" set "Tab size" and "Indent size" to 4, and select the "Insert spaces" radio button. +

+If you suspect mixed tabs and spaces are causing problems in leading whitespace, run Python with the -t switch or, run Tools/Scripts/tabnanny.py to check a directory tree in batch mode. +

+ +Edit this entry / +Log info + +/ Last changed on Mon Feb 12 15:04:14 2001 by +Steve Holden +

+ +


+

8.5. How do I emulate os.kill() in Windows?

+Use win32api: +

+

+    def kill(pid):
+        """kill function for Win32"""
+        import win32api
+        handle = win32api.OpenProcess(1, 0, pid)
+        return (0 != win32api.TerminateProcess(handle, 0))
+
+

+ +Edit this entry / +Log info + +/ Last changed on Sat Aug 8 18:55:06 1998 by +Jeff Bauer +

+ +


+

8.6. Why does os.path.isdir() fail on NT shared directories?

+The solution appears to be always append the "\\" on +the end of shared drives. +

+

+  >>> import os
+  >>> os.path.isdir( '\\\\rorschach\\public')
+  0
+  >>> os.path.isdir( '\\\\rorschach\\public\\')
+  1
+
+[Blake Winton responds:] +I've had the same problem doing "Start >> Run" and then a +directory on a shared drive. If I use "\\rorschach\public", +it will fail, but if I use "\\rorschach\public\", it will +work. For that matter, os.stat() does the same thing (well, +it gives an error for "\\\\rorschach\\public", but you get +the idea)... +

+I've got a theory about why this happens, but it's only +a theory. NT knows the difference between shared directories, +and regular directories. "\\rorschach\public" isn't a +directory, it's _really_ an IPC abstraction. This is sort +of lended credence to by the fact that when you're mapping +a network drive, you can't map "\\rorschach\public\utils", +but only "\\rorschach\public". +

+[Clarification by funkster@midwinter.com] +It's not actually a Python +question, as Python is working just fine; it's clearing up something +a bit muddled about Windows networked drives. +

+It helps to think of share points as being like drive letters. +Example: +

+        k: is not a directory
+        k:\ is a directory
+        k:\media is a directory
+        k:\media\ is not a directory
+
+The same rules apply if you substitute "k:" with "\\conky\foo": +
+        \\conky\foo  is not a directory
+        \\conky\foo\ is a directory
+        \\conky\foo\media is a directory
+        \\conky\foo\media\ is not a directory
+
+

+ +Edit this entry / +Log info + +/ Last changed on Sun Jan 31 08:44:48 1999 by +GvR +

+ +


+

8.7. PyRun_SimpleFile() crashes on Windows but not on Unix

+I've seen a number of reports of PyRun_SimpleFile() failing +in a Windows port of an application embedding Python that worked +fine on Unix. PyRun_SimpleString() works fine on both platforms. +

+I think this happens because the application was compiled with a +different set of compiler flags than Python15.DLL. It seems that some +compiler flags affect the standard I/O library in such a way that +using different flags makes calls fail. You need to set it for +the non-debug multi-threaded DLL (/MD on the command line, or can be set via MSVC under Project Settings->C++/Code Generation then the "Use rum-time library" dropdown.) +

+Also note that you can not mix-and-match Debug and Release versions. If you wish to use the Debug Multithreaded DLL, then your module _must_ have an "_d" appended to the base name. +

+ +Edit this entry / +Log info + +/ Last changed on Wed Nov 17 17:37:07 1999 by +Mark Hammond +

+ +


+

8.8. Import of _tkinter fails on Windows 95/98

+Sometimes, the import of _tkinter fails on Windows 95 or 98, +complaining with a message like the following: +

+

+  ImportError: DLL load failed: One of the library files needed
+  to run this application cannot be found.
+
+It could be that you haven't installed Tcl/Tk, but if you did +install Tcl/Tk, and the Wish application works correctly, +the problem may be that its installer didn't +manage to edit the autoexec.bat file correctly. It tries to add a +statement that changes the PATH environment variable to include +the Tcl/Tk 'bin' subdirectory, but sometimes this edit doesn't +quite work. Opening it with notepad usually reveals what the +problem is. +

+(One additional hint, noted by David Szafranski: you can't use +long filenames here; e.g. use C:\PROGRA~1\Tcl\bin instead of +C:\Program Files\Tcl\bin.) +

+ +Edit this entry / +Log info + +/ Last changed on Wed Dec 2 22:32:41 1998 by +GvR +

+ +


+

8.9. Can't extract the downloaded documentation on Windows

+Sometimes, when you download the documentation package to a Windows +machine using a web browser, the file extension of the saved file +ends up being .EXE. This is a mistake; the extension should be .TGZ. +

+Simply rename the downloaded file to have the .TGZ extension, and +WinZip will be able to handle it. (If your copy of WinZip doesn't, +get a newer one from http://www.winzip.com.) +

+ +Edit this entry / +Log info + +/ Last changed on Sat Nov 21 13:41:35 1998 by +GvR +

+ +


+

8.10. Can't get Py_RunSimpleFile() to work.

+This is very sensitive to the compiler vendor, version and (perhaps) +even options. If the FILE* structure in your embedding program isn't +the same as is assumed by the Python interpreter it won't work. +

+The Python 1.5.* DLLs (python15.dll) are all compiled +with MS VC++ 5.0 and with multithreading-DLL options (/MD, I think). +

+If you can't change compilers or flags, try using Py_RunSimpleString(). +A trick to get it to run an arbitrary file is to construct a call to +execfile() with the name of your file as argument. +

+ +Edit this entry / +Log info + +/ Last changed on Wed Jan 13 10:58:14 1999 by +GvR +

+ +


+

8.11. Where is Freeze for Windows?

+("Freeze" is a program that allows you to ship a Python program +as a single stand-alone executable file. It is not a compiler, +your programs don't run any faster, but they are more easily +distributable (to platforms with the same OS and CPU). Read the +README file of the freeze program for more disclaimers.) +

+You can use freeze on Windows, but you must download the source +tree (see http://www.python.org/download/download_source.html). +This is recommended for Python 1.5.2 (and betas thereof) only; +older versions don't quite work. +

+You need the Microsoft VC++ 5.0 compiler (maybe it works with +6.0 too). You probably need to build Python -- the project files +are all in the PCbuild directory. +

+The freeze program is in the Tools\freeze subdirectory of the source +tree. +

+ +Edit this entry / +Log info + +/ Last changed on Wed Feb 17 18:47:24 1999 by +GvR +

+ +


+

8.12. Is a *.pyd file the same as a DLL?

+Yes, .pyd files are dll's. But there are a few differences. If you +have a DLL named foo.pyd, then it must have a function initfoo(). You +can then write Python "import foo", and Python will search for foo.pyd +(as well as foo.py, foo.pyc) and if it finds it, will attempt to call +initfoo() to initialize it. You do not link your .exe with foo.lib, +as that would cause Windows to require the DLL to be present. +

+Note that the search path for foo.pyd is PYTHONPATH, not the same as +the path that Windows uses to search for foo.dll. Also, foo.pyd need +not be present to run your program, whereas if you linked your program +with a dll, the dll is required. Of course, foo.pyd is required if +you want to say "import foo". In a dll, linkage is declared in the +source code with __declspec(dllexport). In a .pyd, linkage is defined +in a list of available functions. +

+ +Edit this entry / +Log info + +/ Last changed on Tue Nov 23 02:40:08 1999 by +Jameson Quinn +

+ +


+

8.13. Missing cw3215mt.dll (or missing cw3215.dll)

+Sometimes, when using Tkinter on Windows, you get an error that +cw3215mt.dll or cw3215.dll is missing. +

+Cause: you have an old Tcl/Tk DLL built with cygwin in your path +(probably C:\Windows). You must use the Tcl/Tk DLLs from the +standard Tcl/Tk installation (Python 1.5.2 comes with one). +

+ +Edit this entry / +Log info + +/ Last changed on Fri Jun 11 00:54:13 1999 by +GvR +

+ +


+

8.14. How to make python scripts executable:

+[Blake Coverett] +

+Win2K: +

+The standard installer already associates the .py extension with a file type +(Python.File) and gives that file type an open command that runs the +interpreter (D:\Program Files\Python\python.exe "%1" %*). This is enough to +make scripts executable from the command prompt as 'foo.py'. If you'd +rather be able to execute the script by simple typing 'foo' with no +extension you need to add .py to the PATHEXT environment variable. +

+WinNT: +

+The steps taken by the installed as described above allow you do run a +script with 'foo.py', but a long time bug in the NT command processor +prevents you from redirecting the input or output of any script executed in +this way. This is often important. +

+An appropriate incantation for making a Python script executable under WinNT +is to give the file an extension of .cmd and add the following as the first +line: +

+

+    @setlocal enableextensions & python -x %~f0 %* & goto :EOF
+
+Win9x: +

+[Due to Bruce Eckel] +

+

+  @echo off
+  rem = """
+  rem run python on this bat file. Needs the full path where
+  rem you keep your python files. The -x causes python to skip
+  rem the first line of the file:
+  python -x c:\aaa\Python\\"%0".bat %1 %2 %3 %4 %5 %6 %7 %8 %9
+  goto endofpython
+  rem """
+
+
+  # The python program goes here:
+
+
+  print "hello, Python"
+
+
+  # For the end of the batch file:
+  rem = """
+  :endofpython
+  rem """
+
+

+ +Edit this entry / +Log info + +/ Last changed on Tue Nov 30 10:25:17 1999 by +GvR +

+ +


+

8.15. Warning about CTL3D32 version from installer

+The Python installer issues a warning like this: +

+

+  This version uses CTL3D32.DLL whitch is not the correct version.
+  This version is used for windows NT applications only.
+
+[Tim Peters] +This is a Microsoft DLL, and a notorious +source of problems. The msg means what it says: you have the wrong version +of this DLL for your operating system. The Python installation did not +cause this -- something else you installed previous to this overwrote the +DLL that came with your OS (probably older shareware of some sort, but +there's no way to tell now). If you search for "CTL3D32" using any search +engine (AltaVista, for example), you'll find hundreds and hundreds of web +pages complaining about the same problem with all sorts of installation +programs. They'll point you to ways to get the correct version reinstalled +on your system (since Python doesn't cause this, we can't fix it). +

+David A Burton has written a little program to fix this. Go to +http://www.burtonsys.com/download.html and click on "ctl3dfix.zip" +

+ +Edit this entry / +Log info + +/ Last changed on Thu Oct 26 15:42:00 2000 by +GvR +

+ +


+

8.16. How can I embed Python into a Windows application?

+Edward K. Ream <edream@tds.net> writes +

+When '##' appears in a file name below, it is an abbreviated version number. For example, for Python 2.1.1, ## will be replaced by 21. +

+Embedding the Python interpreter in a Windows app can be summarized as +follows: +

+1. Do _not_ build Python into your .exe file directly. On Windows, +Python must be a DLL to handle importing modules that are themselves +DLL's. (This is the first key undocumented fact.) Instead, link to +python##.dll; it is typically installed in c:\Windows\System. +

+You can link to Python statically or dynamically. Linking statically +means linking against python##.lib The drawback is that your app won't +run if python##.dll does not exist on your system. +

+General note: python##.lib is the so-called "import lib" corresponding +to python.dll. It merely defines symbols for the linker. +

+Borland note: convert python##.lib to OMF format using Coff2Omf.exe +first. +

+Linking dynamically greatly simplifies link options; everything happens +at run time. Your code must load python##.dll using the Windows +LoadLibraryEx() routine. The code must also use access routines and +data in python##.dll (that is, Python's C API's) using pointers +obtained by the Windows GetProcAddress() routine. Macros can make +using these pointers transparent to any C code that calls routines in +Python's C API. +

+2. If you use SWIG, it is easy to create a Python "extension module" +that will make the app's data and methods available to Python. SWIG +will handle just about all the grungy details for you. The result is C +code that you link _into your .exe file_ (!) You do _not_ have to +create a DLL file, and this also simplifies linking. +

+3. SWIG will create an init function (a C function) whose name depends +on the name of the extension module. For example, if the name of the +module is leo, the init function will be called initleo(). If you use +SWIG shadow classes, as you should, the init function will be called +initleoc(). This initializes a mostly hidden helper class used by the +shadow class. +

+The reason you can link the C code in step 2 into your .exe file is that +calling the initialization function is equivalent to importing the +module into Python! (This is the second key undocumented fact.) +

+4. In short, you can use the following code to initialize the Python +interpreter with your extension module. +

+

+    #include "python.h"
+    ...
+    Py_Initialize();  // Initialize Python.
+    initmyAppc();  // Initialize (import) the helper class. 
+    PyRun_SimpleString("import myApp") ;  // Import the shadow class.
+
+5. There are two problems with Python's C API which will become apparent +if you use a compiler other than MSVC, the compiler used to build +python##.dll. +

+Problem 1: The so-called "Very High Level" functions that take FILE * +arguments will not work in a multi-compiler environment; each compiler's +notion of a struct FILE will be different. From an implementation +standpoint these are very _low_ level functions. +

+Problem 2: SWIG generates the following code when generating wrappers to +void functions: +

+

+    Py_INCREF(Py_None);
+    _resultobj = Py_None;
+    return _resultobj;
+
+Alas, Py_None is a macro that expands to a reference to a complex data +structure called _Py_NoneStruct inside python##.dll. Again, this code +will fail in a mult-compiler environment. Replace such code by: +

+

+    return Py_BuildValue("");
+
+It may be possible to use SWIG's %typemap command to make the change +automatically, though I have not been able to get this to work (I'm a +complete SWIG newbie). +

+6. Using a Python shell script to put up a Python interpreter window +from inside your Windows app is not a good idea; the resulting window +will be independent of your app's windowing system. Rather, you (or the +wxPythonWindow class) should create a "native" interpreter window. It +is easy to connect that window to the Python interpreter. You can +redirect Python's i/o to _any_ object that supports read and write, so +all you need is a Python object (defined in your extension module) that +contains read() and write() methods. +

+ +Edit this entry / +Log info + +/ Last changed on Thu Jan 31 16:29:34 2002 by +Victor Kryukov +

+ +


+

8.17. Setting up IIS 5 to use Python for CGI

+In order to set up Internet Information Services 5 to use Python for CGI processing, please see the following links: +

+http://www.e-coli.net/pyiis_server.html (for Win2k Server) +http://www.e-coli.net/pyiis.html (for Win2k pro) +

+ +Edit this entry / +Log info + +/ Last changed on Fri Mar 22 22:05:51 2002 by +douglas savitsky +

+ +


+

8.18. How do I run a Python program under Windows?

+This is not necessarily quite the straightforward question it appears +to be. If you are already familiar with running programs from the +Windows command line then everything will seem really easy and +obvious. If your computer experience is limited then you might need a +little more guidance. Also there are differences between Windows 95, +98, NT, ME, 2000 and XP which can add to the confusion. You might +think of this as "why I pay software support charges" if you have a +helpful and friendly administrator to help you set things up without +having to understand all this yourself. If so, then great! Show them +this page and it should be a done deal. +

+Unless you use some sort of integrated development environment (such +as PythonWin or IDLE, to name only two in a growing family) then you +will end up typing Windows commands into what is variously referred +to as a "DOS window" or "Command prompt window". Usually you can +create such a window from your Start menu (under Windows 2000 I use +"Start | Programs | Accessories | Command Prompt"). You should be +able to recognize when you have started such a window because you will +see a Windows "command prompt", which usually looks like this: +

+

+    C:\>
+
+The letter may be different, and there might be other things after it, +so you might just as easily see something like: +

+

+    D:\Steve\Projects\Python>
+
+depending on how your computer has been set up and what else you have +recently done with it. Once you have started such a window, you are +well on the way to running Python programs. +

+You need to realize that your Python scripts have to be processed by +another program, usually called the "Python interpreter". The +interpreter reads your script, "compiles" it into "Python bytecodes" +(which are instructions for an imaginary computer known as the "Python +Virtual Machine") and then executes the bytecodes to run your +program. So, how do you arrange for the interpreter to handle your +Python? +

+First, you need to make sure that your command window recognises the +word "python" as an instruction to start the interpreter. If you have +opened a command window, you should try entering the command: +

+

+    python
+
+and hitting return. If you then see something like: +

+

+    Python 2.2 (#28, Dec 21 2001, 12:21:22) [MSC 32 bit (Intel)] on win32
+    Type "help", "copyright", "credits" or "license" for more information.
+    >>>
+
+then this part of the job has been correctly managed during Python's +installation process, and you have started the interpreter in +"interactive mode". That means you can enter Python statements or +expressions interactively and have them executed or evaluated while +you wait. This is one of Python's strongest features, but it takes a +little getting used to. Check it by entering a few expressions of your +choice and seeing the results... +

+

+    >>> print "Hello"
+    Hello
+    >>> "Hello" * 3
+    HelloHelloHello
+
+When you want to end your interactive Python session, enter a +terminator (hold the Ctrl key down while you enter a Z, then hit the +"Enter" key) to get back to your Windows command prompt. You may also +find that you have a Start-menu entry such as "Start | Programs | +Python 2.2 | Python (command line)" that results in you seeing the +">>>" prompt in a new window. If so, the window will disappear after +you enter the terminator -- Windows runs a single "python" command in +the window, which terminates when you terminate the interpreter. +

+If the "python" command, instead of displaying the interpreter prompt ">>>", gives you a message like +

+

+    'python' is not recognized as an internal or external command,
+    operable program or batch file.
+
+or +

+

+    Bad command or filename
+
+then you need to make sure that your computer knows where to find the +Python interpreter. To do this you will have to modify a setting +called the PATH, which is a just list of directories where Windows +will look for programs. Rather than just enter the right command every +time you create a command window, you should arrange for Python's +installation directory to be added to the PATH of every command window +as it starts. If you installed Python fairly recently then the command +

+

+    dir C:\py*
+
+will probably tell you where it is installed. Alternatively, perhaps +you made a note. Otherwise you will be reduced to a search of your +whole disk ... break out the Windows explorer and use "Tools | Find" +or hit the "Search" button and look for "python.exe". Suppose you +discover that Python is installed in the C:\Python22 directory (the +default at the time of writing) then you should make sure that +entering the command +

+

+    c:\Python22\python
+
+starts up the interpreter as above (and don't forget you'll need a +"CTRL-Z" and an "Enter" to get out of it). Once you have verified the +directory, you need to add it to the start-up routines your computer +goes through. For older versions of Windows the easiest way to do +this is to edit the C:\AUTOEXEC.BAT file. You would want to add a line +like the following to AUTOEXEC.BAT: +

+

+    PATH C:\Python22;%PATH%
+
+For Windows NT, 2000 and (I assume) XP, you will need to add a string +such as +

+

+    ;C:\Python22
+
+to the current setting for the PATH environment variable, which you +will find in the properties window of "My Computer" under the +"Advanced" tab. Note that if you have sufficient privilege you might +get a choice of installing the settings either for the Current User or +for System. The latter is preferred if you want everybody to be able +to run Python on the machine. +

+If you aren't confident doing any of these manipulations yourself, ask +for help! At this stage you may or may not want to reboot your system +to make absolutely sure the new setting has "taken" (don't you love +the way Windows gives you these freqeuent coffee breaks). You probably +won't need to for Windows NT, XP or 2000. You can also avoid it in +earlier versions by editing the file C:\WINDOWS\COMMAND\CMDINIT.BAT +instead of AUTOEXEC.BAT. +

+You should now be able to start a new command window, enter +

+

+    python
+
+at the "C:>" (or whatever) prompt, and see the ">>>" prompt that +indicates the Python interpreter is reading interactive commands. +

+Let's suppose you have a program called "pytest.py" in directory +"C:\Steve\Projects\Python". A session to run that program might look +like this: +

+

+    C:\> cd \Steve\Projects\Python
+    C:\Steve\Projects\Python> python pytest.py
+
+Because you added a file name to the command to start the interpreter, +when it starts up it reads the Python script in the named file, +compiles it, executes it, and terminates (so you see another "C:\>" +prompt). You might also have entered +

+

+    C:\> python \Steve\Projects\Python\pytest.py
+
+if you hadn't wanted to change your current directory. +

+Under NT, 2000 and XP you may well find that the installation process +has also arranged that the command +

+

+    pytest.py
+
+(or, if the file isn't in the current directory) +

+

+    C:\Steve\Projects\Python\pytest.py
+
+will automatically recognize the ".py" extension and run the Python +interpreter on the named file. Using this feature is fine, but some +versions of Windows have bugs which mean that this form isn't exactly +equivalent to using the interpreter explicitly, so be careful. Easier +to remember, for now, that +

+

+    python C:\Steve\Projects\Python\pytest.py
+
+works pretty close to the same, and redirection will work (more) +reliably. +

+The important things to remember are: +

+1. Start Python from the Start Menu, or make sure the PATH is set +correctly so Windows can find the Python interpreter. +

+

+    python
+
+should give you a '>>>" prompt from the Python interpreter. Don't +forget the CTRL-Z and ENTER to terminate the interpreter (and, if you +started the window from the Start Menu, make the window disappear). +

+2. Once this works, you run programs with commands: +

+

+    python {program-file}
+
+3. When you know the commands to use you can build Windows shortcuts +to run the Python interpreter on any of your scripts, naming +particular working directories, and adding them to your menus, but +that's another lessFAQ. Take a look at +

+

+    python --help
+
+if your needs are complex. +

+4. Interactive mode (where you see the ">>>" prompt) is best used +not for running programs, which are better executed as in steps 2 +and 3, but for checking that individual statements and expressions do +what you think they will, and for developing code by experiment. +

+ +Edit this entry / +Log info + +/ Last changed on Tue Aug 20 16:19:53 2002 by +GvR +

+ +


+Python home / +Python FAQ Wizard 1.0.3 / +Feedback to GvR +

Python Powered
+ + --- python3.3-3.3.0.orig/debian/mincheck.py +++ python3.3-3.3.0/debian/mincheck.py @@ -0,0 +1,41 @@ + +import sys + +def get_listed(fn): + modules = set() + for line in open(fn).readlines(): + modules.add(line.split()[1]) + return modules + +def get_dependencies(fn): + t = eval(open(fn).read()) + modules = set() + depgraph = t['depgraph'] + for mod, deps in depgraph.items(): + if mod != '__main__': + modules.add(mod) + modules.update(deps.keys()) + return depgraph, modules + +def main(): + mods = get_listed(sys.argv[1]) + depgraph, deps = get_dependencies(sys.argv[2]) + print("Listed modules:", sorted(mods)) + print("") + print("Dependent modules:", sorted(deps)) + print("") + + missing = deps.difference(mods) + if missing: + print("Missing modules in python-minimal:") + print(missing) + for m in missing: + users = [] + for caller, callees in depgraph.items(): + if m in callees: + users.append(caller) + print(m, "used in: ", users) + sys.exit(len(missing)) + +main() + --- python3.3-3.3.0.orig/debian/idle-PVER.overrides.in +++ python3.3-3.3.0/debian/idle-PVER.overrides.in @@ -0,0 +1,2 @@ +# icon in dependent package +idle-@PVER@ binary: menu-icon-missing --- python3.3-3.3.0.orig/debian/PVER-doc.doc-base.PVER-tut.in +++ python3.3-3.3.0/debian/PVER-doc.doc-base.PVER-tut.in @@ -0,0 +1,13 @@ +Document: @PVER@-tut +Title: Python Tutorial (v@VER@) +Author: Guido van Rossum, Fred L. Drake, Jr., editor +Abstract: This tutorial introduces the reader informally to the basic + concepts and features of the Python language and system. It helps + to have a Python interpreter handy for hands-on experience, but + all examples are self-contained, so the tutorial can be read + off-line as well. +Section: Programming/Python + +Format: HTML +Index: /usr/share/doc/@PVER@/html/tutorial/index.html +Files: /usr/share/doc/@PVER@/html/tutorial/*.html --- python3.3-3.3.0.orig/debian/libpython.symbols.in +++ python3.3-3.3.0/debian/libpython.symbols.in @@ -0,0 +1,1466 @@ + PyAST_Check@Base @SVER@ + PyAST_Compile@Base @SVER@ + PyAST_CompileEx@Base @SVER@ + PyAST_FromNode@Base @SVER@ + PyAST_Validate@Base @SVER@ + PyAST_mod2obj@Base @SVER@ + PyAST_obj2mod@Base @SVER@ + PyArena_AddPyObject@Base @SVER@ + PyArena_Free@Base @SVER@ + PyArena_Malloc@Base @SVER@ + PyArena_New@Base @SVER@ + PyArg_Parse@Base @SVER@ + PyArg_ParseTuple@Base @SVER@ + PyArg_ParseTupleAndKeywords@Base @SVER@ + PyArg_UnpackTuple@Base @SVER@ + PyArg_VaParse@Base @SVER@ + PyArg_VaParseTupleAndKeywords@Base @SVER@ + PyArg_ValidateKeywordArguments@Base @SVER@ + PyBaseObject_Type@Base @SVER@ + PyBool_FromLong@Base @SVER@ + PyBool_Type@Base @SVER@ + PyBuffer_FillContiguousStrides@Base @SVER@ + PyBuffer_FillInfo@Base @SVER@ + PyBuffer_FromContiguous@Base @SVER@ + PyBuffer_GetPointer@Base @SVER@ + PyBuffer_IsContiguous@Base @SVER@ + PyBuffer_Release@Base @SVER@ + PyBuffer_ToContiguous@Base @SVER@ + PyBufferedIOBase_Type@Base @SVER@ + PyBufferedRWPair_Type@Base @SVER@ + PyBufferedRandom_Type@Base @SVER@ + PyBufferedReader_Type@Base @SVER@ + PyBufferedWriter_Type@Base @SVER@ + PyByteArrayIter_Type@Base @SVER@ + PyByteArray_AsString@Base @SVER@ + PyByteArray_Concat@Base @SVER@ + PyByteArray_Fini@Base @SVER@ + PyByteArray_FromObject@Base @SVER@ + PyByteArray_FromStringAndSize@Base @SVER@ + PyByteArray_Init@Base @SVER@ + PyByteArray_Resize@Base @SVER@ + PyByteArray_Size@Base @SVER@ + PyByteArray_Type@Base @SVER@ + PyBytesIO_Type@Base @SVER@ + PyBytesIter_Type@Base @SVER@ + PyBytes_AsString@Base @SVER@ + PyBytes_AsStringAndSize@Base @SVER@ + PyBytes_Concat@Base @SVER@ + PyBytes_ConcatAndDel@Base @SVER@ + PyBytes_DecodeEscape@Base @SVER@ + PyBytes_Fini@Base @SVER@ + PyBytes_FromFormat@Base @SVER@ + PyBytes_FromFormatV@Base @SVER@ + PyBytes_FromObject@Base @SVER@ + PyBytes_FromString@Base @SVER@ + PyBytes_FromStringAndSize@Base @SVER@ + PyBytes_Repr@Base @SVER@ + PyBytes_Size@Base @SVER@ + PyBytes_Type@Base @SVER@ + (optional)PyCArgObject_new@Base @SVER@ + (optional)PyCArg_Type@Base @SVER@ + (optional)PyCArrayType_Type@Base @SVER@ + (optional)PyCArrayType_from_ctype@Base @SVER@ + (optional)PyCArray_Type@Base @SVER@ + (optional)PyCData_AtAddress@Base @SVER@ + (optional)PyCData_FromBaseObj@Base @SVER@ + (optional)PyCData_Type@Base @SVER@ + (optional)PyCData_get@Base @SVER@ + (optional)PyCData_set@Base @SVER@ + (optional)PyCField_FromDesc@Base @SVER@ + (optional)PyCField_Type@Base @SVER@ + (optional)PyCFuncPtrType_Type@Base @SVER@ + (optional)PyCFuncPtr_Type@Base @SVER@ + PyCFunction_Call@Base @SVER@ + PyCFunction_ClearFreeList@Base @SVER@ + PyCFunction_Fini@Base @SVER@ + PyCFunction_GetFlags@Base @SVER@ + PyCFunction_GetFunction@Base @SVER@ + PyCFunction_GetSelf@Base @SVER@ + PyCFunction_New@Base @SVER@ + PyCFunction_NewEx@Base @SVER@ + PyCFunction_Type@Base @SVER@ + (optional)PyCPointerType_Type@Base @SVER@ + (optional)PyCPointer_Type@Base @SVER@ + (optional)PyCSimpleType_Type@Base @SVER@ + (optional)PyCStgDict_Type@Base @SVER@ + (optional)PyCStgDict_clone@Base @SVER@ + (optional)PyCStructType_Type@Base @SVER@ + (optional)PyCStructUnionType_update_stgdict@Base @SVER@ + (optional)PyCThunk_Type@Base @SVER@ + PyCallIter_New@Base @SVER@ + PyCallIter_Type@Base @SVER@ + PyCallable_Check@Base @SVER@ + PyCapsule_GetContext@Base @SVER@ + PyCapsule_GetDestructor@Base @SVER@ + PyCapsule_GetName@Base @SVER@ + PyCapsule_GetPointer@Base @SVER@ + PyCapsule_Import@Base @SVER@ + PyCapsule_IsValid@Base @SVER@ + PyCapsule_New@Base @SVER@ + PyCapsule_SetContext@Base @SVER@ + PyCapsule_SetDestructor@Base @SVER@ + PyCapsule_SetName@Base @SVER@ + PyCapsule_SetPointer@Base @SVER@ + PyCapsule_Type@Base @SVER@ + PyCell_Get@Base @SVER@ + PyCell_New@Base @SVER@ + PyCell_Set@Base @SVER@ + PyCell_Type@Base @SVER@ + PyClassMethodDescr_Type@Base @SVER@ + PyClassMethod_New@Base @SVER@ + PyClassMethod_Type@Base @SVER@ + PyCode_Addr2Line@Base @SVER@ + PyCode_New@Base @SVER@ + PyCode_NewEmpty@Base @SVER@ + PyCode_Optimize@Base @SVER@ + PyCode_Type@Base @SVER@ + PyCodec_BackslashReplaceErrors@Base @SVER@ + PyCodec_Decode@Base @SVER@ + PyCodec_Decoder@Base @SVER@ + PyCodec_Encode@Base @SVER@ + PyCodec_Encoder@Base @SVER@ + PyCodec_IgnoreErrors@Base @SVER@ + PyCodec_IncrementalDecoder@Base @SVER@ + PyCodec_IncrementalEncoder@Base @SVER@ + PyCodec_KnownEncoding@Base @SVER@ + PyCodec_LookupError@Base @SVER@ + PyCodec_Register@Base @SVER@ + PyCodec_RegisterError@Base @SVER@ + PyCodec_ReplaceErrors@Base @SVER@ + PyCodec_StreamReader@Base @SVER@ + PyCodec_StreamWriter@Base @SVER@ + PyCodec_StrictErrors@Base @SVER@ + PyCodec_XMLCharRefReplaceErrors@Base @SVER@ + PyCompileString@Base @SVER@ + PyComplex_AsCComplex@Base @SVER@ + PyComplex_FromCComplex@Base @SVER@ + PyComplex_FromDoubles@Base @SVER@ + PyComplex_ImagAsDouble@Base @SVER@ + PyComplex_RealAsDouble@Base @SVER@ + PyComplex_Type@Base @SVER@ + PyDescr_NewClassMethod@Base @SVER@ + PyDescr_NewGetSet@Base @SVER@ + PyDescr_NewMember@Base @SVER@ + PyDescr_NewMethod@Base @SVER@ + PyDescr_NewWrapper@Base @SVER@ + PyDictItems_Type@Base @SVER@ + PyDictIterItem_Type@Base @SVER@ + PyDictIterKey_Type@Base @SVER@ + PyDictIterValue_Type@Base @SVER@ + PyDictKeys_Type@Base @SVER@ + PyDictProxy_New@Base @SVER@ + PyDictProxy_Type@Base @SVER@ + PyDictValues_Type@Base @SVER@ + PyDict_Clear@Base @SVER@ + PyDict_ClearFreeList@Base @SVER@ + PyDict_Contains@Base @SVER@ + PyDict_Copy@Base @SVER@ + PyDict_DelItem@Base @SVER@ + PyDict_DelItemString@Base @SVER@ + PyDict_Fini@Base @SVER@ + PyDict_GetItem@Base @SVER@ + (optional)PyDict_GetItemProxy@Base @SVER@ + PyDict_GetItemString@Base @SVER@ + PyDict_GetItemWithError@Base @SVER@ + PyDict_Items@Base @SVER@ + PyDict_Keys@Base @SVER@ + PyDict_Merge@Base @SVER@ + PyDict_MergeFromSeq2@Base @SVER@ + PyDict_New@Base @SVER@ + PyDict_Next@Base @SVER@ + PyDict_SetItem@Base @SVER@ + (optional)PyDict_SetItemProxy@Base @SVER@ + PyDict_SetItemString@Base @SVER@ + PyDict_Size@Base @SVER@ + PyDict_Type@Base @SVER@ + PyDict_Update@Base @SVER@ + PyDict_Values@Base @SVER@ + PyEllipsis_Type@Base @SVER@ + PyEnum_Type@Base @SVER@ + PyErr_BadArgument@Base @SVER@ + PyErr_BadInternalCall@Base @SVER@ + PyErr_CheckSignals@Base @SVER@ + PyErr_Clear@Base @SVER@ + PyErr_Display@Base @SVER@ + PyErr_ExceptionMatches@Base @SVER@ + PyErr_Fetch@Base @SVER@ + PyErr_Format@Base @SVER@ + PyErr_GetExcInfo@Base @SVER@ + PyErr_GivenExceptionMatches@Base @SVER@ + PyErr_NewException@Base @SVER@ + PyErr_NewExceptionWithDoc@Base @SVER@ + PyErr_NoMemory@Base @SVER@ + PyErr_NormalizeException@Base @SVER@ + PyErr_Occurred@Base @SVER@ + PyErr_Print@Base @SVER@ + PyErr_PrintEx@Base @SVER@ + PyErr_ProgramText@Base @SVER@ + PyErr_Restore@Base @SVER@ + PyErr_SetExcInfo@Base @SVER@ + PyErr_SetFromErrno@Base @SVER@ + PyErr_SetFromErrnoWithFilename@Base @SVER@ + PyErr_SetFromErrnoWithFilenameObject@Base @SVER@ + PyErr_SetImportError@Base @SVER@ + PyErr_SetInterrupt@Base @SVER@ + PyErr_SetNone@Base @SVER@ + PyErr_SetObject@Base @SVER@ + PyErr_SetString@Base @SVER@ + PyErr_SyntaxLocation@Base @SVER@ + PyErr_SyntaxLocationEx@Base @SVER@ + PyErr_Warn@Base @SVER@ + PyErr_WarnEx@Base @SVER@ + PyErr_WarnExplicit@Base @SVER@ + PyErr_WarnFormat@Base @SVER@ + PyErr_WriteUnraisable@Base @SVER@ + PyEval_AcquireLock@Base @SVER@ + PyEval_AcquireThread@Base @SVER@ + PyEval_CallFunction@Base @SVER@ + PyEval_CallMethod@Base @SVER@ + PyEval_CallObjectWithKeywords@Base @SVER@ + PyEval_EvalCode@Base @SVER@ + PyEval_EvalCodeEx@Base @SVER@ + PyEval_EvalFrame@Base @SVER@ + PyEval_EvalFrameEx@Base @SVER@ + PyEval_GetBuiltins@Base @SVER@ + PyEval_GetCallStats@Base @SVER@ + PyEval_GetFrame@Base @SVER@ + PyEval_GetFuncDesc@Base @SVER@ + PyEval_GetFuncName@Base @SVER@ + PyEval_GetGlobals@Base @SVER@ + PyEval_GetLocals@Base @SVER@ + PyEval_InitThreads@Base @SVER@ + PyEval_MergeCompilerFlags@Base @SVER@ + PyEval_ReInitThreads@Base @SVER@ + PyEval_ReleaseLock@Base @SVER@ + PyEval_ReleaseThread@Base @SVER@ + PyEval_RestoreThread@Base @SVER@ + PyEval_SaveThread@Base @SVER@ + PyEval_SetProfile@Base @SVER@ + PyEval_SetTrace@Base @SVER@ + PyEval_ThreadsInitialized@Base @SVER@ + (optional)PyExc_ArgError@Base @SVER@ + PyExc_ArithmeticError@Base @SVER@ + PyExc_AssertionError@Base @SVER@ + PyExc_AttributeError@Base @SVER@ + PyExc_BaseException@Base @SVER@ + PyExc_BlockingIOError@Base @SVER@ + PyExc_BrokenPipeError@Base @SVER@ + PyExc_BufferError@Base @SVER@ + PyExc_BytesWarning@Base @SVER@ + PyExc_ChildProcessError@Base @SVER@ + PyExc_ConnectionAbortedError@Base @SVER@ + PyExc_ConnectionError@Base @SVER@ + PyExc_ConnectionRefusedError@Base @SVER@ + PyExc_ConnectionResetError@Base @SVER@ + PyExc_DeprecationWarning@Base @SVER@ + PyExc_EOFError@Base @SVER@ + PyExc_EnvironmentError@Base @SVER@ + PyExc_Exception@Base @SVER@ + PyExc_FileExistsError@Base @SVER@ + PyExc_FileNotFoundError@Base @SVER@ + PyExc_FloatingPointError@Base @SVER@ + PyExc_FutureWarning@Base @SVER@ + PyExc_GeneratorExit@Base @SVER@ + PyExc_IOError@Base @SVER@ + PyExc_ImportError@Base @SVER@ + PyExc_ImportWarning@Base @SVER@ + PyExc_IndentationError@Base @SVER@ + PyExc_IndexError@Base @SVER@ + PyExc_InterruptedError@Base @SVER@ + PyExc_IsADirectoryError@Base @SVER@ + PyExc_KeyError@Base @SVER@ + PyExc_KeyboardInterrupt@Base @SVER@ + PyExc_LookupError@Base @SVER@ + PyExc_MemoryError@Base @SVER@ + PyExc_NameError@Base @SVER@ + PyExc_NotADirectoryError@Base @SVER@ + PyExc_NotImplementedError@Base @SVER@ + PyExc_OSError@Base @SVER@ + PyExc_OverflowError@Base @SVER@ + PyExc_PendingDeprecationWarning@Base @SVER@ + PyExc_PermissionError@Base @SVER@ + PyExc_ProcessLookupError@Base @SVER@ + PyExc_RecursionErrorInst@Base @SVER@ + PyExc_ReferenceError@Base @SVER@ + PyExc_ResourceWarning@Base @SVER@ + PyExc_RuntimeError@Base @SVER@ + PyExc_RuntimeWarning@Base @SVER@ + PyExc_StopIteration@Base @SVER@ + PyExc_SyntaxError@Base @SVER@ + PyExc_SyntaxWarning@Base @SVER@ + PyExc_SystemError@Base @SVER@ + PyExc_SystemExit@Base @SVER@ + PyExc_TabError@Base @SVER@ + PyExc_TimeoutError@Base @SVER@ + PyExc_TypeError@Base @SVER@ + PyExc_UnboundLocalError@Base @SVER@ + PyExc_UnicodeDecodeError@Base @SVER@ + PyExc_UnicodeEncodeError@Base @SVER@ + PyExc_UnicodeError@Base @SVER@ + PyExc_UnicodeTranslateError@Base @SVER@ + PyExc_UnicodeWarning@Base @SVER@ + PyExc_UserWarning@Base @SVER@ + PyExc_ValueError@Base @SVER@ + PyExc_Warning@Base @SVER@ + PyExc_ZeroDivisionError@Base @SVER@ + PyException_GetCause@Base @SVER@ + PyException_GetContext@Base @SVER@ + PyException_GetTraceback@Base @SVER@ + PyException_SetCause@Base @SVER@ + PyException_SetContext@Base @SVER@ + PyException_SetTraceback@Base @SVER@ + PyFPE_counter@Base @SVER@ + PyFPE_dummy@Base @SVER@ + PyFPE_jbuf@Base @SVER@ + PyFileIO_Type@Base @SVER@ + PyFile_FromFd@Base @SVER@ + PyFile_GetLine@Base @SVER@ + PyFile_NewStdPrinter@Base @SVER@ + PyFile_WriteObject@Base @SVER@ + PyFile_WriteString@Base @SVER@ + PyFilter_Type@Base @SVER@ + PyFloat_AsDouble@Base @SVER@ + PyFloat_ClearFreeList@Base @SVER@ + PyFloat_Fini@Base @SVER@ + PyFloat_FromDouble@Base @SVER@ + PyFloat_FromString@Base @SVER@ + PyFloat_GetInfo@Base @SVER@ + PyFloat_GetMax@Base @SVER@ + PyFloat_GetMin@Base @SVER@ + PyFloat_Type@Base @SVER@ + PyFrame_BlockPop@Base @SVER@ + PyFrame_BlockSetup@Base @SVER@ + PyFrame_ClearFreeList@Base @SVER@ + PyFrame_FastToLocals@Base @SVER@ + PyFrame_Fini@Base @SVER@ + PyFrame_GetLineNumber@Base @SVER@ + PyFrame_LocalsToFast@Base @SVER@ + PyFrame_New@Base @SVER@ + PyFrame_Type@Base @SVER@ + PyFrozenSet_New@Base @SVER@ + PyFrozenSet_Type@Base @SVER@ + PyFunction_GetAnnotations@Base @SVER@ + PyFunction_GetClosure@Base @SVER@ + PyFunction_GetCode@Base @SVER@ + PyFunction_GetDefaults@Base @SVER@ + PyFunction_GetGlobals@Base @SVER@ + PyFunction_GetKwDefaults@Base @SVER@ + PyFunction_GetModule@Base @SVER@ + PyFunction_New@Base @SVER@ + PyFunction_NewWithQualName@Base @SVER@ + PyFunction_SetAnnotations@Base @SVER@ + PyFunction_SetClosure@Base @SVER@ + PyFunction_SetDefaults@Base @SVER@ + PyFunction_SetKwDefaults@Base @SVER@ + PyFunction_Type@Base @SVER@ + PyFuture_FromAST@Base @SVER@ + PyGC_Collect@Base @SVER@ + PyGILState_Ensure@Base @SVER@ + PyGILState_GetThisThreadState@Base @SVER@ + PyGILState_Release@Base @SVER@ + PyGen_NeedsFinalizing@Base @SVER@ + PyGen_New@Base @SVER@ + PyGen_Type@Base @SVER@ + PyGetSetDescr_Type@Base @SVER@ + PyGrammar_AddAccelerators@Base @SVER@ + PyGrammar_FindDFA@Base @SVER@ + PyGrammar_LabelRepr@Base @SVER@ + PyGrammar_RemoveAccelerators@Base @SVER@ + PyIOBase_Type@Base @SVER@ + PyImport_AddModule@Base @SVER@ + PyImport_AddModuleObject@Base @SVER@ + PyImport_AppendInittab@Base @SVER@ + PyImport_Cleanup@Base @SVER@ + PyImport_ExecCodeModule@Base @SVER@ + PyImport_ExecCodeModuleEx@Base @SVER@ + PyImport_ExecCodeModuleObject@Base @SVER@ + PyImport_ExecCodeModuleWithPathnames@Base @SVER@ + PyImport_ExtendInittab@Base @SVER@ + PyImport_FrozenModules@Base @SVER@ + PyImport_GetImporter@Base @SVER@ + PyImport_GetMagicNumber@Base @SVER@ + PyImport_GetMagicTag@Base @SVER@ + PyImport_GetModuleDict@Base @SVER@ + PyImport_Import@Base @SVER@ + PyImport_ImportFrozenModule@Base @SVER@ + PyImport_ImportFrozenModuleObject@Base @SVER@ + PyImport_ImportModule@Base @SVER@ + PyImport_ImportModuleLevel@Base @SVER@ + PyImport_ImportModuleLevelObject@Base @SVER@ + PyImport_ImportModuleNoBlock@Base @SVER@ + PyImport_Inittab@Base @SVER@ + PyImport_ReloadModule@Base @SVER@ + PyIncrementalNewlineDecoder_Type@Base @SVER@ + PyInstanceMethod_Function@Base @SVER@ + PyInstanceMethod_New@Base @SVER@ + PyInstanceMethod_Type@Base @SVER@ + PyInterpreterState_Clear@Base @SVER@ + PyInterpreterState_Delete@Base @SVER@ + PyInterpreterState_Head@Base @SVER@ + PyInterpreterState_New@Base @SVER@ + PyInterpreterState_Next@Base @SVER@ + PyInterpreterState_ThreadHead@Base @SVER@ + PyIter_Next@Base @SVER@ + PyListIter_Type@Base @SVER@ + PyListRevIter_Type@Base @SVER@ + PyList_Append@Base @SVER@ + PyList_AsTuple@Base @SVER@ + PyList_ClearFreeList@Base @SVER@ + PyList_Fini@Base @SVER@ + PyList_GetItem@Base @SVER@ + PyList_GetSlice@Base @SVER@ + PyList_Insert@Base @SVER@ + PyList_New@Base @SVER@ + PyList_Reverse@Base @SVER@ + PyList_SetItem@Base @SVER@ + PyList_SetSlice@Base @SVER@ + PyList_Size@Base @SVER@ + PyList_Sort@Base @SVER@ + PyList_Type@Base @SVER@ + PyLongRangeIter_Type@Base @SVER@ + PyLong_AsDouble@Base @SVER@ + PyLong_AsLong@Base @SVER@ + PyLong_AsLongAndOverflow@Base @SVER@ + PyLong_AsLongLong@Base @SVER@ + PyLong_AsLongLongAndOverflow@Base @SVER@ + PyLong_AsSize_t@Base @SVER@ + PyLong_AsSsize_t@Base @SVER@ + PyLong_AsUnsignedLong@Base @SVER@ + PyLong_AsUnsignedLongLong@Base @SVER@ + PyLong_AsUnsignedLongLongMask@Base @SVER@ + PyLong_AsUnsignedLongMask@Base @SVER@ + PyLong_AsVoidPtr@Base @SVER@ + PyLong_Fini@Base @SVER@ + PyLong_FromDouble@Base @SVER@ + PyLong_FromLong@Base @SVER@ + PyLong_FromLongLong@Base @SVER@ + PyLong_FromSize_t@Base @SVER@ + PyLong_FromSsize_t@Base @SVER@ + PyLong_FromString@Base @SVER@ + PyLong_FromUnicode@Base @SVER@ + PyLong_FromUnicodeObject@Base @SVER@ + PyLong_FromUnsignedLong@Base @SVER@ + PyLong_FromUnsignedLongLong@Base @SVER@ + PyLong_FromVoidPtr@Base @SVER@ + PyLong_GetInfo@Base @SVER@ + PyLong_Type@Base @SVER@ + PyMap_Type@Base @SVER@ + PyMapping_Check@Base @SVER@ + PyMapping_GetItemString@Base @SVER@ + PyMapping_HasKey@Base @SVER@ + PyMapping_HasKeyString@Base @SVER@ + PyMapping_Items@Base @SVER@ + PyMapping_Keys@Base @SVER@ + PyMapping_Length@Base @SVER@ + PyMapping_SetItemString@Base @SVER@ + PyMapping_Size@Base @SVER@ + PyMapping_Values@Base @SVER@ + PyMarshal_Init@Base @SVER@ + PyMarshal_ReadLastObjectFromFile@Base @SVER@ + PyMarshal_ReadLongFromFile@Base @SVER@ + PyMarshal_ReadObjectFromFile@Base @SVER@ + PyMarshal_ReadObjectFromString@Base @SVER@ + PyMarshal_ReadShortFromFile@Base @SVER@ + PyMarshal_WriteLongToFile@Base @SVER@ + PyMarshal_WriteObjectToFile@Base @SVER@ + PyMarshal_WriteObjectToString@Base @SVER@ + PyMem_Free@Base @SVER@ + PyMem_Malloc@Base @SVER@ + PyMem_Realloc@Base @SVER@ + PyMemberDescr_Type@Base @SVER@ + PyMember_GetOne@Base @SVER@ + PyMember_SetOne@Base @SVER@ + PyMemoryView_FromBuffer@Base @SVER@ + PyMemoryView_FromMemory@Base @SVER@ + PyMemoryView_FromObject@Base @SVER@ + PyMemoryView_GetContiguous@Base @SVER@ + PyMemoryView_Type@Base @SVER@ + PyMethodDescr_Type@Base @SVER@ + PyMethod_ClearFreeList@Base @SVER@ + PyMethod_Fini@Base @SVER@ + PyMethod_Function@Base @SVER@ + PyMethod_New@Base @SVER@ + PyMethod_Self@Base @SVER@ + PyMethod_Type@Base @SVER@ + PyModule_AddIntConstant@Base @SVER@ + PyModule_AddObject@Base @SVER@ + PyModule_AddStringConstant@Base @SVER@ + PyModule_GetDef@Base @SVER@ + PyModule_GetDict@Base @SVER@ + PyModule_GetFilename@Base @SVER@ + PyModule_GetFilenameObject@Base @SVER@ + PyModule_GetName@Base @SVER@ + PyModule_GetNameObject@Base @SVER@ + PyModule_GetState@Base @SVER@ + PyModule_GetWarningsModule@Base @SVER@ + PyModule_New@Base @SVER@ + PyModule_NewObject@Base @SVER@ + PyModule_Type@Base @SVER@ + PyNode_AddChild@Base @SVER@ + PyNode_Compile@Base @SVER@ + PyNode_Free@Base @SVER@ + PyNode_ListTree@Base @SVER@ + PyNode_New@Base @SVER@ + PyNumber_Absolute@Base @SVER@ + PyNumber_Add@Base @SVER@ + PyNumber_And@Base @SVER@ + PyNumber_AsOff_t@Base @SVER@ + PyNumber_AsSsize_t@Base @SVER@ + PyNumber_Check@Base @SVER@ + PyNumber_Divmod@Base @SVER@ + PyNumber_Float@Base @SVER@ + PyNumber_FloorDivide@Base @SVER@ + PyNumber_InPlaceAdd@Base @SVER@ + PyNumber_InPlaceAnd@Base @SVER@ + PyNumber_InPlaceFloorDivide@Base @SVER@ + PyNumber_InPlaceLshift@Base @SVER@ + PyNumber_InPlaceMultiply@Base @SVER@ + PyNumber_InPlaceOr@Base @SVER@ + PyNumber_InPlacePower@Base @SVER@ + PyNumber_InPlaceRemainder@Base @SVER@ + PyNumber_InPlaceRshift@Base @SVER@ + PyNumber_InPlaceSubtract@Base @SVER@ + PyNumber_InPlaceTrueDivide@Base @SVER@ + PyNumber_InPlaceXor@Base @SVER@ + PyNumber_Index@Base @SVER@ + PyNumber_Invert@Base @SVER@ + PyNumber_Long@Base @SVER@ + PyNumber_Lshift@Base @SVER@ + PyNumber_Multiply@Base @SVER@ + PyNumber_Negative@Base @SVER@ + PyNumber_Or@Base @SVER@ + PyNumber_Positive@Base @SVER@ + PyNumber_Power@Base @SVER@ + PyNumber_Remainder@Base @SVER@ + PyNumber_Rshift@Base @SVER@ + PyNumber_Subtract@Base @SVER@ + PyNumber_ToBase@Base @SVER@ + PyNumber_TrueDivide@Base @SVER@ + PyNumber_Xor@Base @SVER@ + PyOS_AfterFork@Base @SVER@ + PyOS_FiniInterrupts@Base @SVER@ + PyOS_InitInterrupts@Base @SVER@ + PyOS_InputHook@Base @SVER@ + PyOS_InterruptOccurred@Base @SVER@ + PyOS_Readline@Base @SVER@ + PyOS_ReadlineFunctionPointer@Base @SVER@ + PyOS_StdioReadline@Base @SVER@ + PyOS_double_to_string@Base @SVER@ + PyOS_getsig@Base @SVER@ + PyOS_mystricmp@Base @SVER@ + PyOS_mystrnicmp@Base @SVER@ + PyOS_setsig@Base @SVER@ + PyOS_snprintf@Base @SVER@ + PyOS_string_to_double@Base @SVER@ + PyOS_strtol@Base @SVER@ + PyOS_strtoul@Base @SVER@ + PyOS_vsnprintf@Base @SVER@ + PyObject_ASCII@Base @SVER@ + PyObject_AsCharBuffer@Base @SVER@ + PyObject_AsFileDescriptor@Base @SVER@ + PyObject_AsReadBuffer@Base @SVER@ + PyObject_AsWriteBuffer@Base @SVER@ + PyObject_Bytes@Base @SVER@ + PyObject_Call@Base @SVER@ + PyObject_CallFunction@Base @SVER@ + PyObject_CallFunctionObjArgs@Base @SVER@ + PyObject_CallMethod@Base @SVER@ + PyObject_CallMethodObjArgs@Base @SVER@ + PyObject_CallObject@Base @SVER@ + PyObject_CheckReadBuffer@Base @SVER@ + PyObject_ClearWeakRefs@Base @SVER@ + PyObject_CopyData@Base @SVER@ + PyObject_DelItem@Base @SVER@ + PyObject_DelItemString@Base @SVER@ + PyObject_Dir@Base @SVER@ + PyObject_Format@Base @SVER@ + PyObject_Free@Base @SVER@ + PyObject_GC_Del@Base @SVER@ + PyObject_GC_Track@Base @SVER@ + PyObject_GC_UnTrack@Base @SVER@ + PyObject_GenericGetAttr@Base @SVER@ + PyObject_GenericGetDict@Base @SVER@ + PyObject_GenericSetAttr@Base @SVER@ + PyObject_GenericSetDict@Base @SVER@ + PyObject_GetAttr@Base @SVER@ + PyObject_GetAttrString@Base @SVER@ + PyObject_GetBuffer@Base @SVER@ + PyObject_GetItem@Base @SVER@ + PyObject_GetIter@Base @SVER@ + PyObject_HasAttr@Base @SVER@ + PyObject_HasAttrString@Base @SVER@ + PyObject_Hash@Base @SVER@ + PyObject_HashNotImplemented@Base @SVER@ + PyObject_Init@Base @SVER@ + PyObject_InitVar@Base @SVER@ + PyObject_IsInstance@Base @SVER@ + PyObject_IsSubclass@Base @SVER@ + PyObject_IsTrue@Base @SVER@ + PyObject_Length@Base @SVER@ + PyObject_Malloc@Base @SVER@ + PyObject_Not@Base @SVER@ + PyObject_Print@Base @SVER@ + PyObject_Realloc@Base @SVER@ + PyObject_Repr@Base @SVER@ + PyObject_RichCompare@Base @SVER@ + PyObject_RichCompareBool@Base @SVER@ + PyObject_SelfIter@Base @SVER@ + PyObject_SetAttr@Base @SVER@ + PyObject_SetAttrString@Base @SVER@ + PyObject_SetItem@Base @SVER@ + PyObject_Size@Base @SVER@ + PyObject_Str@Base @SVER@ + PyObject_Type@Base @SVER@ + (optional)PyObject_stgdict@Base @SVER@ + PyParser_ASTFromFile@Base @SVER@ + PyParser_ASTFromString@Base @SVER@ + PyParser_AddToken@Base @SVER@ + PyParser_ClearError@Base @SVER@ + PyParser_Delete@Base @SVER@ + PyParser_New@Base @SVER@ + PyParser_ParseFile@Base @SVER@ + PyParser_ParseFileFlags@Base @SVER@ + PyParser_ParseFileFlagsEx@Base @SVER@ + PyParser_ParseString@Base @SVER@ + PyParser_ParseStringFlags@Base @SVER@ + PyParser_ParseStringFlagsFilename@Base @SVER@ + PyParser_ParseStringFlagsFilenameEx@Base @SVER@ + PyParser_SetError@Base @SVER@ + PyParser_SimpleParseFile@Base @SVER@ + PyParser_SimpleParseFileFlags@Base @SVER@ + PyParser_SimpleParseString@Base @SVER@ + PyParser_SimpleParseStringFilename@Base @SVER@ + PyParser_SimpleParseStringFlags@Base @SVER@ + PyParser_SimpleParseStringFlagsFilename@Base @SVER@ + PyProperty_Type@Base @SVER@ + PyRangeIter_Type@Base @SVER@ + PyRange_Type@Base @SVER@ + PyRawIOBase_Type@Base @SVER@ + PyReversed_Type@Base @SVER@ + PyRun_AnyFile@Base @SVER@ + PyRun_AnyFileEx@Base @SVER@ + PyRun_AnyFileExFlags@Base @SVER@ + PyRun_AnyFileFlags@Base @SVER@ + PyRun_File@Base @SVER@ + PyRun_FileEx@Base @SVER@ + PyRun_FileExFlags@Base @SVER@ + PyRun_FileFlags@Base @SVER@ + PyRun_InteractiveLoop@Base @SVER@ + PyRun_InteractiveLoopFlags@Base @SVER@ + PyRun_InteractiveOne@Base @SVER@ + PyRun_InteractiveOneFlags@Base @SVER@ + PyRun_SimpleFile@Base @SVER@ + PyRun_SimpleFileEx@Base @SVER@ + PyRun_SimpleFileExFlags@Base @SVER@ + PyRun_SimpleString@Base @SVER@ + PyRun_SimpleStringFlags@Base @SVER@ + PyRun_String@Base @SVER@ + PyRun_StringFlags@Base @SVER@ + PySTEntry_Type@Base @SVER@ + PyST_GetScope@Base @SVER@ + PySeqIter_New@Base @SVER@ + PySeqIter_Type@Base @SVER@ + PySequence_Check@Base @SVER@ + PySequence_Concat@Base @SVER@ + PySequence_Contains@Base @SVER@ + PySequence_Count@Base @SVER@ + PySequence_DelItem@Base @SVER@ + PySequence_DelSlice@Base @SVER@ + PySequence_Fast@Base @SVER@ + PySequence_GetItem@Base @SVER@ + PySequence_GetSlice@Base @SVER@ + PySequence_In@Base @SVER@ + PySequence_InPlaceConcat@Base @SVER@ + PySequence_InPlaceRepeat@Base @SVER@ + PySequence_Index@Base @SVER@ + PySequence_Length@Base @SVER@ + PySequence_List@Base @SVER@ + PySequence_Repeat@Base @SVER@ + PySequence_SetItem@Base @SVER@ + PySequence_SetSlice@Base @SVER@ + PySequence_Size@Base @SVER@ + PySequence_Tuple@Base @SVER@ + PySetIter_Type@Base @SVER@ + PySet_Add@Base @SVER@ + PySet_Clear@Base @SVER@ + PySet_ClearFreeList@Base @SVER@ + PySet_Contains@Base @SVER@ + PySet_Discard@Base @SVER@ + PySet_Fini@Base @SVER@ + PySet_New@Base @SVER@ + PySet_Pop@Base @SVER@ + PySet_Size@Base @SVER@ + PySet_Type@Base @SVER@ + PySignal_SetWakeupFd@Base @SVER@ + PySlice_Fini@Base @SVER@ + PySlice_GetIndices@Base @SVER@ + PySlice_GetIndicesEx@Base @SVER@ + PySlice_New@Base @SVER@ + PySlice_Type@Base @SVER@ + PyState_AddModule@Base @SVER@ + PyState_FindModule@Base @SVER@ + PyState_RemoveModule@Base @SVER@ + PyStaticMethod_New@Base @SVER@ + PyStaticMethod_Type@Base @SVER@ + PyStdPrinter_Type@Base @SVER@ + PyStringIO_Type@Base @SVER@ + PyStructSequence_GetItem@Base @SVER@ + PyStructSequence_InitType@Base @SVER@ + PyStructSequence_New@Base @SVER@ + PyStructSequence_NewType@Base @SVER@ + PyStructSequence_SetItem@Base @SVER@ + PyStructSequence_UnnamedField@Base @SVER@ + PySuper_Type@Base @SVER@ + PySymtable_Build@Base @SVER@ + PySymtable_Free@Base @SVER@ + PySymtable_Lookup@Base @SVER@ + PySys_AddWarnOption@Base @SVER@ + PySys_AddWarnOptionUnicode@Base @SVER@ + PySys_AddXOption@Base @SVER@ + PySys_FormatStderr@Base @SVER@ + PySys_FormatStdout@Base @SVER@ + PySys_GetObject@Base @SVER@ + PySys_GetXOptions@Base @SVER@ + PySys_HasWarnOptions@Base @SVER@ + PySys_ResetWarnOptions@Base @SVER@ + PySys_SetArgv@Base @SVER@ + PySys_SetArgvEx@Base @SVER@ + PySys_SetObject@Base @SVER@ + PySys_SetPath@Base @SVER@ + PySys_WriteStderr@Base @SVER@ + PySys_WriteStdout@Base @SVER@ + PyTextIOBase_Type@Base @SVER@ + PyTextIOWrapper_Type@Base @SVER@ + PyThreadState_Clear@Base @SVER@ + PyThreadState_Delete@Base @SVER@ + PyThreadState_DeleteCurrent@Base @SVER@ + PyThreadState_Get@Base @SVER@ + PyThreadState_GetDict@Base @SVER@ + PyThreadState_New@Base @SVER@ + PyThreadState_Next@Base @SVER@ + PyThreadState_SetAsyncExc@Base @SVER@ + PyThreadState_Swap@Base @SVER@ + PyThread_GetInfo@Base @SVER@ + PyThread_ReInitTLS@Base @SVER@ + PyThread_acquire_lock@Base @SVER@ + PyThread_acquire_lock_timed@Base @SVER@ + PyThread_allocate_lock@Base @SVER@ + PyThread_create_key@Base @SVER@ + PyThread_delete_key@Base @SVER@ + PyThread_delete_key_value@Base @SVER@ + PyThread_exit_thread@Base @SVER@ + PyThread_free_lock@Base @SVER@ + PyThread_get_key_value@Base @SVER@ + PyThread_get_stacksize@Base @SVER@ + PyThread_get_thread_ident@Base @SVER@ + PyThread_init_thread@Base @SVER@ + PyThread_release_lock@Base @SVER@ + PyThread_set_key_value@Base @SVER@ + PyThread_set_stacksize@Base @SVER@ + PyThread_start_new_thread@Base @SVER@ + PyToken_OneChar@Base @SVER@ + PyToken_ThreeChars@Base @SVER@ + PyToken_TwoChars@Base @SVER@ + PyTokenizer_FindEncoding@Base @SVER@ + PyTokenizer_FindEncodingFilename@Base @SVER@ + PyTokenizer_Free@Base @SVER@ + PyTokenizer_FromFile@Base @SVER@ + PyTokenizer_FromString@Base @SVER@ + PyTokenizer_FromUTF8@Base @SVER@ + PyTokenizer_Get@Base @SVER@ + PyTraceBack_Here@Base @SVER@ + PyTraceBack_Print@Base @SVER@ + PyTraceBack_Type@Base @SVER@ + PyTupleIter_Type@Base @SVER@ + PyTuple_ClearFreeList@Base @SVER@ + PyTuple_Fini@Base @SVER@ + PyTuple_GetItem@Base @SVER@ + PyTuple_GetSlice@Base @SVER@ + PyTuple_New@Base @SVER@ + PyTuple_Pack@Base @SVER@ + PyTuple_SetItem@Base @SVER@ + PyTuple_Size@Base @SVER@ + PyTuple_Type@Base @SVER@ + PyType_ClearCache@Base @SVER@ + PyType_FromSpec@Base @SVER@ + PyType_FromSpecWithBases@Base @SVER@ + PyType_GenericAlloc@Base @SVER@ + PyType_GenericNew@Base @SVER@ + PyType_GetFlags@Base @SVER@ + PyType_IsSubtype@Base @SVER@ + PyType_Modified@Base @SVER@ + PyType_Ready@Base @SVER@ + PyType_Type@Base @SVER@ + (optional)PyType_stgdict@Base @SVER@ + PyUnicodeDecodeError_Create@Base @SVER@ + PyUnicodeDecodeError_GetEncoding@Base @SVER@ + PyUnicodeDecodeError_GetEnd@Base @SVER@ + PyUnicodeDecodeError_GetObject@Base @SVER@ + PyUnicodeDecodeError_GetReason@Base @SVER@ + PyUnicodeDecodeError_GetStart@Base @SVER@ + PyUnicodeDecodeError_SetEnd@Base @SVER@ + PyUnicodeDecodeError_SetReason@Base @SVER@ + PyUnicodeDecodeError_SetStart@Base @SVER@ + PyUnicodeEncodeError_Create@Base @SVER@ + PyUnicodeEncodeError_GetEncoding@Base @SVER@ + PyUnicodeEncodeError_GetEnd@Base @SVER@ + PyUnicodeEncodeError_GetObject@Base @SVER@ + PyUnicodeEncodeError_GetReason@Base @SVER@ + PyUnicodeEncodeError_GetStart@Base @SVER@ + PyUnicodeEncodeError_SetEnd@Base @SVER@ + PyUnicodeEncodeError_SetReason@Base @SVER@ + PyUnicodeEncodeError_SetStart@Base @SVER@ + PyUnicodeIter_Type@Base @SVER@ + PyUnicodeTranslateError_Create@Base @SVER@ + PyUnicodeTranslateError_GetEnd@Base @SVER@ + PyUnicodeTranslateError_GetObject@Base @SVER@ + PyUnicodeTranslateError_GetReason@Base @SVER@ + PyUnicodeTranslateError_GetStart@Base @SVER@ + PyUnicodeTranslateError_SetEnd@Base @SVER@ + PyUnicodeTranslateError_SetReason@Base @SVER@ + PyUnicodeTranslateError_SetStart@Base @SVER@ + PyUnicode_Append@Base @SVER@ + PyUnicode_AppendAndDel@Base @SVER@ + PyUnicode_AsASCIIString@Base @SVER@ + PyUnicode_AsCharmapString@Base @SVER@ + PyUnicode_AsDecodedObject@Base @SVER@ + PyUnicode_AsDecodedUnicode@Base @SVER@ + PyUnicode_AsEncodedObject@Base @SVER@ + PyUnicode_AsEncodedString@Base @SVER@ + PyUnicode_AsEncodedUnicode@Base @SVER@ + PyUnicode_AsLatin1String@Base @SVER@ + PyUnicode_AsRawUnicodeEscapeString@Base @SVER@ + PyUnicode_AsUCS4@Base @SVER@ + PyUnicode_AsUCS4Copy@Base @SVER@ + PyUnicode_AsUTF16String@Base @SVER@ + PyUnicode_AsUTF32String@Base @SVER@ + PyUnicode_AsUTF8@Base @SVER@ + PyUnicode_AsUTF8AndSize@Base @SVER@ + PyUnicode_AsUTF8String@Base @SVER@ + PyUnicode_AsUnicode@Base @SVER@ + PyUnicode_AsUnicodeAndSize@Base @SVER@ + PyUnicode_AsUnicodeCopy@Base @SVER@ + PyUnicode_AsUnicodeEscapeString@Base @SVER@ + PyUnicode_AsWideChar@Base @SVER@ + PyUnicode_AsWideCharString@Base @SVER@ + PyUnicode_BuildEncodingMap@Base @SVER@ + PyUnicode_ClearFreeList@Base @SVER@ + PyUnicode_Compare@Base @SVER@ + PyUnicode_CompareWithASCIIString@Base @SVER@ + PyUnicode_Concat@Base @SVER@ + PyUnicode_Contains@Base @SVER@ + PyUnicode_CopyCharacters@Base @SVER@ + PyUnicode_Count@Base @SVER@ + PyUnicode_Decode@Base @SVER@ + PyUnicode_DecodeASCII@Base @SVER@ + PyUnicode_DecodeCharmap@Base @SVER@ + PyUnicode_DecodeFSDefault@Base @SVER@ + PyUnicode_DecodeFSDefaultAndSize@Base @SVER@ + PyUnicode_DecodeLatin1@Base @SVER@ + PyUnicode_DecodeLocale@Base @SVER@ + PyUnicode_DecodeLocaleAndSize@Base @SVER@ + PyUnicode_DecodeRawUnicodeEscape@Base @SVER@ + PyUnicode_DecodeUTF16@Base @SVER@ + PyUnicode_DecodeUTF16Stateful@Base @SVER@ + PyUnicode_DecodeUTF32@Base @SVER@ + PyUnicode_DecodeUTF32Stateful@Base @SVER@ + PyUnicode_DecodeUTF7@Base @SVER@ + PyUnicode_DecodeUTF7Stateful@Base @SVER@ + PyUnicode_DecodeUTF8@Base @SVER@ + PyUnicode_DecodeUTF8Stateful@Base @SVER@ + PyUnicode_DecodeUnicodeEscape@Base @SVER@ + PyUnicode_Encode@Base @SVER@ + PyUnicode_EncodeASCII@Base @SVER@ + PyUnicode_EncodeCharmap@Base @SVER@ + PyUnicode_EncodeDecimal@Base @SVER@ + PyUnicode_EncodeFSDefault@Base @SVER@ + PyUnicode_EncodeUTF8@Base @SVER@ + PyUnicode_EncodeUnicodeEscape@Base @SVER@ + PyUnicode_FSConverter@Base @SVER@ + PyUnicode_FSDecoder@Base @SVER@ + PyUnicode_Fill@Base @SVER@ + PyUnicode_Find@Base @SVER@ + PyUnicode_FindChar@Base @SVER@ + PyUnicode_Format@Base @SVER@ + PyUnicode_FromEncodedObject@Base @SVER@ + PyUnicode_FromFormat@Base @SVER@ + PyUnicode_FromFormatV@Base @SVER@ + PyUnicode_FromKindAndData@Base @SVER@ + PyUnicode_FromObject@Base @SVER@ + PyUnicode_FromOrdinal@Base @SVER@ + PyUnicode_FromString@Base @SVER@ + PyUnicode_FromStringAndSize@Base @SVER@ + PyUnicode_FromUnicode@Base @SVER@ + PyUnicode_FromWideChar@Base @SVER@ + PyUnicode_GetDefaultEncoding@Base @SVER@ + PyUnicode_GetLength@Base @SVER@ + PyUnicode_GetMax@Base @SVER@ + PyUnicode_GetSize@Base @SVER@ + PyUnicode_EncodeLatin1@Base @SVER@ + PyUnicode_EncodeLocale@Base @SVER@ + PyUnicode_EncodeRawUnicodeEscape@Base @SVER@ + PyUnicode_EncodeUTF16@Base @SVER@ + PyUnicode_EncodeUTF32@Base @SVER@ + PyUnicode_EncodeUTF7@Base @SVER@ + PyUnicode_InternFromString@Base @SVER@ + PyUnicode_InternImmortal@Base @SVER@ + PyUnicode_InternInPlace@Base @SVER@ + PyUnicode_IsIdentifier@Base @SVER@ + PyUnicode_Join@Base @SVER@ + PyUnicode_New@Base @SVER@ + PyUnicode_Partition@Base @SVER@ + PyUnicode_RPartition@Base @SVER@ + PyUnicode_RSplit@Base @SVER@ + PyUnicode_ReadChar@Base @SVER@ + PyUnicode_Replace@Base @SVER@ + PyUnicode_Resize@Base @SVER@ + PyUnicode_RichCompare@Base @SVER@ + PyUnicode_Split@Base @SVER@ + PyUnicode_Splitlines@Base @SVER@ + PyUnicode_Substring@Base @SVER@ + PyUnicode_Tailmatch@Base @SVER@ + PyUnicode_TransformDecimalToASCII@Base @SVER@ + PyUnicode_Translate@Base @SVER@ + PyUnicode_TranslateCharmap@Base @SVER@ + PyUnicode_Type@Base @SVER@ + PyUnicode_WriteChar@Base @SVER@ + PyWeakref_GetObject@Base @SVER@ + PyWeakref_NewProxy@Base @SVER@ + PyWeakref_NewRef@Base @SVER@ + PyWrapperDescr_Type@Base @SVER@ + PyWrapper_New@Base @SVER@ + PyZip_Type@Base @SVER@ + Py_AddPendingCall@Base @SVER@ + Py_AtExit@Base @SVER@ + Py_BuildValue@Base @SVER@ + Py_BytesWarningFlag@Base @SVER@ + Py_CompileString@Base @SVER@ + Py_CompileStringExFlags@Base @SVER@ + Py_CompileStringFlags@Base @SVER@ + Py_DebugFlag@Base @SVER@ + Py_DecRef@Base @SVER@ + Py_DontWriteBytecodeFlag@Base @SVER@ + Py_EndInterpreter@Base @SVER@ + Py_Exit@Base @SVER@ + Py_FatalError@Base @SVER@ + Py_FdIsInteractive@Base @SVER@ + Py_FileSystemDefaultEncoding@Base @SVER@ + Py_Finalize@Base @SVER@ + Py_FrozenFlag@Base @SVER@ + Py_FrozenMain@Base @SVER@ + Py_GetArgcArgv@Base @SVER@ + Py_GetBuildInfo@Base @SVER@ + Py_GetCompiler@Base @SVER@ + Py_GetCopyright@Base @SVER@ + Py_GetExecPrefix@Base @SVER@ + Py_GetPath@Base @SVER@ + Py_GetPlatform@Base @SVER@ + Py_GetPrefix@Base @SVER@ + Py_GetProgramFullPath@Base @SVER@ + Py_GetProgramName@Base @SVER@ + Py_GetPythonHome@Base @SVER@ + Py_GetRecursionLimit@Base @SVER@ + Py_GetVersion@Base @SVER@ + Py_HasFileSystemDefaultEncoding@Base @SVER@ + Py_HashRandomizationFlag@Base @SVER@ + Py_IgnoreEnvironmentFlag@Base @SVER@ + Py_IncRef@Base @SVER@ + Py_Initialize@Base @SVER@ + Py_InitializeEx@Base @SVER@ + Py_InspectFlag@Base @SVER@ + Py_InteractiveFlag@Base @SVER@ + Py_IsInitialized@Base @SVER@ + Py_Main@Base @SVER@ + Py_MakePendingCalls@Base @SVER@ + Py_NewInterpreter@Base @SVER@ + Py_NoSiteFlag@Base @SVER@ + Py_NoUserSiteDirectory@Base @SVER@ + Py_OptimizeFlag@Base @SVER@ + Py_QuietFlag@Base @SVER@ + Py_ReprEnter@Base @SVER@ + Py_ReprLeave@Base @SVER@ + Py_SetPath@Base @SVER@ + Py_SetProgramName@Base @SVER@ + Py_SetPythonHome@Base @SVER@ + Py_SetRecursionLimit@Base @SVER@ + Py_SymtableString@Base @SVER@ + Py_UNICODE_strcat@Base @SVER@ + Py_UNICODE_strchr@Base @SVER@ + Py_UNICODE_strcmp@Base @SVER@ + Py_UNICODE_strcpy@Base @SVER@ + Py_UNICODE_strlen@Base @SVER@ + Py_UNICODE_strncmp@Base @SVER@ + Py_UNICODE_strncpy@Base @SVER@ + Py_UNICODE_strrchr@Base @SVER@ + Py_UnbufferedStdioFlag@Base @SVER@ + Py_UniversalNewlineFgets@Base @SVER@ + Py_UseClassExceptionsFlag@Base @SVER@ + Py_VaBuildValue@Base @SVER@ + Py_VerboseFlag@Base @SVER@ + Py_hexdigits@Base @SVER@ + Py_meta_grammar@Base @SVER@ + Py_pgen@Base @SVER@ + _PyAccu_Accumulate@Base @SVER@ + _PyAccu_Destroy@Base @SVER@ + _PyAccu_Finish@Base @SVER@ + _PyAccu_FinishAsList@Base @SVER@ + _PyAccu_Init@Base @SVER@ + _PyArg_NoKeywords@Base @SVER@ + _PyArg_ParseTupleAndKeywords_SizeT@Base @SVER@ + _PyArg_ParseTuple_SizeT@Base @SVER@ + _PyArg_Parse_SizeT@Base @SVER@ + _PyArg_VaParseTupleAndKeywords_SizeT@Base @SVER@ + _PyArg_VaParse_SizeT@Base @SVER@ + _PyBuiltin_Init@Base @SVER@ + _PyByteArray_empty_string@Base @SVER@ + _PyBytesIOBuffer_Type@Base @SVER@ + _PyBytes_Join@Base @SVER@ + _PyBytes_Resize@Base @SVER@ + _PyCFunction_DebugMallocStats@Base @SVER@ + _PyCapsule_hack@Base @SVER@ + _PyCode_CheckLineNumber@Base @SVER@ + _PyCodec_Lookup@Base @SVER@ + _PyComplex_FormatAdvancedWriter@Base @SVER@ + _PyDebugAllocatorStats@Base @SVER@ + _PyDictKeys_DecRef@Base @SVER@ + _PyDict_Contains@Base @SVER@ + _PyDict_DebugMallocStats@Base @SVER@ + _PyDict_GetItemId@Base @SVER@ + _PyDict_GetItemIdWithError@Base @SVER@ + _PyDict_HasOnlyStringKeys@Base @SVER@ + _PyDict_KeysSize@Base @SVER@ + _PyDict_LoadGlobal@Base @SVER@ + _PyDict_MaybeUntrack@Base @SVER@ + _PyDict_NewKeysForClass@Base @SVER@ + _PyDict_NewPresized@Base @SVER@ + _PyDict_Next@Base @SVER@ + _PyErr_BadInternalCall@Base @SVER@ + _PyDict_SetItemId@Base @SVER@ + _PyEval_CallTracing@Base @SVER@ + _PyEval_FiniThreads@Base @SVER@ + _PyEval_GetSwitchInterval@Base @SVER@ + _PyEval_SetSwitchInterval@Base @SVER@ + _PyEval_SignalAsyncExc@Base @SVER@ + _PyEval_SliceIndex@Base @SVER@ + _PyExc_Fini@Base @SVER@ + _PyExc_Init@Base @SVER@ + _PyFaulthandler_Fini@Base @SVER@ + _PyFaulthandler_Init@Base @SVER@ + _PyFileIO_closed@Base @SVER@ + _PyFloat_DebugMallocStats@Base @SVER@ + _PyFloat_FormatAdvancedWriter@Base @SVER@ + _PyFloat_Init@Base @SVER@ + _PyFloat_Pack4@Base @SVER@ + _PyFloat_Pack8@Base @SVER@ + _PyFloat_Unpack4@Base @SVER@ + _PyFloat_Unpack8@Base @SVER@ + _PyFrame_DebugMallocStats@Base @SVER@ + _PyFrame_Init@Base @SVER@ + _PyGC_Dump@Base @SVER@ + _PyGC_Fini@Base @SVER@ + _PyGC_generation0@Base @SVER@ + _PyGILState_Fini@Base @SVER@ + _PyGILState_Init@Base @SVER@ + _PyGILState_Reinit@Base @SVER@ + _PyGen_FetchStopIterationValue@Base @SVER@ + _PyGen_Send@Base @SVER@ + _PyIOBase_check_closed@Base @SVER@ + _PyIOBase_check_readable@Base @SVER@ + _PyIOBase_check_seekable@Base @SVER@ + _PyIOBase_check_writable@Base @SVER@ + _PyIOBase_finalize@Base @SVER@ + _PyIO_ConvertSsize_t@Base @SVER@ + _PyIO_Module@Base @SVER@ + _PyIO_empty_bytes@Base @SVER@ + _PyIO_empty_str@Base @SVER@ + _PyIO_find_line_ending@Base @SVER@ + _PyIO_str_close@Base @SVER@ + _PyIO_str_closed@Base @SVER@ + _PyIO_str_decode@Base @SVER@ + _PyIO_str_encode@Base @SVER@ + _PyIO_str_fileno@Base @SVER@ + _PyIO_str_flush@Base @SVER@ + _PyIO_str_getstate@Base @SVER@ + _PyIO_str_isatty@Base @SVER@ + _PyIO_str_newlines@Base @SVER@ + _PyIO_str_nl@Base @SVER@ + _PyIO_str_read1@Base @SVER@ + _PyIO_str_read@Base @SVER@ + _PyIO_str_readable@Base @SVER@ + _PyIO_str_readall@Base @SVER@ + _PyIO_str_readinto@Base @SVER@ + _PyIO_str_readline@Base @SVER@ + _PyIO_str_reset@Base @SVER@ + _PyIO_str_seek@Base @SVER@ + _PyIO_str_seekable@Base @SVER@ + _PyIO_str_setstate@Base @SVER@ + _PyIO_str_tell@Base @SVER@ + _PyIO_str_truncate@Base @SVER@ + _PyIO_str_writable@Base @SVER@ + _PyIO_str_write@Base @SVER@ + _PyIO_trap_eintr@Base @SVER@ + _PyIO_zero@Base @SVER@ + _PyImportHooks_Init@Base @SVER@ + _PyImportZip_Init@Base @SVER@ + _PyImport_AcquireLock@Base @SVER@ + _PyImport_DynLoadFiletab@Base @SVER@ + _PyImport_FindBuiltin@Base @SVER@ + _PyImport_FindExtensionObject@Base @SVER@ + _PyImport_Fini@Base @SVER@ + _PyImport_FixupBuiltin@Base @SVER@ + _PyImport_FixupExtensionObject@Base @SVER@ + _PyImport_GetDynLoadFunc@Base @SVER@ + _PyImport_Init@Base @SVER@ + _PyImport_Inittab@Base @SVER@ + _PyImport_LoadDynamicModule@Base @SVER@ + _PyImport_ReInitLock@Base @SVER@ + _PyImport_ReleaseLock@Base @SVER@ + _PyIncrementalNewlineDecoder_decode@Base @SVER@ + _PyList_DebugMallocStats@Base @SVER@ + _PyList_Extend@Base @SVER@ + _PyLong_AsByteArray@Base @SVER@ + _PyLong_AsInt@Base @SVER@ + _PyLong_AsTime_t@Base @SVER@ + _PyLong_Copy@Base @SVER@ + _PyLong_DigitValue@Base @SVER@ + _PyLong_DivmodNear@Base @SVER@ + _PyLong_Format@Base @SVER@ + _PyLong_FormatAdvancedWriter@Base @SVER@ + _PyLong_FormatWriter@Base @SVER@ + _PyLong_Frexp@Base @SVER@ + _PyLong_FromByteArray@Base @SVER@ + _PyLong_FromTime_t@Base @SVER@ + _PyLong_Init@Base @SVER@ + _PyLong_New@Base @SVER@ + _PyLong_NumBits@Base @SVER@ + _PyLong_Sign@Base @SVER@ + _PyManagedBuffer_Type@Base @SVER@ + _PyMethodWrapper_Type@Base @SVER@ + _PyMethod_DebugMallocStats@Base @SVER@ + _PyModule_Clear@Base @SVER@ + _PyNamespace_New@Base @SVER@ + _PyNamespace_Type@Base @SVER@ + _PyNode_SizeOf@Base @SVER@ + _PyOS_GetOpt@Base @SVER@ + _PyOS_IsMainThread@Base @SVER@ + _PyOS_ReadlineTState@Base @SVER@ + _PyOS_ResetGetOpt@Base @SVER@ + _PyOS_URandom@Base @SVER@ + _PyOS_optarg@Base @SVER@ + _PyOS_opterr@Base @SVER@ + _PyOS_optind@Base @SVER@ + _PyObjectDict_SetItem@Base @SVER@ + _PyObject_CallFunction_SizeT@Base @SVER@ + _PyObject_CallMethodId@Base @SVER@ + _PyObject_CallMethodObjIdArgs@Base @SVER@ + _PyObject_CallMethodId_SizeT@Base @SVER@ + _PyObject_CallMethod_SizeT@Base @SVER@ + _PyObject_DebugMallocStats@Base @SVER@ + _PyObject_DebugTypeStats@Base @SVER@ + _PyObject_Dump@Base @SVER@ + _PyObject_GC_Malloc@Base @SVER@ + _PyObject_GC_New@Base @SVER@ + _PyObject_GC_NewVar@Base @SVER@ + _PyObject_GC_Resize@Base @SVER@ + _PyObject_GC_Track@Base @SVER@ + _PyObject_GC_UnTrack@Base @SVER@ + _PyObject_GenericGetAttrWithDict@Base @SVER@ + _PyObject_GenericSetAttrWithDict@Base @SVER@ + _PyObject_GetAttrId@Base @SVER@ + _PyObject_GetBuiltin@Base @SVER@ + _PyObject_GetDictPtr@Base @SVER@ + _PyObject_HasAttrId@Base @SVER@ + _PyObject_IsAbstract@Base @SVER@ + _PyObject_LengthHint@Base @SVER@ + _PyObject_LookupSpecial@Base @SVER@ + _PyObject_New@Base @SVER@ + _PyObject_NewVar@Base @SVER@ + _PyObject_NextNotImplemented@Base @SVER@ + _PyObject_RealIsInstance@Base @SVER@ + _PyObject_RealIsSubclass@Base @SVER@ + _PyObject_SetAttrId@Base @SVER@ + _PyParser_Grammar@Base @SVER@ + _PyParser_TokenNames@Base @SVER@ + _PyRandom_Init@Base @SVER@ + _PySequence_BytesToCharpArray@Base @SVER@ + _PySequence_IterSearch@Base @SVER@ + _PySet_DebugMallocStats@Base @SVER@ + _PySet_NextEntry@Base @SVER@ + _PySet_Update@Base @SVER@ + _PySlice_FromIndices@Base @SVER@ + _PyState_AddModule@Base @SVER@ + _PySys_ImplCacheTag@Base @SVER@ + _PySys_ImplName@Base @SVER@ + _PySys_Init@Base @SVER@ + _PyThreadState_Current@Base @SVER@ + _PyThreadState_GetFrame@Base @SVER@ + _PyThreadState_Init@Base @SVER@ + _PyThreadState_Prealloc@Base @SVER@ + _PyThread_CurrentFrames@Base @SVER@ + _PyTime_Init@Base @SVER@ + _PyTime_ObjectToTime_t@Base @SVER@ + _PyTime_ObjectToTimespec@Base @SVER@ + _PyTime_ObjectToTimeval@Base @SVER@ + _PyTime_gettimeofday@Base @SVER@ + _PyTime_gettimeofday_info@Base @SVER@ + _PyTrash_delete_later@Base @SVER@ + _PyTrash_delete_nesting@Base @SVER@ + _PyTrash_deposit_object@Base @SVER@ + _PyTrash_destroy_chain@Base @SVER@ + _PyTrash_thread_deposit_object@Base @SVER@ + _PyTrash_thread_destroy_chain@Base @SVER@ + _PyTuple_DebugMallocStats@Base @SVER@ + _PyTuple_MaybeUntrack@Base @SVER@ + _PyTuple_Resize@Base @SVER@ + _PyType_CalculateMetaclass@Base @SVER@ + _PyType_Lookup@Base @SVER@ + _PyUnicodeTranslateError_Create@Base @SVER@ + _PyUnicodeWriter_Dealloc@Base @SVER@ + _PyUnicodeWriter_Finish@Base @SVER@ + _PyUnicodeWriter_Init@Base @SVER@ + _PyUnicodeWriter_PrepareInternal@Base @SVER@ + _PyUnicodeWriter_WriteStr@Base @SVER@ + _PyUnicode_AsASCIIString@Base @SVER@ + _PyUnicode_AsKind@Base @SVER@ + _PyUnicode_AsLatin1String@Base @SVER@ + _PyUnicode_AsUTF8String@Base @SVER@ + _PyUnicode_BidirectionalNames@Base @SVER@ + _PyUnicode_CategoryNames@Base @SVER@ + _PyUnicode_ClearStaticStrings@Base @SVER@ + _PyUnicode_Copy@Base @SVER@ + _PyUnicode_Database_Records@Base @SVER@ + _PyUnicode_DecodeUnicodeInternal@Base @SVER@ + _PyUnicode_EastAsianWidthNames@Base @SVER@ + _PyUnicode_EncodeCharmap@Base @SVER@ + _PyUnicode_EncodeUTF16@Base @SVER@ + _PyUnicode_EncodeUTF32@Base @SVER@ + _PyUnicode_EncodeUTF7@Base @SVER@ + _PyUnicode_ExtendedCase@Base @SVER@ + _PyUnicode_FastCopyCharacters@Base @SVER@ + _PyUnicode_FastFill@Base @SVER@ + _PyUnicode_FindMaxChar@Base @SVER@ + _PyUnicode_Fini@Base @SVER@ + _PyUnicode_FormatAdvancedWriter@Base @SVER@ + _PyUnicode_FromASCII@Base @SVER@ + _PyUnicode_FromId@Base @SVER@ + _PyUnicode_Init@Base @SVER@ + _PyUnicode_HasNULChars@Base @SVER@ + _PyUnicode_InsertThousandsGrouping@Base @SVER@ + _PyUnicode_IsAlpha@Base @SVER@ + _PyUnicode_IsCaseIgnorable@Base @SVER@ + _PyUnicode_IsCased@Base @SVER@ + _PyUnicode_IsDecimalDigit@Base @SVER@ + _PyUnicode_IsDigit@Base @SVER@ + _PyUnicode_IsLinebreak@Base @SVER@ + _PyUnicode_IsLowercase@Base @SVER@ + _PyUnicode_IsNumeric@Base @SVER@ + _PyUnicode_IsPrintable@Base @SVER@ + _PyUnicode_IsTitlecase@Base @SVER@ + _PyUnicode_IsUppercase@Base @SVER@ + _PyUnicode_IsWhitespace@Base @SVER@ + _PyUnicode_IsXidContinue@Base @SVER@ + _PyUnicode_IsXidStart@Base @SVER@ + _PyUnicode_Ready@Base @SVER@ + _PyUnicode_ToDecimalDigit@Base @SVER@ + _PyUnicode_ToDigit@Base @SVER@ + _PyUnicode_ToFoldedFull@Base @SVER@ + _PyUnicode_ToLowerFull@Base @SVER@ + _PyUnicode_ToLowercase@Base @SVER@ + _PyUnicode_ToNumeric@Base @SVER@ + _PyUnicode_ToTitleFull@Base @SVER@ + _PyUnicode_ToTitlecase@Base @SVER@ + _PyUnicode_ToUpperFull@Base @SVER@ + _PyUnicode_ToUppercase@Base @SVER@ + _PyUnicode_TransformDecimalAndSpaceToASCII@Base @SVER@ + _PyUnicode_TranslateCharmap@Base @SVER@ + _PyUnicode_TypeRecords@Base @SVER@ + _PyUnicode_XStrip@Base @SVER@ + _PyWarnings_Init@Base @SVER@ + _PyWeakref_CallableProxyType@Base @SVER@ + _PyWeakref_ClearRef@Base @SVER@ + _PyWeakref_GetWeakrefCount@Base @SVER@ + _PyWeakref_ProxyType@Base @SVER@ + _PyWeakref_RefType@Base @SVER@ + _Py_Assert@Base @SVER@ + _Py_Assign@Base @SVER@ + _Py_Attribute@Base @SVER@ + _Py_AugAssign@Base @SVER@ + _Py_BinOp@Base @SVER@ + _Py_BoolOp@Base @SVER@ + _Py_Break@Base @SVER@ + _Py_BreakPoint@Base @SVER@ + _Py_BuildValue_SizeT@Base @SVER@ + _Py_Bytes@Base @SVER@ + _Py_Call@Base @SVER@ + _Py_CheckRecursionLimit@Base @SVER@ + _Py_CheckRecursiveCall@Base @SVER@ + _Py_ClassDef@Base @SVER@ + _Py_Compare@Base @SVER@ + _Py_Continue@Base @SVER@ + _Py_Dealloc@Base @SVER@ + _Py_Delete@Base @SVER@ + _Py_Dict@Base @SVER@ + _Py_DictComp@Base @SVER@ + _Py_DisplaySourceLine@Base @SVER@ + _Py_DumpTraceback@Base @SVER@ + _Py_DumpTracebackThreads@Base @SVER@ + _Py_Ellipsis@Base @SVER@ + _Py_EllipsisObject@Base @SVER@ + _Py_ExceptHandler@Base @SVER@ + _Py_Expr@Base @SVER@ + _Py_Expression@Base @SVER@ + _Py_ExtSlice@Base @SVER@ + _Py_FalseStruct@Base @SVER@ + _Py_Finalizing@Base @SVER@ + _Py_For@Base @SVER@ + _Py_FreeCharPArray@Base @SVER@ + _Py_FunctionDef@Base @SVER@ + _Py_GeneratorExp@Base @SVER@ + _Py_Global@Base @SVER@ + _Py_HashBytes@Base @SVER@ + _Py_HashDouble@Base @SVER@ + _Py_HashPointer@Base @SVER@ + _Py_HashSecret@Base @SVER@ + _Py_If@Base @SVER@ + _Py_IfExp@Base @SVER@ + _Py_Import@Base @SVER@ + _Py_ImportFrom@Base @SVER@ + _Py_Index@Base @SVER@ + _Py_InitializeEx_Private@Base @SVER@ + _Py_Interactive@Base @SVER@ + _Py_Lambda@Base @SVER@ + _Py_List@Base @SVER@ + _Py_ListComp@Base @SVER@ + _Py_M__importlib@Base @SVER@ + _Py_Mangle@Base @SVER@ + _Py_Module@Base @SVER@ + _Py_Name@Base @SVER@ + _Py_NoneStruct@Base @SVER@ + _Py_Nonlocal@Base @SVER@ + _Py_NotImplementedStruct@Base @SVER@ + _Py_Num@Base @SVER@ + _Py_PackageContext@Base @SVER@ + _Py_Pass@Base @SVER@ + _Py_PyAtExit@Base @SVER@ + _Py_Raise@Base @SVER@ + _Py_ReadyTypes@Base @SVER@ + _Py_ReleaseInternedUnicodeStrings@Base @SVER@ + _Py_RestoreSignals@Base @SVER@ + _Py_Return@Base @SVER@ + _Py_Set@Base @SVER@ + _Py_SetComp@Base @SVER@ + _Py_Slice@Base @SVER@ + _Py_Starred@Base @SVER@ + _Py_Str@Base @SVER@ + _Py_Subscript@Base @SVER@ + _Py_Suite@Base @SVER@ + _Py_SwappedOp@Base @SVER@ + _Py_TrueStruct@Base @SVER@ + _Py_Try@Base @SVER@ + _Py_Tuple@Base @SVER@ + _Py_UnaryOp@Base @SVER@ + _Py_VaBuildValue_SizeT@Base @SVER@ + _Py_While@Base @SVER@ + _Py_With@Base @SVER@ + _Py_Yield@Base @SVER@ + _Py_YieldFrom@Base @SVER@ + _Py_abstract_hack@Base @SVER@ + _Py_acosh@Base @SVER@ + _Py_add_one_to_index_C@Base @SVER@ + _Py_add_one_to_index_F@Base @SVER@ + _Py_addarc@Base @SVER@ + _Py_addbit@Base @SVER@ + _Py_adddfa@Base @SVER@ + _Py_addfirstsets@Base @SVER@ + _Py_addlabel@Base @SVER@ + _Py_addstate@Base @SVER@ + _Py_alias@Base @SVER@ + _Py_arg@Base @SVER@ + _Py_arguments@Base @SVER@ + _Py_ascii_whitespace@Base @SVER@ + _Py_asinh@Base @SVER@ + _Py_atanh@Base @SVER@ + _Py_bytes_capitalize@Base @SVER@ + _Py_bytes_isalnum@Base @SVER@ + _Py_bytes_isalpha@Base @SVER@ + _Py_bytes_isdigit@Base @SVER@ + _Py_bytes_islower@Base @SVER@ + _Py_bytes_isspace@Base @SVER@ + _Py_bytes_istitle@Base @SVER@ + _Py_bytes_isupper@Base @SVER@ + _Py_bytes_lower@Base @SVER@ + _Py_bytes_maketrans@Base @SVER@ + _Py_bytes_swapcase@Base @SVER@ + _Py_bytes_title@Base @SVER@ + _Py_bytes_upper@Base @SVER@ + _Py_c_abs@Base @SVER@ + _Py_c_diff@Base @SVER@ + _Py_c_neg@Base @SVER@ + _Py_c_pow@Base @SVER@ + _Py_c_prod@Base @SVER@ + _Py_c_quot@Base @SVER@ + _Py_c_sum@Base @SVER@ + _Py_capitalize__doc__@Base @SVER@ + _Py_char2wchar@Base @SVER@ + _Py_comprehension@Base @SVER@ + _Py_ctype_table@Base @SVER@ + _Py_ctype_tolower@Base @SVER@ + _Py_ctype_toupper@Base @SVER@ + _Py_delbitset@Base @SVER@ + _Py_device_encoding@Base @SVER@ + (arch=!m68k)_Py_dg_dtoa@Base @SVER@ + (arch=!m68k)_Py_dg_freedtoa@Base @SVER@ + _Py_dg_infinity@Base @SVER@ + _Py_dg_stdnan@Base @SVER@ + (arch=!m68k)_Py_dg_strtod@Base @SVER@ + _Py_dg_infinity@Base @SVER@ + _Py_dg_stdnan@Base @SVER@ + _Py_expm1@Base @SVER@ + _Py_findlabel@Base @SVER@ + _Py_fopen@Base @SVER@ + (arch=i386 lpia m68k)_Py_force_double@Base @SVER@ + (arch=amd64 i386 lpia)_Py_get_387controlword@Base @SVER@ + _Py_hgidentifier@Base @SVER@ + _Py_hgversion@Base @SVER@ + _Py_isalnum__doc__@Base @SVER@ + _Py_isalpha__doc__@Base @SVER@ + _Py_isdigit__doc__@Base @SVER@ + _Py_islower__doc__@Base @SVER@ + _Py_isspace__doc__@Base @SVER@ + _Py_istitle__doc__@Base @SVER@ + _Py_isupper__doc__@Base @SVER@ + _Py_keyword@Base @SVER@ + _Py_log1p@Base @SVER@ + _Py_lower__doc__@Base @SVER@ + _Py_maketrans__doc__@Base @SVER@ + _Py_mergebitset@Base @SVER@ + _Py_meta_grammar@Base @SVER@ + _Py_newbitset@Base @SVER@ + _Py_newgrammar@Base @SVER@ + _Py_normalize_encoding@Base @SVER@ + _Py_parse_inf_or_nan@Base @SVER@ + _Py_pgen@Base @SVER@ + _Py_samebitset@Base @SVER@ + (arch=amd64 i386 lpia)_Py_set_387controlword@Base @SVER@ + _Py_stat@Base @SVER@ + _Py_swapcase__doc__@Base @SVER@ + _Py_title__doc__@Base @SVER@ + _Py_translatelabels@Base @SVER@ + _Py_upper__doc__@Base @SVER@ + _Py_wchar2char@Base @SVER@ + _Py_wfopen@Base @SVER@ + _Py_wgetcwd@Base @SVER@ + _Py_withitem@Base @SVER@ + _Py_wreadlink@Base @SVER@ + _Py_wrealpath@Base @SVER@ + _Py_wstat@Base @SVER@ + + asdl_int_seq_new@Base @SVER@ + asdl_seq_new@Base @SVER@ + + (optional|regex)"^_ctypes_.*@Base$" @SVER@ + (optional|regex)"^ffi_type_.*@Base$" @SVER@ + (optional|regex)"^ffi_closure_.*@Base$" @SVER@ + + (optional|regex)"^PyInit_.*@Base$" @SVER@ --- python3.3-3.3.0.orig/debian/README.source +++ python3.3-3.3.0/debian/README.source @@ -0,0 +1,7 @@ +The source tarball is lacking the files Lib/profile.py and Lib/pstats.py, +which Debian considers to have a license non-suitable for main (the use +of these modules limited to python). + +The package uses quilt to apply / unapply patches. +See /usr/share/doc/quilt/README.source. The series file is generated +during the build. --- python3.3-3.3.0.orig/debian/idle-PVER.1.in +++ python3.3-3.3.0/debian/idle-PVER.1.in @@ -0,0 +1,104 @@ +.TH IDLE 1 "21 September 2004" +.SH NAME +\fBIDLE\fP \- An Integrated DeveLopment Environment for Python +.SH SYNTAX +.B idle [ \fI-dins\fP ] [ \fI-t title\fP ] [ \fIfile\fP ...] +.PP +.B idle [ \fI-dins\fP ] [ \fI-t title\fP ] ( \fI-c cmd\fP | \fI-r file\fP ) [ \fIarg\fP ...] +.PP +.B idle [ \fI-dins\fP ] [ \fI-t title\fP ] - [ \fIarg\fP ...] +.SH DESCRIPTION +This manual page documents briefly the +.BR idle +command. +This manual page was written for Debian +because the original program does not have a manual page. +For more information, refer to IDLE's help menu. +.PP +.B IDLE +is an Integrated DeveLopment Environment for Python. IDLE is based on +Tkinter, Python's bindings to the Tk widget set. Features are 100% pure +Python, multi-windows with multiple undo and Python colorizing, a Python +shell window subclass, a debugger. IDLE is cross-platform, i.e. it works +on all platforms where Tk is installed. +.LP +.SH OPTIONS +.TP +.B \-h +.PD +Print this help message and exit. +.TP +.B \-n +.PD +Run IDLE without a subprocess (see Help/IDLE Help for details). +.PP +The following options will override the IDLE 'settings' configuration: +.TP +.B \-e +.PD +Open an edit window. +.TP +.B \-i +.PD +Open a shell window. +.PP +The following options imply -i and will open a shell: +.TP +.B \-c cmd +.PD +Run the command in a shell, or +.TP +.B \-r file +.PD +Run script from file. +.PP +.TP +.B \-d +.PD +Enable the debugger. +.TP +.B \-s +.PD +Run $IDLESTARTUP or $PYTHONSTARTUP before anything else. +.TP +.B \-t title +.PD +Set title of shell window. +.PP +A default edit window will be bypassed when -c, -r, or - are used. +.PP +[arg]* and [file]* are passed to the command (-c) or script (-r) in sys.argv[1:]. +.SH EXAMPLES +.TP +idle +.PD +Open an edit window or shell depending on IDLE's configuration. +.TP +idle foo.py foobar.py +.PD +Edit the files, also open a shell if configured to start with shell. +.TP +idle -est "Baz" foo.py +.PD +Run $IDLESTARTUP or $PYTHONSTARTUP, edit foo.py, and open a shell +window with the title "Baz". +.TP +idle -c "import sys; print sys.argv" "foo" +.PD +Open a shell window and run the command, passing "-c" in sys.argv[0] +and "foo" in sys.argv[1]. +.TP +idle -d -s -r foo.py "Hello World" +.PD +Open a shell window, run a startup script, enable the debugger, and +run foo.py, passing "foo.py" in sys.argv[0] and "Hello World" in +sys.argv[1]. +.TP +echo "import sys; print sys.argv" | idle - "foobar" +.PD +Open a shell window, run the script piped in, passing '' in sys.argv[0] +and "foobar" in sys.argv[1]. +.SH SEE ALSO +python(1). +.SH AUTHORS +Various. --- python3.3-3.3.0.orig/debian/pylogo.xpm +++ python3.3-3.3.0/debian/pylogo.xpm @@ -0,0 +1,351 @@ +/* XPM */ +static char * pylogo_xpm[] = { +"32 32 316 2", +" c None", +". c #8DB0CE", +"+ c #6396BF", +"@ c #4985B7", +"# c #4181B5", +"$ c #417EB2", +"% c #417EB1", +"& c #4D83B0", +"* c #6290B6", +"= c #94B2CA", +"- c #70A1C8", +"; c #3D83BC", +"> c #3881BD", +", c #387DB6", +"' c #387CB5", +") c #387BB3", +"! c #3779B0", +"~ c #3778AE", +"{ c #3776AB", +"] c #3776AA", +"^ c #3775A9", +"/ c #4A7FAC", +"( c #709FC5", +"_ c #3A83BE", +": c #5795C7", +"< c #94B9DB", +"[ c #73A4CE", +"} c #3D80B7", +"| c #387CB4", +"1 c #377AB2", +"2 c #377AB0", +"3 c #3777AC", +"4 c #3774A7", +"5 c #3773A5", +"6 c #3C73A5", +"7 c #4586BB", +"8 c #4489C1", +"9 c #A7C7E1", +"0 c #F7F9FD", +"a c #E1E9F1", +"b c #4C89BC", +"c c #3779AF", +"d c #3778AD", +"e c #3873A5", +"f c #4B7CA4", +"g c #3982BE", +"h c #4389C1", +"i c #A6C6E1", +"j c #F6F9FC", +"k c #D6E4F0", +"l c #4A88BB", +"m c #3773A6", +"n c #366F9F", +"o c #366E9D", +"p c #376E9C", +"q c #4A8BC0", +"r c #79A7CD", +"s c #548EBD", +"t c #387AB0", +"u c #3773A4", +"v c #366D9C", +"w c #387FBA", +"x c #387DB7", +"y c #387BB4", +"z c #3775A8", +"A c #366FA0", +"B c #4981AF", +"C c #427BAA", +"D c #3772A4", +"E c #376B97", +"F c #77A3C8", +"G c #4586BC", +"H c #3882BE", +"I c #3B76A7", +"J c #3B76A6", +"K c #366E9E", +"L c #376B98", +"M c #376B96", +"N c #5681A3", +"O c #F5EEB8", +"P c #FFED60", +"Q c #FFE85B", +"R c #FFE659", +"S c #FDE55F", +"T c #5592C4", +"U c #3A83BF", +"V c #3882BD", +"W c #387FB9", +"X c #3779AE", +"Y c #366F9E", +"Z c #366C98", +"` c #376A94", +" . c #5D85A7", +".. c #F5EDB7", +"+. c #FFEA5D", +"@. c #FFE75A", +"#. c #FFE354", +"$. c #FDDD56", +"%. c #669DC8", +"&. c #3885C3", +"*. c #3884C2", +"=. c #387EB8", +"-. c #387CB6", +";. c #377AB1", +">. c #3772A3", +",. c #366D9B", +"'. c #F5EBB5", +"). c #FFE557", +"!. c #FFE455", +"~. c #FFDF50", +"{. c #FFDB4C", +"]. c #FAD862", +"^. c #8EB4D2", +"/. c #3C86C1", +"(. c #3883C0", +"_. c #3882BF", +":. c #3881BC", +"<. c #3880BB", +"[. c #3775AA", +"}. c #F5EAB3", +"|. c #FFE051", +"1. c #FFDE4F", +"2. c #FFDA4A", +"3. c #FED446", +"4. c #F5DF9D", +"5. c #77A5CA", +"6. c #3885C2", +"7. c #387BB2", +"8. c #6B8EA8", +"9. c #F8E7A1", +"0. c #FFE153", +"a. c #FFDD4E", +"b. c #FFDB4B", +"c. c #FFD746", +"d. c #FFD645", +"e. c #FFD342", +"f. c #F6DB8D", +"g. c #508DBE", +"h. c #3771A3", +"i. c #376A95", +"j. c #3D6F97", +"k. c #C3CBC2", +"l. c #FBD964", +"m. c #FFDC4D", +"n. c #FFD544", +"o. c #FFD040", +"p. c #F9CF58", +"q. c #3F83BB", +"r. c #376B95", +"s. c #3A6C95", +"t. c #4E7BA0", +"u. c #91AABC", +"v. c #F6E4A3", +"w. c #FFDA4B", +"x. c #FFD646", +"y. c #FFD443", +"z. c #FFD241", +"A. c #FFCE3D", +"B. c #FFCC3B", +"C. c #FCC83E", +"D. c #3880BC", +"E. c #3C79AC", +"F. c #5F8DB4", +"G. c #7AA0C0", +"H. c #82A6C3", +"I. c #82A3BF", +"J. c #82A2BE", +"K. c #82A1BB", +"L. c #82A1B9", +"M. c #8BA4B5", +"N. c #C1C5AE", +"O. c #F2E19F", +"P. c #FDD74C", +"Q. c #FFD94A", +"R. c #FFD343", +"S. c #FFCE3E", +"T. c #FFCB39", +"U. c #FFC937", +"V. c #FEC636", +"W. c #3D79AB", +"X. c #9DB6C6", +"Y. c #D0CFA2", +"Z. c #EFE598", +"`. c #F8EE9B", +" + c #F8EB97", +".+ c #F8E996", +"++ c #F8E894", +"@+ c #FAE489", +"#+ c #FCDB64", +"$+ c #FFDA4D", +"%+ c #FFCF3E", +"&+ c #FFCB3A", +"*+ c #FFC734", +"=+ c #FFC532", +"-+ c #3F82B7", +";+ c #387EB9", +">+ c #9EB9D0", +",+ c #F2E287", +"'+ c #FDEB69", +")+ c #FEEC60", +"!+ c #FFEB5E", +"~+ c #FFE254", +"{+ c #FFE152", +"]+ c #FFD747", +"^+ c #FFC633", +"/+ c #FCC235", +"(+ c #578FBE", +"_+ c #6996BC", +":+ c #DED9A8", +"<+ c #FEEC62", +"[+ c #FFE658", +"}+ c #FFDF51", +"|+ c #FFDE50", +"1+ c #FFD03F", +"2+ c #FFCD3C", +"3+ c #FFC431", +"4+ c #FFBF2C", +"5+ c #FAC244", +"6+ c #85AACA", +"7+ c #A1BBD2", +"8+ c #F7E47C", +"9+ c #FFE456", +"0+ c #FFC735", +"a+ c #FFBC29", +"b+ c #F7D280", +"c+ c #9DBAD2", +"d+ c #3B7CB2", +"e+ c #ABC2D6", +"f+ c #FDEB7B", +"g+ c #FFC12E", +"h+ c #FDBD30", +"i+ c #F4DEA8", +"j+ c #5F91BA", +"k+ c #ABC1D4", +"l+ c #FDEE7E", +"m+ c #FFE253", +"n+ c #FFCC3C", +"o+ c #FFBA27", +"p+ c #FAC75B", +"q+ c #4A82B0", +"r+ c #3877AB", +"s+ c #3774A6", +"t+ c #AAC0D4", +"u+ c #FDEE7D", +"v+ c #FFEC5F", +"w+ c #FFE255", +"x+ c #FFD848", +"y+ c #FFD444", +"z+ c #FFCF3F", +"A+ c #FFBC2A", +"B+ c #FFBB28", +"C+ c #FDBA32", +"D+ c #447AA8", +"E+ c #4379A7", +"F+ c #FFE95C", +"G+ c #FFE558", +"H+ c #FFE355", +"I+ c #FED84B", +"J+ c #FCD149", +"K+ c #FBCE47", +"L+ c #FBCD46", +"M+ c #FBC840", +"N+ c #FBC63E", +"O+ c #FBC037", +"P+ c #FAC448", +"Q+ c #FDD44C", +"R+ c #FCD14E", +"S+ c #FFC836", +"T+ c #FFC22F", +"U+ c #FFC02D", +"V+ c #FFE052", +"W+ c #FFC636", +"X+ c #FFCF5C", +"Y+ c #FFD573", +"Z+ c #FFC33E", +"`+ c #FEBD2D", +" @ c #FFDB4D", +".@ c #FFD949", +"+@ c #FFD545", +"@@ c #FFD140", +"#@ c #FFCB48", +"$@ c #FFF7E4", +"%@ c #FFFCF6", +"&@ c #FFE09D", +"*@ c #FFBA2E", +"=@ c #FDBE2F", +"-@ c #FFD748", +";@ c #FFCA38", +">@ c #FFC844", +",@ c #FFF2D7", +"'@ c #FFF9EC", +")@ c #FFDB94", +"!@ c #FFB92D", +"~@ c #FAC54D", +"{@ c #FDD54E", +"]@ c #FFBD2D", +"^@ c #FFC858", +"/@ c #FFD174", +"(@ c #FFBF3E", +"_@ c #FCBD3C", +":@ c #FAD66A", +"<@ c #FECD3F", +"[@ c #FFC330", +"}@ c #FFBD2A", +"|@ c #FFB724", +"1@ c #FFB521", +"2@ c #FFB526", +"3@ c #FBC457", +"4@ c #F7E09E", +"5@ c #F8D781", +"6@ c #FAC349", +"7@ c #FCC134", +"8@ c #FEBE2C", +"9@ c #FBBE3F", +"0@ c #F7CF79", +"a@ c #F5D795", +" . + @ # $ % % & * = ", +" - ; > > , ' ) ! ~ { ] ^ / ", +" ( _ : < [ } | 1 2 ~ 3 4 5 5 6 ", +" 7 8 9 0 a b 2 c d 3 { 5 5 5 e f ", +" g h i j k l c ~ { { m 5 5 n o p ", +" > > q r s t c c d 4 5 u n v v v ", +" w x ' y 2 c d d z 5 u A v v v v ", +" B C 5 D v v v v E ", +" F G H H H x ' ) c c c d I J 5 K v v L M N O P Q R S ", +" T U H V V W ' ) c c X ~ 5 5 5 Y v v Z ` ` ...+.@.#.#.$. ", +" %.&.*.> w W =.-.;.c 3 { ^ 5 5 >.o v ,.E ` ` .'.).!.#.~.{.]. ", +"^./.(._.:.<., ' ) ;.X d [.5 5 >.K v ,.E ` ` ` .}.#.|.1.{.2.3.4.", +"5.6.(.H H x ' 7.c c 3 3 4 5 D K v v ,.` ` ` ` 8.9.0.a.b.c.d.e.f.", +"g._.> <.w ' ' | 2 3 { z 5 5 h.v v v i.` ` ` j.k.l.m.{.d.n.e.o.p.", +"q.> > :.-.' 1 c c c ] 5 5 >.v v ,.r.` ` s.t.u.v.{.w.x.y.z.A.B.C.", +"D.D.w -.' 1 c c c E.F.G.H.I.J.J.K.L.L.L.M.N.O.P.Q.c.R.S.B.T.U.V.", +"D.D.=.' ' 1 c c W.X.Y.Z.`.`.`.`.`. +.+++@+#+$+Q.d.R.%+B.&+*+=+=+", +"-+;+-.' ;.2 c c >+,+'+)+P P P !+Q R ~+{+1.{.]+d.y.%+B.&+^+=+=+/+", +"(+' ' ;.c X X _+:+<+P P P P !+R [+~+}+|+{.]+n.R.1+2+&+^+=+3+4+5+", +"6+' ) ! ~ { { 7+8+P P P P !+R 9+#.{+{.w.]+y.z.S.&+0+=+=+3+4+a+b+", +"c+d+7.! d 3 z e+f+P P P !+R 9+#.{+m.{.]+y.1+B.&+0+=+=+g+4+a+h+i+", +" j+c d 3 { 4 k+l+P P !+@.9+m+1.m.{.]+y.1+n+B.*+=+=+g+a+a+o+p+ ", +" q+r+{ s+m t+u+v+@.R w+{+}+{.x+d.y+z+n+B.0+=+=+g+A+a+B+C+ ", +" * D+E+E+ +.F+G+H+}+}+{.I+J+K+L+M+M+M+M+N+O+O+O+O+P+ ", +" ).).#.{+a.{.x+Q+R+ ", +" #.m+1.a.{.x+y.o.2+B.S+=+=+T+U+O+ ", +" 0.V+{.{.x+n.o.2+B.B.W+X+Y+Z+a+`+ ", +" @{..@+@n.@@B.B.S+^+#@$@%@&@*@=@ ", +" ].-@x.y.o.%+;@S+=+=+>@,@'@)@!@~@ ", +" {@z.z+2+U.=+=+=+T+]@^@/@(@_@ ", +" :@<@U.=+=+[@4+}@|@1@2@3@ ", +" 4@5@6@7@8@a+a+9@0@a@ "}; --- python3.3-3.3.0.orig/debian/libPVER-dev.overrides.in +++ python3.3-3.3.0/debian/libPVER-dev.overrides.in @@ -0,0 +1,3 @@ +lib@PVER@-dev binary: python-script-but-no-python-dep + +lib@PVER@-dev binary: arch-dependent-file-not-in-arch-specific-directory --- python3.3-3.3.0.orig/debian/libPVER.symbols.lpia.in +++ python3.3-3.3.0/debian/libPVER.symbols.lpia.in @@ -0,0 +1,6 @@ +libpython@VER@m.so.1.0 libpython@VER@ #MINVER# +#include "libpython.symbols" + PyModule_Create2@Base @SVER@ + _Py_force_double@Base @SVER@ + _Py_get_387controlword@Base @SVER@ + _Py_set_387controlword@Base @SVER@ --- python3.3-3.3.0.orig/debian/README.python +++ python3.3-3.3.0/debian/README.python @@ -0,0 +1,153 @@ + + Python 2.x for Debian + --------------------- + +This is Python 2.x packaged for Debian. + +This document contains information specific to the Debian packages of +Python 2.x. + + + + [TODO: This document is not yet up-to-date with the packages.] + + + + + + +Currently, it features those two main topics: + + 1. Release notes for the Debian packages: + 2. Notes for developers using the Debian Python packages: + +Release notes and documentation from the upstream package are installed +in /usr/share/doc/python/. + +Up-to-date information regarding Python on Debian systems is also +available as http://www.debian.org/~flight/python/. + +There's a mailing list for discussion of issues related to Python on Debian +systems: debian-python@lists.debian.org. The list is not intended for +general Python problems, but as a forum for maintainers of Python-related +packages and interested third parties. + + + +1. Release notes for the Debian packages: + + +Results of the regression test: +------------------------------ + +The package does successfully run the regression tests for all included +modules. Seven packages are skipped since they are platform-dependent and +can't be used with Linux. + + +Noteworthy changes since the 1.4 packages: +----------------------------------------- + +- Threading support enabled. +- Tkinter for Tcl/Tk 8.x. +- New package python-zlib. +- The dbmmodule was dropped. Use bsddb instead. gdbmmodule is provided + for compatibility's sake. +- python-elisp adheres to the new emacs add-on policy; it now depends + on emacsen. python-elisp probably won't work correctly with emacs19. + Refer to /usr/doc/python-elisp/ for more information. +- Remember that 1.5 has dropped the `ni' interface in favor of a generic + `packages' concept. +- Python 1.5 regression test as additional package python-regrtest. You + don't need to install this package unless you don't trust the + maintainer ;-). +- once again, modified upstream's compileall.py and py_compile.py. + Now they support compilation of optimized byte-code (.pyo) for use + with "python -O", removal of .pyc and .pyo files where the .py source + files are missing (-d) and finally the fake of a installation directory + when .py files have to be compiled out of place for later installation + in a different directory (-i destdir, used in ./debian/rules). +- The Debian packages for python 1.4 do call + /usr/lib/python1.4/compileall.py in their postrm script. Therefore + I had to provide a link from /usr/lib/python1.5/compileall.py, otherwise + the old packages won't be removed completely. THIS IS A SILLY HACK! + + + +2. Notes for developers using the Debian python packages: + + +Embedding python: +---------------- + +The files for embedding python resp. extending the python interpreter +are included in the python-dev package. With the configuration in the +Debian GNU/Linux packages of python 1.5, you will want to use something +like + + -I/usr/include/python1.5 (e.g. for config.h) + -L/usr/lib/python1.5/config -lpython1.5 (... -lpthread) + (also for Makefile.pre.in, Setup etc.) + +Makefile.pre.in automatically gets that right. Note that unlike 1.4, +python 1.5 has only one library, libpython1.5.a. + +Currently, there's no shared version of libpython. Future version of +the Debian python packages will support this. + + +Python extension packages: +------------------------- + +According to www.python.org/doc/essays/packages.html, extension packages +should only install into /usr/lib/python1.5/site-packages/ (resp. +/usr/lib/site-python/ for packages that are definitely version independent). +No extension package should install files directly into /usr/lib/python1.5/. + +But according to the FSSTND, only Debian packages are allowed to use +/usr/lib/python1.5/. Therefore Debian Python additionally by default +searches a second hierarchy in /usr/local/lib/. These directories take +precedence over their equivalents in /usr/lib/. + +a) Locally installed Python add-ons + + /usr/local/lib/python1.5/site-packages/ + /usr/local/lib/site-python/ (version-independent modules) + +b) Python add-ons packaged for Debian + + /usr/lib/python1.5/site-packages/ + /usr/lib/site-python/ (version-independent modules) + +Note that no package must install files directly into /usr/lib/python1.5/ +or /usr/local/lib/python1.5/. Only the site-packages directory is allowed +for third-party extensions. + +Use of the new `package' scheme is strongly encouraged. The `ni' interface +is obsolete in python 1.5. + +Header files for extensions go into /usr/include/python1.5/. + + +Installing extensions for local use only: +---------------------------------------- + +Most extensions use Python's Makefile.pre.in. Note that Makefile.pre.in +by default will install files into /usr/lib/, not into /usr/local/lib/, +which is not allowed for local extensions. You'll have to change the +Makefile accordingly. Most times, "make prefix=/usr/local install" will +work. + + +Packaging python extensions for Debian: +-------------------------------------- + +Maintainers of Python extension packages should read README.maintainers. + + + + + 03/09/98 + Gregor Hoffleit + +Last change: 07/16/1999 --- python3.3-3.3.0.orig/debian/README.Tk +++ python3.3-3.3.0/debian/README.Tk @@ -0,0 +1,8 @@ +Tkinter documentation can be found at + + http://www.pythonware.com/library/index.htm + +more specific: + + http://www.pythonware.com/library/tkinter/introduction/index.htm + http://www.pythonware.com/library/tkinter/an-introduction-to-tkinter.pdf --- python3.3-3.3.0.orig/debian/PVER.postinst.in +++ python3.3-3.3.0/debian/PVER.postinst.in @@ -0,0 +1,30 @@ +#! /bin/sh -e + +if [ "$1" = configure ]; then + ( + files=$(dpkg -L @PVER@ | sed -n '/^\/usr\/lib\/@PVER@\/.*\.py$/p') + @PVER@ /usr/lib/@PVER@/py_compile.py $files + if grep -sq '^byte-compile[^#]*optimize' /etc/python/debian_config; then + @PVER@ -O /usr/lib/@PVER@/py_compile.py $files + fi + ) +fi + +oldlocalsite=/usr/local/lib/@PVER@/site-packages +case "$1" in + configure|abort-upgrade|abort-remove|abort-deconfigure) + # issue #623057 + if [ -d $oldlocalsite -a ! -h $oldlocalsite ]; then + rmdir --ignore-fail-on-non-empty $oldlocalsite 2>/dev/null || true + fi + ;; + + *) + echo "postinst called with unknown argument \`$1'" >&2 + exit 1 + ;; +esac + +#DEBHELPER# + +exit 0 --- python3.3-3.3.0.orig/debian/libPVER.symbols.i386.in +++ python3.3-3.3.0/debian/libPVER.symbols.i386.in @@ -0,0 +1,8 @@ +libpython@VER@m.so.1.0 libpython@VER@ #MINVER# +#include "libpython.symbols" + PyModule_Create2@Base @SVER@ + _Py_force_double@Base @SVER@ + _Py_get_387controlword@Base @SVER@ + _Py_set_387controlword@Base @SVER@ + + (optional)__gnu_lto_v1@Base @SVER@ --- python3.3-3.3.0.orig/debian/changelog.shared +++ python3.3-3.3.0/debian/changelog.shared @@ -0,0 +1,3 @@ + * Link the interpreter against the shared runtime library. With + gcc-4.1 the difference in the pystones benchmark dropped from about + 12% to about 5%. --- python3.3-3.3.0.orig/debian/dh_doclink +++ python3.3-3.3.0/debian/dh_doclink @@ -0,0 +1,28 @@ +#! /bin/sh + +pkg=`echo $1 | sed 's/^-p//'` +target=$2 + +ln -sf $target debian/$pkg/usr/share/doc/$pkg + +f=debian/$pkg.postinst.debhelper +if [ ! -e $f ] || [ "`grep -c '^# dh_doclink' $f`" -eq 0 ]; then +cat >> $f <> $f <&2 + exit 1 + ;; +esac + +#DEBHELPER# + +exit 0 --- python3.3-3.3.0.orig/debian/rules +++ python3.3-3.3.0/debian/rules @@ -0,0 +1,1336 @@ +#!/usr/bin/make -f +# Sample debian/rules that uses debhelper. GNU copyright 1997 by Joey Hess. + +unexport LANG LC_ALL LC_CTYPE LC_COLLATE LC_TIME LC_NUMERIC LC_MESSAGES +unexport CFLAGS CXXFLAGS LDFLAGS CPPFLAGS + +export SHELL = /bin/bash + +# Uncomment this to turn on verbose mode. +#export DH_VERBOSE=1 + +vafilt = $(subst $(2)=,,$(filter $(2)=%,$(1))) +DPKG_VARS := $(shell dpkg-architecture) +DEB_BUILD_ARCH ?= $(call vafilt,$(DPKG_VARS),DEB_BUILD_ARCH) +DEB_BUILD_GNU_TYPE ?= $(call vafilt,$(DPKG_VARS),DEB_BUILD_GNU_TYPE) +DEB_HOST_ARCH ?= $(call vafilt,$(DPKG_VARS),DEB_HOST_ARCH) +DEB_HOST_ARCH_ENDIAN ?= $(call vafilt,$(DPKG_VARS),DEB_HOST_ARCH_ENDIAN) +DEB_HOST_ARCH_OS ?= $(call vafilt,$(DPKG_VARS),DEB_HOST_ARCH_OS) +DEB_HOST_GNU_TYPE ?= $(call vafilt,$(DPKG_VARS),DEB_HOST_GNU_TYPE) +DEB_HOST_MULTIARCH ?= $(call vafilt,$(DPKG_VARS),DEB_HOST_MULTIARCH) + +CHANGELOG_VARS := $(shell dpkg-parsechangelog | \ + sed -n 's/ /_/g;/^[^_]/s/^\([^:]*\):_\(.*\)/\1=\2/p') +PKGSOURCE := $(call vafilt,$(CHANGELOG_VARS),Source) +PKGVERSION := $(call vafilt,$(CHANGELOG_VARS),Version) + +on_buildd := $(shell [ -f /CurrentlyBuilding -o "$$LOGNAME" = buildd ] && echo yes) + +ifneq (,$(findstring nocheck, $(DEB_BUILD_OPTIONS))) + WITHOUT_CHECK := yes +endif +WITHOUT_BENCH := +ifneq (,$(findstring nobench, $(DEB_BUILD_OPTIONS))) + WITHOUT_BENCH := yes +endif +ifeq ($(on_buildd),yes) + ifneq (,$(findstring $(DEB_HOST_ARCH), armel hppa mips mipsel s390)) + WITHOUT_CHECK := yes + endif + ifneq (,$(findstring $(DEB_HOST_ARCH), armel hppa mips mipsel s390)) + WITHOUT_BENCH := yes + endif +endif +ifneq ($(DEB_HOST_GNU_TYPE),$(DEB_BUILD_GNU_TYPE)) + WITHOUT_BENCH := yes + WITHOUT_CHECK := yes +endif +WITHOUT_CHECK := yes + +COMMA = , +ifneq (,$(filter parallel=%,$(subst $(COMMA), ,$(DEB_BUILD_OPTIONS)))) + NJOBS := -j $(subst parallel=,,$(filter parallel=%,$(subst $(COMMA), ,$(DEB_BUILD_OPTIONS)))) +endif + +distribution := $(shell lsb_release -is) + +VER=3.3 +SVER=3.3.0~b1 +NVER=3.4 +PVER=python3.3 +PRIORITY=$(shell echo $(VER) | tr -d '.')0 + +PREVVER := $(shell awk '/^python/ && NR > 1 {print substr($$2,2,length($$2)-2); exit}' debian/changelog) + +# default versions are built from the python-defaults source package +# keep the definition to adjust package priorities. +DEFAULT_VERSION = no +STATIC_PYTHON=yes + +MIN_MODS := $(shell awk '/^ / && $$2 == "module" { print $$1 }' \ + debian/PVER-minimal.README.Debian.in) +MIN_EXTS := $(shell awk '/^ / && $$2 ~ /^extension/ { print $$1 }' \ + debian/PVER-minimal.README.Debian.in) +MIN_BUILTINS := $(shell awk '/^ / && $$2 == "builtin" { print $$1 }' \ + debian/PVER-minimal.README.Debian.in) +MIN_PACKAGES := $(shell awk '/^ / && $$2 == "package" { print $$1 }' \ + debian/PVER-minimal.README.Debian.in) +MIN_ENCODINGS := $(foreach i, \ + $(filter-out \ + big5% bz2% cp932.py cp949.py cp950.py euc_% \ + gb% iso2022% johab.py shift_jis% , \ + $(shell cd Lib/encodings && echo *.py)), \ + encodings/$(i)) \ + codecs.py stringprep.py + +with_tk := no +with_interp := static +#with_interp := shared + +PY_INTERPRETER = /usr/bin/python$(VER) + +ifeq ($(DEFAULT_VERSION),yes) + PY_PRIO = standard + #PYSTDDEP = , python (>= $(VER)) +else + PY_PRIO = optional +endif +ifeq ($(distribution),Ubuntu) + PY_MINPRIO = required + PY_MINPRIO = optional + with_fpectl = yes + #with_udeb = yes +else + PY_MINPRIO = $(PY_PRIO) + with_fpectl = yes +endif + +CC=$(DEB_HOST_GNU_TYPE)-gcc +CXX=$(DEB_HOST_GNU_TYPE)-g++ + +DPKG_CPPFLAGS:= $(shell dpkg-buildflags --get CPPFLAGS) +DPKG_CFLAGS := $(shell dpkg-buildflags --get CFLAGS) +DPKG_LDFLAGS := $(shell dpkg-buildflags --get LDFLAGS) +OPT_CFLAGS := $(filter-out -O%,$(DPKG_CFLAGS)) # default is -O3 +DEBUG_CFLAGS := $(patsubst -O%,-O0,$(DPKG_CFLAGS)) + +# on alpha, use -O2 only, use -mieee +ifeq ($(DEB_HOST_ARCH),alpha) + OPT_CFLAGS += -mieee + DEBUG_CFLAGS += -mieee + EXTRA_OPT_FLAGS += -O2 +endif +ifeq ($(DEB_HOST_ARCH),m68k) + EXTRA_OPT_FLAGS += -O2 +endif + +ifeq ($(DEB_HOST_GNU_TYPE),$(DEB_BUILD_GNU_TYPE)) + ifeq ($(DEB_HOST_ARCH_OS),linux) + ifneq (,$(findstring $(DEB_HOST_ARCH), amd64 armel armhf i386 powerpc ppc64)) + with_pgo := yes + endif + endif +endif + +ifneq (,$(findstring $(DEB_HOST_ARCH), amd64 armel armhf i386)) + with_lto := yes +endif + +ifneq (,$(findstring noopt, $(DEB_BUILD_OPTIONS))) + OPT_CFLAGS := $(filter-out -O%, $(OPT_CFLAGS)) + EXTRA_OPT_CFLAGS = -O0 + with_pgo = + with_lto = +endif + +ifeq ($(with_lto),yes) + LTO_CFLAGS = -g -flto -fuse-linker-plugin + EXTRA_OPT_CFLAGS += $(LTO_CFLAGS) +endif + +make_build_target = $(if $(with_pgo),profile-opt) + +buildd_static := $(CURDIR)/build-static +buildd_shared := $(CURDIR)/build-shared +buildd_debug := $(CURDIR)/build-debug +buildd_shdebug := $(CURDIR)/build-shdebug + +d := debian/tmp +scriptdir = usr/share/lib/python$(VER) +scriptdir = usr/share/python$(VER) +scriptdir = usr/lib/python$(VER) + +# package names and directories +p_base := $(PVER) +p_min := $(PVER)-minimal +p_lib := lib$(PVER) +p_tk := $(PVER)-tk +p_dev := $(PVER)-dev +p_exam := $(PVER)-examples +p_idle := idle-$(PVER) +p_doc := $(PVER)-doc +p_dbg := $(PVER)-dbg +p_udeb := $(PVER)-udeb + +p_lbase := lib$(PVER)-stdlib +p_lmin := lib$(PVER)-minimal +p_ldev := lib$(PVER)-dev +p_ldbg := lib$(PVER)-dbg + +d_base := debian/$(p_base) +d_min := debian/$(p_min) +d_lib := debian/$(p_lib) +d_tk := debian/$(p_tk) +d_dev := debian/$(p_dev) +d_exam := debian/$(p_exam) +d_idle := debian/$(p_idle) +d_doc := debian/$(p_doc) +d_dbg := debian/$(p_dbg) +d_udeb := debian/$(p_udeb) + +d_lbase := debian/$(p_lbase) +d_lmin := debian/$(p_lmin) +d_ldev := debian/$(p_ldev) +d_ldbg := debian/$(p_ldbg) + +build-arch: stamps/stamp-build +build-indep: stamps/stamp-build-doc +build: build-arch +stamps/stamp-build: stamps/stamp-build-static stamps/stamp-mincheck \ + stamps/stamp-build-shared stamps/stamp-build-debug \ + stamps/stamp-build-shared-debug \ + stamps/stamp-check stamps/stamp-pystone stamps/stamp-pybench + touch $@ + +PROFILE_EXCLUDES = test_compiler test_distutils test_platform test_subprocess \ + test_multiprocessing test_socketserver \ + test_thread test_threaded_import test_threadedtempfile \ + test_threading test_threading_local test_threadsignals \ + test_dbm_dumb test_dbm_ndbm test_pydoc test_sundry \ + test_signal test_ioctl test_gdb test_io +# FIXME: test_mailxbox breaks, 20090703 +PROFILE_EXCLUDES += test_mailbox +# FIXME: test_xmlrpc breaks, 20090818 +PROFILE_EXCLUDES += test_xmlrpc +# FIXME: test_telnetlib uses network resources +PROFILE_EXCLUDES += test_telnetlib + +PROFILE_TASK = ../Lib/test/regrtest.py \ + -x $(sort $(TEST_EXCLUDES) $(PROFILE_EXCLUDES)) + +stamps/stamp-build-static: stamps/stamp-configure-static + dh_testdir + $(MAKE) $(NJOBS) -C $(buildd_static) \ + EXTRA_CFLAGS="$(EXTRA_OPT_CFLAGS)" \ + PROFILE_TASK='$(PROFILE_TASK)' $(make_build_target) + touch stamps/stamp-build-static + +stamps/stamp-build-shared: stamps/stamp-configure-shared + dh_testdir + $(MAKE) $(NJOBS) -C $(buildd_shared) \ + EXTRA_CFLAGS="$(EXTRA_OPT_CFLAGS)" + : # build a static library with PIC objects + $(MAKE) $(NJOBS) -C $(buildd_shared) \ + EXTRA_CFLAGS="$(EXTRA_OPT_CFLAGS)" \ + LIBRARY=libpython$(VER)m-pic.a libpython$(VER)m-pic.a + touch stamps/stamp-build-shared + +stamps/stamp-build-debug: stamps/stamp-configure-debug + dh_testdir + $(MAKE) $(NJOBS) -C $(buildd_debug) \ + EXTRA_CFLAGS="$(DEBUG_CFLAGS)" + touch stamps/stamp-build-debug + +stamps/stamp-build-shared-debug: stamps/stamp-configure-shared-debug + dh_testdir + : # build the shared debug library + $(MAKE) $(NJOBS) -C $(buildd_shdebug) \ + EXTRA_CFLAGS="$(DEBUG_CFLAGS)" \ + libpython$(VER)dm.so pybuilddir.txt + touch stamps/stamp-build-shared-debug + +common_configure_args = \ + --prefix=/usr \ + --enable-ipv6 \ + --enable-loadable-sqlite-extensions \ + --with-dbmliborder=bdb:gdbm \ + --with-computed-gotos \ + --with-system-expat \ + +ifeq ($(DEB_HOST_ARCH), avr32) + common_configure_args += --without-ffi +else + common_configure_args += --with-system-ffi +endif + +ifeq ($(with_fpectl),yes) + common_configure_args += \ + --with-fpectl +endif + +ifneq ($(DEB_HOST_GNU_TYPE),$(DEB_BUILD_GNU_TYPE)) + common_configure_args += --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) + config_site = ac_cv_file__dev_ptmx=yes ac_cv_file__dev_ptc=yes + ifeq (,$(filter $(DEB_HOST_ARCH),arm m68k)) + ifeq ($(DEB_HOST_ARCH_ENDIAN),little) + config_site += ac_cv_little_endian_double=yes + else + config_site += ac_cv_big_endian_double=yes + endif + endif +endif + +stamps/stamp-configure-shared: stamps/stamp-patch + rm -rf $(buildd_shared) + mkdir -p $(buildd_shared) + cd $(buildd_shared) && \ + CC="$(CC)" CXX="$(CXX)" CFLAGS="$(OPT_CFLAGS)" \ + CPPFLAGS="$(DPKG_CPPFLAGS)" LDFLAGS="$(DPKG_LDFLAGS)" \ + $(config_site) \ + ../configure \ + --enable-shared \ + $(common_configure_args) + + $(call __post_configure,$(buildd_shared)) + + @echo XXXXXXX pyconfig.h + -cat $(buildd_shared)/pyconfig.h + + touch $@ + +stamps/stamp-configure-static: stamps/stamp-patch + rm -rf $(buildd_static) + mkdir -p $(buildd_static) + cd $(buildd_static) && \ + CC="$(CC)" CXX="$(CXX)" CFLAGS="$(OPT_CFLAGS)" \ + CPPFLAGS="$(DPKG_CPPFLAGS)" LDFLAGS="$(DPKG_LDFLAGS)" \ + $(config_site) \ + ../configure \ + $(common_configure_args) + + $(call __post_configure,$(buildd_static)) + touch $@ + +stamps/stamp-configure-debug: stamps/stamp-patch + rm -rf $(buildd_debug) + mkdir -p $(buildd_debug) + cd $(buildd_debug) && \ + CC="$(CC)" CXX="$(CXX)" CFLAGS="$(DEBUG_CFLAGS)" \ + CPPFLAGS="$(DPKG_CPPFLAGS)" LDFLAGS="$(DPKG_LDFLAGS)" \ + $(config_site) \ + ../configure \ + $(common_configure_args) \ + --with-pydebug + + $(call __post_configure,$(buildd_debug)) + touch $@ + +stamps/stamp-configure-shared-debug: stamps/stamp-patch + rm -rf $(buildd_shdebug) + mkdir -p $(buildd_shdebug) + cd $(buildd_shdebug) && \ + CC="$(CC)" CXX="$(CXX)" CFLAGS="$(DEBUG_CFLAGS)" \ + CPPFLAGS="$(DPKG_CPPFLAGS)" LDFLAGS="$(DPKG_LDFLAGS)" \ + $(config_site) \ + ../configure \ + $(common_configure_args) \ + --enable-shared \ + --with-pydebug + + $(call __post_configure,$(buildd_shdebug)) + touch $@ + +define __post_configure + egrep \ + "^#($$(awk -v ORS='|' '$$2 ~ /^extension$$/ {print $$1}' debian/PVER-minimal.README.Debian.in)XX)" \ + Modules/Setup.dist \ + | sed -e 's/^#//' -e 's/-Wl,-Bdynamic//;s/-Wl,-Bstatic//' \ + >> $(1)/Modules/Setup.local + + : # unconditionally run makesetup + cd $(1) && \ + ../Modules/makesetup -c ../Modules/config.c.in -s Modules \ + Modules/Setup.config Modules/Setup.local Modules/Setup + mv $(1)/config.c $(1)/Modules/ + + : # and fix the timestamps + $(MAKE) -C $(1) Makefile Modules/config.c + + : # apply workaround for missing os.fsync + sed 's/HAVE_SYNC/HAVE_FSYNC/g' $(1)/pyconfig.h \ + > $(1)/pyconfig.h.new + touch -r $(1)/pyconfig.h $(1)/pyconfig.h.new + mv -f $(1)/pyconfig.h.new $(1)/pyconfig.h +endef + +stamps/stamp-mincheck: stamps/stamp-build-static debian/PVER-minimal.README.Debian.in +ifeq ($(DEB_HOST_GNU_TYPE),$(DEB_BUILD_GNU_TYPE)) + for m in $(MIN_MODS) $(MIN_PACKAGES) $(MIN_EXTS) $(MIN_BUILTINS); do \ + echo "import $$m"; \ + done > $(buildd_static)/minmods.py + cd $(buildd_static) && ./python ../debian/pymindeps.py minmods.py \ + > $(buildd_static)/mindeps.txt + -if [ -x /usr/bin/dot ]; then \ + python debian/depgraph.py < $(buildd_static)/mindeps.txt \ + > $(buildd_static)/mindeps.dot; \ + dot -Tpng -o $(buildd_static)/mindeps.png \ + $(buildd_static)/mindeps.dot; \ + else true; fi + cd $(buildd_static) && ./python ../debian/mincheck.py \ + minmods.py mindeps.txt +endif + touch stamps/stamp-mincheck + +TEST_RESOURCES = all +ifeq ($(on_buildd),yes) + TEST_RESOURCES := $(TEST_RESOURCES),-network,-urlfetch +endif +TESTOPTS = $(NJOBS) -w -u$(TEST_RESOURCES) +TEST_EXCLUDES = +# profile.py and pstats.py removed from sources +TEST_EXCLUDES += test_pstats test_profile test_cprofile +ifeq ($(on_buildd),yes) + TEST_EXCLUDES += test_tcl test_codecmaps_cn test_codecmaps_hk \ + test_codecmaps_jp test_codecmaps_kr test_codecmaps_tw \ + test_normalization test_ossaudiodev +endif +ifeq (,$(wildcard /dev/dsp)) + TEST_EXCLUDES += test_linuxaudiodev test_ossaudiodev +endif +ifneq (,$(filter $(DEB_HOST_ARCH), hppa)) + TEST_EXCLUDES += test_fork1 test_multiprocessing test_socketserver test_threading test_wait3 test_wait4 test_gdb +endif +ifneq (,$(filter $(DEB_HOST_ARCH), arm avr32)) + TEST_EXCLUDES += test_ctypes +endif +ifneq (,$(filter $(DEB_HOST_ARCH), arm armel avr32 m68k)) + ifeq ($(on_buildd),yes) + TEST_EXCLUDES += test_compiler + endif +endif +ifneq (,$(filter $(DEB_HOST_ARCH), sparc sparc64)) + TEST_EXCLUDES += test_gdb +endif +ifneq (,$(filter $(DEB_HOST_ARCH), hurd-i386)) + TEST_EXCLUDES += test_imaplib test_io test_logging test_random test_signal test_socket test_socketserver test_ssl test_threading +endif + +# in debug builds only +TEST_EXCLUDES += test_gdb + +# for debug builds only +TEST_EXCLUDES += test_gdb + +ifneq (,$(TEST_EXCLUDES)) + TESTOPTS += -x $(sort $(TEST_EXCLUDES)) +endif + +ifneq (,$(wildcard /usr/bin/localedef)) + SET_LOCPATH = LOCPATH=$(CURDIR)/locales +endif + +stamps/stamp-check: +ifeq ($(WITHOUT_CHECK),yes) + echo "check run disabled for this build" > $(buildd_static)/test_results +else + : # build locales needed by the testsuite + rm -rf locales + mkdir locales + if which localedef >/dev/null 2>&1; then \ + sh debian/locale-gen; \ + fi + + @echo ========== test environment ============ + @env + @echo ======================================== + + ifeq (,$(findstring $(DEB_HOST_ARCH), alpha)) + ( \ + echo '#! /bin/sh'; \ + echo 'set -x'; \ + echo 'export $(SET_LOCPATH)'; \ + echo '$(buildd_static)/python $(CURDIR)/debian/script.py test_results '\''make test TESTOPTS="$(filter-out test_gdb,$(TESTOPTS))"'\'; \ + echo 'echo DONE'; \ + ) > $(buildd_debug)/run_tests + chmod 755 $(buildd_debug)/run_tests + @echo "BEGIN test debug" + -cd $(buildd_debug) && time xvfb-run -a -e xvfb-run.log ./run_tests + @echo "END test debug" + endif + + ( \ + echo '#! /bin/sh'; \ + echo 'set -x'; \ + echo 'export $(SET_LOCPATH)'; \ + echo '$(buildd_static)/python $(CURDIR)/debian/script.py test_results '\''make test EXTRA_CFLAGS="$(EXTRA_OPT_CFLAGS)" TESTOPTS="$(TESTOPTS)"'\'; \ + echo 'echo DONE'; \ + ) > $(buildd_static)/run_tests + chmod 755 $(buildd_static)/run_tests + @echo "BEGIN test static" + -cd $(buildd_static) && time xvfb-run -a -e xvfb-run.log ./run_tests + @echo "END test static" + + ( \ + echo '#! /bin/sh'; \ + echo 'set -x'; \ + echo 'export $(SET_LOCPATH)'; \ + echo '$(buildd_static)/python $(CURDIR)/debian/script.py test_results '\''make test EXTRA_CFLAGS="$(EXTRA_OPT_CFLAGS)" TESTOPTS="$(TESTOPTS)"'\'; \ + echo 'echo DONE'; \ + ) > $(buildd_shared)/run_tests + chmod 755 $(buildd_shared)/run_tests + @echo "BEGIN test shared" + -cd $(buildd_shared) && time xvfb-run -a -e xvfb-run.log ./run_tests + @echo "END test shared" +endif + cp -p $(buildd_static)/test_results debian/ + touch stamps/stamp-check + +stamps/stamp-pystone: +ifeq ($(DEB_HOST_GNU_TYPE),$(DEB_BUILD_GNU_TYPE)) + @echo "BEGIN pystone static" + cd $(buildd_static) && ./python ../Lib/test/pystone.py + cd $(buildd_static) && ./python ../Lib/test/pystone.py + @echo "END pystone static" + @echo "BEGIN pystone shared" + cd $(buildd_shared) \ + && LD_LIBRARY_PATH=. ./python ../Lib/test/pystone.py + cd $(buildd_shared) \ + && LD_LIBRARY_PATH=. ./python ../Lib/test/pystone.py + @echo "END pystone shared" + @echo "BEGIN pystone debug" + cd $(buildd_debug) && ./python ../Lib/test/pystone.py + cd $(buildd_debug) && ./python ../Lib/test/pystone.py + @echo "END pystone debug" +endif + touch stamps/stamp-pystone + +stamps/stamp-pybench: + echo "pybench run disabled for this build" > $(buildd_static)/pybench.log + +#ifeq (,$(filter $(DEB_HOST_ARCH), arm armel avr32 hppa mips mipsel m68k)) + pybench_options = -C 2 -n 5 -w 4 +#endif + +stamps/stamp-pybenchx: +ifeq ($(WITHOUT_BENCH),yes) + echo "pybench run disabled for this build" > $(buildd_static)/pybench.log +else + @echo "BEGIN pybench static" + cd $(buildd_static) \ + && time ./python ../Tools/pybench/pybench.py -f run1.pybench $(pybench_options) + cd $(buildd_static) \ + && ./python ../Tools/pybench/pybench.py -f run2.pybench -c run1.pybench $(pybench_options) + @echo "END pybench static" + @echo "BEGIN pybench shared" + cd $(buildd_shared) \ + && LD_LIBRARY_PATH=. ./python ../Tools/pybench/pybench.py -f run1.pybench $(pybench_options) + cd $(buildd_shared) \ + && LD_LIBRARY_PATH=. ./python ../Tools/pybench/pybench.py -f run2.pybench -c run1.pybench $(pybench_options) + @echo "END pybench shared" + @echo "BEGIN shared/static comparision" + $(buildd_static)/python Tools/pybench/pybench.py \ + -s $(buildd_static)/run2.pybench -c $(buildd_shared)/run2.pybench \ + | tee $(buildd_static)/pybench.log + @echo "END shared/static comparision" +endif + touch stamps/stamp-pybench + +minimal-test: + rm -rf mintest + mkdir -p mintest/lib mintest/dynlib mintest/testlib mintest/all-lib + cp -p $(buildd_static)/python mintest/ + cp -p $(foreach i,$(MIN_MODS),Lib/$(i).py) \ + mintest/lib/ + cp -a $(foreach i,$(MIN_PACKAGES),Lib/$(i)) \ + mintest/lib/ + cp -p $(wildcard $(foreach i,$(MIN_EXTS),$(buildd_static)/build/lib*/$(i).*.so)) \ + mintest/dynlib/ + cp -p Lib/unittest.py mintest/lib/ + cp -pr Lib/test mintest/lib/ + cp -pr Lib mintest/all-lib + cp -p $(buildd_static)/build/lib*/*.so mintest/all-lib/ + ( \ + echo "import sys"; \ + echo "sys.path = ["; \ + echo " '$(CURDIR)/mintest/lib',"; \ + echo " '$(CURDIR)/mintest/dynlib',"; \ + echo "]"; \ + cat Lib/test/regrtest.py; \ + ) > mintest/lib/test/mintest.py + cd mintest && ./python -E -S lib/test/mintest.py \ + -x test_codecencodings_cn test_codecencodings_hk \ + test_codecencodings_jp test_codecencodings_kr \ + test_codecencodings_tw test_codecs test_multibytecodec \ + +stamps/stamp-doc-html: + dh_testdir + $(MAKE) -C Doc html + touch stamps/stamp-doc-html + +build-doc: stamps/stamp-patch stamps/stamp-build-doc +stamps/stamp-build-doc: stamps/stamp-doc-html + touch stamps/stamp-build-doc + +control-file: + sed -e "s/@PVER@/$(PVER)/g" \ + -e "s/@VER@/$(VER)/g" \ + -e "s/@PYSTDDEP@/$(PYSTDDEP)/g" \ + -e "s/@PRIO@/$(PY_PRIO)/g" \ + -e "s/@MINPRIO@/$(PY_MINPRIO)/g" \ + debian/control.in \ + $(if $(with_udeb),debian/control.udeb) \ + > debian/control.tmp +ifeq ($(distribution),Ubuntu) + ifneq (,$(findstring ubuntu, $(PKGVERSION))) + m='Ubuntu Core Developers '; \ + sed -i "/^Maintainer:/s/\(.*\)/Maintainer: $$m\nXSBC-Original-\1/" \ + debian/control.tmp + endif +endif + [ -e debian/control ] \ + && cmp -s debian/control debian/control.tmp \ + && rm -f debian/control.tmp && exit 0; \ + mv debian/control.tmp debian/control + + + +clean: control-file + dh_testdir + dh_testroot + $(MAKE) -f debian/rules unpatch + rm -rf stamps .pc + rm -f debian/test_results + + $(MAKE) -C Doc clean + sed 's/^@/#/' Makefile.pre.in | $(MAKE) -f - srcdir=. distclean + rm -rf $(buildd_static) $(buildd_shared) $(buildd_debug) $(buildd_shdebug) + find -name '*.py[co]' | xargs -r rm -f + rm -f Lib/lib2to3/*.pickle + rm -rf Lib/plat-$(DEB_HOST_MULTIARCH) + rm -rf locales + rm -rf $(d)-dbg + + for f in debian/*.in; do \ + f2=`echo $$f | sed "s,PVER,$(PVER),g;s/@VER@/$(VER)/g;s,\.in$$,,"`; \ + if [ $$f2 != debian/control ] && [ $$f2 != debian/source.lintian-overrides ]; then \ + rm -f $$f2; \ + fi; \ + done + dh_clean + +stamps/stamp-control: + : # We have to prepare the various control files + + for f in debian/*.in; do \ + f2=`echo $$f | sed "s,PVER,$(PVER),g;s/@VER@/$(VER)/g;s,\.in$$,,"`; \ + if [ $$f2 != debian/control ]; then \ + sed -e "s/@PVER@/$(PVER)/g;s/@VER@/$(VER)/g;s/@SVER@/$(SVER)/g" \ + -e "s/@PRIORITY@/$(PRIORITY)/g" \ + -e "s,@SCRIPTDIR@,/$(scriptdir),g" \ + -e "s,@INFO@,$(info_docs),g" \ + <$$f >$$f2; \ + fi; \ + done + +2to3-man: + help2man --no-info --version-string=$(VER) --no-discard-stderr \ + --name 'Python2 to Python3 converter' \ + 2to3-$(VER) > debian/2to3-3.1 + help2man --no-info --version-string=$(VER) --no-discard-stderr \ + --name 'pysetup tool' \ + pysetup$(VER) > debian/pysetup3.1 + help2man --no-info --version-string=$(VER) --no-discard-stderr \ + --name 'create virtual python environments' \ + pyvenv-$(VER) > debian/pyvenv3.1 + +install: build-arch stamps/stamp-install +stamps/stamp-install: stamps/stamp-build control-file stamps/stamp-control + dh_testdir + dh_testroot + dh_clean -k + dh_installdirs + + : # make install into tmp and subsequently move the files into + : # their packages' directories. + install -d $(d)/usr +ifeq ($(with_interp),static) + $(MAKE) -C $(buildd_static) install prefix=$(CURDIR)/$(d)/usr + sed -e '/^OPT/s,-O3,-O2,' \ + -e 's/$(LTO_CFLAGS)//g' \ + -e 's,^RUNSHARED *=.*,RUNSHARED=,' \ + -e '/BLDLIBRARY/s/-L\. //' \ + $(buildd_shared)/$(shell cat $(buildd_shared)/pybuilddir.txt)/_sysconfigdata.py \ + > $(d)/$(scriptdir)/_sysconfigdata.py +else + $(MAKE) -C $(buildd_shared) install prefix=$(CURDIR)/$(d)/usr +endif + mv $(d)/usr/bin/python-config.sh $(d)/usr/bin/python$(VER)m-config + rm -f $(d)/$(scriptdir)/lib-dynload/*.py + sed -i 's/ -O3 / -O2 /g;s/$(LTO_CFLAGS)//g;s/-fprofile-use *-fprofile-correction//g' \ + $(d)/$(scriptdir)/_sysconfigdata.py + mv $(d)/$(scriptdir)/_sysconfigdata.py \ + $(d)/$(scriptdir)/plat-$(DEB_HOST_MULTIARCH)/_sysconfigdata_m.py + cp -p debian/_sysconfigdata.py $(d)/$(scriptdir)/ + + -find $(d)/usr/lib/python$(VER) -name '*_failed*.so' + find $(d)/usr/lib/python$(VER) -name '*_failed*.so' | xargs -r rm -f + + for i in $(d)/$(scriptdir)/lib-dynload/*.so; do \ + b=$$(basename $$i .cpython-33m.so); \ + d=$${b}.cpython-33m-$(DEB_HOST_MULTIARCH).so; \ + mv $$i $(d)/$(scriptdir)/lib-dynload/$$d; \ + done + + mv $(d)/usr/lib/libpython*.a $(d)/usr/lib/$(DEB_HOST_MULTIARCH)/ + + mkdir -p $(d)/usr/lib/python3 + mv $(d)/usr/lib/python$(VER)/site-packages \ + $(d)/usr/lib/python3/dist-packages + rm -f $(d)/usr/lib/python3/dist-packages/README + + : # remove files, which are not packaged + rm -rf $(d)/usr/lib/python$(VER)/ctypes/macholib + rm -f $(d)/$(scriptdir)/plat-*/regen + rm -f $(d)/$(scriptdir)/lib2to3/*.pickle + + : # cannot build it, zlib maintainer won't provide a mingw build + find $(d) -name 'wininst*.exe' | xargs -r rm -f + + : # fix some file permissions + chmod a-x $(d)/$(scriptdir)/{runpy,fractions,lib2to3/refactor,tkinter/tix}.py + +# : # move manpages to new names +# if [ -d $(d)/usr/man/man1 ]; then \ +# mkdir -p $(d)/usr/share/man +# mv $(d)/usr/man/man1/* $(d)/usr/share/man/man1/; \ +# rm -rf $(d)/usr/man/; \ +# fi + + mkdir -p $(d)/usr/share/man/man1 + cp -p Misc/python.man $(d)/usr/share/man/man1/python$(VER).1 + ln -sf python$(VER).1 $(d)/usr/share/man/man1/python$(VER)m.1 + cp -p debian/pydoc.1 $(d)/usr/share/man/man1/pydoc$(VER).1 + + : # Symlinks to /usr/bin for some tools + ln -sf ../lib/python$(VER)/pdb.py $(d)/usr/bin/pdb$(VER) + cp -p debian/pdb.1 $(d)/usr/share/man/man1/pdb$(VER).1 + cp -p debian/2to3-3.1 $(d)/usr/share/man/man1/2to3-$(VER).1 + cp -p debian/pysetup3.1 $(d)/usr/share/man/man1/pysetup$(VER).1 + cp -p debian/pyvenv3.1 $(d)/usr/share/man/man1/pyvenv-$(VER).1 + + : # versioned install only + rm -f $(d)/usr/bin/{2to3,idle3,pydoc3,pysetup3,python3,python3-config} + rm -f $(d)/usr/lib/*/pkgconfig/python3.pc + + dh_installdirs -p$(p_lib) \ + usr/lib/$(DEB_HOST_MULTIARCH) \ + $(scriptdir)/config-$(VER)m-$(DEB_HOST_MULTIARCH) \ + usr/share/doc + : # install the shared library + cp -p $(buildd_shared)/libpython$(VER)m.so.1.0 \ + $(d_lib)/usr/lib/$(DEB_HOST_MULTIARCH)/ + dh_link -p$(p_lib) \ + /usr/lib/$(DEB_HOST_MULTIARCH)/libpython$(VER)m.so.1.0 \ + /usr/lib/$(DEB_HOST_MULTIARCH)/libpython$(VER)m.so.1 \ + /usr/lib/$(DEB_HOST_MULTIARCH)/libpython$(VER)m.so.1 \ + /$(scriptdir)/config-$(VER)m-$(DEB_HOST_MULTIARCH)/libpython$(VER)m.so \ + /usr/lib/$(DEB_HOST_MULTIARCH)/libpython$(VER)m.so.1 \ + /$(scriptdir)/config-$(VER)m-$(DEB_HOST_MULTIARCH)/libpython$(VER).so + + ln -sf $(p_base) $(d_lib)/usr/share/doc/$(p_lib) + + ln -sf libpython$(VER)m.so.1 $(d)/usr/lib/$(DEB_HOST_MULTIARCH)/libpython$(VER)m.so + +ifeq ($(with_interp),shared) + : # install the statically linked runtime + install -m755 $(buildd_static)/python $(d)/usr/bin/python$(VER)-static +endif + + cp -p Tools/i18n/pygettext.py $(d)/usr/bin/pygettext$(VER) + cp -p debian/pygettext.1 $(d)/usr/share/man/man1/pygettext$(VER).1 + + : # install the Makefile of the shared python build + sed -e '/^OPT/s,-O3,-O2,' \ + -e 's/$(LTO_CFLAGS)//g' \ + -e 's,^RUNSHARED *=.*,RUNSHARED=,' \ + -e '/BLDLIBRARY/s/-L\. //' \ + $(buildd_shared)/Makefile \ + > $(d)/$(scriptdir)/config-$(VER)m-$(DEB_HOST_MULTIARCH)/Makefile + + : # Move the the minimal libraries into $(p_lmin). + dh_installdirs -p$(p_lmin) \ + etc/$(PVER) \ + usr/bin \ + usr/share/man/man1 \ + $(scriptdir)/lib-dynload + -cd $(d); for i in $(MIN_EXTS); do \ + test -e $(scriptdir)/lib-dynload/$$i.*.so \ + && echo $(scriptdir)/lib-dynload/$$i.*.so; \ + done + + DH_COMPAT=2 dh_movefiles -p$(p_lmin) --sourcedir=$(d) \ + $(foreach i,$(MIN_MODS),$(scriptdir)/$(i).py) \ + $(foreach i,$(MIN_PACKAGES),$(scriptdir)/$(i)) \ + $(foreach i,$(MIN_ENCODINGS),$(scriptdir)/$(i)) \ + $(scriptdir)/site.py \ + $(scriptdir)/_sysconfigdata.py \ + $(scriptdir)/plat-$(DEB_HOST_MULTIARCH)/_sysconfigdata_m.py \ + $(shell cd $(d); for i in $(MIN_EXTS); do \ + test -e $(scriptdir)/lib-dynload/$$i.*.so \ + && echo $(scriptdir)/lib-dynload/$$i.*.so; \ + done) + ls -l $(d_lmin)/$(scriptdir)/lib-dynload + rm -rf $(d_lmin)/$(scriptdir)/importlib/test + + : # Move the binary and the minimal libraries into $(p_min). + dh_installdirs -p$(p_min) \ + usr/bin \ + usr/share/man/man1 + DH_COMPAT=2 dh_movefiles -p$(p_min) --sourcedir=$(d) \ + usr/bin/python$(VER) \ + usr/bin/python$(VER)m \ + usr/share/man/man1/python$(VER).1 \ + usr/share/man/man1/python$(VER)m.1 + + rv=0; \ + for i in $(MIN_EXTS); do \ + if [ -f $(d)/$(scriptdir)/lib-dynload/$$i.so ]; then \ + echo >&2 "extension $$i not mentioned in Setup.dist"; \ + rv=1; \ + fi; \ + done; \ + exit $$rv; + + : # Install sitecustomize.py + cp -p debian/sitecustomize.py $(d_lmin)/etc/$(PVER)/ + dh_link -p$(p_lmin) \ + /etc/$(PVER)/sitecustomize.py /$(scriptdir)/sitecustomize.py + + : # Move the static library and the header files into $(p_dev). +# mv $(d)/usr/share/include/python$(VER)/* $(d)/usr/include/python$(VER)/. +# rm -rf $(d)/usr/share/include + + cp $(d)/usr/bin/$(PVER)m-config $(d)/usr/bin/$(DEB_HOST_MULTIARCH)-$(PVER)m-config + ln -sf $(DEB_HOST_MULTIARCH)-$(PVER)m-config $(d)/usr/bin/$(DEB_HOST_MULTIARCH)-$(PVER)-config + + dh_installdirs -p$(p_ldev) \ + usr/bin \ + $(scriptdir) \ + usr/include \ + usr/share/man/man1 + + DH_COMPAT=2 dh_movefiles -p$(p_ldev) --sourcedir=$(d) \ + usr/bin/$(DEB_HOST_MULTIARCH)-$(PVER)*-config \ + usr/lib/python$(VER)/config-$(VER)m-$(DEB_HOST_MULTIARCH) \ + usr/include \ + usr/lib/$(DEB_HOST_MULTIARCH)/libpython$(VER)m.{a,so} \ + usr/lib/$(DEB_HOST_MULTIARCH)/pkgconfig/python-$(VER)*.pc \ + usr/lib/python$(VER)/distutils/command/wininst-*.exe + +# sed 's/@subdir@/$(PVER)m/;s/@header@/pyconfig.h/' \ +# debian/multiarch.h.in > $(d_ldev)/usr/include/$(PVER)m/pyconfig.h + + sed -i '/^Cflags:/s,$$, -I$${includedir}/$(DEB_HOST_MULTIARCH)/python$(VER)m,' \ + $(d_ldev)/usr/lib/$(DEB_HOST_MULTIARCH)/pkgconfig/python-$(VER).pc + + dh_link -p$(p_ldev) \ + /usr/lib/$(PVER)/config-$(VER)m-$(DEB_HOST_MULTIARCH)/libpython$(VER)m.a \ + /usr/lib/$(DEB_HOST_MULTIARCH)/libpython$(VER)m.a + + cp -p $(buildd_shared)/libpython$(VER)m-pic.a \ + $(d_ldev)/usr/lib/python$(VER)/config-$(VER)m-$(DEB_HOST_MULTIARCH)/ + + : # symlinks for the "old" include directory name + ln -sf python$(VER)m $(d_ldev)/usr/include/python$(VER) + + dh_installdirs -p$(p_dev) \ + usr/share/doc/python$(VER) \ + usr/share/man/man1 \ + $(scriptdir) \ + $(scriptdir)/doc/html + cp -p Misc/HISTORY Misc/README.valgrind Misc/gdbinit \ + debian/README.maintainers \ + debian/test_results $(buildd_static)/pybench.log \ + $(d_dev)/usr/share/doc/python$(VER)/ + + DH_COMPAT=2 dh_movefiles -p$(p_dev) --sourcedir=$(d) \ + usr/bin/python$(VER)*-config + + : # in $(p_ldev), prefix python-config with triplets + cp -p debian/python3-config.1 \ + $(d_ldev)/usr/share/man/man1/$(DEB_HOST_MULTIARCH)-$(PVER)m-config.1 + ln -sf $(DEB_HOST_MULTIARCH)-$(PVER)m-config.1.gz \ + $(d_ldev)/usr/share/man/man1/$(DEB_HOST_MULTIARCH)-$(PVER)-config.1.gz +ifneq ($(DEB_HOST_MULTIARCH),$(DEB_HOST_GNU_TYPE)) + ln -sf $(DEB_HOST_MULTIARCH)-$(PVER)m-config \ + $(d_ldev)/usr/bin/$(DEB_HOST_GNU_TYPE)-$(PVER)m-config + ln -sf $(DEB_HOST_MULTIARCH)-$(PVER)-config \ + $(d_ldev)/usr/bin/$(DEB_HOST_GNU_TYPE)-$(PVER)-config + ln -sf $(DEB_HOST_MULTIARCH)-$(PVER)-config.1.gz \ + $(d_ldev)/usr/share/man/man1/$(DEB_HOST_GNU_TYPE)-$(PVER)-config.1.gz + ln -sf $(DEB_HOST_MULTIARCH)-$(PVER)-config.1.gz \ + $(d_ldev)/usr/share/man/man1/$(DEB_HOST_GNU_TYPE)-$(PVER)m-config.1.gz +endif + ln -sf $(DEB_HOST_MULTIARCH)-$(PVER)m-config $(d_dev)/usr/bin/$(PVER)m-config + ln -sf $(DEB_HOST_MULTIARCH)-$(PVER)m-config.1.gz $(d_dev)/usr/share/man/man1/$(PVER)m-config.1.gz + + ln -sf $(DEB_HOST_MULTIARCH)-$(PVER)-config $(d_dev)/usr/bin/$(PVER)-config + ln -sf $(DEB_HOST_MULTIARCH)-$(PVER)-config.1.gz $(d_dev)/usr/share/man/man1/$(PVER)-config.1.gz + +ifeq ($(with_tk),yes) + : # Move the Tkinter files into $(p_tk). + dh_installdirs -p$(p_tk) \ + $(scriptdir) \ + usr/lib/python$(VER)/lib-dynload + DH_COMPAT=2 dh_movefiles -p$(p_tk) --sourcedir=$(d) \ + usr/lib/python$(VER)/lib-dynload/_tkinter*.so +endif + +# : # The test framework into $(p_base), regression tests dropped + DH_COMPAT=2 dh_movefiles -p$(p_base) --sourcedir=$(d) \ + $(scriptdir)/test/{regrtest.py,support.py,__init__.py,pystone.py} + rm -rf $(d)/$(scriptdir)/test + rm -rf $(d)/$(scriptdir)/ctypes/test + rm -rf $(d)/$(scriptdir)/bsddb/test + rm -rf $(d)/$(scriptdir)/distutils/tests + rm -rf $(d)/$(scriptdir)/email/test + rm -rf $(d)/$(scriptdir)/importlib/test + rm -rf $(d)/$(scriptdir)/json/tests + rm -rf $(d)/$(scriptdir)/lib2to3/tests + rm -rf $(d)/$(scriptdir)/sqlite3/test + rm -rf $(d)/$(scriptdir)/packaging/tests + rm -rf $(d)/$(scriptdir)/tkinter/test + rm -rf $(d)/$(scriptdir)/unittest/test + + : # IDLE + mv $(d)/usr/bin/idle$(VER) $(d)/usr/bin/idle-python$(VER) + rm -f $(d)/usr/lib/python$(VER)/idlelib/idle.bat + dh_installdirs -p$(p_idle) \ + usr/bin \ + usr/share/man/man1 + DH_COMPAT=2 dh_movefiles -p$(p_idle) --sourcedir=$(d) \ + usr/bin/idle-python$(VER) + cp -p debian/idle-$(PVER).1 $(d_idle)/usr/share/man/man1/ + + : # Move the demos and tools into $(p_exam)'s doc directory + dh_installdirs -p$(p_exam) \ + usr/share/doc/python$(VER)/examples + + cp -rp Tools/* $(d_exam)/usr/share/doc/python$(VER)/examples/ + rm -rf $(d_exam)/usr/share/doc/python$(VER)/examples/Tools/{buildbot,msi} + : # XXX: We don't need rgb.txt, we'll use our own: + rm -rf $(d_exam)/usr/share/doc/python$(VER)/examples/Tools/pynche/X + + : # Replace all '#!' calls to python with $(PY_INTERPRETER) + : # and make them executable + for i in `find debian -mindepth 3 -type f ! -name '*.dpatch'`; do \ + sed '1s,#!.*python[^ ]*\(.*\),#! $(PY_INTERPRETER)\1,' \ + $$i > $$i.temp; \ + if cmp --quiet $$i $$i.temp; then \ + rm -f $$i.temp; \ + else \ + mv -f $$i.temp $$i; \ + chmod 755 $$i; \ + echo "fixed interpreter: $$i"; \ + fi; \ + done + + : # Move the docs into $(p_base)'s /usr/share/doc/$(PVER) directory, + : # all other packages only have a copyright file. + dh_installdocs -p$(p_base) \ + README Misc/NEWS Misc/ACKS + ln -sf NEWS.gz $(d_base)/usr/share/doc/$(p_base)/changelog.gz + dh_installdocs --all -N$(p_base) -N$(p_dev) -N$(p_dbg) -N$(p_lib) debian/README.Debian + + : # IDLE has its own changelogs, docs... + dh_installchangelogs -p$(p_idle) Lib/idlelib/ChangeLog + dh_installdocs -p$(p_idle) Lib/idlelib/{NEWS,README,TODO,extend}.txt + + mkdir -p $(d_idle)/usr/share/applications + cp -p debian/idle.desktop \ + $(d_idle)/usr/share/applications/idle-$(PVER).desktop + + : # those packages have own README.Debian's + install -m 644 -p debian/README.$(p_base) \ + $(d_base)/usr/share/doc/$(PVER)/README.Debian + install -m 644 -p debian/README.$(p_idle) \ + $(d_idle)/usr/share/doc/$(p_idle)/README.Debian +ifeq ($(with_tk),yes) + cp -p debian/README.Tk $(d_tk)/usr/share/doc/$(p_tk)/ +endif + + : # library files into $(p_lbase) + dh_installdirs -p$(p_lbase) \ + usr/lib + dh_movefiles -p$(p_lbase) \ + usr/lib/python$(VER) + + : # The rest goes into $(p_base) + mkdir -p $(d)/usr/lib/python3/dist-packages + (cd $(d) && tar cf - .) | (cd $(d_base) && tar xpf -) + rm -f $(d_base)/usr/bin/python + rm -f $(d_base)/usr/bin/pyvenv + + : # Install menu icon + dh_installdirs -p$(p_base) usr/share/pixmaps + cp -p debian/pylogo.xpm $(d_base)/usr/share/pixmaps/$(PVER).xpm + + : # generate binfmt file + mkdir -p $(d_min)/usr/share/binfmts +ifeq ($(DEB_HOST_GNU_TYPE),$(DEB_BUILD_GNU_TYPE)) + $(buildd_static)/python debian/mkbinfmt.py $(PVER) \ + > $(d_min)/usr/share/binfmts/$(PVER) +else + $(PVER) debian/mkbinfmt.py $(PVER) > $(d_min)/usr/share/binfmts/$(PVER) +endif + + : # desktop entry + mkdir -p $(d_base)/usr/share/applications + cp -p debian/$(PVER).desktop \ + $(d_base)/usr/share/applications/$(PVER).desktop + + : # remove some things + -find debian -name .cvsignore | xargs rm -f + -find debian -name '*.py[co]' | xargs rm -f + + : # remove empty directories, when all components are in place + -find debian ! -name lib-dynload ! -name dist-packages -type d -empty -delete + + : # install debug package + rm -rf $(d)-dbg + $(MAKE) -C $(buildd_debug) install DESTDIR=$(CURDIR)/$(d)-dbg + : # install the Makefile of the shared python debug build + sed -e '/^OPT/s,-O3,-O2,' \ + -e 's/$(LTO_CFLAGS)//g' \ + -e 's,^RUNSHARED *=.*,RUNSHARED=,' \ + -e '/BLDLIBRARY/s/-L\. //' \ + $(buildd_shdebug)/Makefile \ + > $(d)-dbg/$(scriptdir)/config-$(VER)dm-$(DEB_HOST_MULTIARCH)/Makefile + sed -e 's,^RUNSHARED *=.*,RUNSHARED=,' \ + -e '/BLDLIBRARY/s/-L\. //' \ + $(buildd_shdebug)/$(shell cat $(buildd_shdebug)/pybuilddir.txt)/_sysconfigdata.py \ + > $(d)-dbg/$(scriptdir)/_sysconfigdata.py + rm -f $(d)-dbg/$(scriptdir)/lib-dynload/_sysconfigdata.py + sed -i 's/ -O3 / -O2 /g;s/$(LTO_CFLAGS)//g;s/-fprofile-use *-fprofile-correction//g' \ + $(d)-dbg/$(scriptdir)/_sysconfigdata.py + mv $(d)-dbg/$(scriptdir)/_sysconfigdata.py \ + $(d)-dbg/$(scriptdir)/plat-$(DEB_HOST_MULTIARCH)/_sysconfigdata_dm.py + + mv $(d)-dbg/usr/lib/libpython*.a $(d)-dbg/usr/lib/$(DEB_HOST_MULTIARCH)/ + + for i in $(d)-dbg/$(scriptdir)/lib-dynload/*.so; do \ + b=$$(basename $$i .cpython-33dm.so); \ + d=$${b}.cpython-33dm-$(DEB_HOST_MULTIARCH).so; \ + mv $$i $(d)-dbg/$(scriptdir)/lib-dynload/$$d; \ + done + + dh_installdirs -p$(p_ldbg) \ + usr/bin \ + usr/share/man/man1 \ + $(scriptdir)/lib-dynload \ + $(scriptdir)/plat-$(DEB_HOST_MULTIARCH) \ + usr/include/$(PVER)dm \ + usr/include/$(DEB_HOST_MULTIARCH)/$(PVER)dm \ + usr/lib/$(DEB_HOST_MULTIARCH)/pkgconfig + + cp -p $(d)-dbg/$(scriptdir)/lib-dynload/*.so \ + $(d_ldbg)/$(scriptdir)/lib-dynload/ + cp -p $(d)-dbg/$(scriptdir)/plat-$(DEB_HOST_MULTIARCH)/_sysconfigdata_dm.py \ + $(d_ldbg)/$(scriptdir)/plat-$(DEB_HOST_MULTIARCH)/ + cp -p $(buildd_shdebug)/libpython$(VER)dm.so.1.0 \ + $(d_ldbg)/usr/lib/$(DEB_HOST_MULTIARCH)/ + dh_link -p$(p_ldbg) \ + /usr/lib/$(DEB_HOST_MULTIARCH)/libpython$(VER)dm.so.1.0 \ + /usr/lib/$(DEB_HOST_MULTIARCH)/libpython$(VER)dm.so.1 \ + /usr/lib/$(DEB_HOST_MULTIARCH)/libpython$(VER)dm.so.1 \ + /usr/lib/$(DEB_HOST_MULTIARCH)/libpython$(VER)dm.so + sed -e '/^Libs:/s,-lpython$(VER),-lpython$(VER)dm,' \ + -e '/^Cflags:/s,$$, -I$${includedir}/$(DEB_HOST_MULTIARCH)/python$(VER)dm,' \ + $(d)-dbg/usr/lib/$(DEB_HOST_MULTIARCH)/pkgconfig/python-$(VER).pc \ + > $(d_ldbg)/usr/lib/$(DEB_HOST_MULTIARCH)/pkgconfig/python-$(VER)-dbg.pc + + dh_installdirs -p$(p_dbg) \ + usr/bin \ + usr/share/man/man1 \ + usr/share/doc/$(p_base) + cp -p Misc/SpecialBuilds.txt $(d_dbg)/usr/share/doc/$(p_base)/ + cp -p debian/$(PVER)-dbg.README.Debian \ + $(d_dbg)/usr/share/doc/$(p_base)/README.debug + cp -p $(buildd_debug)/python $(d_dbg)/usr/bin/$(PVER)dm + ln -sf python$(VER)dm $(d_dbg)/usr/bin/$(PVER)-dbg + +ifneq ($(with_tk),yes) + rm -f $(d_ldbg)/$(scriptdir)/lib-dynload/_tkinter*.so + rm -f $(d_ldbg)/usr/lib/debug/$(scriptdir)/lib-dynload/_tkinter*.so +endif +ifneq ($(with_gdbm),yes) + rm -f $(d_ldbg)/$(scriptdir)/lib-dynload/_gdbm*.so + rm -f $(d_ldbg)/usr/lib/debug/$(scriptdir)/lib-dynload/_gdbm*.so +endif + + cp -a $(d)-dbg/$(scriptdir)/config-$(VER)dm-$(DEB_HOST_MULTIARCH) \ + $(d_ldbg)/$(scriptdir)/ + dh_link -p$(p_ldbg) \ + /usr/lib/$(DEB_HOST_MULTIARCH)/libpython$(VER)dm.so \ + /$(scriptdir)/config-$(VER)dm-$(DEB_HOST_MULTIARCH)/libpython$(VER)dm.so \ + /usr/lib/$(DEB_HOST_MULTIARCH)/libpython$(VER)dm.so \ + /$(scriptdir)/config-$(VER)dm-$(DEB_HOST_MULTIARCH)/libpython$(VER).so \ + /$(scriptdir)/config-$(VER)dm-$(DEB_HOST_MULTIARCH)/libpython$(VER)dm.a \ + /usr/lib/$(DEB_HOST_MULTIARCH)/libpython$(VER)dm.a + + for i in $(d_ldev)/usr/include/$(PVER)m/*; do \ + i=$$(basename $$i); \ + case $$i in pyconfig.h) continue; esac; \ + ln -sf ../$(PVER)m/$$i $(d_ldbg)/usr/include/$(PVER)dm/$$i; \ + done + cp -p $(buildd_debug)/pyconfig.h $(d_ldbg)/usr/include/$(DEB_HOST_MULTIARCH)/$(PVER)dm/ +# sed 's/@subdir@/$(PVER)dm/;s/@header@/pyconfig.h/' \ +# debian/multiarch.h.in > $(d_ldbg)/usr/include/$(PVER)dm/pyconfig.h + + ln -sf $(PVER).1.gz $(d_dbg)/usr/share/man/man1/$(PVER)-dbg.1.gz + + : # in $(p_ldbg), prefix python-config with triplets + cp $(d)-dbg/usr/bin/python-config.sh \ + $(d_ldbg)/usr/bin/$(DEB_HOST_MULTIARCH)-$(PVER)dm-config + ln -sf $(DEB_HOST_MULTIARCH)-$(PVER)dm-config \ + $(d_ldbg)/usr/bin/$(DEB_HOST_MULTIARCH)-$(PVER)-dbg-config + ln -sf $(DEB_HOST_MULTIARCH)-$(PVER)m-config.1.gz \ + $(d_ldbg)/usr/share/man/man1/$(DEB_HOST_MULTIARCH)-$(PVER)dm-config.1.gz + ln -sf $(DEB_HOST_MULTIARCH)-$(PVER)m-config.1.gz \ + $(d_ldbg)/usr/share/man/man1/$(DEB_HOST_MULTIARCH)-$(PVER)-dbg-config.1.gz +ifneq ($(DEB_HOST_MULTIARCH),$(DEB_HOST_GNU_TYPE)) + ln -sf $(DEB_HOST_MULTIARCH)-$(PVER)dm-config \ + $(d_ldbg)/usr/bin/$(DEB_HOST_GNU_TYPE)-$(PVER)dm-config + ln -sf $(DEB_HOST_MULTIARCH)-$(PVER)-config.1.gz \ + $(d_ldbg)/usr/share/man/man1/$(DEB_HOST_GNU_TYPE)-$(PVER)dm-config.1.gz + ln -sf $(DEB_HOST_MULTIARCH)-$(PVER)dm-config \ + $(d_ldbg)/usr/bin/$(DEB_HOST_GNU_TYPE)-$(PVER)-dbg-config +endif + ln -sf $(DEB_HOST_MULTIARCH)-$(PVER)dm-config $(d_dbg)/usr/bin/$(PVER)dm-config + ln -sf $(DEB_HOST_MULTIARCH)-$(PVER)dm-config.1.gz $(d_dbg)/usr/share/man/man1/$(PVER)dm-config.1.gz + + ln -sf $(DEB_HOST_MULTIARCH)-$(PVER)-dbg-config $(d_dbg)/usr/bin/$(PVER)-dbg-config + ln -sf $(DEB_HOST_MULTIARCH)-$(PVER)-dbg-config.1.gz $(d_dbg)/usr/share/man/man1/$(PVER)-dbg-config.1.gz + + : # symlinks for the "old" include / config directory names + ln -sf $(PVER)-config.1.gz $(d_dbg)/usr/share/man/man1/$(PVER)-dbg-config.1.gz + ln -sf $(PVER).1.gz $(d_dbg)/usr/share/man/man1/$(PVER)dm.1.gz + ln -sf $(PVER)-config.1.gz $(d_dbg)/usr/share/man/man1/$(PVER)dm-config.1.gz + +ifeq ($(with_udeb),yes) + : # Copy the most important files from $(p_min) into $(p_udeb). + dh_installdirs -p$(p_udeb) \ + etc/$(PVER) \ + usr/bin \ + usr/include/$(PVER)mu \ + $(scriptdir)/lib-dynload \ + $(scriptdir)/config-$(VER)m-$(DEB_HOST_MULTIARCH) + cp -p $(d_min)/usr/bin/python$(VER) $(d_udeb)/usr/bin/ + ln -sf python$(VER)mu $(d_udeb)/usr/bin/python$(VER) + ln -sf python$(VER) $(d_udeb)/usr/bin/python3 + cp -p $(foreach i,$(MIN_MODS),$(d_min)/$(scriptdir)/$(i).py) \ + $(d_udeb)/$(scriptdir)/ + cp -a $(foreach i,$(MIN_PACKAGES),$(d_min)/$(scriptdir)/$(i)) \ + $(d_udeb)/$(scriptdir)/ + cp -p $(foreach i,$(MIN_ENCODINGS),$(d_min)/$(scriptdir)/$(i)) \ + $(d_udeb)/$(scriptdir)/ + cp -p $(d_min)/$(scriptdir)/config-$(VER)m-$(DEB_HOST_MULTIARCH)/Makefile \ + $(d_udeb)/$(scriptdir)/config-$(VER)m-$(DEB_HOST_MULTIARCH)/ + cp -p $(d_min)/usr/include/$(DEB_HOST_MULTIARCH)/$(PVER)m/pyconfig.h \ + $(d_udeb)/usr/include/$(DEB_HOST_MULTIARCH)/$(PVER)m/ + cp -p $(d_min)/$(scriptdir)/site.py $(d_udeb)/$(scriptdir)/ + cp -p debian/sitecustomize.py $(d_udeb)/etc/$(PVER)/ + dh_link -p$(p_udeb) /etc/$(PVER)/sitecustomize.py \ + /$(scriptdir)/sitecustomize.py +endif + + for i in debian/*.overrides; do \ + b=$$(basename $$i .overrides); \ + install -D -m 644 $$i debian/$$b/usr/share/lintian/overrides/$$b; \ + done + + touch stamps/stamp-install + +# Build architecture-independent files here. +binary-indep: build-indep install stamps/stamp-control + dh_testdir -i + dh_testroot -i + + : # $(p_doc) package + dh_installdirs -p$(p_doc) \ + usr/share/doc/$(p_base) \ + usr/share/doc/$(p_doc) + dh_installdocs -p$(p_doc) + cp -a Doc/build/html $(d_doc)/usr/share/doc/$(p_base)/ + rm -f $(d_doc)/usr/share/doc/$(p_base)/html/_static/jquery.js + dh_link -p$(p_doc) \ + /usr/share/doc/$(p_base)/html /usr/share/doc/$(p_doc)/html \ + /usr/share/javascript/jquery/jquery.js /usr/share/doc/$(p_base)/html/_static/jquery.js \ + /usr/share/javascript/underscore/underscore.js /usr/share/doc/$(p_base)/html/_static/underscore.js + + : # devhelp docs + python debian/pyhtml2devhelp.py \ + $(d_doc)/usr/share/doc/$(p_base)/html index.html $(VER) \ + > $(d_doc)/usr/share/doc/$(p_base)/html/$(PVER).devhelp + gzip -9v $(d_doc)/usr/share/doc/$(p_base)/html/$(PVER).devhelp + dh_link -p$(p_doc) \ + /usr/share/doc/$(p_base)/html /usr/share/devhelp/books/$(PVER) + + dh_installdebconf -i $(dh_args) + dh_installexamples -i $(dh_args) + dh_installmenu -i $(dh_args) + -dh_icons -i $(dh_args) || dh_iconcache -i $(dh_args) + dh_installchangelogs -i $(dh_args) + dh_link -i $(dh_args) + dh_compress -i $(dh_args) -X.py -X.cls -X.css -X.txt -X.json -X.js -Xobjects.inv -Xgdbinit + dh_fixperms -i $(dh_args) + + : # make python scripts starting with '#!' executable + for i in `find debian -mindepth 3 -type f ! -name '*.dpatch' ! -perm 755`; do \ + if head -1 $$i | grep -q '^#!'; then \ + chmod 755 $$i; \ + echo "make executable: $$i"; \ + fi; \ + done + -find $(d_doc) -name '*.txt' -perm 755 -exec chmod 644 {} \; + + dh_installdeb -i $(dh_args) + dh_gencontrol -i $(dh_args) + dh_md5sums -i $(dh_args) + dh_builddeb -i $(dh_args) + +# Build architecture-dependent files here. +binary-arch: build-arch install + dh_testdir -a + dh_testroot -a +# dh_installdebconf -a + dh_installexamples -a + dh_installmenu -a + -dh_icons -a || dh_iconcache -a +# dh_installmime -a + dh_installchangelogs -a + for i in $(p_dev) $(p_dbg); do \ + rm -rf debian/$$i/usr/share/doc/$$i; \ + ln -s $(p_base) debian/$$i/usr/share/doc/$$i; \ + done + for i in $(p_lbase); do \ + rm -rf debian/$$i/usr/share/doc/$$i; \ + ln -s $(p_lmin) debian/$$i/usr/share/doc/$$i; \ + done + for i in $(p_ldev) $(p_ldbg) $(p_lib); do \ + rm -rf debian/$$i/usr/share/doc/$$i; \ + ln -s $(p_lbase) debian/$$i/usr/share/doc/$$i; \ + done + -find debian ! -perm -200 -print -exec chmod +w {} \; +ifneq ($(with_tk),yes) + rm -f $(d_lbase)/$(scriptdir)/lib-dynload/_tkinter*.so +endif +ifneq ($(with_gdbm),yes) + rm -f $(d_lbase)/$(scriptdir)/lib-dynload/_gdbm*.so +endif + + dh_strip -a -N$(p_dbg) -Xdebug -Xdbg --dbg-package=$(p_dbg) + cp Tools/gdb/libpython.py $(d_dbg)/usr/lib/debug/usr/bin/$(PVER)m-gdb.py + ln -sf $(PVER)m-gdb.py $(d_dbg)/usr/lib/debug/usr/bin/$(PVER)dm-gdb.py + ln -sf $(PVER)m-gdb.py $(d_dbg)/usr/lib/debug/usr/bin/$(PVER)-dbg-gdb.py + ln -sf ../bin/$(PVER)m-gdb.py \ + $(d_dbg)/usr/lib/debug/usr/lib/lib$(PVER)m.so.1.0-gdb.py + ln -sf ../bin/$(PVER)m-gdb.py \ + $(d_dbg)/usr/lib/lib$(PVER)dm.so.1.0-gdb.py + dh_link -a + dh_compress -a -X.py + dh_fixperms -a + chmod 644 $(d_lmin)/$(scriptdir)/token.py + + : # make python scripts starting with '#!' executable + for i in `find debian -mindepth 3 -type f ! -name '*.dpatch' ! -perm 755`; do \ + if head -1 $$i | grep -q '^#!'; then \ + chmod 755 $$i; \ + echo "make executable: $$i"; \ + fi; \ + done + + dh_makeshlibs -p$(p_lib) -V '$(p_lib)' + dh_makeshlibs -p$(p_ldbg) -V '$(p_ldbg)' +# don't include the following symbols, found in extensions +# which either can be built as builtin or extension. + sed -ri \ + -e '/^ (PyInit_|_add_one_to_index|asdl_)/d' \ + -e '/^ (PyExpat_XML_|PyExpat_Xml)/d' \ + -e '/^ (ffi_type_|_ctypes_)/d' \ + $(d_lib)/DEBIAN/symbols $(d_ldbg)/DEBIAN/symbols + dh_installdeb -a + dh_shlibdeps -a + dh_gencontrol -a + dh_md5sums -a + dh_builddeb -a + +# rules to patch the unpacked files in the source directory +# --------------------------------------------------------------------------- +# various rules to unpack addons and (un)apply patches. +# - patch / apply-patches +# - unpatch / reverse-patches + +patchdir = debian/patches + +glibc_version := $(shell dpkg -s locales | awk '/^Version:/ {print $$2}') +broken_utimes := $(shell dpkg --compare-versions $(glibc_version) lt 2.3.5 && echo yes || echo no) +old_sphinx := $(shell dpkg --compare-versions $$(dpkg -l python-sphinx | awk '/^ii *python-sphinx/ {print $$3}') lt 1 && echo yes || echo no) + +$(patchdir)/series: $(patchdir)/series.in + cpp -E \ + -D$(distribution) \ + $(if $(filter $(broken_utimes),yes),-DBROKEN_UTIMES) \ + $(if $(filter $(old_sphinx),yes),-DOLD_SPHINX) \ + -Darch_os_$(DEB_HOST_ARCH_OS) -Darch_$(DEB_HOST_ARCH) \ + -o - $(patchdir)/series.in \ + | egrep -v '^(#.*|$$)' > $(patchdir)/series + +patch-stamp: stamps/stamp-patch +patch: stamps/stamp-patch +stamps/stamp-patch: $(patchdir)/series + dh_testdir + QUILT_PATCHES=$(patchdir) quilt push -a || test $$? = 2 + rm -rf autom4te.cache configure + autoconf + mkdir -p stamps + echo ""; echo "Patches applied in this version:" > stamps/pxx + for i in $$(cat $(patchdir)/series); do \ + echo ""; echo "$$i:"; \ + sed -n 's/^# *DP: */ /p' $(patchdir)/$$i; \ + done >> stamps/pxx + + touch Parser/acceler.c Parser/grammar1.c Parser/listnode.c \ + Parser/node.c Parser/parser.c Parser/bitset.c Parser/metagrammar.c \ + Parser/firstsets.c Parser/grammar.c Parser/pgen.c + touch Objects/obmalloc.c Python/dynamic_annotations.c \ + Python/mysnprintf.c Python/pyctype.c Parser/tokenizer_pgen.c \ + Parser/printgrammar.c Parser/parsetok_pgen.c Parser/pgenmain.c + @sleep 1 + touch Grammar/Grammar + @sleep 1 + touch Include/graminit.h + @sleep 1 + touch Python/graminit.c + + mv stamps/pxx $@ + +reverse-patches: unpatch +unpatch: + QUILT_PATCHES=$(patchdir) quilt pop -a -R || test $$? = 2 + rm -f stamps/stamp-patch $(patchdir)/series + rm -rf configure autom4te.cache + +update-patches: $(patchdir)/series + export QUILT_PATCHES=$(patchdir); \ + export QUILT_REFRESH_ARGS="--no-timestamps --no-index -pab"; \ + export QUILT_DIFF_ARGS="--no-timestamps --no-index -pab"; \ + while quilt push; do quilt refresh; done + +binary: binary-indep binary-arch + +.PHONY: control-file configure build clean binary-indep binary-arch binary install + +# Local Variables: +# mode: makefile +# end: --- python3.3-3.3.0.orig/debian/libPVER-stdlib.overrides.in +++ python3.3-3.3.0/debian/libPVER-stdlib.overrides.in @@ -0,0 +1,15 @@ +# idlelib images +lib@PVER@-stdlib binary: image-file-in-usr-lib + +# license file referred by the standard library +lib@PVER@-stdlib binary: extra-license-file + +# template files +lib@PVER@-stdlib binary: interpreter-not-absolute usr/lib/python3.3/venv/scripts/posix/pydoc #!__VENV_PYTHON__ +lib@PVER@-stdlib binary: unusual-interpreter usr/lib/python3.3/venv/scripts/posix/pydoc #!__VENV_PYTHON__ + +# the split is the reason for that +lib@PVER@-stdlib binary: python-script-but-no-python-dep + +# lintian omission, multiarch string is encoded in the filename +lib@PVER@-stdlib binary: arch-dependent-file-not-in-arch-specific-directory --- python3.3-3.3.0.orig/debian/PVER-doc.doc-base.PVER-dist.in +++ python3.3-3.3.0/debian/PVER-doc.doc-base.PVER-dist.in @@ -0,0 +1,13 @@ +Document: @PVER@-dist +Title: Distributing Python Modules (v@VER@) +Author: Greg Ward +Abstract: This document describes the Python Distribution Utilities + (``Distutils'') from the module developer's point-of-view, describing + how to use the Distutils to make Python modules and extensions easily + available to a wider audience with very little overhead for + build/release/install mechanics. +Section: Programming/Python + +Format: HTML +Index: /usr/share/doc/@PVER@/html/distutils/index.html +Files: /usr/share/doc/@PVER@/html/distutils/*.html --- python3.3-3.3.0.orig/debian/libPVER.overrides.in +++ python3.3-3.3.0/debian/libPVER.overrides.in @@ -0,0 +1 @@ +lib@PVER@ binary: package-name-doesnt-match-sonames --- python3.3-3.3.0.orig/debian/PVER-dbg.postinst.in +++ python3.3-3.3.0/debian/PVER-dbg.postinst.in @@ -0,0 +1,24 @@ +#! /bin/sh -e + +if [ "$1" = configure ]; then + if [ -d /usr/include/@PVER@_d ] && [ ! -h /usr/include/@PVER@_d ]; then + if rmdir /usr/include/@PVER@_d 2> /dev/null; then + ln -sf @PVER@dmu /usr/include/@PVER@_d + else + echo >&2 "WARNING: non-empty directory on upgrade: /usr/include/@PVER@_d" + ls -l /usr/include/@PVER@_d + fi + fi + if [ -d /usr/lib/@PVER@/config_d ] && [ ! -h /usr/lib/@PVER@/config_d ]; then + if rmdir /usr/lib/@PVER@/config_d 2> /dev/null; then + ln -sf config-dmu /usr/lib/@PVER@/config_d + else + echo >&2 "WARNING: non-empty directory on upgrade: /usr/lib/@PVER@/config_d" + ls -l /usr/lib/@PVER@/config_d + fi + fi +fi + +#DEBHELPER# + +exit 0 --- python3.3-3.3.0.orig/debian/control.stdlib +++ python3.3-3.3.0/debian/control.stdlib @@ -0,0 +1,16 @@ +Package: @PVER@-tk +Architecture: any +Depends: @PVER@ (= ${Source-Version}), ${shlibs:Depends} +Suggests: tix +XB-Python-Version: @VER@ +Description: Tkinter - Writing Tk applications with Python (v@VER@) + A module for writing portable GUI applications with Python (v@VER@) using Tk. + Also known as Tkinter. + +Package: @PVER@-gdbm +Architecture: any +Depends: @PVER@ (= ${Source-Version}), ${shlibs:Depends} +Description: GNU dbm database support for Python (v@VER@) + GNU dbm database module for Python. Install this if you want to + create or read GNU dbm database files with Python. + --- python3.3-3.3.0.orig/debian/README.dbm +++ python3.3-3.3.0/debian/README.dbm @@ -0,0 +1,72 @@ + + Python and dbm modules on Debian + -------------------------------- + +This file documents the configuration of the dbm modules for Debian. It +gives hints at the preferred use of the dbm modules. + + +The preferred way to access dbm databases in Python is the anydbm module. +dbm databases behave like mappings (dictionaries). + +Since there exist several dbm database formats, we choose the following +layout for Python on Debian: + + * creating a new database with anydbm will create a Berkeley DB 2.X Hash + database file. This is the standard format used by libdb starting + with glibc 2.1. + + * opening an existing database with anydbm will try to guess the format + of the file (using whichdb) and then load it using one of the bsddb, + bsddb1, gdbm or dbm (only if the python-gdbm package is installed) + or dumbdbm modules. + + * The modules use the following database formats: + + - bsddb: Berkeley DB 2.X Hash (as in libc6 >=2.1 or libdb2) + - bsddb1: Berkeley DB 1.85 Hash (as in libc6 >=2.1 or libdb2) + - gdbm: GNU dbm 1.x or ndbm + - dbm: " (nearly the same as the gdbm module for us) + - dumbdbm: a hand-crafted format only used in this module + + That means that all usual formats should be readable with anydbm. + + * If you want to create a database in a format different from DB 2.X, + you can still directly use the specified module. + + * I.e. bsddb is the preferred module, and DB 2.X is the preferred format. + + * Note that the db1hash and bsddb1 modules are Debian specific. anydbm + and whichdb have been modified to support DB 2.X Hash files (see + below for details). + + + +For experts only: +---------------- + +Although bsddb employs the new DB 2.X format and uses the new Sleepycat +DB 2 library as included with glibc >= 2.1, it's still using the old +DB 1.85 API (which is still supported by DB 2). + +A more recent version 1.1 of the BSD DB module (available from +http://starship.skyport.net/robind/python/) directly uses the DB 2.X API. +It has a richer set of features. + + +On a glibc 2.1 system, bsddb is linked with -ldb, bsddb1 is linked with +-ldb1 and gdbm as well as dbm are linked with -lgdbm. + +On a glibc 2.0 system (e.g. potato for m68k or slink), bsddb will be +linked with -ldb2 while bsddb1 will be linked with -ldb (therefore +python-base here depends on libdb2). + + +db1hash and bsddb1 nearly completely identical to dbhash and bsddb. The +only difference is that bsddb is linked with the real DB 2 library, while +bsddb1 is linked with an library which provides compatibility with legacy +DB 1.85 databases. + + + July 16, 1999 + Gregor Hoffleit --- python3.3-3.3.0.orig/debian/PVER.menu.in +++ python3.3-3.3.0/debian/PVER.menu.in @@ -0,0 +1,4 @@ +?package(@PVER@):needs="text" section="Applications/Programming"\ + title="Python (v@VER@)"\ + icon="/usr/share/pixmaps/@PVER@.xpm"\ + command="/usr/bin/python@VER@" --- python3.3-3.3.0.orig/debian/PVER.prerm.in +++ python3.3-3.3.0/debian/PVER.prerm.in @@ -0,0 +1,38 @@ +#! /bin/sh -e +# +# prerm script for the Debian @PVER@-base package. +# Written 1998 by Gregor Hoffleit . +# + +remove_bytecode() +{ + pkg=$1 + max=$(LANG=C LC_ALL=C xargs --show-limits < /dev/null 2>&1 | awk '/Maximum/ {print int($NF / 4)}') + dpkg -L $pkg \ + | awk -F/ 'BEGIN {OFS="/"} /\.py$/ {$NF=sprintf("__pycache__/%s.*.py[co]", substr($NF,1,length($NF)-3)); print}' \ + | xargs --max-chars="$max" echo \ + | while read files; do rm -f $files; done + find /usr/lib/python3 /usr/lib/@PVER@ -name dist-packages -prune -o -name __pycache__ -empty -print \ + | xargs -r rm -rf +} + +case "$1" in + remove|upgrade) + remove_bytecode @PVER@ + oldlocalsite=/usr/local/lib/@PVER@/site-packages + # issue #623057 + if [ -d $oldlocalsite -a ! -h $oldlocalsite ]; then + rmdir --ignore-fail-on-non-empty $oldlocalsite 2>/dev/null || true + fi + ;; + deconfigure) + ;; + failed-upgrade) + ;; + *) + echo "prerm called with unknown argument \`$1'" >&2 + exit 1 + ;; +esac + +#DEBHELPER# --- python3.3-3.3.0.orig/debian/libPVER-minimal.overrides.in +++ python3.3-3.3.0/debian/libPVER-minimal.overrides.in @@ -0,0 +1,5 @@ +# intentional +lib@PVER@-minimal binary: python-script-but-no-python-dep + +# lintian omission, multiarch string is encoded in the filename +lib@PVER@-minimal binary: arch-dependent-file-not-in-arch-specific-directory --- python3.3-3.3.0.orig/debian/_sysconfigdata.py +++ python3.3-3.3.0/debian/_sysconfigdata.py @@ -0,0 +1,6 @@ +import sys + +if hasattr(sys, 'gettotalrefcount'): + from _sysconfigdata_dm import * +else: + from _sysconfigdata_m import * --- python3.3-3.3.0.orig/debian/pyvenv3.1 +++ python3.3-3.3.0/debian/pyvenv3.1 @@ -0,0 +1,34 @@ +.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.40.10. +.TH PYVENV-3.3 "1" "June 2012" "pyvenv-3.3 3.3" "User Commands" +.SH NAME +pyvenv-3.3 \- create virtual python environments +.SH DESCRIPTION +usage: venv [\-h] [\-\-system\-site\-packages] [\-\-symlinks] [\-\-clear] [\-\-upgrade] +.IP +ENV_DIR [ENV_DIR ...] +.PP +Creates virtual Python environments in one or more target directories. +.SS "positional arguments:" +.TP +ENV_DIR +A directory to create the environment in. +.SS "optional arguments:" +.TP +\fB\-h\fR, \fB\-\-help\fR +show this help message and exit +.TP +\fB\-\-system\-site\-packages\fR +Give the virtual environment access to the system +site\-packages dir. +.TP +\fB\-\-symlinks\fR +Attempt to symlink rather than copy. +.TP +\fB\-\-clear\fR +Delete the environment directory if it already exists. +If not specified and the directory exists, an error is +raised. +.TP +\fB\-\-upgrade\fR +Upgrade the environment directory to use this version +of Python, assuming Python has been upgraded in\-place. --- python3.3-3.3.0.orig/debian/pymindeps.py +++ python3.3-3.3.0/debian/pymindeps.py @@ -0,0 +1,175 @@ +#! /usr/bin/python + +# Matthias Klose +# Modified to only exclude module imports from a given module. + +# Copyright 2004 Toby Dickenson +# +# Permission is hereby granted, free of charge, to any person obtaining +# a copy of this software and associated documentation files (the +# "Software"), to deal in the Software without restriction, including +# without limitation the rights to use, copy, modify, merge, publish, +# distribute, sublicense, and/or sell copies of the Software, and to +# permit persons to whom the Software is furnished to do so, subject +# to the following conditions: +# +# The above copyright notice and this permission notice shall be included +# in all copies or substantial portions of the Software. +# +# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, +# EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF +# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. +# IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY +# CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, +# TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE +# SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. + +import os, sys, pprint +import modulefinder +import imp + +class mymf(modulefinder.ModuleFinder): + def __init__(self,*args,**kwargs): + self._depgraph = {} + self._types = {} + self._last_caller = None + modulefinder.ModuleFinder.__init__(self, *args, **kwargs) + + def import_hook(self, name, caller=None, fromlist=None, level=-1): + old_last_caller = self._last_caller + try: + self._last_caller = caller + return modulefinder.ModuleFinder.import_hook(self, name, caller, + fromlist, level) + finally: + self._last_caller = old_last_caller + + def import_module(self, partnam, fqname, parent): + m = modulefinder.ModuleFinder.import_module(self, + partnam, fqname, parent) + if m is not None and self._last_caller: + caller = self._last_caller.__name__ + if '.' in caller: + caller = caller[:caller.index('.')] + callee = m.__name__ + if '.' in callee: + callee = callee[:callee.index('.')] + #print "XXX last_caller", caller, "MOD", callee + #self._depgraph.setdefault(self._last_caller.__name__,{})[r.__name__] = 1 + #if caller in ('pdb', 'doctest') or callee in ('pdb', 'doctest'): + # print caller, "-->", callee + if caller != callee: + self._depgraph.setdefault(caller,{})[callee] = 1 + return m + + def find_module(self, name, path, parent=None): + if parent is not None: + # assert path is not None + fullname = parent.__name__+'.'+name + elif name == "__init__": + fullname = os.path.basename(path[0]) + else: + fullname = name + if self._last_caller: + caller = self._last_caller.__name__ + if fullname in excluded_imports.get(caller, []): + #self.msgout(3, "find_module -> Excluded", fullname) + raise ImportError(name) + + if fullname in self.excludes: + #self.msgout(3, "find_module -> Excluded", fullname) + raise ImportError(name) + + if path is None: + if name in sys.builtin_module_names: + return (None, None, ("", "", imp.C_BUILTIN)) + + path = self.path + return imp.find_module(name, path) + + def load_module(self, fqname, fp, pathname, file_info): + suffix, mode, type = file_info + m = modulefinder.ModuleFinder.load_module(self, fqname, + fp, pathname, file_info) + if m is not None: + self._types[m.__name__] = type + return m + + def load_package(self, fqname, pathname): + m = modulefinder.ModuleFinder.load_package(self, fqname,pathname) + if m is not None: + self._types[m.__name__] = imp.PKG_DIRECTORY + return m + +def reduce_depgraph(dg): + pass + +# guarded imports, which don't need to be included in python-minimal +excluded_imports = { + 'argparse': set(('gettext',)), + 'codecs': set(('encodings',)), + 'collections': set(('cPickle', 'pickle', 'doctest')), + 'copy': set(('reprlib',)), + 'functools': set(('_dummy_thread',)), + 'hashlib': set(('logging', '_hashlib')), + #'hashlib': set(('_hashlib', '_md5', '_sha', '_sha256','_sha512',)), + 'heapq': set(('doctest',)), + 'io': set(('_dummy_thread',)), + 'logging': set(('multiprocessing',)), + 'os': set(('nt', 'ntpath', 'os2', 'os2emxpath', 'mac', 'macpath', + 'riscos', 'riscospath', 'riscosenviron')), + 'optparse': set(('gettext',)), + 'pickle': set(('argparse', 'doctest', 'pprint')), + 'platform': set(('plistlib', 'tempfile')), + #'socket': set(('_ssl',)), + 'subprocess': set(('threading',)), + 'sysconfig': set(('pprint','_osx_support')), + } + +def main(argv): + # Parse command line + import getopt + try: + opts, args = getopt.getopt(sys.argv[1:], "dmp:qx:") + except getopt.error as msg: + print(msg) + return + + # Process options + debug = 1 + domods = 0 + addpath = [] + exclude = [] + for o, a in opts: + if o == '-d': + debug = debug + 1 + if o == '-m': + domods = 1 + if o == '-p': + addpath = addpath + a.split(os.pathsep) + if o == '-q': + debug = 0 + if o == '-x': + exclude.append(a) + + path = sys.path[:] + path = addpath + path + + if debug > 1: + print("version:", sys.version) + print("path:") + for item in path: + print(" ", repr(item)) + + #exclude = ['__builtin__', 'sys', 'os'] + exclude = [] + mf = mymf(path, debug, exclude) + for arg in args: + mf.run_script(arg) + + depgraph = reduce_depgraph(mf._depgraph) + + pprint.pprint({'depgraph':mf._depgraph, 'types':mf._types}) + +if __name__=='__main__': + main(sys.argv[1:]) --- python3.3-3.3.0.orig/debian/libPVER-minimal.postinst.in +++ python3.3-3.3.0/debian/libPVER-minimal.postinst.in @@ -0,0 +1,13 @@ +#! /bin/sh + +set -e + +if [ ! -f /etc/@PVER@/sitecustomize.py ]; then + cat <<-EOF + # Empty sitecustomize.py to avoid a dangling symlink +EOF +fi + +#DEBHELPER# + +exit 0 --- python3.3-3.3.0.orig/debian/changelog +++ python3.3-3.3.0/debian/changelog @@ -0,0 +1,2501 @@ +python3.3 (3.3.0-9ubuntu1) raring; urgency=low + + * Build-depend on python3:any instead of python3. + + -- Matthias Klose Fri, 25 Jan 2013 17:23:38 +0100 + +python3.3 (3.3.0-9) experimental; urgency=low + + * Update to 20130125 from the 3.3 branch. + * Update cross build patches, and allow the package to cross build. + + -- Matthias Klose Fri, 25 Jan 2013 17:06:25 +0100 + +python3.3 (3.3.0-8) experimental; urgency=low + + * Update to 20130105 from the 3.3 branch. + * python-config --help returns with an exit value 0. LP: #1093860. + * Update package description for the -dbg packages. Closes: #696616. + + -- Matthias Klose Sat, 05 Jan 2013 18:39:32 +0100 + +python3.3 (3.3.0-7) experimental; urgency=low + + * Update to 20121220 from the 3.3 branch. + * debian/patches/sys-multiarch.diff: Expose multiarch triplet value + as sys.implementation._multiarch (Barry Warsaw). Closes: #695959. + Note: Usage of sysconfig.get_config_var('MULTIARCH') is preferred. + * Set the install schema to `unix_prefix', if a virtual environment + is detected (VIRTUAL_ENV env var present). Closes: #695758. + * python3.3-dev, libpython3.3-dev: Drop the dependency on libssl-dev. + + -- Matthias Klose Fri, 21 Dec 2012 07:24:41 +0100 + +python3.3 (3.3.0-6) experimental; urgency=low + + * Don't use xattrs on kfreebsd and the Hurd. + + -- Matthias Klose Tue, 04 Dec 2012 04:36:42 +0100 + +python3.3 (3.3.0-5) experimental; urgency=low + + * Update to 20121203 from the 3.3 branch. + * Make python3.3, python3.3-{minimal,dev,dbg} Multi-Arch: allowed. + * Use a shell implementation for the python-config script. + + -- Matthias Klose Mon, 03 Dec 2012 21:52:33 +0100 + +python3.3 (3.3.0-4) experimental; urgency=low + + * Update to 20121128 from the 3.3 branch. + * Don't link extensions with the shared libpython library. + * Override pointless lintian warning `hardening-no-fortify-functions' + for binaries built without optimization. + + -- Matthias Klose Wed, 28 Nov 2012 13:47:16 +0100 + +python3.3 (3.3.0-3) experimental; urgency=low + + * Update to 20121106 from the 3.3 branch. + * Filter-out cflags for profiled builds from _sysconfigdata. + * Fix multiarch plat-linux installation. LP: #1075891. + * Install _sysconfigdata.py from the shared builds. LP: #1075903. + + -- Matthias Klose Wed, 07 Nov 2012 14:31:02 +0100 + +python3.3 (3.3.0-2) experimental; urgency=low + + * Update to 20121021 from the 3.3 branch. + * Fix the interpreter name for the python3.3-dbg-config script. + + -- Matthias Klose Sun, 21 Oct 2012 09:51:05 +0200 + +python3.3 (3.3.0-1) experimental; urgency=low + + * Python 3.3.0 release. + + -- Matthias Klose Sat, 29 Sep 2012 12:59:24 +0200 + +python3.3 (3.3.0~rc3-1) experimental; urgency=low + + * Python 3.3.0 release candidate 3. + * Don't try to write lib2to3's pickled grammar files. Closes: #687200. + * Fix python-config manpage symlink. Closes: #687201. + + -- Matthias Klose Mon, 24 Sep 2012 16:22:17 +0200 + +python3.3 (3.3.0~rc2-2ubuntu1) quantal; urgency=low + + * Encode the version in the devhelp documentation name. LP: #787039. + + -- Matthias Klose Mon, 10 Sep 2012 12:56:13 +0200 + +python3.3 (3.3.0~rc2-2) experimental; urgency=low + + * Fix typo fixing the pkgconfig file. + + -- Matthias Klose Mon, 10 Sep 2012 11:13:51 +0200 + +python3.3 (3.3.0~rc2-1) experimental; urgency=low + + * Python 3.3.0 release candidate 2. + * Add the platform include dir to pkgconfig's CFlags. + * Hint on installing the python-gdbm package on failing _gdbm import. + LP: #995616. + * libpython3.3: Fix libpython3.3.so symlink. Closes: #686377. + * Don't use `-n' anymore to start idle in the desktop/menu files. + + -- Matthias Klose Sun, 09 Sep 2012 13:38:55 +0200 + +python3.3 (3.3.0~rc1-2) experimental; urgency=low + + * distutils: Add the multiarch python path to the include directories. + Closes: #685041. + * Remove /etc/python3.3 in libpython3.3-minimal instead of python3.3-minimal. + Closes: #681979. + * Remove /etc/python/sysconfig.cfg, not available anymore in python3.3. + Closes: #685016. + * Don't ship the _gdbm and _tkinter extensions in the -dbg package. + Closes: #685261. + * Fix verbose parallel builds for the sharedmods target. + * Don't install the pickled lib2to3 grammar files. Closes: #685214. + * Build extensions with fortify flags. + * Overwrite arch-dependent-file-not-in-arch-specific-directory warnings. + + -- Matthias Klose Tue, 28 Aug 2012 19:47:58 +0200 + +python3.3 (3.3.0~rc1-1) experimental; urgency=low + + * Python 3.3.0 release candidate 1. + + -- Matthias Klose Sun, 26 Aug 2012 23:15:00 +0200 + +python3.3 (3.3.0~b2-1) experimental; urgency=low + + * Python 3.3.0 beta2 release. + * Fix removal of the _tkinter and dbm extensions for multiarch builds. + Closes: #684461. + * Use _sysconfigdata.py in distutils to initialize distutils. + Closes: #682475. + * Fix symlink for static libpython. Closes: #684608. + + -- Matthias Klose Mon, 13 Aug 2012 11:05:00 +0200 + +python3.3 (3.3.0~b1-3) experimental; urgency=low + + * Update to 20120712 from the trunk. + * Install separate _sysconfigdata.py for normal and debug builds. + * Install into multiarch locations. + * Split out multiarch packages libpython3.3-{minimal,stdlib,dev,dbg}. + + -- Matthias Klose Fri, 13 Jul 2012 00:43:42 +0200 + +python3.3 (3.3.0~b1-2) experimental; urgency=low + + * Update to 20120701 from the trunk. + + -- Matthias Klose Sun, 01 Jul 2012 11:45:12 +0200 + +python3.3 (3.3.0~b1-1) experimental; urgency=low + + * Python 3.3.0 beta1 release. + * Fix symlink for the -gdb.py file. + * debian/copyright: Add libmpdec license. + * Enable fortified build. + + -- Matthias Klose Wed, 27 Jun 2012 08:44:56 +0200 + +python3.3 (3.3.0~a4-1) experimental; urgency=low + + * Python 3.3.0 alpha4 release. + * Update to 20120620 from the trunk. + * Build _ctypes as an extension, not a builtin. + * Mark symbols defined in the _ctypes extension as optional. + * Remove references to the removed pyton3.3-documenting file. + * The wininst-* files cannot be built within Debian from the included + sources, needing a zlib mingw build, which the zlib maintainer isn't + going to provide. + * Use the underscore.js file provided by the libjs-underscore package. + * Let pydoc handle dist-packages the same as site-packages. + * Avoid runtime path for the sqlite extension. + + -- Matthias Klose Wed, 20 Jun 2012 13:09:19 +0200 + +python3.3 (3.3.0~a3-1) experimental; urgency=low + + * Python 3.3.0 alpha3 release. + * Build the dbm extension using db5.3. + * Update symbols file for a3. + + -- Matthias Klose Wed, 02 May 2012 23:28:46 +0200 + +python3.3 (3.3.0~a2-1) experimental; urgency=low + + * Python 3.3.0 alpha2 release. + * Update to 20120404 from the trunk. + * Build-depend on expat (>= 2.1). + + -- Matthias Klose Wed, 04 Apr 2012 16:31:34 +0200 + +python3.3 (3.3.0~a1-1) experimental; urgency=low + + * Python 3.3.0 alpha1 release. + * Update to 20120321 from the trunk. + * Update debian/copyright. + * Build-depend on expat (>= 2.1~). + + -- Matthias Klose Thu, 22 Mar 2012 06:14:01 +0100 + +python3.3 (3.3~20120109-1) experimental; urgency=low + + * 3.3 20120109 snapshot from the trunk. + * Merge packaging from python3.2 3.2.2-4. + + -- Matthias Klose Sun, 08 Jan 2012 09:44:33 +0100 + +python3.3 (3.3~20110523-1) experimental; urgency=low + + * Initial Python 3.3 packaging. + + -- Matthias Klose Mon, 23 May 2011 09:20:52 +0200 + +python3.2 (3.2.2-4) unstable; urgency=low + + * The static library belongs into the -dev package. + * Remove obsolete attributes in the control file. + + -- Matthias Klose Sat, 07 Jan 2012 20:46:39 +0100 + +python3.2 (3.2.2-3) unstable; urgency=low + + * Update to 20120106 from the 3.2 branch. + * Install manual pages for 2to3 and python-config. + * Fix file permission of token.py module. + * Add the ability to build an python3.x udeb, as copy of the + python3.x-minimal package (Colin Watson). + * Overwrite some lintian warnings: + - The -dbg interpreters are not unusual. + - The -gdb.py files don't need a python dependency. + - lintian can't handle a whatis entry starting with one word on the line. + * Fix test failures related to distutils debian installation layout. + * Update symbols files. + * Add build-arch/build-indep targets. + * Regenerate Setup and Makefiles after correcting Setup.local. + * profiled-build.diff: Pass PY_CFLAGS instead of CFLAGS for the profiled + build. + * Pass dpkg-buildflags to the build process, and build third party + extensions with these flags. + * Add support to build using -flto (and -g1) on some architectures. + * Disable pgo builds for some architectures (for now, keep just + amd64 armel armhf i386 powerpc ppc64). + * Build-depend on libgdbm-dev to build and run the gdbm tests. + * Build-depend on xvfb to run the tkinter tests. + + -- Matthias Klose Fri, 06 Jan 2012 20:10:13 +0100 + +python3.2 (3.2.2-2) unstable; urgency=low + + * Update platform patches (alpha, hppa, mips, sparc). + + -- Matthias Klose Fri, 02 Dec 2011 10:24:05 +0100 + +python3.2 (3.2.2-1) unstable; urgency=low + + * Python 3.2.2 release. + * Update to 20111201 from the 3.2 branch. + * Search headers in /usr/include/ncursesw for the curses/panel extensions. + * New patch, ctypes-arm, allow for ",hard-float" after libc6 in ldconfig -p + output (Loic Minier). LP: #898172. + + -- Matthias Klose Thu, 01 Dec 2011 13:19:16 +0100 + +python3.2 (3.2.2~rc1-1) unstable; urgency=low + + * Python 3.2.2 release candidate 1. + + -- Matthias Klose Sun, 14 Aug 2011 20:25:35 +0200 + +python3.2 (3.2.1-2) unstable; urgency=low + + * Update to 20110803 from the 3.2 branch. + * Revert previous change to treat Linux 3.x as Linux 2. Use the + plat-linux3 directory instead. + * Use linux-any for some build dependencies. Closes: #634310. + + -- Matthias Klose Wed, 03 Aug 2011 15:16:05 +0200 + +python3.2 (3.2.1-1) unstable; urgency=medium + + * Python 3.2.1 release. + * Update lib-argparse patch (Pino Toscano). Closes: #631635. + * Treat Linux 3.x as Linux 2. Closes: #633015. + + -- Matthias Klose Sun, 10 Jul 2011 21:46:36 +0200 + +python3.2 (3.2.1~rc2-1) unstable; urgency=low + + * Python 3.2.1 release candidate 2. + * Add profile/pstats to the python3.2 package, update debian copyright. + * Don't run the benchmark on hurd-i386. + * Disable threading tests on hurd-i386. Closes: #631634. + * Don't add the bsddb multilib path, if already in the standard lib path. + + -- Matthias Klose Mon, 04 Jul 2011 20:27:52 +0200 + +python3.2 (3.2.1~rc1-1) unstable; urgency=low + + * Python 3.2.1 release candidate 1. + * Only enable sphinx-0.x patches when building with sphinx-0.x. + + -- Matthias Klose Wed, 18 May 2011 12:15:47 +0200 + +python3.2 (3.2-4) unstable; urgency=low + + * Update to 20110504 from the 3.2 branch. + * Disable the profiled build on ia64 and m68k. + * Update symbols file for m68k (Thorsten Glaser). + + -- Matthias Klose Wed, 04 May 2011 21:32:08 +0200 + +python3.2 (3.2-3) unstable; urgency=low + + * Update to 20110427 from the 3.2 branch. + - Fix argparse import. Closes: #624277. + * Keep the ssl.PROTOCOL_SSLv2 module constant , just raise an exception + when trying to create a PySSL object. #624127. + * Don't depend on the locale and specific awk implementations in prerm. + Closes: #623466, #620836. + * Remove the old local site directory. Closes: #623057. + + -- Matthias Klose Wed, 27 Apr 2011 20:40:29 +0200 + +python3.2 (3.2-2) unstable; urgency=low + + * Update to 20110419 from the 3.2 branch. + * Re-enable profile-guided builds. + * Build without OpenSSL v2 support. Closes: #622004. + * Force linking the curses module against libncursesw. Closes: #622064. + * Re-enable running the testsuite during the build. + + -- Matthias Klose Tue, 19 Apr 2011 17:54:36 +0200 + +python3.2 (3.2-1) unstable; urgency=low + + * Python 3.2 final release. + + -- Matthias Klose Sun, 20 Feb 2011 19:22:24 +0100 + +python3.2 (3.2~rc3-1) experimental; urgency=low + + * Python 3.2 release candidate 3. + + -- Matthias Klose Mon, 14 Feb 2011 16:12:14 +0100 + +python3.2 (3.2~rc1-2) experimental; urgency=low + + * Fix upgrade of the python3.2-dev package. Closes: #610370. + + -- Matthias Klose Wed, 19 Jan 2011 02:21:19 +0100 + +python3.2 (3.2~rc1-1) experimental; urgency=low + + * Python 3.2 release candidate 1. + + -- Matthias Klose Sun, 16 Jan 2011 22:17:09 +0100 + +python3.2 (3.2~b2-1) experimental; urgency=low + + * Python 3.2 beta2 release. + * Fix FTBFS on hurd-i386 (Pino Toscano). Closes: #606152). + + -- Matthias Klose Tue, 21 Dec 2010 21:23:21 +0100 + +python3.2 (3.2~b1-1) experimental; urgency=low + + * Python 3.2 beta1 release. + * Configure with --enable-loadable-sqlite-extensions. + + -- Matthias Klose Mon, 06 Dec 2010 12:19:09 +0100 + +python3.2 (3.2~a4-2) experimental; urgency=low + + * Fix build failure on the hurd. + + -- Matthias Klose Fri, 26 Nov 2010 06:38:41 +0100 + +python3.2 (3.2~a4-1) experimental; urgency=low + + * Python 3.2 alpha4 release. + * Update to the py3k branch (20101124). + * Move the Makefile into the -min package, required by sysconfig. + Addresses: #603237. + + -- Matthias Klose Wed, 24 Nov 2010 22:20:32 +0100 + +python3.2 (3.2~a3-2) experimental; urgency=low + + * Update to the py3k branch (20101018). + - Issue #10094: Use versioned .so files on GNU/kfreeBSD and the GNU Hurd. + Closes: #600183. + + -- Matthias Klose Mon, 18 Oct 2010 19:34:39 +0200 + +python3.2 (3.2~a3-1) experimental; urgency=low + + * Python 3.2 alpha3 release. + * Make Lib/plat-gnukfreebsd[78] ready for python3. Closes: #597874. + + -- Matthias Klose Tue, 12 Oct 2010 16:13:15 +0200 + +python3.2 (3.2~a2-7) experimental; urgency=low + + * Update to the py3k branch (20100926). + + -- Matthias Klose Sun, 26 Sep 2010 14:41:18 +0200 + +python3.2 (3.2~a2-6) experimental; urgency=low + + * Update to the py3k branch (20100919). + * Update GNU/Hurd patches (Pino Toscano). Closes: #597320. + + -- Matthias Klose Sun, 19 Sep 2010 12:45:14 +0200 + +python3.2 (3.2~a2-5) experimental; urgency=low + + * Update to the py3k branch (20100916). + * Provide Lib/plat-gnukfreebsd[78] (Jakub Wilk). Addresses: #593818. + * Assume working semaphores, don't rely on running kernel for the check. + LP: #630511. + + -- Matthias Klose Thu, 16 Sep 2010 14:41:58 +0200 + +python3.2 (3.2~a2-4) experimental; urgency=low + + * Update to the py3k branch (20100911). + * Add the sysconfig module to python3.2-minimal. + * Remove dist-packages/README. + * Make xargs --show-limits in the maintainer scripts independent from + the locale. + + -- Matthias Klose Sat, 11 Sep 2010 20:59:47 +0200 + +python3.2 (3.2~a2-3) experimental; urgency=low + + * Update to the py3k branch (20100910). + * Disable profile feedback based optimization on armel. + * Add copyright information for expat, libffi and zlib. Sources + for the wininst-* files are in PC/bdist_wininst. Closes: #596276. + * Run the testsuite in parallel, when parallel= is set in DEB_BUILD_OPTIONS. + + -- Matthias Klose Fri, 10 Sep 2010 20:28:16 +0200 + +python3.2 (3.2~a2-2) experimental; urgency=low + + * Fix distutils.sysconfig.get_makefile_name for debug builds. + + -- Matthias Klose Thu, 09 Sep 2010 02:40:11 +0200 + +python3.2 (3.2~a2-1) experimental; urgency=low + + * Python 3.2 alpha2 release. + * Update to the py3k branch (20100908). + * Provide /usr/lib/python3/dist-packages as location for public python + packages. + + -- Matthias Klose Wed, 08 Sep 2010 17:36:06 +0200 + +python3.2 (3.2~a1-1) experimental; urgency=low + + * Python 3.2 alpha1 release. + - Files removed: Lib/profile.py, Lib/pstats.py, PC/icons/source.xar. + * Update to the py3k branch (20100827). + * Fix detection of ffi.h header file. Closes: #591408. + * python3.1-dev: Depend on libssl-dev. LP: #611845. + + -- Matthias Klose Fri, 27 Aug 2010 21:40:31 +0200 + +python3.2 (3.2~~20100707-0ubuntu1) maverick; urgency=low + + * Move the pkgconfig file into the -dev package. + * Update preremoval scripts for __pycache__ layout. + * Run hooks from /usr/share/python3/runtime.d/ + * Update distutils-install-layout and debug-build patches. + + -- Matthias Klose Wed, 07 Jul 2010 12:38:52 +0200 + +python3.2 (3.2~~20100706-0ubuntu1) maverick; urgency=low + + * Test build, taken from the py3k branch (20100706). + * Merge with the python3.1 packaging. + + -- Matthias Klose Tue, 06 Jul 2010 17:10:51 +0200 + +python3.2 (3.2~~20100704-0ubuntu1) maverick; urgency=low + + * Test build, taken from the py3k branch (20100704). + + -- Matthias Klose Sun, 04 Jul 2010 16:04:45 +0200 + +python3.2 (3.2~~20100421-0ubuntu1) lucid; urgency=low + + * Test build, taken from the py3k branch (20100421). + + -- Matthias Klose Wed, 21 Apr 2010 22:04:14 +0200 + +python3.1 (3.1.2+20100703-1) unstable; urgency=low + + * Update to the 3.1 release branch, 20100703. + * Convert internal dpatch system to quilt. + * Update module list for python3-minimal. + + -- Matthias Klose Sat, 03 Jul 2010 14:18:18 +0200 + +python3.1 (3.1.2-3) unstable; urgency=low + + * Update to the 3.1 release branch, 20100508. + * Fix backport of issue #8140. Closes: #578896. + + -- Matthias Klose Sat, 08 May 2010 15:37:35 +0200 + +python3.1 (3.1.2-2) unstable; urgency=low + + * Update to the 3.1 release branch, 20100421. + * Update patch for issue #8032, gdb7 hooks for debugging. + * Fix issue #8233: When run as a script, py_compile.py optionally + takes a single argument `-`. + * Don't build-depend on locales on avr32. + + -- Matthias Klose Wed, 21 Apr 2010 21:12:37 +0200 + +python3.1 (3.1.2-1) unstable; urgency=low + + * Python 3.1.2 release. + * Fix issue #4961: Inconsistent/wrong result of askyesno function in + tkMessageBox with Tcl8.5. LP: #462950. + * Don't complain when /usr/local is not writable on installation. + * Apply proposed patch for issue #8032, gdb7 hooks for debugging. + + -- Matthias Klose Sun, 21 Mar 2010 17:59:49 +0100 + +python3.1 (3.1.2~rc1-2) unstable; urgency=low + + * Update to the 3.1 release branch, 20100316. + * Backport issue #8140: Extend compileall to compile single files. + Add -i option. + + -- Matthias Klose Tue, 16 Mar 2010 02:38:45 +0100 + +python3.1 (3.1.2~rc1-1) unstable; urgency=low + + * Python 3.1.2 release candidate 1. + - Replace the Monty Python audio test file. Closes: #568676. + * Build using libdb4.8-dev. Only used for the dbm extension; the bsddb3 + extension isn't built from the core packages anymore. + + -- Matthias Klose Thu, 11 Mar 2010 17:26:17 +0100 + +python3.1 (3.1.1-3) unstable; urgency=low + + * Update to the 3.1 release branch, 20100119. + * Hurd fixes (Pino Toscano): + - hurd-broken-poll.dpatch: ported from 2.5. + - hurd-disable-nonworking-constants.dpatch: disable a few constants from + the public API whose C counterparts are not implemented, so using them + either always blocks or always fails (caused issues in the test suite). + - hurd-path_max.dpatch (hurd only): change few PATH_MAX occurrences to + MAXPATHLEN (which is defined by the python lib if not defined by the OS). + - cthreads.dpatch: Refresh. + - Exclude the profiled build for hurd. + - Disable six blocking tests from the test suite. + * Don't run the testsuite on armel and hppa until someone figures out + the blocking tests. + + -- Matthias Klose Tue, 19 Jan 2010 22:02:14 +0100 + +python3.1 (3.1.1-2) unstable; urgency=low + + * Update to the 3.1 release branch, 20100116. + * Fix bashism in makesetup shell script. Closes: #530170, #530171. + * Fix build issues on avr (Bradley Smith). Closes: #528439. + - Configure --without-ffi. + - Don't run lengthly tests. + + -- Matthias Klose Sat, 16 Jan 2010 23:28:05 +0100 + +python3.1 (3.1.1-1) experimental; urgency=low + + * Python 3.1.1 final release. + * Update to the 3.1 release branch, 20091011. + * Remove /usr/local/lib/python3.1 on package removal, if empty. + * Build _hashlib as a builtin. LP: #445530. + * python3.1-doc: Don't compress the sphinx inventory. + * python3.1-doc: Fix jquery.js symlink. LP: #447370. + * Run the benchmark with -C 2 -n 5 -w 4 on all architectures. + * python3.1-dbg: Don't create debug subdirectory in /usr/local. No + separate debug directory needed anymore. + * Fix title of devhelp document. LP: #423551. + + -- Matthias Klose Sun, 11 Oct 2009 22:01:57 +0200 + +python3.1 (3.1-1) experimental; urgency=low + + * Python 3.1 final release. + * Update to the 3.1 release branch, 20090723. + * Add explicit build dependency on tk8.5-dev. + + -- Matthias Klose Thu, 23 Jul 2009 15:20:35 +0200 + +python3.1 (3.1-0ubuntu2) karmic; urgency=low + + * Disable profile feedback based optimization on amd64 (GCC + PR gcov-profile/38292). + + -- Matthias Klose Fri, 24 Jul 2009 16:27:22 +0200 + +python3.1 (3.1-0ubuntu1) karmic; urgency=low + + * Python 3.1 final release. + * Update to the 3.1 release branch, 20090723. + * Add explicit build dependency on tk8.5-dev. + + -- Matthias Klose Thu, 23 Jul 2009 18:52:17 +0200 + +python3.1 (3.1~rc2+20090622-1) experimental; urgency=low + + [Matthias Klose] + * Python 3.1 rc2 release. Closes: #529320. + * Update to the trunk, 20090622, remove patches integrated upstream. + * Configure with --with-fpectl --with-dbmliborder=bdb --with-wide-unicode. + NOTE: The --with-wide-unicode configuration will break most extensions + built with 3.1~a1, but is consistent with python2.x configurations. + * Add symbols files for libpython3.1 and python3.1-dbg, don't include symbols + from builtins, which can either be built as builtins or extensions. + * Keep an empty lib-dynload in python3.1-minimal to avoid a warning on + startup. + * python3.1-doc: Depend on libjs-jquery, use jquery.js from this package. + Closes: #523485. + * Do not add /usr/lib/pythonXY.zip on sys.path. + * Add symbols files for libpython3.1 and python3.1-dbg, don't include symbols + from builtins, which can either be built as builtins or extensions. + * Keep an empty lib-dynload in python3.1-minimal to avoid a warning on + startup. + * Fix some lintian warnings. + * Use the information in /etc/lsb-release for platform.dist(). LP: #196526. + * Move the bdist_wininst files into the -dev package (only needed to build + windows installers). + * Document changes to the site directory name in the installation manual. + * Don't build a profiled binary. Closes: #521811. + + * Address issues when working with PYTHONUSERBASE and non standard prefix + (pointed out by Larry Hastings): + - distutils.sysconfig.get_python_lib(): Only return ".../dist-packages" if + prefix is the default prefix and if PYTHONUSERBASE is not set in the + environment. + - site.addusersitepackages(): Add USER_BASE/.../dist-packages to sys.path. + * Always use the `unix_prefix' scheme for setup.py install in a virtualenv + setup. LP: #339904. + * Don't make the setup.py install options --install-layout=deb and --prefix + conflict with each other. + * distutils: Always install into `/usr/local/lib/python3.1/dist-packages' + if an option `--prefix=/usr/local' is present (except for virtualenv + and PYTHONUSERBASE installations). LP: #362570. + * Always use `site-packages' as site directory name in virtualenv. + + [Marc Deslauriers] + * debian/pyhtml2devhelp.py: update for sphinx generated documentation. + * debian/rules: re-enable documentation files for devhelp. + + -- Matthias Klose Mon, 22 Jun 2009 16:18:39 +0200 + +python3.1 (3.1~a1+20090322-1) experimental; urgency=low + + * Python 3.1 alpha1 release. + * Update to the trunk, 20090322. + * Update installation schemes: LP: #338395. + - When the --prefix option is used for setup.py install, Use the + `unix_prefix' scheme. + - Use the `deb_system' scheme if --install-layout=deb is specified. + - Use the the `unix_local' scheme if neither --install-layout=deb + nor --prefix is specified. + * Use the information in /etc/lsb-release for platform.dist(). LP: #196526. + * pydoc: Fix detection of local documentation files. + * Build a shared library configured --with-pydebug. LP: #322580. + * Fix some lintian warnings. + + -- Matthias Klose Mon, 23 Mar 2009 00:01:27 +0100 + +python3.1 (3.1~~20090226-1) experimental; urgency=low + + * Python-3.1 snapshot (20090226), upload to experimental. + + -- Matthias Klose Thu, 26 Feb 2009 16:18:41 +0100 + +python3.1 (3.1~~20090222-0ubuntu1) jaunty; urgency=low + + * Python-3.1 snapshot (20090222). + * Build the _dbm extension using the Berkeley DB backend. + + -- Matthias Klose Sun, 22 Feb 2009 12:58:58 +0100 + +python3.0 (3.0.1-0ubuntu4) jaunty; urgency=low + + * Don't build-depend on locales on sparc. Currently not installable. + + -- Matthias Klose Sun, 22 Feb 2009 12:48:38 +0100 + +python3.0 (3.0.1-0ubuntu3) jaunty; urgency=low + + * Update to 20090222 from the release30-maint branch. + + -- Matthias Klose Sun, 22 Feb 2009 11:09:58 +0100 + +python3.0 (3.0.1-0ubuntu2) jaunty; urgency=low + + * Allow docs to be built with Sphinx 0.5.x. + + -- Matthias Klose Tue, 17 Feb 2009 12:58:02 +0100 + +python3.0 (3.0.1-0ubuntu1) jaunty; urgency=low + + * New upstream version. + + -- Matthias Klose Mon, 16 Feb 2009 17:18:23 +0100 + +python3.0 (3.0-0ubuntu2) jaunty; urgency=low + + * Update to 20090213 from the release30-maint branch. + + -- Matthias Klose Fri, 13 Feb 2009 15:49:12 +0100 + +python3.0 (3.0-0ubuntu1) jaunty; urgency=low + + * Final Python-3.0 release. + + -- Matthias Klose Thu, 04 Dec 2008 09:00:09 +0100 + +python3.0 (3.0~rc3-0ubuntu4) jaunty; urgency=low + + * Update to 20081127 from the py3k branch. + * Ensure that all extensions from the -minimal package are statically + linked into the interpreter. LP: #301597. + * Include expat, _elementtree, datetime in -minimal to link + these extensions statically. + + -- Matthias Klose Thu, 27 Nov 2008 08:49:02 +0100 + +python3.0 (3.0~rc3-0ubuntu3) jaunty; urgency=low + + * Ignore errors when running the profile task. + + -- Matthias Klose Sun, 23 Nov 2008 15:50:17 +0100 + +python3.0 (3.0~rc3-0ubuntu2) jaunty; urgency=low + + * Don't run test_ioctl on the buildd, before the buildd chroot is fixed: + Unable to open /dev/tty. + + -- Matthias Klose Sun, 23 Nov 2008 15:28:02 +0100 + +python3.0 (3.0~rc3-0ubuntu1) jaunty; urgency=low + + * Update to the python-3.0 release candidate 3. + + -- Matthias Klose Sun, 23 Nov 2008 13:14:20 +0100 + +python3.0 (3.0~rc1+20081027-0ubuntu1) intrepid; urgency=low + + * Update to 20081027 from the py3k branch. LP: #279227. + * Fix typos and section names in doc-base files. LP: #273344. + * Build a new package libpython3.0. + * For locally installed packages, create a directory + /usr/local/lib/python3.0/dist-packages. This is the default for + installations done with distutils and setuptools. Third party stuff + packaged within the distribution goes to /usr/lib/python3.0/dist-packages. + There is no /usr/lib/python3.0/site-packages in the file system and + on sys.path. No package within the distribution must not install + anything in this location. + * distutils: Add an option --install-layout=deb, which + - installs into $prefix/dist-packages instead of $prefix/site-packages. + - doesn't encode the python version into the egg name. + + -- Matthias Klose Mon, 27 Oct 2008 23:38:42 +0100 + +python3.0 (3.0~b3+20080915-0ubuntu1) intrepid; urgency=low + + * Update to 20080915 from the py3k branch. + * Build gdbm + + -- Matthias Klose Mon, 15 Sep 2008 23:56:44 +0200 + +python3.0 (3.0~b3-0ubuntu1~ppa1) intrepid; urgency=low + + * Python 3.0 beta3 release. + + -- Matthias Klose Sun, 24 Aug 2008 03:49:26 +0200 + +python3.0 (3.0~b2-0ubuntu1~ppa1) intrepid; urgency=low + + * Python 3.0 beta2 release. + + -- Matthias Klose Thu, 07 Aug 2008 14:57:02 +0000 + +python3.0 (3.0~b1-0ubuntu1~ppa1) intrepid; urgency=low + + * Python 3.0 beta1 release. + + -- Matthias Klose Tue, 15 Jul 2008 16:10:52 +0200 + +python3.0 (3.0~a5+0530-0ubuntu1) intrepid; urgency=low + + * Update to snapshot taken from the py3k branch. + + -- Matthias Klose Thu, 29 May 2008 15:50:55 +0200 + +python3.0 (3.0~a1-0ubuntu2) gutsy; urgency=low + + * Disable running the benchmark. + + -- Matthias Klose Fri, 31 Aug 2007 23:22:34 +0000 + +python3.0 (3.0~a1-0ubuntu1) gutsy; urgency=low + + * First Python-3.0 alpha release. + + -- Matthias Klose Fri, 31 Aug 2007 21:26:21 +0200 + +python2.6 (2.6~alpha~pre1-~0ubuntu1~ppa1) gutsy; urgency=low + + * Snapshot build, an "how to use tilde in version numbers" upload. + * SVN 20070831. + + -- Matthias Klose Fri, 31 Aug 2007 15:56:09 +0200 + +python2.5 (2.5.2-4) unstable; urgency=low + + * Update to 20080427, taken from the 2.5 release branch. + - Fix issues #2670, #2682. + * Disable running pybench on the hppa buildd (ftbfs). + * Allow setting BASECFLAGS, OPT and EXTRA_LDFLAGS (like, CC, CXX, CPP, + CFLAGS, CPPFLAGS, CCSHARED, LDSHARED) from the environment. + * Support parallel= in DEB_BUILD_OPTIONS (see #209008). + + -- Matthias Klose Sun, 27 Apr 2008 10:40:51 +0200 + +python2.5 (2.5.2-3) unstable; urgency=medium + + * Update to 20080416, taken from the 2.5 release branch. + - Fix CVE-2008-1721, integer signedness error in the zlib extension module. + - Fix urllib2 file descriptor happens byte-at-a-time, reverting + a fix for excessively large memory allocations when calling .read() + on a socket object wrapped with makefile(). + * Disable some regression tests on some architectures: + - arm: test_compiler, test_ctypes. + - armel: test_compiler. + - hppa: test_fork1, test_wait3. + - m68k: test_bsddb3, test_compiler. + * Build-depend on libffi-dev instead of libffi4-dev. + * Fix CVE-2008-1679, integer overflows in the imageop module. + + -- Matthias Klose Wed, 16 Apr 2008 23:37:46 +0200 + +python2.5 (2.5.2-2) unstable; urgency=low + + * Use site.addsitedir() to add directories in /usr/local to sys.path. + Addresses: #469157, #469818. + + -- Matthias Klose Sat, 08 Mar 2008 16:11:23 +0100 + +python2.5 (2.5.2-1) unstable; urgency=low + + * Python 2.5.2 release. + * Merge from Ubuntu: + - Move site customization into sitecustomize.py, don't make site.py + a config file. Addresses: #309719, #413172, #457361. + - Move site.py to python2.4-minimal, remove `addbuilddir' from site.py, + which is unnecessary for installed builds. + - python2.5-dev: Recommend libc-dev instead of suggesting it. LP: #164909. + - Fix issue 961805, Tk Text.edit_modified() fails. LP: #84720. + + -- Matthias Klose Thu, 28 Feb 2008 23:18:52 +0100 + +python2.5 (2.5.1-7) unstable; urgency=low + + * Update to 20080209, taken from the 2.5 release branch. + * Build the _bsddb extension with db-4.5 again; 4.6 is seriously + broken when used with the _bsddb extension. + * Do not run pybench on arm and armel. + * python2.5: Provide python2.5-wsgiref. + * Fix a pseudo RC report with duplicated attributes in the control + file. Closes: #464307. + + -- Matthias Klose Sun, 10 Feb 2008 00:22:57 +0100 + +python2.5 (2.5.1-6) unstable; urgency=low + + * Update to 20080102, taken from the 2.5 release branch. + - Only define _BSD_SOURCE on OpenBSD systems. Closes: #455400. + * Fix handling of packages in linecache.py (Kevin Goodsell). LP: #70902. + * Bump debhelper to v5. + * Register binfmt for .py[co] files. + * Use absolute paths when byte-compiling files. Addresses: #453346. + Closes: #413566, LP: #177722. + * CVE-2007-4965, http://bugs.python.org/issue1179: + Multiple integer overflows in the imageop module in Python 2.5.1 and + earlier allow context-dependent attackers to cause a denial of service + (application crash) and possibly obtain sensitive information (memory + contents) via crafted arguments to (1) the tovideo method, and unspecified + other vectors related to (2) imageop.c, (3) rbgimgmodule.c, and other + files, which trigger heap-based buffer overflows. + Patch prepared by Stephan Herrmann. Closes: #443333, LP: #163845. + * Register info docs when doing source only uploads. LP: #174786. + * Remove deprecated value from categories in desktop file. LP: #172874. + * python2.5-dbg: Don't include the gdbm and _tkinter extensions, now provided + in separate packages. + * Provide a symlink changelog -> NEWS. Closes: #439271. + * Fix build failure on hurd, working around poll() on systems on which it + returns an error on invalid FDs. Closes: #438914. + * Configure --with-system-ffi on all architectures. Closes: #448520. + * Fix version numbers in copyright and README files (Dan O'Huiginn). + Closes: #446682. + * Move some documents from python2.5 to python2.5-dev. + + -- Matthias Klose Wed, 02 Jan 2008 22:22:19 +0100 + +python2.5 (2.5.1-5) unstable; urgency=low + + * Build the _bsddb extension with db-4.6. + + -- Matthias Klose Fri, 17 Aug 2007 00:39:35 +0200 + +python2.5 (2.5.1-4) unstable; urgency=low + + * Update to 20070813, taken from the 2.5 release branch. + * Include plat-mac/plistlib.py (plat-mac is not in sys.path by default. + Closes: #435826. + * Use emacs22 to build the documentation in info format. Closes: #434969. + * Build-depend on db-dev (>= 4.6). Closes: #434965. + + -- Matthias Klose Mon, 13 Aug 2007 22:22:44 +0200 + +python2.5 (2.5.1-3) unstable; urgency=high + + * Support mixed-endian IEEE floating point, as found in the ARM old-ABI + (Aurelien Jarno). Closes: #434905. + + -- Matthias Klose Fri, 27 Jul 2007 20:01:35 +0200 + +python2.5 (2.5.1-2) unstable; urgency=low + + * Update to 20070717, taken from the 2.5 release branch. + * Fix reference count for sys.pydebug variable. Addresses: #431393. + * Build depend on libbluetooth-dev instead of libbluetooth2-dev. + + -- Matthias Klose Tue, 17 Jul 2007 14:09:47 +0200 + +python2.5 (2.5.1-1) unstable; urgency=low + + * Python-2.5.1 release. + * Build-depend on gcc-4.1 (>= 4.1.2-4) on alpha, powerpc, s390, sparc. + * Merge from Ubuntu: + - Add debian/patches/subprocess-eintr-safety.dpatch (LP: #87292): + - Create and use wrappers around read(), write(), and os.waitpid() in the + subprocess module which retry the operation on an EINTR (which happens + if e. g. an alarm was raised while the system call was in progress). + It is incredibly hard and inconvenient to sensibly handle this in + applications, so let's fix this at the right level. + - Patch based on original proposal of Peter <85>strand + in http://python.org/sf/1068268. + - Add two test cases. + - Change the interpreter to build and install python extensions + built with the python-dbg interpreter with a different name into + the same path (by appending `_d' to the extension name). The debug build + of the interpreter tries to first load a foo_d.so or foomodule_d.so + extension, then tries again with the normal name. + - When trying to import the profile and pstats modules, don't + exit, add a hint to the exception pointing to the python-profiler + package, don't exit. + - Keep the module version in the .egg-info name, only remove the + python version. + - python2.5-dbg: Install Misc/SpecialBuilds.txt, document the + debug changes in README.debug. + * Update to 20070425, taken from the 2.5 release branch. + + -- Matthias Klose Wed, 25 Apr 2007 22:12:50 +0200 + +python2.5 (2.5-6) unstable; urgency=medium + + * webbrowser.py: Recognize other browsers: www-browser, x-www-browser, + iceweasel, iceape. + * Move pyconfig.h from the python2.5-dev into the python2.5 package; + required by builds for pure python modules without having python2.5-dev + installed (matching the functionality in python2.4). + * Move the unicodedata module into python2.5-minimal; allows byte compilation + of UTF8 encoded files. + * Do not install anymore outdated debhelper sample scripts. + * Install Misc/SpecialBuilds.txt as python2.5-dbg document. + + -- Matthias Klose Wed, 21 Feb 2007 01:17:12 +0100 + +python2.5 (2.5-5) unstable; urgency=high + + * Do not run the python benchmark on m68k. Timer problems. + Fixes FTBFS on m68k. + * Update to 20061209, taken from the 2.5 release branch. + - Fixes building the library reference in info format. + + -- Matthias Klose Sat, 9 Dec 2006 13:40:48 +0100 + +python2.5 (2.5-4) unstable; urgency=medium + + * Update to 20061203, taken from the 2.5 release branch. + - Fixes build failures on knetfreebsd and the hurd. Closes: #397000. + * Clarify README about distutils. Closes: #396394. + * Move python2.5-config to python2.5-dev. Closes: #401451. + * Cleanup build-conflicts. Addresses: #394512. + + -- Matthias Klose Sun, 3 Dec 2006 18:22:49 +0100 + +python2.5 (2.5-3.1) unstable; urgency=low + + * Non-maintainer upload. + * python2.5-minimal depends on python-minimal (>= 2.4.4-1) because it's the + first version which lists python2.5 as an unsupported runtime (ie a + runtime that is available but for which modules are not auto-compiled). + And being listed there is required for python-central to accept the + installation of python2.5-minimal. Closes: #397006 + + -- Raphael Hertzog Wed, 22 Nov 2006 15:41:06 +0100 + +python2.5 (2.5-3) unstable; urgency=medium + + * Update to 20061029 (2.4.4 was released on 20061019), taken from + the 2.5 release branch. We do not want to have regressions in + 2.5 compared to the 2.4.4 release. + * Don't run pybench on m68k, fails in the calibration loop. Closes: #391030. + * Run the installation/removal hooks. Closes: #383292, #391036. + + -- Matthias Klose Sun, 29 Oct 2006 11:35:19 +0100 + +python2.5 (2.5-2) unstable; urgency=medium + + * Update to 20061003, taken from the 2.5 release branch. + * On arm and m68k, don't run the pybench in debug mode. + * Fix building the source within exec_prefix (Alexander Wirt). + Closes: #385336. + + -- Matthias Klose Tue, 3 Oct 2006 10:08:36 +0200 + +python2.5 (2.5-1) unstable; urgency=low + + * Python 2.5 release. + * Update to 20060926, taken from the 2.5 release branch. + * Run the Python benchmark during the build, compare the results + of the static and shared builds. + * Fix invalid html in python2.5.devhelp.gz. + * Add a python2.5 console entry to the menu (hidden by default). + * python2.5: Suggest python-profiler. + + -- Matthias Klose Tue, 26 Sep 2006 02:36:11 +0200 + +python2.5 (2.5~c1-1) unstable; urgency=low + + * Python 2.5 release candidate 1. + * Update to trunk 20060818. + + -- Matthias Klose Sat, 19 Aug 2006 19:21:05 +0200 + +python2.5 (2.5~b3-1) unstable; urgency=low + + * Build the _ctypes module for m68k-linux. + + -- Matthias Klose Fri, 11 Aug 2006 18:19:19 +0000 + +python2.5 (2.5~b3-0ubuntu1) edgy; urgency=low + + * Python 2.5 beta3 release. + * Update to trunk 20060811. + * Rebuild the documentation. + * Fix value of sys.exec_prefix in the debug build. + * Do not build the library reference in info format; fails to build. + * Link the interpreter against the shared runtime library. With + gcc-4.1 the difference in the pystones benchmark dropped from about + 12% to about 6%. + * Install the statically linked version of the interpreter as + python2.5-static for now. + * Link the shared libpython with -O1. + + -- Matthias Klose Thu, 10 Aug 2006 14:04:48 +0000 + +python2.5 (2.4.3+2.5b2-3) unstable; urgency=low + + * Disable the testsuite on s390; don't care about "minimally configured" + buildd's. + + -- Matthias Klose Sun, 23 Jul 2006 11:45:03 +0200 + +python2.5 (2.4.3+2.5b2-2) unstable; urgency=low + + * Update to trunk 20060722. + * Merge idle-lib from idle-python2.5 into python2.5. + * Merge lib-tk from python-tk into python2.5. + * Tkinter.py: Suggest installation of python-tk package on failed + import of the _tkinter extension. + * Don't run the testsuite for the debug build on alpha. + * Don't run the test_compiler test on m68k. Just takes too long. + * Disable building ctypes on m68k (requires support for closures). + + -- Matthias Klose Sat, 22 Jul 2006 22:26:42 +0200 + +python2.5 (2.4.3+2.5b2-1) unstable; urgency=low + + * Python 2.5 beta2 release. + * Update to trunk 20060716. + * When built on a buildd, do not run the following test which try to + access the network: test_codecmaps_cn, test_codecmaps_hk, test_codecmaps_jp, + test_codecmaps_kr, test_codecmaps_tw, test_normalization. + * When built on a buildd, do not run tests requiring missing write permissions: + test_ossaudiodev. + + -- Matthias Klose Sun, 16 Jul 2006 02:53:50 +0000 + +python2.5 (2.4.3+2.5b2-0ubuntu1) edgy; urgency=low + + * Python 2.5 beta2 release. + + -- Matthias Klose Thu, 13 Jul 2006 17:16:52 +0000 + +python2.5 (2.4.3+2.5b1-1ubuntu2) edgy; urgency=low + + * Fix python-dev dependencies. + * Update to trunk 20060709. + + -- Matthias Klose Sun, 9 Jul 2006 18:50:32 +0200 + +python2.5 (2.4.3+2.5b1-1ubuntu1) edgy; urgency=low + + * Python 2.5 beta1 release. + * Update to trunk 20060623. + * Merge changes from the python2.4 packages. + * python2.5-minimal: Add _struct. + + -- Matthias Klose Fri, 23 Jun 2006 16:04:46 +0200 + +python2.5 (2.4.3+2.5a1-1) experimental; urgency=low + + * Update to trunk 20060409. + * Run testsuite for debug build as well. + * Build-depend on gcc-4.1. + + -- Matthias Klose Sun, 9 Apr 2006 22:27:05 +0200 + +python2.5 (2.4.3+2.5a1-0ubuntu1) dapper; urgency=low + + * Python 2.5 alpha1 release. + * Drop integrated patches. + * Add build dependencies on libsqlite3-dev and libffi4-dev. + * Add (build-)dependency on mime-support, libgpmg1 (test suite). + * Build using the system FFI. + * python2.5 provides python2.5-ctypes and python2.5-pysqlite2, + python2.5-elementtree. + * Move hashlib.py to python-minimal. + * Lib/hotshot/pstats.py: Error out on missing profile/pstats modules. + + -- Matthias Klose Wed, 5 Apr 2006 14:56:15 +0200 + +python2.4 (2.4.3-8ubuntu1) edgy; urgency=low + + * Resynchronize with Debian unstable. Remaining changes: + - Apply langpack-gettext patch. + - diff.gz contains pregenerated html and info docs. + - Build the -doc package from this source. + + -- Matthias Klose Thu, 22 Jun 2006 18:39:57 +0200 + +python2.4 (2.4.3-8) unstable; urgency=low + + * Remove python2.4's dependency on python-central. On installation of + the runtime, call hooks /usr/share/python/runtime.d/*.rtinstall. + On removal, call hooks /usr/share/python/runtime.d/*.rtremove. + Addresses: #372658. + * Call the rtinstall hooks only, if it's a new installation, or the first + installation using the hooks. Adresses: #373677. + + -- Matthias Klose Sun, 18 Jun 2006 00:56:13 +0200 + +python2.4 (2.4.3-7) unstable; urgency=medium + + * Reupload, depend on python-central (>= 0.4.15). + * Add build-conflict on python-xml. + + -- Matthias Klose Wed, 14 Jun 2006 18:56:57 +0200 + +python2.4 (2.4.3-6) medium; urgency=low + + * idle-python2.4: Remove the old postinst and prerm scripts. + * Name the runtime correctly in python2.4-minimal's installation + scripts. + + -- Matthias Klose Mon, 12 Jun 2006 17:39:56 +0000 + +python2.4 (2.4.3-5) unstable; urgency=low + + * python2.4-prerm: Handle the case, when python-central is not installed. + * idle-python2.4: Depend on python-tk instead of python2.4-tk. + + -- Matthias Klose Fri, 9 Jun 2006 05:17:17 +0200 + +python2.4 (2.4.3-4) unstable; urgency=low + + * SVN update up to 2006-06-07 + * Use python-central. + * Don't build the -tk and -gdbm packages from this source; now built + from the python-stdlib-extensions source. + * Remove leftover build dependency on libgmp3-dev. + * Do not build-depend on libbluetooth1-dev and libgpmg1-dev on + hurd-i386, kfreebsd-i386, kfreebsd-amd64. Closes: #365830. + * Do not run the test_tcl test; hangs for unknown reasons on at least + the following buildds: vivaldi(m68k), goedel (alpha), mayer (mipsel). + And no virtual package to file bug reports for the buildds ... + Closes: #364419. + * Move the Makefile from python2.4-dev to python2.4. Closes: #366473. + * Fix typo in pdb(1). Closes: #365772. + * New autoconf likes the mandir in /usr/share instead of /usr; work + with both locations. Closes: #367618. + + -- Matthias Klose Wed, 7 Jun 2006 21:37:20 +0200 + +python2.4 (2.4.3-3) unstable; urgency=low + + * SVN update up to 2006-04-21 + * Update locale aliases from /usr/share/X11/locale/locale.alias. + * Start idle with option -n from the desktop menu, so that the program + can be started in parallel. + * Testsuite related changes only: + - Add build dependencies mime-support, libgpmg1 (needed by test cases). + - Run the testsuite with bsddb, audio and curses resources enabled. + - Re-run the failed tests in verbose mode. + - Run the test suite for the debug build as well. + - Build depend on netbase, needed by test_socketmodule. + - Build depend on libgpmg1, needed by test_curses. + - On the buildds do not run the tests needing the network resource. + * Update python logo. + * Check for the availability of the profile and pstats modules when + importing hotshot.pstats. Closes: #334067. + * Don't build the -doc package from the python2.4 source. + * Set OPT in the installed Makefile to -O2. + + -- Matthias Klose Fri, 21 Apr 2006 19:58:43 +0200 + +python2.4 (2.4.3-2) unstable; urgency=low + + * Add (build-)dependency on mime-support. + + -- Matthias Klose Tue, 4 Apr 2006 22:21:41 +0200 + +python2.4 (2.4.3-1) unstable; urgency=low + + * Python 2.4.3 release. + + -- Matthias Klose Thu, 30 Mar 2006 23:42:37 +0200 + +python2.4 (2.4.3-0ubuntu1) dapper; urgency=low + + * Python 2.4.3 release. + - Fixed a bug that the gb18030 codec raises RuntimeError on encoding + surrogate pair area on UCS4 build. Ubuntu: #29289. + + -- Matthias Klose Thu, 30 Mar 2006 10:57:32 +0200 + +python2.4 (2.4.2+2.4.3c1-0ubuntu1) dapper; urgency=low + + * SVN update up to 2006-03-25 (2.4.3 candidate 1). + - Regenerate the documentation. + + -- Matthias Klose Mon, 27 Mar 2006 12:03:05 +0000 + +python2.4 (2.4.2-1ubuntu3) dapper; urgency=low + + * SVN update up to 2006-03-04 + - Regenerate the documentation. + - map.mmap(-1, size, ...) can return anonymous memory again on Unix. + Ubuntu #26201. + * Build-depend on libncursesw5-dev, ncursesw5 is preferred for linking. + Provides UTF-8 compliant curses bindings. + * Fix difflib where certain patterns of differences were making difflib + touch the recursion limit. + + -- Matthias Klose Sat, 4 Mar 2006 21:38:24 +0000 + +python2.4 (2.4.2-1ubuntu2) dapper; urgency=low + + * SVN update up to 2006-01-17 + - pwd is now a builtin module, remove it from python-minimal. + - Regenerate the documentation. + * python2.4-tk: Suggest tix instead of tix8.1. + * Move config/Makefile from the -dev package into the runtime package + to be able to use the bdist_wininst distutils command. Closes: #348335. + + -- Matthias Klose Tue, 17 Jan 2006 11:02:24 +0000 + +python2.4 (2.4.2-1ubuntu1) dapper; urgency=low + + * Temporarily remove build dependency on lsb-release. + + -- Matthias Klose Sun, 20 Nov 2005 17:40:18 +0100 + +python2.4 (2.4.2-1build1) dapper; urgency=low + + * Rebuild (openssl-0.9.8). + + -- Matthias Klose Sun, 20 Nov 2005 15:27:24 +0000 + +python2.4 (2.4.2-1) unstable; urgency=low + + * Python 2.4.2 release. + + -- Matthias Klose Thu, 29 Sep 2005 01:49:28 +0200 + +python2.4 (2.4.1+2.4.2rc1-1) unstable; urgency=low + + * Python 2.4.2 release candidate 1. + * Fix "Fatal Python error" from cStringIO's writelines. + Patch by Andrew Bennetts. + + -- Matthias Klose Thu, 22 Sep 2005 10:33:22 +0200 + +python2.4 (2.4.1-5) unstable; urgency=low + + * CVS update up to 2005-09-14 + - Regenerate the html and info docs. + * Add some more locale aliases. + * Fix substitution pf python version in README.python2.4-minimal. + Closes: #327487. + * On m68k, build using -O2 (closes: #326903). + * On Debian, don't configure --with-fpectl, which stopped working with + glibc-2.3.5. + + -- Matthias Klose Wed, 14 Sep 2005 17:32:56 +0200 + +python2.4 (2.4.1-4) unstable; urgency=low + + * CVS update up to 2005-09-04 + - teTeX 3.0 related fixes (closes: #322407). + - Regenerate the html and info docs. + * Add entry for IDLE in the Gnome menus. + * Don't build-depend on libbluetooth-dev on the Hurd (closes: #307037). + * Reenable the cthreads patch for the Hurd (closes: #307052). + + -- Matthias Klose Sun, 4 Sep 2005 18:31:42 +0200 + +python2.4 (2.4.1-3) unstable; urgency=low + + * Synchronise with Ubuntu: + - Build a python2.4-minimal package. + + -- Matthias Klose Tue, 12 Jul 2005 00:23:10 +0000 + +python2.4 (2.4.1-2ubuntu3) breezy; urgency=low + + * CVS update up to 2005-07-07 + * Regenerate the documentation. + + -- Matthias Klose Thu, 7 Jul 2005 09:21:28 +0200 + +python2.4 (2.4.1-2ubuntu2) breezy; urgency=low + + * CVS update up to 2005-06-15 + * Regenerate the documentation. + * Synchronize with Debian. Ubuntu 10485. + * idle-python2.4 enhances python2.4. Ubuntu 11562. + * README.Debian: Fix reference to the doc directory (closes: #311677). + + -- Matthias Klose Wed, 15 Jun 2005 08:56:57 +0200 + +python2.4 (2.4.1-2ubuntu1) breezy; urgency=low + + * Update build dependencies: + db4.2-dev -> db4.3-dev, + libreadline4-dev -> libreadline5-dev. + * python2.4-dev: Add missing templates to generate HTML docs. Ubuntu 11531. + + -- Matthias Klose Sun, 29 May 2005 00:01:05 +0200 + +python2.4 (2.4.1-2) unstable; urgency=low + + * Add the debug symbols for the python2.4, python2.4-gdbm + and python2.4-tk packages to the python2.4-dbg package. + * Add gdbinit example to doc directory. + + -- Matthias Klose Thu, 5 May 2005 11:12:32 +0200 + +python2.4 (2.4.1-1ubuntu2) breezy; urgency=low + + * Add the debug symbols for the python2.4, python2.4-minimal, python2.4-gdbm + and python2.4-tk packages to the python2.4-dbg package. Ubuntu 10261, + * Add gdbinit example to doc directory. + * For os.utime, use utimes(2), correctly working with glibc-2.3.5. + Ubuntu 10294. + + -- Matthias Klose Thu, 5 May 2005 09:06:07 +0200 + +python2.4 (2.4.1-1ubuntu1) breezy; urgency=low + + * Reupload as 2.4.1-1ubuntu1. + + -- Matthias Klose Thu, 14 Apr 2005 10:46:32 +0200 + +python2.4 (2.4.1-1) unstable; urgency=low + + * Python 2.4.1 release. + * Fix noise in python-doc installation/removal. + * New Python section for the info docs. + + -- Matthias Klose Wed, 30 Mar 2005 19:42:03 +0200 + +python2.4 (2.4.1-0) hoary; urgency=low + + * Python 2.4.1 release. + * Fix noise in python-doc installation/removal. + * New Python section for the info docs. + + -- Matthias Klose Wed, 30 Mar 2005 16:35:34 +0200 + +python2.4 (2.4+2.4.1rc2-2) unstable; urgency=low + + * Add the valgrind support file to /etc/python2.4 + * Build the -dbg package with -DPy_USING_MEMORY_DEBUGGER. + * Lib/locale.py: + - correctly parse LANGUAGE as a colon separated list of languages. + - prefer LC_ALL, LC_CTYPE and LANG over LANGUAGE to get the correct + encoding. + - Don't map 'utf8', 'utf-8' to 'utf', which is not a known encoding + for glibc. + * Fix two typos in python(1). Addresses: #300124. + + -- Matthias Klose Sat, 19 Mar 2005 21:50:14 +0100 + +python2.4 (2.4+2.4.1rc2-1) unstable; urgency=low + + * Python 2.4.1 release candidate 2. + * Build-depend on libbluetooth1-dev. + + -- Matthias Klose Sat, 19 Mar 2005 00:57:14 +0100 + +python2.4 (2.4dfsg-2) unstable; urgency=low + + * CVS update up to 2005-03-03 + + -- Matthias Klose Thu, 3 Mar 2005 22:22:16 +0100 + +python2.4 (2.4dfsg-1ubuntu4) hoary; urgency=medium + + * Move exception finalisation later in the shutdown process - this + fixes the crash seen in bug #1165761, taken from CVS. + * codecs.StreamReader: Reset codec when seeking. Ubuntu #6972. + * Apply fix for SF1124295, fixing an obscure bit of Zope's security machinery. + * distutils: Don't add standard library dirs to library_dirs + and runtime_library_dirs. On amd64, runtime paths pointing to /usr/lib64 + aren't recognized by dpkg-shlibdeps, and the packages containing these + libraries aren't added to ${shlibs:Depends}. + * Lib/locale.py: + - correctly parse LANGUAGE as a colon separated list of languages. + - prefer LC_ALL, LC_CTYPE and LANG over LANGUAGE to get the correct + encoding. + - Don't map 'utf8', 'utf-8' to 'utf', which is not a known encoding + for glibc. + * os.py: Avoid using items() in environ.update(). Fixes #1124513. + * Python/pythonrun.c: + * Build depend on locales, generate the locales needed for the + testsuite. + * Add build dependency on libbluetooth1-dev, adding some bluetooth + functionality to the socket module. + * Lib/test/test_sundry.py: Don't fail on import of profile & pstats, + which are separated out to the python-profiler package. + * Fix typos in manpage. + + -- Matthias Klose Tue, 29 Mar 2005 13:35:53 +0200 + + +python2.4 (2.4dfsg-1ubuntu3) hoary; urgency=low + + * debian/patches/langpack-gettext.dpatch: + - langpack support for python-gettext added + + -- Michael Vogt Tue, 1 Mar 2005 13:13:36 +0100 + +python2.4 (2.4dfsg-1ubuntu2) hoary; urgency=low + + * Revert 'essential' status on python2.4-minimal. This status on + on python-minimal is sufficient (Ubuntu #6392). + + -- Matthias Klose Wed, 9 Feb 2005 23:09:42 +0100 + +python2.4 (2.4dfsg-1ubuntu1) hoary; urgency=low + + * Resyncronise with Debian. + * Mark the python2.4-minimal package as 'essential'. + + -- Matthias Klose Wed, 9 Feb 2005 13:31:09 +0100 + +python2.4 (2.4dfsg-1) unstable; urgency=medium + + * Add licenses and acknowledgements for incorporated software in the + debian/copyright file (addresses: #293932). + * Replace md5 implementation with one having a DFSG conforming license. + * Remove the profile.py and pstats.py modules from the source package, + not having a DFSG conforming license. The modules can be found in + the python2.x-profile package in the non-free section. + Addresses: #293932. + * Add missing norwegian locales (Tollef Fog Heen). + * CVS updates of the release24-maint branch upto 2005-02-08 (date of + the Python 2.3.5 release). + + -- Matthias Klose Tue, 8 Feb 2005 19:13:10 +0100 + +python2.4 (2.4-7ubuntu1) hoary; urgency=low + + * Fix the name of the python-dbg man page. + * Resyncronise with Debian. + * Move more modules to -minimal (new code in copy.py requires these): + dis, inspect, opcode, token, tokenize. + + -- Matthias Klose Tue, 8 Feb 2005 19:13:10 +0100 + +python2.4 (2.4-7) unstable; urgency=medium + + * Add licenses and acknowledgements for incorporated software in the + debian/copyright file (addresses: #293932). + * Replace md5 implementation with one having a DFSG conforming license. + * Add missing norwegian locales (Tollef Fog Heen). + * CVS updates of the release24-maint branch upto 2005-02-08 (date of + the Python 2.3.5 release). + + -- Matthias Klose Tue, 8 Feb 2005 19:13:10 +0100 + +python2.4 (2.4-6) unstable; urgency=low + + * Build a python2.4-dbg package using --with-pydebug. Add a debug + directory /lib-dynload/debug to sys.path instead of + /lib-dynload und install the extension modules of the + debug build in this directory. + Change the module load path to load extension modules from other + site-packages/debug directories (for further details see the + README in the python2.4-dbg package). Closes: #5415. + * Apply the pydebug-path patch. The package was already built in -5. + + -- Matthias Klose Fri, 4 Feb 2005 22:15:13 +0100 + +python2.4 (2.4-5) unstable; urgency=high + + * Fix a flaw in SimpleXMLRPCServerthat can affect any XML-RPC servers. + This affects any programs have been written that allow remote + untrusted users to do unrestricted traversal and can allow them to + access or change function internals using the im_* and func_* attributes. + References: CAN-2005-0089. + * CVS updates of the release24-maint branch upto 2005-02-04. + + -- Matthias Klose Fri, 4 Feb 2005 08:12:10 +0100 + +python2.4 (2.4-4) unstable; urgency=medium + + * Update debian/copyright to the 2.4 license text (closes: #290898). + * Remove /usr/bin/smtpd.py (closes: #291049). + + -- Matthias Klose Mon, 17 Jan 2005 23:54:37 +0100 + +python2.4 (2.4-3ubuntu6) hoary; urgency=low + + * Use old-style dpatches instead of dpatch-run. + + -- Tollef Fog Heen Mon, 7 Feb 2005 15:58:05 +0100 + +python2.4 (2.4-3ubuntu5) hoary; urgency=low + + * Actually apply the patch as well (add to list of patches in + debian/rules) + + -- Tollef Fog Heen Sun, 6 Feb 2005 15:12:58 +0100 + +python2.4 (2.4-3ubuntu4) hoary; urgency=low + + * Add nb_NO and nn_NO locales to Lib/locale.py + + -- Tollef Fog Heen Sun, 6 Feb 2005 14:33:05 +0100 + +python2.4 (2.4-3ubuntu3) hoary; urgency=low + + * Fix a flaw in SimpleXMLRPCServerthat can affect any XML-RPC servers. + This affects any programs have been written that allow remote + untrusted users to do unrestricted traversal and can allow them to + access or change function internals using the im_* and func_* attributes. + References: CAN-2005-0089. + + -- Matthias Klose Wed, 2 Feb 2005 09:08:20 +0000 + +python2.4 (2.4-3ubuntu2) hoary; urgency=low + + * Build a python2.4-dbg package using --with-pydebug. Add a debug + directory /lib-dynload/debug to sys.path instead of + /lib-dynload und install the extension modules of the + debug build in this directory. + Change the module load path to load extension modules from other + site-packages/debug directories (for further details see the + README in the python2.4-dbg package). Closes: #5415. + * Update debian/copyright to the 2.4 license text (closes: #290898). + * Add operator and copy to the -minimal package. + + -- Matthias Klose Mon, 17 Jan 2005 23:19:47 +0100 + +python2.4 (2.4-3ubuntu1) hoary; urgency=low + + * Resynchronise with Debian. + * python2.4: Depend on the very same version of python2.4-minimal. + * Docment, that time.strptime currently cannot be used, if the + python-minimal package is installed without the python package. + + -- Matthias Klose Sun, 9 Jan 2005 19:35:48 +0100 + +python2.4 (2.4-3) unstable; urgency=medium + + * Build the fpectl module. + * Updated to CVS release24-maint 20050107. + + -- Matthias Klose Sat, 8 Jan 2005 19:05:21 +0100 + +python2.4 (2.4-2ubuntu5) hoary; urgency=low + + * Updated to CVS release24-maint 20050102. + * python-minimal: + - os.py: Use dict instead of UserDict, remove UserDict from -minimal. + - add pickle, threading, needed for subprocess module. + - optparse.py: conditionally import gettext, if not available, + define _ as the identity function. Patch taken from the trunk. + Avoids import of _locale, locale, gettext, copy, repr, itertools, + collections, token, tokenize. + - Add a build check to make sure that the minimal module list is + closed under dependency. + * Fix lintian warnings. + + -- Matthias Klose Sun, 2 Jan 2005 22:00:14 +0100 + +python2.4 (2.4-2ubuntu4) hoary; urgency=low + + * Add UserDict.py to the -minimal package, since os.py needs it. + + -- Colin Watson Thu, 30 Dec 2004 20:41:28 +0000 + +python2.4 (2.4-2ubuntu3) hoary; urgency=low + + * Add os.py and traceback.py to the -minimal package, get the list + of modules from the README. + + -- Matthias Klose Mon, 27 Dec 2004 08:20:45 +0100 + +python2.4 (2.4-2ubuntu2) hoary; urgency=low + + * Add compileall.py and py_compile.py to the -minimal package, not + just to the README ... + + -- Matthias Klose Sat, 25 Dec 2004 22:24:56 +0100 + +python2.4 (2.4-2ubuntu1) hoary; urgency=low + + * Separate the interpreter and a minimal subset of modules into + a python2.4-minimal package. See the README.Debian.gz in this + package. + * Move site.py to python2.4-minimal as well. + * Add documentation files for devhelp. + + -- Matthias Klose Sun, 19 Dec 2004 22:47:32 +0100 + +python2.4 (2.4-2) unstable; urgency=medium + + * Updated patch for #283108. Thanks to Jim Meyering. + + -- Matthias Klose Fri, 3 Dec 2004 17:00:16 +0100 + +python2.4 (2.4-1) unstable; urgency=low + + * Final 2.4 release. + * Flush stdout/stderr if closed (SF #1074011). + + -- Matthias Klose Wed, 1 Dec 2004 07:54:34 +0100 + +python2.4 (2.3.97-2) unstable; urgency=low + + * Don't run test_tcl, hanging on the buildds. + + -- Matthias Klose Fri, 19 Nov 2004 23:48:42 +0100 + +python2.4 (2.3.97-1) unstable; urgency=low + + * Python 2.4 Release Candidate 1. + + -- Matthias Klose Fri, 19 Nov 2004 21:27:02 +0100 + +python2.4 (2.3.96-1) experimental; urgency=low + + * Updated to CVS release24-maint 20041113. + * Build the docs in info format again. + + -- Matthias Klose Sat, 13 Nov 2004 21:21:10 +0100 + +python2.4 (2.3.95-2) experimental; urgency=low + + * Move distutils package from the python2.4-dev into the python2.4 + package. + + -- Matthias Klose Thu, 11 Nov 2004 22:56:14 +0100 + +python2.4 (2.3.95-1) experimental; urgency=low + + * Python 2.4 beta2 release. + + -- Matthias Klose Thu, 4 Nov 2004 23:43:47 +0100 + +python2.4 (2.3.94-1) experimental; urgency=low + + * Python 2.4 beta1 release. + + -- Matthias Klose Sat, 16 Oct 2004 08:33:57 +0200 + +python2.4 (2.3.93-1) experimental; urgency=low + + * Python 2.4 alpha3 release. + + -- Matthias Klose Fri, 3 Sep 2004 21:53:47 +0200 + +python2.4 (2.3.92-1) experimental; urgency=low + + * Python 2.4 alpha2 release. + + -- Matthias Klose Thu, 5 Aug 2004 23:53:18 +0200 + +python2.4 (2.3.91-1) experimental; urgency=low + + * Python 2.4 alpha1 release. + Highlights: http://www.python.org/2.4/highlights.html + + -- Matthias Klose Fri, 9 Jul 2004 17:38:54 +0200 + +python2.4 (2.3.90-1) experimental; urgency=low + + * Package HEAD branch (pre alpha ..). + + -- Matthias Klose Mon, 14 Jun 2004 23:19:57 +0200 + +python2.3 (2.3.4-1) unstable; urgency=medium + + * Final Python 2.3.4 Release. + * In the API docs, fix signature of PyModule_AddIntConstant (closes: #250826). + * locale.getdefaultlocale: don't fail with empty environment variables. + Closes: #249816. + * Include distutils/command/wininst.exe in -dev package (closes: #249006). + * Disable cthreads on the Hurd (Michael Banck). Closes: #247211. + * Add a note to pygettext(1), that this program is deprecated in favour + of xgettext, which now includes support for Python as well. + Closes: #246332. + + -- Matthias Klose Fri, 28 May 2004 22:59:42 +0200 + +python2.3 (2.3.3.91-1) unstable; urgency=low + + * Python 2.3.4 Release Candidate 1. + * Do not use the default namespace for attributes. Patch taken from the + 2.3 maintenance branch. + The xmllib module is obsolete. Use xml.sax instead. + * http://python.org/sf/945642 - fix nonblocking i/o with ssl socket. + + -- Matthias Klose Thu, 13 May 2004 21:24:52 +0200 + +python2.3 (2.3.3-7) unstable; urgency=low + + * Add a workaround for GNU libc nl_langinfo()'s returning NULL. + Closes: #239237. + Patch taken from 2.3 maintenance branch. + * threading.py: Remove calls to currentThread() in _Condition methods that + were side-effect. Side-effects were deemed unnecessary and were causing + problems at shutdown time when threads were catching exceptions at start + time and then triggering exceptions trying to call currentThread() after + gc'ed. Masked the initial exception which was deemed bad. + Closes: #195812. + * Properly support normalization of empty unicode strings. Closes: #239986. + Patch taken from 2.3 maintenance branch. + * README.maintainers: Add section where to find the documentation tools. + * Fix crash in pyexpat module (closes: #229281). + * For the Hurd, set the interpreters recursion limit to 930. + * Do not try to byte-compile the test files on installation; this + currently breaks the Hurd install. + + -- Matthias Klose Sat, 1 May 2004 07:50:46 +0200 + +python2.3 (2.3.3-6) unstable; urgency=low + + * Don't build the unversioned python{,-*} packages anymore. Now + built from the python-defaults package. + * Update to the proposed python-policy: byte-compile using -E. + * Remove python-elisp's dependency on emacs20 (closes: #232785). + * Don't build python-elisp from the python2.3 source anymore, + get it from python-mode.sf.net as a separate source package. + * python2.3-dev suggests libc-dev (closes: #231091). + * get LDSHARED and CCSHARED (like, CC, CXX, CPP, CFLAGS) from + the environment + * Set CXX in installed config/Makefile (closes: #230273). + + -- Matthias Klose Tue, 24 Feb 2004 07:07:51 +0100 + +python2.3 (2.3.3-5) unstable; urgency=low + + * Build-depend on libdb4.2-dev, instead of libdb4.1-dev. According + to the docs the file format is compatible. + + -- Matthias Klose Mon, 12 Jan 2004 10:37:45 +0100 + +python2.3 (2.3.3-4) unstable; urgency=low + + * Fix broken _bsddb module. setup.py picked up the wrong library. + + -- Matthias Klose Sun, 4 Jan 2004 11:30:00 +0100 + +python2.3 (2.3.3-3) unstable; urgency=low + + * Fix typo in patch (closes: #224797, #226064). + + -- Matthias Klose Sun, 4 Jan 2004 09:23:21 +0100 + +python2.3 (2.3.3-2) unstable; urgency=medium + + * Lib/email/Charset: use locale unaware function to lower case of locale + name (closes: #224797). + * Update python-mode to version from python-mode.sf.net. Fixes highlighting + problems (closes: #223520). + * Backport from mainline: Add IPV6_ socket options from RFCs 3493 and 3542. + + -- Matthias Klose Fri, 2 Jan 2004 14:03:26 +0100 + +python2.3 (2.3.3-1) unstable; urgency=low + + * New upstream release. + * Copy the templates, tools and scripts from the Doc dir in the source + to /usr/share/lib/python2.3/doc in the python2.3-dev package. Needed + for packages building documentation like python does (closes: #207337). + + -- Matthias Klose Fri, 19 Dec 2003 10:57:39 +0100 + +python2.3 (2.3.2.91-1) unstable; urgency=low + + * New upstream version (2.3.3 release candidate). + * Update python-mode.el (closes: #158811, #159630). + Closing unreproducible report (closes: #159628). + + -- Matthias Klose Sat, 6 Dec 2003 14:41:14 +0100 + +python2.3 (2.3.2-7) unstable; urgency=low + + * Put the conflict in the correct direction. python2.3 (2.3.2-6) doesn't + conflict with python (<= 2.3.2-5) but python (2.3.2-6) conflicts with + python2.3 (<= 2.3.2-5) (thanks to Brian May). Really closes #221791. + + -- Matthias Klose Fri, 21 Nov 2003 00:20:02 +0100 + +python2.3 (2.3.2-6) unstable; urgency=low + + * Add conflicts with older python{,2.3} packages to fix overwrite + errors (closes: #221791). + + -- Matthias Klose Thu, 20 Nov 2003 07:24:36 +0100 + +python2.3 (2.3.2-5) unstable; urgency=low + + * Updated to CVS release23-maint 20031119. + * Re-upgrade the dependency of python2.3 on python (>= 2.3) to + a dependency (closes: #221523). + + -- Matthias Klose Wed, 19 Nov 2003 00:30:27 +0100 + +python2.3 (2.3.2-4) unstable; urgency=low + + * Don't build-depend on latex2html (moved to non-free), but keep + the prebuilt docs in debian/patches (closes: #221347). + * Fix typos in the library reference (closes: #220510, #220954). + * Fix typo in python-elisp's autoloading code (closes: #220308). + * Update proposed python policy: private modules can be installed + into /usr/lib/ (arch dependent) and into /usr/share/ + (arch independent). + + -- Matthias Klose Tue, 18 Nov 2003 00:41:39 +0100 + +python2.3 (2.3.2-3) unstable; urgency=low + + * Downgrade the dependency of python2.3 on python (>= 2.3) to + a recommendation. + * Fix path to interpreter in binfmt file. + * Fix segfault in unicodedata module (closes: #218697). + * Adjust python-elisp autoload code (closes: #219821). + + -- Matthias Klose Sun, 9 Nov 2003 19:43:37 +0100 + +python2.3 (2.3.2-2) unstable; urgency=medium + + * Fix broken doc link (closes: #214217). + * Disable wrongly detected large file support for GNU/Hurd. + * Really fix the FTBFS for the binary-indep target (closes: #214303). + + -- Matthias Klose Mon, 6 Oct 2003 07:54:58 +0200 + +python2.3 (2.3.2-1) unstable; urgency=low + + * New upstream version. + * Fix a FTBFS for the binary-indep target. + + -- Matthias Klose Sat, 4 Oct 2003 10:20:15 +0200 + +python2.3 (2.3.1-3) unstable; urgency=low + + * Fix names of codec packages in recommends. + * On alpha compile using -mieee (see #212912). + + -- Matthias Klose Sun, 28 Sep 2003 10:48:12 +0200 + +python2.3 (2.3.1-2) unstable; urgency=low + + * Update python policy draft (closes: #128911, #163785). + * Re-add os.fsync function (closes: #212672). + * Let python2.3-doc conflict with older python2.3 versions (closes: #211882). + * Add recommends for pythonX.Y-japanese-codecs, pythonX.Y-iconvcodec, + pythonX.Y-cjkcodecs, pythonX.Y-korean-codecs (closes: #207161). + * Generate binfmt file (closes: #208005). + * Add IPPROTO_IPV6 option to the socketmodule (closes: #206569). + * Bugs reported against python2.2 and fixed in python2.3: + - Crashes in idle (closes: #186887, #200084). + + -- Matthias Klose Sat, 27 Sep 2003 11:21:47 +0200 + +python2.3 (2.3.1-1) unstable; urgency=low + + * New upstream version (bug fix release). + + -- Matthias Klose Wed, 24 Sep 2003 11:27:43 +0200 + +python2.3 (2.3-4) unstable; urgency=high + + * Disable check for utimes function, which is broken in glibc-2.3.2. + Packages using distutils had '1970/01/01-01:00:01' timestamps in files. + * Bugs fixed by making python2.3 the default python version: + - Canvas.scan_dragto() takes a 3rd optional parmeter "gain". + Closes: #158168. + - New command line parsing module (closes: #38628). + - compileall.py allows compiling single files (closes: #139971). + * Bugs reported for 2.2 and fixed in 2.3: + - Idle does save files with ASCII characters (closes: #179313). + - imaplib support for prefix-quoted strings (closes: #150485). + - posixpath includes getctime (closes: #173827). + - pydoc has support for keywords (closes: #186775). + * Bugs reported for 2.1 and fixed in 2.3: + - Fix handling of "#anchor" URLs in urlparse (closes: #147844). + - Fix readline if C stdin is not a tty, even if sys.stdin is. + Closes: #131810. + * Updated to CVS release23-maint 20030810 (fixing memory leaks in + array and socket modules). + * pydoc's usage output uses the basename of the script. + * Don't explicitely remove /etc/python2.3 on purge (closes: #202864). + * python conflicts with python-xmlbase (closes: #204773). + * Add dependency python (>= 2.3) to python2.3, so make sure the + unversioned names can be used. + + -- Matthias Klose Sun, 10 Aug 2003 09:27:52 +0200 + +python2.3 (2.3-3) unstable; urgency=medium + + * Fix shlibs file. + + -- Matthias Klose Fri, 8 Aug 2003 08:45:12 +0200 + +python2.3 (2.3-2) unstable; urgency=medium + + * Make python2.3 the default python version. + + -- Matthias Klose Tue, 5 Aug 2003 22:13:22 +0200 + +python2.3 (2.3-1) unstable; urgency=low + + * Python 2.3 final release. + + -- Matthias Klose Wed, 30 Jul 2003 08:12:28 +0200 + +python2.3 (2.2.107-1rc2) unstable; urgency=medium + + * Python 2.3 release candidate 2. + * Don't compress .txt files referenced by the html docs (closes: #200298). + * Include the email/_compat* files (closes: #200349). + + -- Matthias Klose Fri, 25 Jul 2003 07:08:09 +0200 + +python2.3 (2.2.106-2beta2) unstable; urgency=medium + + * Python 2.3 beta2 release, updated to CVS 20030704. + - Fixes AssertionError in httplib (closed: #192452). + - Fixes uncaught division by zero in difflib.py (closed: #199287). + * Detect presence of setgroups(2) at configure time (closes: #199839). + * Use default gcc on arm as well. + + -- Matthias Klose Sat, 5 Jul 2003 10:21:33 +0200 + +python2.3 (2.2.105-1beta2) unstable; urgency=low + + * Python 2.3 beta2 release. + - Includes merged idle fork. + - Fixed socket.setdefaulttimeout(). Closes: #189380. + - socket.ssl works with _socketobj. Closes: #196082. + * Do not link libtix to the _tkinter module. It's loaded via + 'package require tix' at runtime. python2.3-tkinter now + suggests tix8.1 instead. + * On arm, use gcc-3.2 to build. + * Add -fno-strict-aliasing rules to OPT to avoid warnings + "dereferencing type-punned pointer will break strict-aliasing rules", + when building with gcc-3.3. + + -- Matthias Klose Mon, 30 Jun 2003 00:19:32 +0200 + +python2.3 (2.2.104-1beta1.1) unstable; urgency=low + + * Non-maintainer upload with maintainer consent. + * debian/control (Build-Depends): s/libgdbmg1-dev/libgdbm-dev/. + + -- James Troup Wed, 4 Jun 2003 02:24:27 +0100 + +python2.3 (2.2.104-1beta1) unstable; urgency=low + + * Python 2.3 beta1 release, updated to CVS 20030514. + - build the current documentation. + * Reenable Tix support. + + -- Matthias Klose Wed, 14 May 2003 07:38:57 +0200 + +python2.3 (2.2.103-1beta1) unstable; urgency=low + + * Python 2.3 beta1 release, updated to CVS 20030506. + - updated due to build problems on mips/mipsel. + - keep the 2.3b1 documentation (doc build problems with cvs). + + -- Matthias Klose Wed, 7 May 2003 06:26:39 +0200 + +python2.3 (2.2.102-1beta1) unstable; urgency=low + + * Python 2.3 beta1 release. + + -- Matthias Klose Sat, 3 May 2003 22:45:16 +0200 + +python2.3 (2.2.101-1exp1) unstable; urgency=medium + + * Python 2.3 alpha2 release, updated to CVS 20030321. + * Tkinter: Catch exceptions thrown for undefined substitutions in + events (needed for tk 8.4.2). + + -- Matthias Klose Fri, 21 Mar 2003 21:32:14 +0100 + +python2.3 (2.2.100-1exp1) unstable; urgency=low + + * Python 2.3 alpha2 release, updated to CVS 20030221. + + -- Matthias Klose Fri, 21 Feb 2003 19:37:17 +0100 + +python2.3 (2.2.99-1exp1) unstable; urgency=low + + * Python 2.3 alpha1 release updated to CVS 20030123. + - should fix the testsuite (and package build) failure on alpha. + * Remove build dependency on libexpat1-dev. Merge the python2.3-xmlbase + package into python2.3 (closes: #177739). + + -- Matthias Klose Thu, 23 Jan 2003 22:48:12 +0100 + +python2.3 (2.2.98-1exp1) unstable; urgency=low + + * Python 2.3 alpha1 release updated to CVS 20030117. + * Build using libdb4.1. + + -- Matthias Klose Sat, 18 Jan 2003 00:14:01 +0100 + +python2.3 (2.2.97-1exp1) unstable; urgency=low + + * Python 2.3 alpha1 release updated to CVS 20030109. + * Build-Depend on g++ (>= 3:3.2). + * Python package maintainers: please wait uploading python dependent + packages until python2.2 and python2.1 are compiled using gcc-3.2. + + -- Matthias Klose Thu, 9 Jan 2003 23:56:42 +0100 + +python2.3 (2.2.96-1exp1) unstable; urgency=low + + * Python 2.3 alpha1 release (not exactly the tarball, but taken from + CVS 20030101). + - Includes support for linking with threaded tk8.4 (closes: #172714). + * Install and register whatsnew document (closes: #173859). + * Properly unregister info documentation. + + -- Matthias Klose Wed, 1 Jan 2003 17:38:54 +0100 + +python2.3 (2.2.95-1exp1) unstable; urgency=low + + * Experimental packages from CVS 021212. + - data in unicodedate module is up to date (closes: #171061). + * Fix idle packaging (closes: #170394). + * Configure using unicode UCS-4 (closes: #171062). + This change breaks compatibility with binary modules, but what do you + expect from experimental packages ... Please recompile dependent packages. + * Don't strip binaries for now. + + -- Matthias Klose Thu, 12 Dec 2002 21:42:27 +0100 + +python2.3 (2.2.94-1exp1) unstable; urgency=low + + * Experimental packages from CVS 021120. + * Remove outdated README.dbm. + * Depend on tk8.4. + * python-elisp: Install emacsen install file with mode 644 (closes: #167718). + + -- Matthias Klose Thu, 21 Nov 2002 01:04:51 +0100 + +python2.3 (2.2.93-1exp1) unstable; urgency=medium + + * Experimental packages from CVS 021015. + * Build a static library libpython2.3-pic.a. + * Enable large file support for the Hurd (closes: #164602). + + -- Matthias Klose Tue, 15 Oct 2002 21:06:27 +0200 + +python2.3 (2.2.92-1exp1) unstable; urgency=low + + * Experimental packages from CVS 020922. + * Fix build error on ia64 (closes: #161234). + * Build depend on gcc-3.2-3.2.1-0pre2 to fix build error on arm. + + -- Matthias Klose Sun, 22 Sep 2002 18:30:28 +0200 + +python2.3 (2.2.91-1exp1) unstable; urgency=low + + * Experimental packages from CVS 020906. + * idle-python2.3: Fix conflict (closes: #159267). + * Fix location of python-mode.el (closes: #159564, #159619). + * Use tix8.1. + * Apply fix for distutils/ccompiler problem (closes: #159288). + + -- Matthias Klose Sat, 7 Sep 2002 09:55:07 +0200 + +python2.3 (2.2.90-1exp1) unstable; urgency=low + + * Experimental packages from CVS 020820. + * Don't build python2.3-elisp, but put the latest version into + python-elisp. + + -- Matthias Klose Thu, 22 Aug 2002 21:52:04 +0200 + +python2.2 (2.2.1-6) unstable; urgency=low + + * CVS updates of the release22-maint branch upto 2002-07-23. + * Enable IPv6 support (closes: #152543). + * Add python2.2-tk suggestion for python2.2 (pydoc -g). + * Fix from SF patch #527518: proxy config with user+pass authentication. + * Point pydoc to the correct location of the docs (closes: #147579). + * Remove '*.py[co]' files, when removing the python package, + not when purging (closes: #147130). + * Update to new py2texi.el version (Milan Zamazal). + + -- Matthias Klose Mon, 29 Jul 2002 23:11:32 +0200 + +python2.2 (2.2.1-5) unstable; urgency=low + + * CVS updates of the release22-maint branch upto 2002-05-03. + * Build the info docs (closes: #145653). + + -- Matthias Klose Fri, 3 May 2002 22:35:46 +0200 + +python2.2 (2.2.1-4) unstable; urgency=high + + * Fix indentation errors introduced in last upload (closes: #143809). + + -- Matthias Klose Sun, 21 Apr 2002 01:00:14 +0200 + +python2.2 (2.2.1-3) unstable; urgency=high + + * Add Build-Conflicts: tcl8.0-dev, tk8.0-dev, tcl8.2-dev, tk8.2-dev. + Closes: #143534 (build a working _tkinter module, on machines, where + 8.0's tk.h gets included). + * CVS updates of the release22-maint branch upto 2002-04-20. + + -- Matthias Klose Sat, 20 Apr 2002 09:22:37 +0200 + +python2.2 (2.2.1-2) unstable; urgency=low + + * Forgot to copy the dlmodule patch from the 2.1.3 package. Really + closes: #141681. + + -- Matthias Klose Sat, 13 Apr 2002 01:28:05 +0200 + +python2.2 (2.2.1-1) unstable; urgency=high + + * Final 2.2.1 release. + * According to report #131813, the python interpreter is much faster on some + architectures, when beeing linked statically with the python library (25%). + Gregor and me tested on i386, m68k and alpha, but we could not reproduce + such a speedup (generally between 5% and 10%). But we are linking the + python executable now statically ... + * Build info docs from the tex source, merge the python-doc-info + package into the python-doc package. + * Always build the dl module. Failure in case of + sizeof(int)!=sizeof(long)!=sizeof(void*) + is delayed until dl.open is called. Closes: #141681. + + -- Matthias Klose Thu, 11 Apr 2002 00:19:19 +0200 + +python2.2 (2.2.0.92-0) unstable; urgency=low + + * Package CVS sources, omit cvs-updates.dpatch (closes: #140977). + + -- Matthias Klose Wed, 3 Apr 2002 08:20:52 +0200 + +python2.2 (2.2-6) unstable; urgency=medium + + * Update to python-2.2.1 release candidate 2 (final release scheduled + for April 10). + * Enable dl module (closes: #138992). + * Build doc files with python binary from package (closes: #139657). + * Build _tkinter module with BLT and Tix support. + * python2.2-elisp: Conflict with python2-elisp (closes: #138970). + * string.split docs updated in python-2.2.1 (closes: #129272). + + -- Matthias Klose Mon, 1 Apr 2002 13:52:36 +0200 + +python2.2 (2.2-5) unstable; urgency=low + + * CVS updates of the release22-maint branch upto 20020310 (aproaching + the first 2.2.1 release candidate). + * Stolen from HEAD: check argument of locale.nl_langinfo (closes: #137371). + + -- Matthias Klose Fri, 15 Mar 2002 01:05:59 +0100 + +python2.2 (2.2-4) unstable; urgency=medium + + * Include test/{__init__.py,README,pystone.py} in package (closes: #129013). + * Fix python-elisp conflict (closes: #129046). + * Don't compress stylesheets (closes: #133179). + * CVS updates of the release22-maint branch upto 20020310. + + -- Matthias Klose Sun, 10 Mar 2002 23:32:28 +0100 + +python2.2 (2.2-3) unstable; urgency=medium + + * Updates from the CVS python22-maint branch up to 20020107. + webbrowser.py: properly escape url's. + * The Hurd does not have large file support: disabled. + + -- Matthias Klose Mon, 7 Jan 2002 21:55:57 +0100 + +python2.2 (2.2-2) unstable; urgency=medium + + * CVS updates of the release22-maint branch upto 20011229. Fixes: + - Include TCP_CORK flag in plat-linux2 headers (fixes: #84340). + - Update CDROM.py module (fixes: #125785). + * Add missing chunk of the GNU/Hurd patch (therefore urgency medium). + * Send anonymous password when using anonftp (closes: #126814). + + -- Matthias Klose Sat, 29 Dec 2001 20:18:26 +0100 + +python2.2 (2.2-1) unstable; urgency=low + + * New upstream version: 2.2. + * Bugs fixed upstream: + - Docs for os.kill reference the signal module for constants. + - Documentation strings in the tutorial end with a period (closes: #94770). + - Tk: grid_location method moved from Grid to Misc (closes: #98338). + - mhlib.SubMessage.getbodytext takes decode parameter (closes: #31876). + - Strings in modules are locale aware (closes: #51444). + - Printable 8-bit characters in strings are correctly printed + (closes: #64354). + - Dictionary can be updated with abstract mapping object (closes: #46566). + * Make site.py a config files. + + -- Matthias Klose Sat, 22 Dec 2001 00:51:46 +0100 + +python2.2 (2.1.99c1-1) unstable; urgency=low + + * New upstream version: 2.2c1 (release candidate). + * Do not provide python2.2-base anymore. + * Install correct README.Debian for python2.2 package. Include hint + where to find Makefile.pre.in. + * Suggest installation of python-ssl. + * Remove idle config files on purge. + * Remove empty /usr/lib/python2.2 directory on purge. + + -- Matthias Klose Sat, 15 Dec 2001 17:56:27 +0100 + +python2.2 (2.1.99beta2-1) unstable; urgency=high + + * debian/rules: Reflect removal of regrtest package (closes: #122278). + Resulted in build failures on all architectures. + * Build -doc package from source. + + -- Matthias Klose Sat, 8 Dec 2001 00:38:41 +0100 + +python2.2 (2.1.99beta2-0.1) unstable; urgency=low + + * Non maintainer upload. + * New upstream version (this is 2.2beta2). + * Do not build the python-regrtest package anymore; keep the test framework + components test/regrtest.py and test/test_support.py in the python + package (closes: #119408). + + -- Gregor Hoffleit Tue, 27 Nov 2001 09:53:26 +0100 + +python2.2 (2.1.99beta1-4) unstable; urgency=low + + * Configure with --with-fpectl (closes: #118125). + * setup.py: Remove broken check for _curses_panel module (#116081). + * idle: Move config-* files to /etc and mark as conffiles (#106390). + * Move idle packages to section `devel'. + + -- Matthias Klose Wed, 31 Oct 2001 10:56:45 +0100 + +python2.2 (2.1.99beta1-3) unstable; urgency=low + + * Fix shlibs file (was still referring to 2.1). Closes: #116810. + * README.Debian: point to draft of python-policy in the python package. + + -- Matthias Klose Wed, 31 Oct 2001 10:56:45 +0100 + +python2.2 (2.1.99beta1-2) unstable; urgency=medium + + * Fix shlibs file (was still referring to 2.1). Closes: #116810. + * Rename package python2.2-base to python2.2. + + -- Matthias Klose Wed, 24 Oct 2001 23:00:50 +0200 + +python2.2 (2.1.99beta1-1) unstable; urgency=low + + * New upstream version (beta). Call the package version 2.1.99beta1-1. + * New maintainer until the final 2.2 release. + * Updated the debian patches. + + -- Matthias Klose Sat, 20 Oct 2001 18:56:26 +0200 + +python2.1 (2.1.1-1.2) unstable; urgency=low + + * Really remove the python alternative. + + -- Matthias Klose Sat, 20 Oct 2001 15:16:56 +0200 + +python2.1 (2.1.1-1.1) unstable; urgency=low + + * README FOR PACKAGE MAINTAINERS: It is planned to remove the python2-XXX + packages from unstable and move on to python2.1. + If you repackage/adapt your modules for python2.1, don't build + python2-XXX and python2.1-XXX packages from the same source package, + so that the python2-XXX package can be removed without influencing the + python2.1-XXX package. + + See the debian-python mailing list at http://lists.debian.org/devel.html + for details and the current discussion and a draft for a debian-python + policy (August to October 2001). + + * Remove alternative for /usr/bin/python. The python-base package now + provides the default python version. + + * Regenerate control file to fix build dependencies (closes: #116190). + * Remove alternative for /usr/bin/{python,pydoc}. + * Provide a libpython2.1.so symlink in /usr/lib/python2.1/config, + so that the shared library is found when -L/usr/lib/python2.1/config + is specified. + * Conflict with old package versions, where /usr/bin/python is a real + program (closes: #115943). + * python2.1-elisp conflicts with python-elisp (closes: #115895). + * We now have 2.1 (closes: #96851, #107849, #110243). + + -- Matthias Klose Fri, 19 Oct 2001 17:34:41 +0200 + +python2.1 (2.1.1-1) unstable; urgency=low + + * Incorporated Matthias' modifications. + + -- Gregor Hoffleit Thu, 11 Oct 2001 00:16:42 +0200 + +python2.1 (2.1.1-0.2) unstable; urgency=low + + * New upstream 2.1.1. + * GPL compatible licence (fixes #84080, #102949, #110643). + * Fixed upstream (closes: #99692, #111340). + * Build in separate build directory. + * Split Debian patches into debian/patches directory. + * Build dependencies: Add libgmp3-dev, libexpat1-dev, tighten + debhelper dependency. + * debian/rules: Updated a "bit". + * python-elisp: Remove custom dependency (closes: #87783), + fix emacs path (closes: #89712), remove emacs19 dependency (#82694). + * Mention distutils in python-dev package description (closes: #108170). + * Update README.Debian (closes: #85430). + * Run versioned python in postinsts (closes: #113349). + * debian/sample.{postinst,prerm}: Change to version independent scripts. + * Use '/usr/bin/env python2.1' as interpreter for all python scripts. + * Add libssl-dev to Build-Conflicts. + * python-elisp: Add support for emacs21 (closes: #98635). + * Do not compress .py files in doc directories. + * Don't link explicitely with libc. + + -- Matthias Klose Wed, 3 Oct 2001 09:53:08 +0200 + +python2.1 (2.1.1-0.1) unstable; urgency=low + + * New upstream version (CVS branch release21-maint, will become 2.1.1): + This CVS branch will be released as 2.1.1 under a GPL compatible + license. + + -- Gregor Hoffleit Wed, 27 Jun 2001 22:47:58 +0200 + +python2 (2.1-0.1) unstable; urgency=low + + * Fixed Makefile.pre.in. + * Fixed the postinst files in order to use 2.1 (instead of 2.0). + * Mention the immanent release of 2.0.1 and 2.1.1, with a GPL + compatible license. + + -- Gregor Hoffleit Sun, 17 Jun 2001 21:05:25 +0200 + +python2 (2.1-0) unstable; urgency=low + + * New upstream version. + * Experimental packages. + + -- Gregor Hoffleit Thu, 10 May 2001 00:20:04 +0200 + +python2 (2.0-7) unstable; urgency=low + + * Rebuilt with recent tcl8.3-dev/tk8.3-dev in order to fix a + dependency problem with python2-tk (closes: #87793, #92962). + * Change postinst to create and update /usr/local/lib/python2.0 and + site-python with permissions and owner as mandated by policy: + 2775 and root:staff (closes: #89047). + * Fix to compileall.py: A superfluous argument made compileall without + options fail (cf. #92990 for python). + * Move the distutils module into python2-dev. It needs Makefile.pre.in + in order to work (closes: #89900). + * Remove build-dependency on libgdbm2-dev (which isn't built anyway). + * Add a build-dependency on libdb2-dev (cf. #90220 for python). + + -- Gregor Hoffleit Sat, 14 Apr 2001 21:07:51 +0200 + +python2 (2.0-6) unstable; urgency=low + + * Remove python-zlib package; merge it into python-base. + * Mark that README.python2 is not yet updated. + + -- Gregor Hoffleit Wed, 21 Feb 2001 12:34:18 +0100 + +python2 (2.0-5) unstable; urgency=low + + * Recompile with tcl/tk8.3 (closes: #82088). + * Modifications to README.why-python2 (closes: #82116). + * Add menu hint to idle2 menu entry. + * idle2 is renamed idle-python2 and now build correctly (closes: #82218). + * Add build-dependency on autoconf (closes: #85339). + * Build bsddbmodule as shared module (Modules/Setup.config.in), + and link libpython2.so with -lm in Makefile (closes: #86027). + * various cleanups in debian/rules, e.g. removing dh_suidregister. + * Make pdb available as /usr/bin/pdb-python2 in python2-dev + (cf. #79870 in python-base). + * Remove libgmp3 from build-dependencies, since we currently can't + build the mpzmodule for Python2 due to license problems. + + -- Gregor Hoffleit Sun, 18 Feb 2001 00:12:17 +0100 + +python2 (2.0-4) unstable; urgency=low + + * control: make python2-elisp conflict with python-elisp (it doesn't + make sense to have both of them installed, does it ?) + * include build-depend on libxmltok1-dev. + * again, build with tcl/tk8.0. + + -- Gregor Hoffleit Wed, 10 Jan 2001 23:37:01 +0100 + +python2 (2.0-3) unstable; urgency=low + + * Modules/Setup.in: Added a missing \ that made _tkinter be built + incorrectly. + * rules: on the fly, change all '#!' python scripts to use python2. + + -- Gregor Hoffleit Wed, 13 Dec 2000 20:07:24 +0100 + +python2 (2.0-2) unstable; urgency=low + + * Aaargh. Remove conflicts/provides/replaces on python-base to make + parallel installation of python-base and python2-base possible. + * Install examples into /usr/share/doc/python2 (not python) and fix + symlink to python2.0 (thanks to Rick Younie for + pointing out this). + * Rename man page to python2.1. + + -- Gregor Hoffleit Wed, 13 Dec 2000 09:31:05 +0100 + +python2 (2.0-1) unstable; urgency=low + + * New upstream version. Initial release for python2. + + -- Gregor Hoffleit Mon, 11 Dec 2000 22:39:46 +0100 --- python3.3-3.3.0.orig/debian/PVER-dev.postinst.in +++ python3.3-3.3.0/debian/PVER-dev.postinst.in @@ -0,0 +1,24 @@ +#! /bin/sh -e + +if [ "$1" = configure ]; then + if [ -d /usr/include/@PVER@ ] && [ ! -h /usr/include/@PVER@ ]; then + if rmdir /usr/include/@PVER@ 2> /dev/null; then + ln -sf @PVER@mu /usr/include/@PVER@ + else + echo >&2 "WARNING: non-empty directory on upgrade: /usr/include/@PVER@" + ls -l /usr/include/@PVER@ + fi + fi + if [ -d /usr/lib/@PVER@/config ] && [ ! -h /usr/lib/@PVER@/config ]; then + if rmdir /usr/lib/@PVER@/config 2> /dev/null; then + ln -sf config-@VER@mu /usr/lib/@PVER@/config + else + echo >&2 "WARNING: non-empty directory on upgrade: /usr/lib/@PVER@/config" + ls -l /usr/lib/@PVER@/config + fi + fi +fi + +#DEBHELPER# + +exit 0 --- python3.3-3.3.0.orig/debian/PVER-minimal.README.Debian.in +++ python3.3-3.3.0/debian/PVER-minimal.README.Debian.in @@ -0,0 +1,154 @@ +Contents of the @PVER@-minimal package +----------------------------------------- + +@PVER@-minimal consists of a minimum set of modules which may be needed +for python scripts used during the boot process. If other packages +are needed in these scripts, don't work around the missing module, but +file a bug report against this package. The modules in this package +are: + + __builtin__ builtin + __future__ module + _bisect extension + _bytesio builtin + _codecs builtin + _collections extension + _compat_pickle module + _datetime extension + _elementtree extension + _fileio builtin + _functools extension + _hashlib extensionx + _heapq extension + _imp builtin + _io builtin + _locale extension + _md5 extension + _pickle extension + _posixsubprocess extension + _random extension + _sha1 extension + _sha256 extension + _sha512 extension + _socket extension + _sre builtin + _ssl extensionx + _stringio extension + _struct extension + _string builtin + _stringio builtin + _symtable builtin + _sysconfigdata module + _thread builtin + _types builtin + _weakref builtin + _weakrefset module + _warnings builtin + configparser module + abc module + argparse module + array extension + atexit extension + base64 module + binascii extension + bisect module + builtins builtin + codecs module + collections package + compileall module + copy module + copyreg module + dis module + errno builtin + exceptions builtin + fcntl extension + fnmatch module + functools module + gc builtin + genericpath module + getopt module + glob module + grp extension + hashlib module + heapq module + imp module + importlib package + inspect module + io module + itertools extension + keyword module + linecache module + locale module + logging package + marshal builtin + math extension + opcode module + operator extension + optparse module + os module + pickle module + pkgutil module + platform module + posix builtin + posixpath module + pwd builtin + pyexpat extension + py_compile module + random module + re module + reprlib module + runpy module + select extension + signal builtin + socket module + spwd extension + sre_compile module + sre_constants module + sre_parse module + ssl module + stat module + string module + struct module + subprocess module + sys builtin + sysconfig module + syslog extension + tempfile module + textwrap module + time extension + token module + tokenize module + traceback module + types module + unicodedata extension + warnings module + weakref module + zipimport extension + zlib extension + +Included are as well the codecs and stringprep modules, and the encodings +modules for all encodings except the multibyte encodings and the bz2 codec. + +The following modules are excluded, their import is guarded from the +importing module: + + Used in Excluded + ------------ ------------------------------------ + io _dummy_thread + os nt ntpath os2 os2emxpath mac macpath + riscos riscospath riscosenviron + optparse gettext + pickle doctest + subprocess threading + +This list was derived by looking at the modules in the perl-base package, +then adding python specific "core modules". + +TODO's +------ + +- time.strptime cannot be used. The required _strptime module is not + included in the -minimal package yet. _strptime, locale, _locale and + calendar have to be added. + +- modules used very often in the testsuite: copy, cPickle, operator. --- python3.3-3.3.0.orig/debian/pdb.1.in +++ python3.3-3.3.0/debian/pdb.1.in @@ -0,0 +1,16 @@ +.TH PDB@VER@ 1 +.SH NAME +pdb@VER@ \- the Python debugger +.SH SYNOPSIS +.PP +.B pdb@VER@ +.I script [...] +.SH DESCRIPTION +.PP +See /usr/lib/python@VER@/pdb.doc for more information on the use +of pdb. When the debugger is started, help is available via the +help command. +.SH SEE ALSO +python@VER@(1). Chapter 9 of the Python Library Reference +(The Python Debugger). Available in the python@VER@-doc package at +/usr/share/doc/python@VER@/html/lib/module-pdb.html. --- python3.3-3.3.0.orig/debian/PVER-doc.doc-base.PVER-inst.in +++ python3.3-3.3.0/debian/PVER-doc.doc-base.PVER-inst.in @@ -0,0 +1,12 @@ +Document: @PVER@-inst +Title: Installing Python Modules (v@VER@) +Author: Greg Ward +Abstract: This document describes the Python Distribution Utilities + (``Distutils'') from the end-user's point-of-view, describing how to + extend the capabilities of a standard Python installation by building + and installing third-party Python modules and extensions. +Section: Programming/Python + +Format: HTML +Index: /usr/share/doc/@PVER@/html/install/index.html +Files: /usr/share/doc/@PVER@/html/install/*.html --- python3.3-3.3.0.orig/debian/PVER-doc.doc-base.PVER-api.in +++ python3.3-3.3.0/debian/PVER-doc.doc-base.PVER-api.in @@ -0,0 +1,13 @@ +Document: @PVER@-api +Title: Python/C API Reference Manual (v@VER@) +Author: Guido van Rossum +Abstract: This manual documents the API used by C (or C++) programmers who + want to write extension modules or embed Python. It is a + companion to *Extending and Embedding the Python Interpreter*, + which describes the general principles of extension writing but + does not document the API functions in detail. +Section: Programming/Python + +Format: HTML +Index: /usr/share/doc/@PVER@/html/c-api/index.html +Files: /usr/share/doc/@PVER@/html/c-api/*.html --- python3.3-3.3.0.orig/debian/PVER-minimal.postrm.in +++ python3.3-3.3.0/debian/PVER-minimal.postrm.in @@ -0,0 +1,17 @@ +#! /bin/sh -e + +if [ "$1" = "remove" ]; then + + (find /usr/lib/@PVER@ -name '*.py[co]' | xargs rm -f {}) 2>/dev/null || true + + for d in `find /usr/lib/@PVER@ -depth -type d -empty 2> /dev/null`; do \ + while rmdir $d 2> /dev/null; do d=`dirname $d`; done; \ + done + + if [ -f /var/lib/python/@PVER@_installed ]; then + rm -f /var/lib/python/@PVER@_installed + rmdir --ignore-fail-on-non-empty /var/lib/python 2>/dev/null + fi + + rmdir --parents /usr/local/lib/@PVER@ 2>/dev/null || true +fi --- python3.3-3.3.0.orig/debian/depgraph.py +++ python3.3-3.3.0/debian/depgraph.py @@ -0,0 +1,199 @@ +#! /usr/bin/python + +# Copyright 2004 Toby Dickenson +# +# Permission is hereby granted, free of charge, to any person obtaining +# a copy of this software and associated documentation files (the +# "Software"), to deal in the Software without restriction, including +# without limitation the rights to use, copy, modify, merge, publish, +# distribute, sublicense, and/or sell copies of the Software, and to +# permit persons to whom the Software is furnished to do so, subject +# to the following conditions: +# +# The above copyright notice and this permission notice shall be included +# in all copies or substantial portions of the Software. +# +# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, +# EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF +# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. +# IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY +# CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, +# TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE +# SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. + + +import sys, getopt, colorsys, imp, md5 + +class pydepgraphdot: + + def main(self,argv): + opts,args = getopt.getopt(argv,'',['mono']) + self.colored = 1 + for o,v in opts: + if o=='--mono': + self.colored = 0 + self.render() + + def fix(self,s): + # Convert a module name to a syntactically correct node name + return s.replace('.','_') + + def render(self): + p,t = self.get_data() + + # normalise our input data + for k,d in p.items(): + for v in d.keys(): + if not p.has_key(v): + p[v] = {} + + f = self.get_output_file() + + f.write('digraph G {\n') + #f.write('concentrate = true;\n') + #f.write('ordering = out;\n') + f.write('ranksep=1.0;\n') + f.write('node [style=filled,fontname=Helvetica,fontsize=10];\n') + allkd = p.items() + allkd.sort() + for k,d in allkd: + tk = t.get(k) + if self.use(k,tk): + allv = d.keys() + allv.sort() + for v in allv: + tv = t.get(v) + if self.use(v,tv) and not self.toocommon(v,tv): + f.write('%s -> %s' % ( self.fix(k),self.fix(v) ) ) + self.write_attributes(f,self.edge_attributes(k,v)) + f.write(';\n') + f.write(self.fix(k)) + self.write_attributes(f,self.node_attributes(k,tk)) + f.write(';\n') + f.write('}\n') + + def write_attributes(self,f,a): + if a: + f.write(' [') + f.write(','.join(a)) + f.write(']') + + def node_attributes(self,k,type): + a = [] + a.append('label="%s"' % self.label(k)) + if self.colored: + a.append('fillcolor="%s"' % self.color(k,type)) + else: + a.append('fillcolor=white') + if self.toocommon(k,type): + a.append('peripheries=2') + return a + + def edge_attributes(self,k,v): + a = [] + weight = self.weight(k,v) + if weight!=1: + a.append('weight=%d' % weight) + length = self.alien(k,v) + if length: + a.append('minlen=%d' % length) + return a + + def get_data(self): + t = eval(sys.stdin.read()) + return t['depgraph'],t['types'] + + def get_output_file(self): + return sys.stdout + + def use(self,s,type): + # Return true if this module is interesting and should be drawn. Return false + # if it should be completely omitted. This is a default policy - please override. + if s=='__main__': + return 0 + #if s in ('os','sys','time','__future__','types','re','string'): + if s in ('sys'): + # nearly all modules use all of these... more or less. They add nothing to + # our diagram. + return 0 + if s.startswith('encodings.'): + return 0 + if self.toocommon(s,type): + # A module where we dont want to draw references _to_. Dot doesnt handle these + # well, so it is probably best to not draw them at all. + return 0 + return 1 + + def toocommon(self,s,type): + # Return true if references to this module are uninteresting. Such references + # do not get drawn. This is a default policy - please override. + # + if s=='__main__': + # references *to* __main__ are never interesting. omitting them means + # that main floats to the top of the page + return 1 + #if type==imp.PKG_DIRECTORY: + # # dont draw references to packages. + # return 1 + return 0 + + def weight(self,a,b): + # Return the weight of the dependency from a to b. Higher weights + # usually have shorter straighter edges. Return 1 if it has normal weight. + # A value of 4 is usually good for ensuring that a related pair of modules + # are drawn next to each other. This is a default policy - please override. + # + if b.split('.')[-1].startswith('_'): + # A module that starts with an underscore. You need a special reason to + # import these (for example random imports _random), so draw them close + # together + return 4 + return 1 + + def alien(self,a,b): + # Return non-zero if references to this module are strange, and should be drawn + # extra-long. the value defines the length, in rank. This is also good for putting some + # vertical space between seperate subsystems. This is a default policy - please override. + # + return 0 + + def label(self,s): + # Convert a module name to a formatted node label. This is a default policy - please override. + # + return '\\.\\n'.join(s.split('.')) + + def color(self,s,type): + # Return the node color for this module name. This is a default policy - please override. + # + # Calculate a color systematically based on the hash of the module name. Modules in the + # same package have the same color. Unpackaged modules are grey + t = self.normalise_module_name_for_hash_coloring(s,type) + return self.color_from_name(t) + + def normalise_module_name_for_hash_coloring(self,s,type): + if type==imp.PKG_DIRECTORY: + return s + else: + i = s.rfind('.') + if i<0: + return '' + else: + return s[:i] + + def color_from_name(self,name): + n = md5.md5(name).digest() + hf = float(ord(n[0])+ord(n[1])*0xff)/0xffff + sf = float(ord(n[2]))/0xff + vf = float(ord(n[3]))/0xff + r,g,b = colorsys.hsv_to_rgb(hf, 0.3+0.6*sf, 0.8+0.2*vf) + return '#%02x%02x%02x' % (r*256,g*256,b*256) + + +def main(): + pydepgraphdot().main(sys.argv[1:]) + +if __name__=='__main__': + main() + + + --- python3.3-3.3.0.orig/debian/README.Debian.in +++ python3.3-3.3.0/debian/README.Debian.in @@ -0,0 +1,8 @@ +The documentation for this package is in /usr/share/doc/@PVER@/. + +A draft of the "Debian Python Policy" can be found in + + /usr/share/doc/python + +Sometime it will be moved to /usr/share/doc/debian-policy in the +debian-policy package. --- python3.3-3.3.0.orig/debian/patches/langpack-gettext.diff +++ python3.3-3.3.0/debian/patches/langpack-gettext.diff @@ -0,0 +1,36 @@ +# DP: Description: support alternative gettext tree in +# DP: /usr/share/locale-langpack; if a file is present in both trees, +# DP: prefer the newer one +# DP: Upstream status: Ubuntu-Specific + +Index: b/Lib/gettext.py +=================================================================== +--- a/Lib/gettext.py ++++ b/Lib/gettext.py +@@ -378,11 +378,26 @@ + if lang == 'C': + break + mofile = os.path.join(localedir, lang, 'LC_MESSAGES', '%s.mo' % domain) ++ mofile_lp = os.path.join("/usr/share/locale-langpack", lang, ++ 'LC_MESSAGES', '%s.mo' % domain) ++ ++ # first look into the standard locale dir, then into the ++ # langpack locale dir ++ ++ # standard mo file + if os.path.exists(mofile): + if all: + result.append(mofile) + else: + return mofile ++ ++ # langpack mofile -> use it ++ if os.path.exists(mofile_lp): ++ if all: ++ result.append(mofile_lp) ++ else: ++ return mofile_lp ++ + return result + + --- python3.3-3.3.0.orig/debian/patches/link-timemodule.diff +++ python3.3-3.3.0/debian/patches/link-timemodule.diff @@ -0,0 +1,13 @@ +Index: b/Modules/Setup.dist +=================================================================== +--- a/Modules/Setup.dist ++++ b/Modules/Setup.dist +@@ -166,7 +166,7 @@ + #cmath cmathmodule.c _math.c # -lm # complex math library functions + #math mathmodule.c _math.c # -lm # math library functions, e.g. sin() + #_struct _struct.c # binary structure packing/unpacking +-#time timemodule.c # -lm # time operations and variables ++#time timemodule.c -lrt # -lm # time operations and variables + #_weakref _weakref.c # basic weak reference support + #_testcapi _testcapimodule.c # Python C API test module + #_random _randommodule.c # Random number generator --- python3.3-3.3.0.orig/debian/patches/hg-updates.diff +++ python3.3-3.3.0/debian/patches/hg-updates.diff @@ -0,0 +1,61543 @@ +# DP: hg updates of the 3.3 release branch (until 2013-01-25, 81727:5464a534e7bd). + +# hg diff -r v3.3.0 | filterdiff --exclude=.hgignore --exclude=.hgeol --exclude=.hgtags --remove-timestamps + +diff -r bd8afb90ebf2 Doc/ACKS.txt +--- a/Doc/ACKS.txt ++++ /dev/null +@@ -1,239 +0,0 @@ +-Contributors to the Python Documentation +----------------------------------------- +- +-This section lists people who have contributed in some way to the Python +-documentation. It is probably not complete -- if you feel that you or +-anyone else should be on this list, please let us know (send email to +-docs@python.org), and we'll be glad to correct the problem. +- +-.. acks:: +- +- * Aahz +- * Michael Abbott +- * Steve Alexander +- * Jim Ahlstrom +- * Fred Allen +- * A. Amoroso +- * Pehr Anderson +- * Oliver Andrich +- * Heidi Annexstad +- * Jesús Cea Avión +- * Manuel Balsera +- * Daniel Barclay +- * Chris Barker +- * Don Bashford +- * Anthony Baxter +- * Alexander Belopolsky +- * Bennett Benson +- * Jonathan Black +- * Robin Boerdijk +- * Michal Bozon +- * Aaron Brancotti +- * Georg Brandl +- * Keith Briggs +- * Ian Bruntlett +- * Lee Busby +- * Arnaud Calmettes +- * Lorenzo M. Catucci +- * Carl Cerecke +- * Mauro Cicognini +- * Gilles Civario +- * Mike Clarkson +- * Steve Clift +- * Dave Cole +- * Matthew Cowles +- * Jeremy Craven +- * Andrew Dalke +- * Ben Darnell +- * L. Peter Deutsch +- * Robert Donohue +- * Fred L. Drake, Jr. +- * Jacques Ducasse +- * Josip Dzolonga +- * Jeff Epler +- * Michael Ernst +- * Blame Andy Eskilsson +- * Carey Evans +- * Martijn Faassen +- * Carl Feynman +- * Dan Finnie +- * Hernán Martínez Foffani +- * Michael Foord +- * Stefan Franke +- * Jim Fulton +- * Peter Funk +- * Ethan Furman +- * Lele Gaifax +- * Matthew Gallagher +- * Gabriel Genellina +- * Ben Gertzfield +- * Nadim Ghaznavi +- * Jonathan Giddy +- * Matt Giuca +- * Shelley Gooch +- * Nathaniel Gray +- * Grant Griffin +- * Thomas Guettler +- * Anders Hammarquist +- * Mark Hammond +- * Harald Hanche-Olsen +- * Manus Hand +- * Gerhard Häring +- * Travis B. Hartwell +- * Tim Hatch +- * Janko Hauser +- * Ben Hayden +- * Thomas Heller +- * Bernhard Herzog +- * Magnus L. Hetland +- * Konrad Hinsen +- * Stefan Hoffmeister +- * Albert Hofkamp +- * Gregor Hoffleit +- * Steve Holden +- * Thomas Holenstein +- * Gerrit Holl +- * Rob Hooft +- * Brian Hooper +- * Randall Hopper +- * Michael Hudson +- * Eric Huss +- * Jeremy Hylton +- * Roger Irwin +- * Jack Jansen +- * Philip H. Jensen +- * Pedro Diaz Jimenez +- * Kent Johnson +- * Lucas de Jonge +- * Andreas Jung +- * Robert Kern +- * Jim Kerr +- * Jan Kim +- * Kamil Kisiel +- * Greg Kochanski +- * Guido Kollerie +- * Peter A. Koren +- * Daniel Kozan +- * Andrew M. Kuchling +- * Dave Kuhlman +- * Erno Kuusela +- * Ross Lagerwall +- * Thomas Lamb +- * Detlef Lannert +- * Piers Lauder +- * Julia Lawall +- * Glyph Lefkowitz +- * Robert Lehmann +- * Marc-André Lemburg +- * Ross Light +- * Gediminas Liktaras +- * Ulf A. Lindgren +- * Everett Lipman +- * Mirko Liss +- * Martin von Löwis +- * Fredrik Lundh +- * Jeff MacDonald +- * John Machin +- * Andrew MacIntyre +- * Vladimir Marangozov +- * Vincent Marchetti +- * Westley Martínez +- * Laura Matson +- * Daniel May +- * Rebecca McCreary +- * Doug Mennella +- * Paolo Milani +- * Skip Montanaro +- * Paul Moore +- * Ross Moore +- * Sjoerd Mullender +- * Dale Nagata +- * Trent Nelson +- * Michal Nowikowski +- * Steffen Daode Nurpmeso +- * Ng Pheng Siong +- * Koray Oner +- * Tomas Oppelstrup +- * Denis S. Otkidach +- * Zooko O'Whielacronx +- * Shriphani Palakodety +- * William Park +- * Joonas Paalasmaa +- * Harri Pasanen +- * Bo Peng +- * Tim Peters +- * Benjamin Peterson +- * Christopher Petrilli +- * Justin D. Pettit +- * Chris Phoenix +- * François Pinard +- * Paul Prescod +- * Eric S. Raymond +- * Edward K. Ream +- * Terry J. Reedy +- * Sean Reifschneider +- * Bernhard Reiter +- * Armin Rigo +- * Wes Rishel +- * Armin Ronacher +- * Jim Roskind +- * Guido van Rossum +- * Donald Wallace Rouse II +- * Mark Russell +- * Nick Russo +- * Chris Ryland +- * Constantina S. +- * Hugh Sasse +- * Bob Savage +- * Scott Schram +- * Neil Schemenauer +- * Barry Scott +- * Joakim Sernbrant +- * Justin Sheehy +- * Charlie Shepherd +- * Yue Shuaijie +- * SilentGhost +- * Michael Simcich +- * Ionel Simionescu +- * Michael Sloan +- * Gregory P. Smith +- * Roy Smith +- * Clay Spence +- * Nicholas Spies +- * Tage Stabell-Kulo +- * Frank Stajano +- * Anthony Starks +- * Greg Stein +- * Peter Stoehr +- * Mark Summerfield +- * Reuben Sumner +- * Kalle Svensson +- * Jim Tittsler +- * David Turner +- * Sandro Tosi +- * Ville Vainio +- * Nadeem Vawda +- * Martijn Vries +- * Charles G. Waldman +- * Greg Ward +- * Barry Warsaw +- * Corran Webster +- * Glyn Webster +- * Bob Weiner +- * Eddy Welbourne +- * Jeff Wheeler +- * Mats Wichmann +- * Gerry Wiener +- * Timothy Wild +- * Paul Winkler +- * Collin Winter +- * Blake Winton +- * Dan Wolfe +- * Adam Woodbeck +- * Steven Work +- * Thomas Wouters +- * Ka-Ping Yee +- * Rory Yorke +- * Moshe Zadka +- * Milan Zamazal +- * Cheng Zhang +diff -r bd8afb90ebf2 Doc/Makefile +--- a/Doc/Makefile ++++ b/Doc/Makefile +@@ -53,7 +53,7 @@ + fi + @if [ ! -d tools/pygments ]; then \ + echo "Checking out Pygments..."; \ +- svn checkout $(SVNROOT)/external/Pygments-1.3.1/pygments tools/pygments; \ ++ svn checkout $(SVNROOT)/external/Pygments-1.5dev-20120930/pygments tools/pygments; \ + fi + + update: clean checkout +@@ -185,7 +185,11 @@ + # for development releases: always build + autobuild-dev: + make update +- make dist SPHINXOPTS='-A daily=1' ++ make dist SPHINXOPTS='-A daily=1 -A versionswitcher=1' ++ ++# for quick rebuilds (HTML only) ++autobuild-html: ++ make html SPHINXOPTS='-A daily=1 -A versionswitcher=1' + + # for stable releases: only build if not in pre-release stage (alpha, beta, rc) + autobuild-stable: +@@ -194,3 +198,4 @@ + exit 1;; \ + esac + @make autobuild-dev ++ +diff -r bd8afb90ebf2 Doc/README.txt +--- a/Doc/README.txt ++++ b/Doc/README.txt +@@ -135,7 +135,7 @@ + as long as you don't change or remove the copyright notice: + + ---------------------------------------------------------------------- +-Copyright (c) 2000-2012 Python Software Foundation. ++Copyright (c) 2000-2013 Python Software Foundation. + All rights reserved. + + Copyright (c) 2000 BeOpen.com. +diff -r bd8afb90ebf2 Doc/about.rst +--- a/Doc/about.rst ++++ b/Doc/about.rst +@@ -29,8 +29,13 @@ + See :ref:`reporting-bugs` for information how to report bugs in this + documentation, or Python itself. + +-.. including the ACKS file here so that it can be maintained separately +-.. include:: ACKS.txt ++ ++Contributors to the Python Documentation ++---------------------------------------- ++ ++Many people have contributed to the Python language, the Python standard ++library, and the Python documentation. See :source:`Misc/ACKS` in the Python ++source distribution for a partial list of contributors. + + It is only with the input and contributions of the Python community + that Python has such wonderful documentation -- Thank You! +diff -r bd8afb90ebf2 Doc/c-api/buffer.rst +--- a/Doc/c-api/buffer.rst ++++ b/Doc/c-api/buffer.rst +@@ -1,5 +1,10 @@ + .. highlightlang:: c + ++.. index:: ++ single: buffer protocol ++ single: buffer interface; (see buffer protocol) ++ single: buffer object; (see buffer protocol) ++ + .. _bufferobjects: + + Buffer Protocol +@@ -10,9 +15,6 @@ + .. sectionauthor:: Stefan Krah + + +-.. index:: +- single: buffer interface +- + Certain objects available in Python wrap access to an underlying memory + array or *buffer*. Such objects include the built-in :class:`bytes` and + :class:`bytearray`, and some extension types like :class:`array.array`. +@@ -24,8 +26,8 @@ + then desirable, in some situations, to access that buffer directly and + without intermediate copying. + +-Python provides such a facility at the C level in the form of the *buffer +-protocol*. This protocol has two sides: ++Python provides such a facility at the C level in the form of the :ref:`buffer ++protocol `. This protocol has two sides: + + .. index:: single: PyBufferProcs + +diff -r bd8afb90ebf2 Doc/c-api/import.rst +--- a/Doc/c-api/import.rst ++++ b/Doc/c-api/import.rst +@@ -76,7 +76,7 @@ + UTF-8 encoded string instead of a Unicode object. + + .. versionchanged:: 3.3 +- Negative values for **level** are no longer accepted. ++ Negative values for *level* are no longer accepted. + + .. c:function:: PyObject* PyImport_Import(PyObject *name) + +diff -r bd8afb90ebf2 Doc/c-api/index.rst +--- a/Doc/c-api/index.rst ++++ b/Doc/c-api/index.rst +@@ -4,9 +4,6 @@ + Python/C API Reference Manual + ################################## + +-:Release: |version| +-:Date: |today| +- + This manual documents the API used by C and C++ programmers who want to write + extension modules or embed Python. It is a companion to :ref:`extending-index`, + which describes the general principles of extension writing but does not +diff -r bd8afb90ebf2 Doc/c-api/object.rst +--- a/Doc/c-api/object.rst ++++ b/Doc/c-api/object.rst +@@ -160,11 +160,11 @@ + a string similar to that returned by :c:func:`PyObject_Repr` in Python 2. + Called by the :func:`ascii` built-in function. + ++ .. index:: string; PyObject_Str (C function) ++ + + .. c:function:: PyObject* PyObject_Str(PyObject *o) + +- .. index:: builtin: str +- + Compute a string representation of object *o*. Returns the string + representation on success, *NULL* on failure. This is the equivalent of the + Python expression ``str(o)``. Called by the :func:`str` built-in function +diff -r bd8afb90ebf2 Doc/c-api/sys.rst +--- a/Doc/c-api/sys.rst ++++ b/Doc/c-api/sys.rst +@@ -61,12 +61,6 @@ + Return the object *name* from the :mod:`sys` module or *NULL* if it does + not exist, without setting an exception. + +-.. c:function:: FILE *PySys_GetFile(char *name, FILE *def) +- +- Return the :c:type:`FILE*` associated with the object *name* in the +- :mod:`sys` module, or *def* if *name* is not in the module or is not associated +- with a :c:type:`FILE*`. +- + .. c:function:: int PySys_SetObject(char *name, PyObject *v) + + Set *name* in the :mod:`sys` module to *v* unless *v* is *NULL*, in which +diff -r bd8afb90ebf2 Doc/c-api/unicode.rst +--- a/Doc/c-api/unicode.rst ++++ b/Doc/c-api/unicode.rst +@@ -735,15 +735,15 @@ + The current locale encoding can be used to decode text from the operating + system. + +-.. c:function:: PyObject* PyUnicode_DecodeLocaleAndSize(const char *str, Py_ssize_t len, int surrogateescape) +- +- Decode a string from the current locale encoding. The decoder is strict if +- *surrogateescape* is equal to zero, otherwise it uses the +- ``'surrogateescape'`` error handler (:pep:`383`) to escape undecodable +- bytes. If a byte sequence can be decoded as a surrogate character and +- *surrogateescape* is not equal to zero, the byte sequence is escaped using +- the ``'surrogateescape'`` error handler instead of being decoded. *str* +- must end with a null character but cannot contain embedded null characters. ++.. c:function:: PyObject* PyUnicode_DecodeLocaleAndSize(const char *str, \ ++ Py_ssize_t len, \ ++ const char *errors) ++ ++ Decode a string from the current locale encoding. The supported ++ error handlers are ``"strict"`` and ``"surrogateescape"`` ++ (:pep:`383`). The decoder uses ``"strict"`` error handler if ++ *errors* is ``NULL``. *str* must end with a null character but ++ cannot contain embedded null characters. + + .. seealso:: + +@@ -754,7 +754,7 @@ + .. versionadded:: 3.3 + + +-.. c:function:: PyObject* PyUnicode_DecodeLocale(const char *str, int surrogateescape) ++.. c:function:: PyObject* PyUnicode_DecodeLocale(const char *str, const char *errors) + + Similar to :c:func:`PyUnicode_DecodeLocaleAndSize`, but compute the string + length using :c:func:`strlen`. +@@ -762,12 +762,13 @@ + .. versionadded:: 3.3 + + +-.. c:function:: PyObject* PyUnicode_EncodeLocale(PyObject *unicode, int surrogateescape) +- +- Encode a Unicode object to the current locale encoding. The encoder is +- strict if *surrogateescape* is equal to zero, otherwise it uses the +- ``'surrogateescape'`` error handler (:pep:`383`). Return a :class:`bytes` +- object. *str* cannot contain embedded null characters. ++.. c:function:: PyObject* PyUnicode_EncodeLocale(PyObject *unicode, const char *errors) ++ ++ Encode a Unicode object to the current locale encoding. The ++ supported error handlers are ``"strict"`` and ``"surrogateescape"`` ++ (:pep:`383`). The encoder uses ``"strict"`` error handler if ++ *errors* is ``NULL``. Return a :class:`bytes` object. *str* cannot ++ contain embedded null characters. + + .. seealso:: + +@@ -813,7 +814,7 @@ + .. c:function:: PyObject* PyUnicode_DecodeFSDefaultAndSize(const char *s, Py_ssize_t size) + + Decode a string using :c:data:`Py_FileSystemDefaultEncoding` and the +- ``'surrogateescape'`` error handler, or ``'strict'`` on Windows. ++ ``"surrogateescape"`` error handler, or ``"strict"`` on Windows. + + If :c:data:`Py_FileSystemDefaultEncoding` is not set, fall back to the + locale encoding. +@@ -826,13 +827,13 @@ + :c:func:`PyUnicode_DecodeLocaleAndSize`. + + .. versionchanged:: 3.2 +- Use ``'strict'`` error handler on Windows. ++ Use ``"strict"`` error handler on Windows. + + + .. c:function:: PyObject* PyUnicode_DecodeFSDefault(const char *s) + + Decode a null-terminated string using :c:data:`Py_FileSystemDefaultEncoding` +- and the ``'surrogateescape'`` error handler, or ``'strict'`` on Windows. ++ and the ``"surrogateescape"`` error handler, or ``"strict"`` on Windows. + + If :c:data:`Py_FileSystemDefaultEncoding` is not set, fall back to the + locale encoding. +@@ -840,13 +841,13 @@ + Use :c:func:`PyUnicode_DecodeFSDefaultAndSize` if you know the string length. + + .. versionchanged:: 3.2 +- Use ``'strict'`` error handler on Windows. ++ Use ``"strict"`` error handler on Windows. + + + .. c:function:: PyObject* PyUnicode_EncodeFSDefault(PyObject *unicode) + + Encode a Unicode object to :c:data:`Py_FileSystemDefaultEncoding` with the +- ``'surrogateescape'`` error handler, or ``'strict'`` on Windows, and return ++ ``"surrogateescape"`` error handler, or ``"strict"`` on Windows, and return + :class:`bytes`. Note that the resulting :class:`bytes` object may contain + null bytes. + +@@ -1083,8 +1084,6 @@ + After completion, *\*byteorder* is set to the current byte order at the end + of input data. + +- In a narrow build codepoints outside the BMP will be decoded as surrogate pairs. +- + If *byteorder* is *NULL*, the codec starts in native order mode. + + Return *NULL* if an exception was raised by the codec. +diff -r bd8afb90ebf2 Doc/copyright.rst +--- a/Doc/copyright.rst ++++ b/Doc/copyright.rst +@@ -4,7 +4,7 @@ + + Python and this documentation is: + +-Copyright © 2001-2012 Python Software Foundation. All rights reserved. ++Copyright © 2001-2013 Python Software Foundation. All rights reserved. + + Copyright © 2000 BeOpen.com. All rights reserved. + +diff -r bd8afb90ebf2 Doc/data/refcounts.dat +--- a/Doc/data/refcounts.dat ++++ b/Doc/data/refcounts.dat +@@ -1315,10 +1315,6 @@ + PySys_AddXOption:void::: + PySys_AddXOption:const wchar_t*:s:: + +-PySys_GetFile:FILE*::: +-PySys_GetFile:char*:name:: +-PySys_GetFile:FILE*:def:: +- + PySys_GetObject:PyObject*::0: + PySys_GetObject:char*:name:: + +diff -r bd8afb90ebf2 Doc/distutils/apiref.rst +--- a/Doc/distutils/apiref.rst ++++ b/Doc/distutils/apiref.rst +@@ -992,6 +992,12 @@ + destination of the symlink will be copied. *update* and *verbose* are the same + as for :func:`copy_file`. + ++ Files in *src* that begin with :file:`.nfs` are skipped (more information on ++ these files is available in answer D2 of the `NFS FAQ page ++ `_. ++ ++ .. versionchanged:: 3.3.1 ++ NFS files are ignored. + + .. function:: remove_tree(directory[, verbose=0, dry_run=0]) + +diff -r bd8afb90ebf2 Doc/distutils/index.rst +--- a/Doc/distutils/index.rst ++++ b/Doc/distutils/index.rst +@@ -6,8 +6,6 @@ + + :Authors: Greg Ward, Anthony Baxter + :Email: distutils-sig@python.org +-:Release: |version| +-:Date: |today| + + This document describes the Python Distribution Utilities ("Distutils") from + the module developer's point of view, describing how to use the Distutils to +diff -r bd8afb90ebf2 Doc/distutils/packageindex.rst +--- a/Doc/distutils/packageindex.rst ++++ b/Doc/distutils/packageindex.rst +@@ -43,9 +43,9 @@ + Maintainers may edit the package information, but not designate other Owners or + Maintainers. + +-By default PyPI will list all versions of a given package. To hide certain +-versions, the Hidden property should be set to yes. This must be edited through +-the web interface. ++By default PyPI displays only the newest version of a given package. The web ++interface lets one change this default behavior and manually select which ++versions to display and hide. + + + .. _pypirc: +diff -r bd8afb90ebf2 Doc/distutils/uploading.rst +--- a/Doc/distutils/uploading.rst ++++ b/Doc/distutils/uploading.rst +@@ -25,21 +25,21 @@ + entered password. This is useful if you do not want to store a clear text + password in the :file:`$HOME/.pypirc` file. + +-You can specify another PyPI server with the :option:`--repository=*url*` option:: ++You can specify another PyPI server with the ``--repository=url`` option:: + + python setup.py sdist bdist_wininst upload -r http://example.com/pypi + + See section :ref:`pypirc` for more on defining several servers. + +-You can use the :option:`--sign` option to tell :command:`upload` to sign each ++You can use the ``--sign`` option to tell :command:`upload` to sign each + uploaded file using GPG (GNU Privacy Guard). The :program:`gpg` program must + be available for execution on the system :envvar:`PATH`. You can also specify +-which key to use for signing using the :option:`--identity=*name*` option. ++which key to use for signing using the ``--identity=name`` option. + +-Other :command:`upload` options include :option:`--repository=` or +-:option:`--repository=

` where *url* is the url of the server and ++Other :command:`upload` options include ``--repository=url`` or ++``--repository=section`` where *url* is the url of the server and + *section* the name of the section in :file:`$HOME/.pypirc`, and +-:option:`--show-response` (which displays the full response text from the PyPI ++``--show-response`` (which displays the full response text from the PyPI + server for help in debugging upload problems). + + PyPI package display +diff -r bd8afb90ebf2 Doc/extending/embedding.rst +--- a/Doc/extending/embedding.rst ++++ b/Doc/extending/embedding.rst +@@ -58,6 +58,7 @@ + int + main(int argc, char *argv[]) + { ++ Py_SetProgramName(argv[0]); /* optional but recommended */ + Py_Initialize(); + PyRun_SimpleString("from time import time,ctime\n" + "print('Today is', ctime(time()))\n"); +@@ -65,9 +66,11 @@ + return 0; + } + +-The above code first initializes the Python interpreter with ++The :c:func:`Py_SetProgramName` function should be called before ++:c:func:`Py_Initialize` to inform the interpreter about paths to Python run-time ++libraries. Next, the Python interpreter is initialized with + :c:func:`Py_Initialize`, followed by the execution of a hard-coded Python script +-that print the date and time. Afterwards, the :c:func:`Py_Finalize` call shuts ++that prints the date and time. Afterwards, the :c:func:`Py_Finalize` call shuts + the interpreter down, followed by the end of the program. In a real program, + you may want to get the Python script from another source, perhaps a text-editor + routine, a file, or a database. Getting the Python code from a file can better +diff -r bd8afb90ebf2 Doc/extending/index.rst +--- a/Doc/extending/index.rst ++++ b/Doc/extending/index.rst +@@ -4,9 +4,6 @@ + Extending and Embedding the Python Interpreter + ################################################## + +-:Release: |version| +-:Date: |today| +- + This document describes how to write modules in C or C++ to extend the Python + interpreter with new modules. Those modules can define new functions but also + new object types and their methods. The document also describes how to embed +diff -r bd8afb90ebf2 Doc/extending/newtypes.rst +--- a/Doc/extending/newtypes.rst ++++ b/Doc/extending/newtypes.rst +@@ -982,13 +982,13 @@ + } + + ++.. index:: ++ single: string; object representation ++ builtin: repr ++ + Object Presentation + ------------------- + +-.. index:: +- builtin: repr +- builtin: str +- + In Python, there are two ways to generate a textual representation of an object: + the :func:`repr` function, and the :func:`str` function. (The :func:`print` + function just calls :func:`str`.) These handlers are both optional. +@@ -1277,9 +1277,9 @@ + bit does not indicate that the slot values are non-*NULL*. The flag may be set + to indicate the presence of a slot, but a slot may still be unfilled.) :: + +- PyNumberMethods tp_as_number; +- PySequenceMethods tp_as_sequence; +- PyMappingMethods tp_as_mapping; ++ PyNumberMethods *tp_as_number; ++ PySequenceMethods *tp_as_sequence; ++ PyMappingMethods *tp_as_mapping; + + If you wish your object to be able to act like a number, a sequence, or a + mapping object, then you place the address of a structure that implements the C +diff -r bd8afb90ebf2 Doc/faq/design.rst +--- a/Doc/faq/design.rst ++++ b/Doc/faq/design.rst +@@ -214,7 +214,7 @@ + generic for a group of types and which were intended to work even for objects + that didn't have methods at all (e.g. tuples). It is also convenient to have a + function that can readily be applied to an amorphous collection of objects when +-you use the functional features of Python (``map()``, ``apply()`` et al). ++you use the functional features of Python (``map()``, ``zip()`` et al). + + In fact, implementing ``len()``, ``max()``, ``min()`` as a built-in function is + actually less code than implementing them as methods for each type. One can +@@ -345,9 +345,6 @@ + + Answer 2: Fortunately, there is `Stackless Python `_, + which has a completely redesigned interpreter loop that avoids the C stack. +-It's still experimental but looks very promising. Although it is binary +-compatible with standard Python, it's still unclear whether Stackless will make +-it into the core -- maybe it's just too revolutionary. + + + Why can't lambda forms contain statements? +@@ -709,7 +706,7 @@ + requested again. This is called "memoizing", and can be implemented like this:: + + # Callers will never provide a third parameter for this function. +- def expensive (arg1, arg2, _cache={}): ++ def expensive(arg1, arg2, _cache={}): + if (arg1, arg2) in _cache: + return _cache[(arg1, arg2)] + +@@ -730,11 +727,11 @@ + reasonable uses of the "go" or "goto" constructs of C, Fortran, and other + languages. For example:: + +- class label: pass # declare a label ++ class label(Exception): pass # declare a label + + try: + ... +- if (condition): raise label() # goto label ++ if condition: raise label() # goto label + ... + except label: # where to goto + pass +diff -r bd8afb90ebf2 Doc/faq/index.rst +--- a/Doc/faq/index.rst ++++ b/Doc/faq/index.rst +@@ -1,10 +1,9 @@ ++.. _faq-index: ++ + ################################### + Python Frequently Asked Questions + ################################### + +-:Release: |version| +-:Date: |today| +- + .. toctree:: + :maxdepth: 1 + +diff -r bd8afb90ebf2 Doc/faq/programming.rst +--- a/Doc/faq/programming.rst ++++ b/Doc/faq/programming.rst +@@ -206,6 +206,58 @@ + declaration for identifying side-effects. + + ++Why do lambdas defined in a loop with different values all return the same result? ++---------------------------------------------------------------------------------- ++ ++Assume you use a for loop to define a few different lambdas (or even plain ++functions), e.g.:: ++ ++ squares = [] ++ for x in range(5): ++ squares.append(lambda: x**2) ++ ++This gives you a list that contains 5 lambdas that calculate ``x**2``. You ++might expect that, when called, they would return, respectively, ``0``, ``1``, ++``4``, ``9``, and ``16``. However, when you actually try you will see that ++they all return ``16``:: ++ ++ >>> squares[2]() ++ 16 ++ >>> squares[4]() ++ 16 ++ ++This happens because ``x`` is not local to the lambdas, but is defined in ++the outer scope, and it is accessed when the lambda is called --- not when it ++is defined. At the end of the loop, the value of ``x`` is ``4``, so all the ++functions now return ``4**2``, i.e. ``16``. You can also verify this by ++changing the value of ``x`` and see how the results of the lambdas change:: ++ ++ >>> x = 8 ++ >>> squares[2]() ++ 64 ++ ++In order to avoid this, you need to save the values in variables local to the ++lambdas, so that they don't rely on the value of the global ``x``:: ++ ++ squares = [] ++ for x in range(5): ++ squares.append(lambda n=x: n**2) ++ ++Here, ``n=x`` creates a new variable ``n`` local to the lambda and computed ++when the lambda is defined so that it has the same value that ``x`` had at ++that point in the loop. This means that the value of ``n`` will be ``0`` ++in the first lambda, ``1`` in the second, ``2`` in the third, and so on. ++Therefore each lambda will now return the correct result:: ++ ++ >>> squares[2]() ++ 4 ++ >>> squares[4]() ++ 16 ++ ++Note that this behaviour is not peculiar to lambdas, but applies to regular ++functions too. ++ ++ + How do I share global variables across modules? + ------------------------------------------------ + +@@ -313,6 +365,31 @@ + g(x, *args, **kwargs) + + ++.. index:: ++ single: argument; difference from parameter ++ single: parameter; difference from argument ++ ++.. _faq-argument-vs-parameter: ++ ++What is the difference between arguments and parameters? ++-------------------------------------------------------- ++ ++:term:`Parameters ` are defined by the names that appear in a ++function definition, whereas :term:`arguments ` are the values ++actually passed to a function when calling it. Parameters define what types of ++arguments a function can accept. For example, given the function definition:: ++ ++ def func(foo, bar=None, **kwargs): ++ pass ++ ++*foo*, *bar* and *kwargs* are parameters of ``func``. However, when calling ++``func``, for example:: ++ ++ func(42, bar=314, extra=somevar) ++ ++the values ``42``, ``314``, and ``somevar`` are arguments. ++ ++ + How do I write a function with output parameters (call by reference)? + --------------------------------------------------------------------- + +diff -r bd8afb90ebf2 Doc/faq/windows.rst +--- a/Doc/faq/windows.rst ++++ b/Doc/faq/windows.rst +@@ -17,9 +17,7 @@ + + This is not necessarily a straightforward question. If you are already familiar + with running programs from the Windows command line then everything will seem +-obvious; otherwise, you might need a little more guidance. There are also +-differences between Windows 95, 98, NT, ME, 2000 and XP which can add to the +-confusion. ++obvious; otherwise, you might need a little more guidance. + + .. sidebar:: |Python Development on XP|_ + :subtitle: `Python Development on XP`_ +@@ -36,7 +34,7 @@ + Unless you use some sort of integrated development environment, you will end up + *typing* Windows commands into what is variously referred to as a "DOS window" + or "Command prompt window". Usually you can create such a window from your +-Start menu; under Windows 2000 the menu selection is :menuselection:`Start --> ++Start menu; under Windows 7 the menu selection is :menuselection:`Start --> + Programs --> Accessories --> Command Prompt`. You should be able to recognize + when you have started such a window because you will see a Windows "command + prompt", which usually looks like this:: +@@ -46,23 +44,27 @@ + The letter may be different, and there might be other things after it, so you + might just as easily see something like:: + +- D:\Steve\Projects\Python> ++ D:\YourName\Projects\Python> + + depending on how your computer has been set up and what else you have recently + done with it. Once you have started such a window, you are well on the way to + running Python programs. + + You need to realize that your Python scripts have to be processed by another +-program called the Python interpreter. The interpreter reads your script, ++program called the Python *interpreter*. The interpreter reads your script, + compiles it into bytecodes, and then executes the bytecodes to run your + program. So, how do you arrange for the interpreter to handle your Python? + + First, you need to make sure that your command window recognises the word + "python" as an instruction to start the interpreter. If you have opened a + command window, you should try entering the command ``python`` and hitting +-return. You should then see something like:: ++return.:: + +- Python 2.2 (#28, Dec 21 2001, 12:21:22) [MSC 32 bit (Intel)] on win32 ++ C:\Users\YourName> python ++ ++You should then see something like:: ++ ++ Python 3.3.0 (v3.3.0:bd8afb90ebf2, Sep 29 2012, 10:55:48) [MSC v.1600 32 bit (Intel)] on win32 + Type "help", "copyright", "credits" or "license" for more information. + >>> + +@@ -82,7 +84,7 @@ + Windows command prompt. + + You may also find that you have a Start-menu entry such as :menuselection:`Start +---> Programs --> Python 2.2 --> Python (command line)` that results in you ++--> Programs --> Python 3.3 --> Python (command line)` that results in you + seeing the ``>>>`` prompt in a new window. If so, the window will disappear + after you enter the Ctrl-Z character; Windows is running a single "python" + command in the window, and closes it when you terminate the interpreter. +@@ -90,8 +92,7 @@ + If the ``python`` command, instead of displaying the interpreter prompt ``>>>``, + gives you a message like:: + +- 'python' is not recognized as an internal or external command, +- operable program or batch file. ++ 'python' is not recognized as an internal or external command, operable program or batch file. + + .. sidebar:: |Adding Python to DOS Path|_ + :subtitle: `Adding Python to DOS Path`_ +@@ -120,115 +121,33 @@ + dir C:\py* + + will probably tell you where it is installed; the usual location is something +-like ``C:\Python23``. Otherwise you will be reduced to a search of your whole ++like ``C:\Python33``. Otherwise you will be reduced to a search of your whole + disk ... use :menuselection:`Tools --> Find` or hit the :guilabel:`Search` + button and look for "python.exe". Supposing you discover that Python is +-installed in the ``C:\Python23`` directory (the default at the time of writing), ++installed in the ``C:\Python33`` directory (the default at the time of writing), + you should make sure that entering the command :: + +- c:\Python23\python ++ c:\Python33\python + + starts up the interpreter as above (and don't forget you'll need a "CTRL-Z" and +-an "Enter" to get out of it). Once you have verified the directory, you need to +-add it to the start-up routines your computer goes through. For older versions +-of Windows the easiest way to do this is to edit the ``C:\AUTOEXEC.BAT`` +-file. You would want to add a line like the following to ``AUTOEXEC.BAT``:: ++an "Enter" to get out of it). Once you have verified the directory, you can ++add it to the system path to make it easier to start Python by just running ++the ``python`` command. This is currently an option in the installer as of ++CPython 3.3. + +- PATH C:\Python23;%PATH% +- +-For Windows NT, 2000 and (I assume) XP, you will need to add a string such as :: +- +- ;C:\Python23 +- +-to the current setting for the PATH environment variable, which you will find in +-the properties window of "My Computer" under the "Advanced" tab. Note that if +-you have sufficient privilege you might get a choice of installing the settings +-either for the Current User or for System. The latter is preferred if you want +-everybody to be able to run Python on the machine. +- +-If you aren't confident doing any of these manipulations yourself, ask for help! +-At this stage you may want to reboot your system to make absolutely sure the new +-setting has taken effect. You probably won't need to reboot for Windows NT, XP +-or 2000. You can also avoid it in earlier versions by editing the file +-``C:\WINDOWS\COMMAND\CMDINIT.BAT`` instead of ``AUTOEXEC.BAT``. +- +-You should now be able to start a new command window, enter ``python`` at the +-``C:\>`` (or whatever) prompt, and see the ``>>>`` prompt that indicates the +-Python interpreter is reading interactive commands. +- +-Let's suppose you have a program called ``pytest.py`` in directory +-``C:\Steve\Projects\Python``. A session to run that program might look like +-this:: +- +- C:\> cd \Steve\Projects\Python +- C:\Steve\Projects\Python> python pytest.py +- +-Because you added a file name to the command to start the interpreter, when it +-starts up it reads the Python script in the named file, compiles it, executes +-it, and terminates, so you see another ``C:\>`` prompt. You might also have +-entered :: +- +- C:\> python \Steve\Projects\Python\pytest.py +- +-if you hadn't wanted to change your current directory. +- +-Under NT, 2000 and XP you may well find that the installation process has also +-arranged that the command ``pytest.py`` (or, if the file isn't in the current +-directory, ``C:\Steve\Projects\Python\pytest.py``) will automatically recognize +-the ".py" extension and run the Python interpreter on the named file. Using this +-feature is fine, but *some* versions of Windows have bugs which mean that this +-form isn't exactly equivalent to using the interpreter explicitly, so be +-careful. +- +-The important things to remember are: +- +-1. Start Python from the Start Menu, or make sure the PATH is set correctly so +- Windows can find the Python interpreter. :: +- +- python +- +- should give you a '>>>' prompt from the Python interpreter. Don't forget the +- CTRL-Z and ENTER to terminate the interpreter (and, if you started the window +- from the Start Menu, make the window disappear). +- +-2. Once this works, you run programs with commands:: +- +- python {program-file} +- +-3. When you know the commands to use you can build Windows shortcuts to run the +- Python interpreter on any of your scripts, naming particular working +- directories, and adding them to your menus. Take a look at :: +- +- python --help +- +- if your needs are complex. +- +-4. Interactive mode (where you see the ``>>>`` prompt) is best used for checking +- that individual statements and expressions do what you think they will, and +- for developing code by experiment. +- ++More information about environment variables can be found on the ++:ref:`Using Python on Windows ` page. + + How do I make Python scripts executable? + ---------------------------------------- + +-On Windows 2000, the standard Python installer already associates the .py ++On Windows, the standard Python installer already associates the .py + extension with a file type (Python.File) and gives that file type an open + command that runs the interpreter (``D:\Program Files\Python\python.exe "%1" + %*``). This is enough to make scripts executable from the command prompt as + 'foo.py'. If you'd rather be able to execute the script by simple typing 'foo' + with no extension you need to add .py to the PATHEXT environment variable. + +-On Windows NT, the steps taken by the installer as described above allow you to +-run a script with 'foo.py', but a longtime bug in the NT command processor +-prevents you from redirecting the input or output of any script executed in this +-way. This is often important. +- +-The incantation for making a Python script executable under WinNT is to give the +-file an extension of .cmd and add the following as the first line:: +- +- @setlocal enableextensions & python -x %~f0 %* & goto :EOF +- +- + Why does Python sometimes take so long to start? + ------------------------------------------------ + +@@ -246,22 +165,11 @@ + offender. + + +-Where is Freeze for Windows? +----------------------------- ++How do I make an executable from a Python script? ++------------------------------------------------- + +-"Freeze" is a program that allows you to ship a Python program as a single +-stand-alone executable file. It is *not* a compiler; your programs don't run +-any faster, but they are more easily distributable, at least to platforms with +-the same OS and CPU. Read the README file of the freeze program for more +-disclaimers. +- +-You can use freeze on Windows, but you must download the source tree (see +-http://www.python.org/download/source). The freeze program is in the +-``Tools\freeze`` subdirectory of the source tree. +- +-You need the Microsoft VC++ compiler, and you probably need to build Python. +-The required project files are in the PCbuild directory. +- ++See http://www.py2exe.org/ for a distutils extension that allows you ++to create console and GUI executables from Python code. + + Is a ``*.pyd`` file the same as a DLL? + -------------------------------------- +@@ -292,7 +200,7 @@ + be a DLL to handle importing modules that are themselves DLL's. (This is the + first key undocumented fact.) Instead, link to :file:`python{NN}.dll`; it is + typically installed in ``C:\Windows\System``. *NN* is the Python version, a +- number such as "23" for Python 2.3. ++ number such as "33" for Python 3.3. + + You can link to Python in two different ways. Load-time linking means + linking against :file:`python{NN}.lib`, while run-time linking means linking +@@ -376,47 +284,6 @@ + object that supports read and write, so all you need is a Python object + (defined in your extension module) that contains read() and write() methods. + +- +-How do I use Python for CGI? +----------------------------- +- +-On the Microsoft IIS server or on the Win95 MS Personal Web Server you set up +-Python in the same way that you would set up any other scripting engine. +- +-Run regedt32 and go to:: +- +- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap +- +-and enter the following line (making any specific changes that your system may +-need):: +- +- .py :REG_SZ: c:\\python.exe -u %s %s +- +-This line will allow you to call your script with a simple reference like: +-``http://yourserver/scripts/yourscript.py`` provided "scripts" is an +-"executable" directory for your server (which it usually is by default). The +-:option:`-u` flag specifies unbuffered and binary mode for stdin - needed when +-working with binary data. +- +-In addition, it is recommended that using ".py" may not be a good idea for the +-file extensions when used in this context (you might want to reserve ``*.py`` +-for support modules and use ``*.cgi`` or ``*.cgp`` for "main program" scripts). +- +-In order to set up Internet Information Services 5 to use Python for CGI +-processing, please see the following links: +- +- http://www.e-coli.net/pyiis_server.html (for Win2k Server) +- http://www.e-coli.net/pyiis.html (for Win2k pro) +- +-Configuring Apache is much simpler. In the Apache configuration file +-``httpd.conf``, add the following line at the end of the file:: +- +- ScriptInterpreterSource Registry +- +-Then, give your Python CGI-scripts the extension .py and put them in the cgi-bin +-directory. +- +- + How do I keep editors from inserting tabs into my Python source? + ---------------------------------------------------------------- + +@@ -460,116 +327,6 @@ + to console subprocesses which are designed to handle those signals. See + :func:`os.kill` for further details. + +- +-Why does os.path.isdir() fail on NT shared directories? +-------------------------------------------------------- +- +-The solution appears to be always append the "\\" on the end of shared +-drives. +- +- >>> import os +- >>> os.path.isdir( '\\\\rorschach\\public') +- 0 +- >>> os.path.isdir( '\\\\rorschach\\public\\') +- 1 +- +-It helps to think of share points as being like drive letters. Example:: +- +- k: is not a directory +- k:\ is a directory +- k:\media is a directory +- k:\media\ is not a directory +- +-The same rules apply if you substitute "k:" with "\\conky\foo":: +- +- \\conky\foo is not a directory +- \\conky\foo\ is a directory +- \\conky\foo\media is a directory +- \\conky\foo\media\ is not a directory +- +- +-cgi.py (or other CGI programming) doesn't work sometimes on NT or win95! +------------------------------------------------------------------------- +- +-Be sure you have the latest python.exe, that you are using python.exe rather +-than a GUI version of Python and that you have configured the server to execute +-:: +- +- "...\python.exe -u ..." +- +-for the CGI execution. The :option:`-u` (unbuffered) option on NT and Win95 +-prevents the interpreter from altering newlines in the standard input and +-output. Without it post/multipart requests will seem to have the wrong length +-and binary (e.g. GIF) responses may get garbled (resulting in broken images, PDF +-files, and other binary downloads failing). +- +- +-Why doesn't os.popen() work in PythonWin on NT? +------------------------------------------------ +- +-The reason that os.popen() doesn't work from within PythonWin is due to a bug in +-Microsoft's C Runtime Library (CRT). The CRT assumes you have a Win32 console +-attached to the process. +- +-You should use the win32pipe module's popen() instead which doesn't depend on +-having an attached Win32 console. +- +-Example:: +- +- import win32pipe +- f = win32pipe.popen('dir /c c:\\') +- print(f.readlines()) +- f.close() +- +- +-Why doesn't os.popen()/win32pipe.popen() work on Win9x? +-------------------------------------------------------- +- +-There is a bug in Win9x that prevents os.popen/win32pipe.popen* from +-working. The good news is there is a way to work around this problem. The +-Microsoft Knowledge Base article that you need to lookup is: Q150956. You will +-find links to the knowledge base at: http://support.microsoft.com/. +- +- +-PyRun_SimpleFile() crashes on Windows but not on Unix; why? +------------------------------------------------------------ +- +-This is very sensitive to the compiler vendor, version and (perhaps) even +-options. If the FILE* structure in your embedding program isn't the same as is +-assumed by the Python interpreter it won't work. +- +-The Python 1.5.* DLLs (``python15.dll``) are all compiled with MS VC++ 5.0 and +-with multithreading-DLL options (``/MD``). +- +-If you can't change compilers or flags, try using :c:func:`Py_RunSimpleString`. +-A trick to get it to run an arbitrary file is to construct a call to +-:func:`exec` and :func:`open` with the name of your file as argument. +- +-Also note that you can not mix-and-match Debug and Release versions. If you +-wish to use the Debug Multithreaded DLL, then your module *must* have ``_d`` +-appended to the base name. +- +- +-Importing _tkinter fails on Windows 95/98: why? +------------------------------------------------- +- +-Sometimes, the import of _tkinter fails on Windows 95 or 98, complaining with a +-message like the following:: +- +- ImportError: DLL load failed: One of the library files needed +- to run this application cannot be found. +- +-It could be that you haven't installed Tcl/Tk, but if you did install Tcl/Tk, +-and the Wish application works correctly, the problem may be that its installer +-didn't manage to edit the autoexec.bat file correctly. It tries to add a +-statement that changes the PATH environment variable to include the Tcl/Tk 'bin' +-subdirectory, but sometimes this edit doesn't quite work. Opening it with +-notepad usually reveals what the problem is. +- +-(One additional hint, noted by David Szafranski: you can't use long filenames +-here; e.g. use ``C:\PROGRA~1\Tcl\bin`` instead of ``C:\Program Files\Tcl\bin``.) +- +- + How do I extract the downloaded documentation on Windows? + --------------------------------------------------------- + +@@ -581,38 +338,3 @@ + able to handle it. (If your copy of WinZip doesn't, get a newer one from + http://www.winzip.com.) + +- +-Missing cw3215mt.dll (or missing cw3215.dll) +--------------------------------------------- +- +-Sometimes, when using Tkinter on Windows, you get an error that cw3215mt.dll or +-cw3215.dll is missing. +- +-Cause: you have an old Tcl/Tk DLL built with cygwin in your path (probably +-``C:\Windows``). You must use the Tcl/Tk DLLs from the standard Tcl/Tk +-installation (Python 1.5.2 comes with one). +- +- +-Warning about CTL3D32 version from installer +--------------------------------------------- +- +-The Python installer issues a warning like this:: +- +- This version uses CTL3D32.DLL which is not the correct version. +- This version is used for windows NT applications only. +- +-Tim Peters: +- +- This is a Microsoft DLL, and a notorious source of problems. The message +- means what it says: you have the wrong version of this DLL for your operating +- system. The Python installation did not cause this -- something else you +- installed previous to this overwrote the DLL that came with your OS (probably +- older shareware of some sort, but there's no way to tell now). If you search +- for "CTL3D32" using any search engine (AltaVista, for example), you'll find +- hundreds and hundreds of web pages complaining about the same problem with +- all sorts of installation programs. They'll point you to ways to get the +- correct version reinstalled on your system (since Python doesn't cause this, +- we can't fix it). +- +-David A Burton has written a little program to fix this. Go to +-http://www.burtonsys.com/downloads.html and click on "ctl3dfix.zip". +diff -r bd8afb90ebf2 Doc/glossary.rst +--- a/Doc/glossary.rst ++++ b/Doc/glossary.rst +@@ -40,16 +40,34 @@ + ABCs with the :mod:`abc` module. + + argument +- A value passed to a function or method, assigned to a named local +- variable in the function body. A function or method may have both +- positional arguments and keyword arguments in its definition. +- Positional and keyword arguments may be variable-length: ``*`` accepts +- or passes (if in the function definition or call) several positional +- arguments in a list, while ``**`` does the same for keyword arguments +- in a dictionary. ++ A value passed to a :term:`function` (or :term:`method`) when calling the ++ function. There are two types of arguments: + +- Any expression may be used within the argument list, and the evaluated +- value is passed to the local variable. ++ * :dfn:`keyword argument`: an argument preceded by an identifier (e.g. ++ ``name=``) in a function call or passed as a value in a dictionary ++ preceded by ``**``. For example, ``3`` and ``5`` are both keyword ++ arguments in the following calls to :func:`complex`:: ++ ++ complex(real=3, imag=5) ++ complex(**{'real': 3, 'imag': 5}) ++ ++ * :dfn:`positional argument`: an argument that is not a keyword argument. ++ Positional arguments can appear at the beginning of an argument list ++ and/or be passed as elements of an :term:`iterable` preceded by ``*``. ++ For example, ``3`` and ``5`` are both positional arguments in the ++ following calls:: ++ ++ complex(3, 5) ++ complex(*(3, 5)) ++ ++ Arguments are assigned to the named local variables in a function body. ++ See the :ref:`calls` section for the rules governing this assignment. ++ Syntactically, any expression can be used to represent an argument; the ++ evaluated value is assigned to the local variable. ++ ++ See also the :term:`parameter` glossary entry, the FAQ question on ++ :ref:`the difference between arguments and parameters ++ `, and :pep:`362`. + + attribute + A value associated with an object which is referenced by name using +@@ -222,8 +240,9 @@ + + function + A series of statements which returns some value to a caller. It can also +- be passed zero or more arguments which may be used in the execution of +- the body. See also :term:`argument` and :term:`method`. ++ be passed zero or more :term:`arguments ` which may be used in ++ the execution of the body. See also :term:`parameter`, :term:`method`, ++ and the :ref:`function` section. + + __future__ + A pseudo-module which programmers can use to enable new language features +@@ -348,24 +367,24 @@ + slowly. See also :term:`interactive`. + + iterable +- An object capable of returning its members one at a +- time. Examples of iterables include all sequence types (such as +- :class:`list`, :class:`str`, and :class:`tuple`) and some non-sequence +- types like :class:`dict` and :class:`file` and objects of any classes you +- define with an :meth:`__iter__` or :meth:`__getitem__` method. Iterables +- can be used in a :keyword:`for` loop and in many other places where a +- sequence is needed (:func:`zip`, :func:`map`, ...). When an iterable +- object is passed as an argument to the built-in function :func:`iter`, it +- returns an iterator for the object. This iterator is good for one pass +- over the set of values. When using iterables, it is usually not necessary +- to call :func:`iter` or deal with iterator objects yourself. The ``for`` ++ An object capable of returning its members one at a time. Examples of ++ iterables include all sequence types (such as :class:`list`, :class:`str`, ++ and :class:`tuple`) and some non-sequence types like :class:`dict`, ++ :term:`file objects `, and objects of any classes you define ++ with an :meth:`__iter__` or :meth:`__getitem__` method. Iterables can be ++ used in a :keyword:`for` loop and in many other places where a sequence is ++ needed (:func:`zip`, :func:`map`, ...). When an iterable object is passed ++ as an argument to the built-in function :func:`iter`, it returns an ++ iterator for the object. This iterator is good for one pass over the set ++ of values. When using iterables, it is usually not necessary to call ++ :func:`iter` or deal with iterator objects yourself. The ``for`` + statement does that automatically for you, creating a temporary unnamed + variable to hold the iterator for the duration of the loop. See also + :term:`iterator`, :term:`sequence`, and :term:`generator`. + + iterator + An object representing a stream of data. Repeated calls to the iterator's +- :meth:`__next__` method (or passing it to the built-in function ++ :meth:`~iterator.__next__` method (or passing it to the built-in function + :func:`next`) return successive items in the stream. When no more data + are available a :exc:`StopIteration` exception is raised instead. At this + point, the iterator object is exhausted and any further calls to its +@@ -402,10 +421,7 @@ + ` for examples of how to create and use key functions. + + keyword argument +- Arguments which are preceded with a ``variable_name=`` in the call. +- The variable name designates the local name in the function to which the +- value is assigned. ``**`` is used to accept or pass a dictionary of +- keyword arguments. See :term:`argument`. ++ See :term:`argument`. + + lambda + An anonymous inline function consisting of a single :term:`expression` +@@ -548,6 +564,53 @@ + subpackages. Technically, a package is a Python module with an + ``__path__`` attribute. + ++ parameter ++ A named entity in a :term:`function` (or method) definition that ++ specifies an :term:`argument` (or in some cases, arguments) that the ++ function can accept. There are five types of parameters: ++ ++ * :dfn:`positional-or-keyword`: specifies an argument that can be passed ++ either :term:`positionally ` or as a :term:`keyword argument ++ `. This is the default kind of parameter, for example *foo* ++ and *bar* in the following:: ++ ++ def func(foo, bar=None): ... ++ ++ * :dfn:`positional-only`: specifies an argument that can be supplied only ++ by position. Python has no syntax for defining positional-only ++ parameters. However, some built-in functions have positional-only ++ parameters (e.g. :func:`abs`). ++ ++ * :dfn:`keyword-only`: specifies an argument that can be supplied only ++ by keyword. Keyword-only parameters can be defined by including a ++ single var-positional parameter or bare ``*`` in the parameter list ++ of the function definition before them, for example *kw_only1* and ++ *kw_only2* in the following:: ++ ++ def func(arg, *, kw_only1, kw_only2): ... ++ ++ * :dfn:`var-positional`: specifies that an arbitrary sequence of ++ positional arguments can be provided (in addition to any positional ++ arguments already accepted by other parameters). Such a parameter can ++ be defined by prepending the parameter name with ``*``, for example ++ *args* in the following:: ++ ++ def func(*args, **kwargs): ... ++ ++ * :dfn:`var-keyword`: specifies that arbitrarily many keyword arguments ++ can be provided (in addition to any keyword arguments already accepted ++ by other parameters). Such a parameter can be defined by prepending ++ the parameter name with ``**``, for example *kwargs* in the example ++ above. ++ ++ Parameters can specify both optional and required arguments, as well as ++ default values for some optional arguments. ++ ++ See also the :term:`argument` glossary entry, the FAQ question on ++ :ref:`the difference between arguments and parameters ++ `, the :class:`inspect.Parameter` class, the ++ :ref:`function` section, and :pep:`362`. ++ + path entry + A single location on the :term:`import path` which the :term:`path + based finder` consults to find modules for importing. +@@ -571,11 +634,7 @@ + that contribute to a namespace package, as defined in :pep:`420`. + + positional argument +- The arguments assigned to local names inside a function or method, +- determined by the order in which they were given in the call. ``*`` is +- used to either accept multiple positional arguments (when in the +- definition), or pass several arguments as a list to a function. See +- :term:`argument`. ++ See :term:`argument`. + + provisional package + A provisional package is one which has been deliberately excluded from +@@ -660,7 +719,7 @@ + sequence + An :term:`iterable` which supports efficient element access using integer + indices via the :meth:`__getitem__` special method and defines a +- :meth:`len` method that returns the length of the sequence. ++ :meth:`__len__` method that returns the length of the sequence. + Some built-in sequence types are :class:`list`, :class:`str`, + :class:`tuple`, and :class:`bytes`. Note that :class:`dict` also + supports :meth:`__getitem__` and :meth:`__len__`, but is considered a +diff -r bd8afb90ebf2 Doc/howto/argparse.rst +--- a/Doc/howto/argparse.rst ++++ b/Doc/howto/argparse.rst +@@ -2,7 +2,7 @@ + Argparse Tutorial + ***************** + +-:author: Tshepang Lekhonkhobe ++:author: Tshepang Lekhonkhobe + + .. _argparse-tutorial: + +diff -r bd8afb90ebf2 Doc/howto/cporting.rst +--- a/Doc/howto/cporting.rst ++++ b/Doc/howto/cporting.rst +@@ -100,25 +100,6 @@ + used in Python 2 was removed. In the C-API, ``PyInt_*`` functions + are replaced by their ``PyLong_*`` equivalents. + +-The best course of action here is using the ``PyInt_*`` functions aliased to +-``PyLong_*`` found in :file:`intobject.h`. The abstract ``PyNumber_*`` APIs +-can also be used in some cases. :: +- +- #include "Python.h" +- #include "intobject.h" +- +- static PyObject * +- add_ints(PyObject *self, PyObject *args) { +- int one, two; +- PyObject *result; +- +- if (!PyArg_ParseTuple(args, "ii:add_ints", &one, &two)) +- return NULL; +- +- return PyInt_FromLong(one + two); +- } +- +- + + Module initialization and state + =============================== +@@ -253,7 +234,7 @@ + + * :c:func:`PyCapsule_GetName` always returns NULL. + +- * :c:func:`PyCapsule_SetName` always throws an exception and ++ * :c:func:`PyCapsule_SetName` always raises an exception and + returns failure. (Since there's no way to store a name + in a CObject, noisy failure of :c:func:`PyCapsule_SetName` + was deemed preferable to silent failure here. If this is +diff -r bd8afb90ebf2 Doc/howto/functional.rst +--- a/Doc/howto/functional.rst ++++ b/Doc/howto/functional.rst +@@ -181,26 +181,26 @@ + + An iterator is an object representing a stream of data; this object returns the + data one element at a time. A Python iterator must support a method called +-``__next__()`` that takes no arguments and always returns the next element of +-the stream. If there are no more elements in the stream, ``__next__()`` must +-raise the ``StopIteration`` exception. Iterators don't have to be finite, +-though; it's perfectly reasonable to write an iterator that produces an infinite +-stream of data. ++:meth:`~iterator.__next__` that takes no arguments and always returns the next ++element of the stream. If there are no more elements in the stream, ++:meth:`~iterator.__next__` must raise the :exc:`StopIteration` exception. ++Iterators don't have to be finite, though; it's perfectly reasonable to write ++an iterator that produces an infinite stream of data. + + The built-in :func:`iter` function takes an arbitrary object and tries to return + an iterator that will return the object's contents or elements, raising + :exc:`TypeError` if the object doesn't support iteration. Several of Python's + built-in data types support iteration, the most common being lists and +-dictionaries. An object is called an **iterable** object if you can get an +-iterator for it. ++dictionaries. An object is called :term:`iterable` if you can get an iterator ++for it. + + You can experiment with the iteration interface manually: + + >>> L = [1,2,3] + >>> it = iter(L) +- >>> it ++ >>> it #doctest: +ELLIPSIS + <...iterator object at ...> +- >>> it.__next__() ++ >>> it.__next__() # same as next(it) + 1 + >>> next(it) + 2 +@@ -213,9 +213,9 @@ + >>> + + Python expects iterable objects in several different contexts, the most +-important being the ``for`` statement. In the statement ``for X in Y``, Y must +-be an iterator or some object for which ``iter()`` can create an iterator. +-These two statements are equivalent:: ++important being the :keyword:`for` statement. In the statement ``for X in Y``, ++Y must be an iterator or some object for which :func:`iter` can create an ++iterator. These two statements are equivalent:: + + + for i in iter(obj): +@@ -246,16 +246,16 @@ + iterator argument and will return the largest or smallest element. The ``"in"`` + and ``"not in"`` operators also support iterators: ``X in iterator`` is true if + X is found in the stream returned by the iterator. You'll run into obvious +-problems if the iterator is infinite; ``max()``, ``min()`` ++problems if the iterator is infinite; :func:`max`, :func:`min` + will never return, and if the element X never appears in the stream, the + ``"in"`` and ``"not in"`` operators won't return either. + + Note that you can only go forward in an iterator; there's no way to get the + previous element, reset the iterator, or make a copy of it. Iterator objects + can optionally provide these additional capabilities, but the iterator protocol +-only specifies the ``next()`` method. Functions may therefore consume all of +-the iterator's output, and if you need to do something different with the same +-stream, you'll have to create a new iterator. ++only specifies the :meth:`~iterator.__next__` method. Functions may therefore ++consume all of the iterator's output, and if you need to do something different ++with the same stream, you'll have to create a new iterator. + + + +@@ -267,15 +267,11 @@ + iterator. + + Calling :func:`iter` on a dictionary returns an iterator that will loop over the +-dictionary's keys: +- +-.. not a doctest since dict ordering varies across Pythons +- +-:: ++dictionary's keys:: + + >>> m = {'Jan': 1, 'Feb': 2, 'Mar': 3, 'Apr': 4, 'May': 5, 'Jun': 6, + ... 'Jul': 7, 'Aug': 8, 'Sep': 9, 'Oct': 10, 'Nov': 11, 'Dec': 12} +- >>> for key in m: ++ >>> for key in m: #doctest: +SKIP + ... print(key, m[key]) + Mar 3 + Feb 2 +@@ -296,18 +292,19 @@ + Applying :func:`iter` to a dictionary always loops over the keys, but + dictionaries have methods that return other iterators. If you want to iterate + over values or key/value pairs, you can explicitly call the +-:meth:`values` or :meth:`items` methods to get an appropriate iterator. ++:meth:`~dict.values` or :meth:`~dict.items` methods to get an appropriate ++iterator. + + The :func:`dict` constructor can accept an iterator that returns a finite stream + of ``(key, value)`` tuples: + + >>> L = [('Italy', 'Rome'), ('France', 'Paris'), ('US', 'Washington DC')] +- >>> dict(iter(L)) ++ >>> dict(iter(L)) #doctest: +SKIP + {'Italy': 'Rome', 'US': 'Washington DC', 'France': 'Paris'} + +-Files also support iteration by calling the ``readline()`` method until there +-are no more lines in the file. This means you can read each line of a file like +-this:: ++Files also support iteration by calling the :meth:`~io.TextIOBase.readline` ++method until there are no more lines in the file. This means you can read each ++line of a file like this:: + + for line in file: + # do something for each line +@@ -410,12 +407,9 @@ + lengths of all the sequences. If you have two lists of length 3, the output + list is 9 elements long: + +-.. doctest:: +- :options: +NORMALIZE_WHITESPACE +- + >>> seq1 = 'abc' + >>> seq2 = (1,2,3) +- >>> [(x,y) for x in seq1 for y in seq2] ++ >>> [(x, y) for x in seq1 for y in seq2] #doctest: +NORMALIZE_WHITESPACE + [('a', 1), ('a', 2), ('a', 3), + ('b', 1), ('b', 2), ('b', 3), + ('c', 1), ('c', 2), ('c', 3)] +@@ -425,9 +419,9 @@ + comprehension below is a syntax error, while the second one is correct:: + + # Syntax error +- [ x,y for x in seq1 for y in seq2] ++ [x, y for x in seq1 for y in seq2] + # Correct +- [ (x,y) for x in seq1 for y in seq2] ++ [(x, y) for x in seq1 for y in seq2] + + + Generators +@@ -448,15 +442,13 @@ + + Here's the simplest example of a generator function: + +-.. testcode:: ++ >>> def generate_ints(N): ++ ... for i in range(N): ++ ... yield i + +- def generate_ints(N): +- for i in range(N): +- yield i +- +-Any function containing a ``yield`` keyword is a generator function; this is +-detected by Python's :term:`bytecode` compiler which compiles the function +-specially as a result. ++Any function containing a :keyword:`yield` keyword is a generator function; ++this is detected by Python's :term:`bytecode` compiler which compiles the ++function specially as a result. + + When you call a generator function, it doesn't return a single value; instead it + returns a generator object that supports the iterator protocol. On executing +@@ -464,12 +456,13 @@ + ``return`` statement. The big difference between ``yield`` and a ``return`` + statement is that on reaching a ``yield`` the generator's state of execution is + suspended and local variables are preserved. On the next call to the +-generator's ``.__next__()`` method, the function will resume executing. ++generator's :meth:`~generator.__next__` method, the function will resume ++executing. + + Here's a sample usage of the ``generate_ints()`` generator: + + >>> gen = generate_ints(3) +- >>> gen ++ >>> gen #doctest: +ELLIPSIS + + >>> next(gen) + 0 +@@ -486,22 +479,21 @@ + You could equally write ``for i in generate_ints(5)``, or ``a,b,c = + generate_ints(3)``. + +-Inside a generator function, the ``return`` statement can only be used without a +-value, and signals the end of the procession of values; after executing a +-``return`` the generator cannot return any further values. ``return`` with a +-value, such as ``return 5``, is a syntax error inside a generator function. The +-end of the generator's results can also be indicated by raising +-``StopIteration`` manually, or by just letting the flow of execution fall off +-the bottom of the function. ++Inside a generator function, ``return value`` is semantically equivalent to ++``raise StopIteration(value)``. If no value is returned or the bottom of the ++function is reached, the procession of values ends and the generator cannot ++return any further values. + + You could achieve the effect of generators manually by writing your own class + and storing all the local variables of the generator as instance variables. For + example, returning a list of integers could be done by setting ``self.count`` to +-0, and having the ``__next__()`` method increment ``self.count`` and return it. ++0, and having the :meth:`~iterator.__next__` method increment ``self.count`` and ++return it. + However, for a moderately complicated generator, writing a corresponding class + can be much messier. + +-The test suite included with Python's library, ``test_generators.py``, contains ++The test suite included with Python's library, ++:source:`Lib/test/test_generators.py`, contains + a number of more interesting examples. Here's one generator that implements an + in-order traversal of a tree using generators recursively. :: + +@@ -544,23 +536,23 @@ + The parentheses aren't always necessary, but it's easier to always add them + instead of having to remember when they're needed. + +-(PEP 342 explains the exact rules, which are that a ``yield``-expression must ++(:pep:`342` explains the exact rules, which are that a ``yield``-expression must + always be parenthesized except when it occurs at the top-level expression on the + right-hand side of an assignment. This means you can write ``val = yield i`` + but have to use parentheses when there's an operation, as in ``val = (yield i) + + 12``.) + +-Values are sent into a generator by calling its ``send(value)`` method. This +-method resumes the generator's code and the ``yield`` expression returns the +-specified value. If the regular ``__next__()`` method is called, the ``yield`` +-returns ``None``. ++Values are sent into a generator by calling its :meth:`send(value) ++` method. This method resumes the generator's code and the ++``yield`` expression returns the specified value. If the regular ++:meth:`~generator.__next__` method is called, the ``yield`` returns ``None``. + + Here's a simple counter that increments by 1 and allows changing the value of + the internal counter. + + .. testcode:: + +- def counter (maximum): ++ def counter(maximum): + i = 0 + while i < maximum: + val = (yield i) +@@ -572,16 +564,16 @@ + + And here's an example of changing the counter: + +- >>> it = counter(10) +- >>> next(it) ++ >>> it = counter(10) #doctest: +SKIP ++ >>> next(it) #doctest: +SKIP + 0 +- >>> next(it) ++ >>> next(it) #doctest: +SKIP + 1 +- >>> it.send(8) ++ >>> it.send(8) #doctest: +SKIP + 8 +- >>> next(it) ++ >>> next(it) #doctest: +SKIP + 9 +- >>> next(it) ++ >>> next(it) #doctest: +SKIP + Traceback (most recent call last): + File "t.py", line 15, in ? + it.next() +@@ -589,20 +581,23 @@ + + Because ``yield`` will often be returning ``None``, you should always check for + this case. Don't just use its value in expressions unless you're sure that the +-``send()`` method will be the only method used resume your generator function. ++:meth:`~generator.send` method will be the only method used resume your ++generator function. + +-In addition to ``send()``, there are two other new methods on generators: ++In addition to :meth:`~generator.send`, there are two other methods on ++generators: + +-* ``throw(type, value=None, traceback=None)`` is used to raise an exception +- inside the generator; the exception is raised by the ``yield`` expression +- where the generator's execution is paused. ++* :meth:`throw(type, value=None, traceback=None) ` is used to ++ raise an exception inside the generator; the exception is raised by the ++ ``yield`` expression where the generator's execution is paused. + +-* ``close()`` raises a :exc:`GeneratorExit` exception inside the generator to +- terminate the iteration. On receiving this exception, the generator's code +- must either raise :exc:`GeneratorExit` or :exc:`StopIteration`; catching the +- exception and doing anything else is illegal and will trigger a +- :exc:`RuntimeError`. ``close()`` will also be called by Python's garbage +- collector when the generator is garbage-collected. ++* :meth:`~generator.close` raises a :exc:`GeneratorExit` exception inside the ++ generator to terminate the iteration. On receiving this exception, the ++ generator's code must either raise :exc:`GeneratorExit` or ++ :exc:`StopIteration`; catching the exception and doing anything else is ++ illegal and will trigger a :exc:`RuntimeError`. :meth:`~generator.close` ++ will also be called by Python's garbage collector when the generator is ++ garbage-collected. + + If you need to run cleanup code when a :exc:`GeneratorExit` occurs, I suggest + using a ``try: ... finally:`` suite instead of catching :exc:`GeneratorExit`. +@@ -624,13 +619,12 @@ + Two of Python's built-in functions, :func:`map` and :func:`filter` duplicate the + features of generator expressions: + +-``map(f, iterA, iterB, ...)`` returns an iterator over the sequence ++:func:`map(f, iterA, iterB, ...) ` returns an iterator over the sequence + ``f(iterA[0], iterB[0]), f(iterA[1], iterB[1]), f(iterA[2], iterB[2]), ...``. + + >>> def upper(s): + ... return s.upper() + +- + >>> list(map(upper, ['sentence', 'fragment'])) + ['SENTENCE', 'FRAGMENT'] + >>> [upper(s) for s in ['sentence', 'fragment']] +@@ -638,11 +632,11 @@ + + You can of course achieve the same effect with a list comprehension. + +-``filter(predicate, iter)`` returns an iterator over all the sequence elements +-that meet a certain condition, and is similarly duplicated by list +-comprehensions. A **predicate** is a function that returns the truth value of +-some condition; for use with :func:`filter`, the predicate must take a single +-value. ++:func:`filter(predicate, iter) ` returns an iterator over all the ++sequence elements that meet a certain condition, and is similarly duplicated by ++list comprehensions. A **predicate** is a function that returns the truth ++value of some condition; for use with :func:`filter`, the predicate must take a ++single value. + + >>> def is_even(x): + ... return (x % 2) == 0 +@@ -657,8 +651,8 @@ + [0, 2, 4, 6, 8] + + +-``enumerate(iter)`` counts off the elements in the iterable, returning 2-tuples +-containing the count and each element. :: ++:func:`enumerate(iter) ` counts off the elements in the iterable, ++returning 2-tuples containing the count and each element. :: + + >>> for item in enumerate(['subject', 'verb', 'object']): + ... print(item) +@@ -674,29 +668,28 @@ + if line.strip() == '': + print('Blank line at line #%i' % i) + +-``sorted(iterable, [key=None], [reverse=False])`` collects all the elements of +-the iterable into a list, sorts the list, and returns the sorted result. The +-``key``, and ``reverse`` arguments are passed through to the constructed list's +-``.sort()`` method. :: ++:func:`sorted(iterable, key=None, reverse=False) ` collects all the ++elements of the iterable into a list, sorts the list, and returns the sorted ++result. The *key*, and *reverse* arguments are passed through to the ++constructed list's :meth:`~list.sort` method. :: + + >>> import random + >>> # Generate 8 random numbers between [0, 10000) + >>> rand_list = random.sample(range(10000), 8) +- >>> rand_list ++ >>> rand_list #doctest: +SKIP + [769, 7953, 9828, 6431, 8442, 9878, 6213, 2207] +- >>> sorted(rand_list) ++ >>> sorted(rand_list) #doctest: +SKIP + [769, 2207, 6213, 6431, 7953, 8442, 9828, 9878] +- >>> sorted(rand_list, reverse=True) ++ >>> sorted(rand_list, reverse=True) #doctest: +SKIP + [9878, 9828, 8442, 7953, 6431, 6213, 2207, 769] + +-(For a more detailed discussion of sorting, see the Sorting mini-HOWTO in the +-Python wiki at http://wiki.python.org/moin/HowTo/Sorting.) ++(For a more detailed discussion of sorting, see the :ref:`sortinghowto`.) + + +-The ``any(iter)`` and ``all(iter)`` built-ins look at the truth values of an +-iterable's contents. :func:`any` returns True if any element in the iterable is +-a true value, and :func:`all` returns True if all of the elements are true +-values: ++The :func:`any(iter) ` and :func:`all(iter) ` built-ins look at the ++truth values of an iterable's contents. :func:`any` returns True if any element ++in the iterable is a true value, and :func:`all` returns True if all of the ++elements are true values: + + >>> any([0,1,0]) + True +@@ -712,7 +705,7 @@ + True + + +-``zip(iterA, iterB, ...)`` takes one element from each iterable and ++:func:`zip(iterA, iterB, ...) ` takes one element from each iterable and + returns them in a tuple:: + + zip(['a', 'b', 'c'], (1, 2, 3)) => +@@ -752,42 +745,44 @@ + Creating new iterators + ---------------------- + +-``itertools.count(n)`` returns an infinite stream of integers, increasing by 1 +-each time. You can optionally supply the starting number, which defaults to 0:: ++:func:`itertools.count(n) ` returns an infinite stream of ++integers, increasing by 1 each time. You can optionally supply the starting ++number, which defaults to 0:: + + itertools.count() => + 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, ... + itertools.count(10) => + 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, ... + +-``itertools.cycle(iter)`` saves a copy of the contents of a provided iterable +-and returns a new iterator that returns its elements from first to last. The +-new iterator will repeat these elements infinitely. :: ++:func:`itertools.cycle(iter) ` saves a copy of the contents of ++a provided iterable and returns a new iterator that returns its elements from ++first to last. The new iterator will repeat these elements infinitely. :: + + itertools.cycle([1,2,3,4,5]) => + 1, 2, 3, 4, 5, 1, 2, 3, 4, 5, ... + +-``itertools.repeat(elem, [n])`` returns the provided element ``n`` times, or +-returns the element endlessly if ``n`` is not provided. :: ++:func:`itertools.repeat(elem, [n]) ` returns the provided ++element *n* times, or returns the element endlessly if *n* is not provided. :: + + itertools.repeat('abc') => + abc, abc, abc, abc, abc, abc, abc, abc, abc, abc, ... + itertools.repeat('abc', 5) => + abc, abc, abc, abc, abc + +-``itertools.chain(iterA, iterB, ...)`` takes an arbitrary number of iterables as +-input, and returns all the elements of the first iterator, then all the elements +-of the second, and so on, until all of the iterables have been exhausted. :: ++:func:`itertools.chain(iterA, iterB, ...) ` takes an arbitrary ++number of iterables as input, and returns all the elements of the first ++iterator, then all the elements of the second, and so on, until all of the ++iterables have been exhausted. :: + + itertools.chain(['a', 'b', 'c'], (1, 2, 3)) => + a, b, c, 1, 2, 3 + +-``itertools.islice(iter, [start], stop, [step])`` returns a stream that's a +-slice of the iterator. With a single ``stop`` argument, it will return the +-first ``stop`` elements. If you supply a starting index, you'll get +-``stop-start`` elements, and if you supply a value for ``step``, elements will +-be skipped accordingly. Unlike Python's string and list slicing, you can't use +-negative values for ``start``, ``stop``, or ``step``. :: ++:func:`itertools.islice(iter, [start], stop, [step]) ` returns ++a stream that's a slice of the iterator. With a single *stop* argument, it ++will return the first *stop* elements. If you supply a starting index, you'll ++get *stop-start* elements, and if you supply a value for *step*, elements ++will be skipped accordingly. Unlike Python's string and list slicing, you can't ++use negative values for *start*, *stop*, or *step*. :: + + itertools.islice(range(10), 8) => + 0, 1, 2, 3, 4, 5, 6, 7 +@@ -796,9 +791,10 @@ + itertools.islice(range(10), 2, 8, 2) => + 2, 4, 6 + +-``itertools.tee(iter, [n])`` replicates an iterator; it returns ``n`` +-independent iterators that will all return the contents of the source iterator. +-If you don't supply a value for ``n``, the default is 2. Replicating iterators ++:func:`itertools.tee(iter, [n]) ` replicates an iterator; it ++returns *n* independent iterators that will all return the contents of the ++source iterator. ++If you don't supply a value for *n*, the default is 2. Replicating iterators + requires saving some of the contents of the source iterator, so this can consume + significant memory if the iterator is large and one of the new iterators is + consumed more than the others. :: +@@ -816,19 +812,21 @@ + Calling functions on elements + ----------------------------- + +-The ``operator`` module contains a set of functions corresponding to Python's +-operators. Some examples are ``operator.add(a, b)`` (adds two values), +-``operator.ne(a, b)`` (same as ``a!=b``), and ``operator.attrgetter('id')`` +-(returns a callable that fetches the ``"id"`` attribute). ++The :mod:`operator` module contains a set of functions corresponding to Python's ++operators. Some examples are :func:`operator.add(a, b) ` (adds ++two values), :func:`operator.ne(a, b) ` (same as ``a != b``), and ++:func:`operator.attrgetter('id') ` ++(returns a callable that fetches the ``.id`` attribute). + +-``itertools.starmap(func, iter)`` assumes that the iterable will return a stream +-of tuples, and calls ``f()`` using these tuples as the arguments:: ++:func:`itertools.starmap(func, iter) ` assumes that the ++iterable will return a stream of tuples, and calls *func* using these tuples as ++the arguments:: + + itertools.starmap(os.path.join, +- [('/usr', 'bin', 'java'), ('/bin', 'python'), +- ('/usr', 'bin', 'perl'),('/usr', 'bin', 'ruby')]) ++ [('/bin', 'python'), ('/usr', 'bin', 'java'), ++ ('/usr', 'bin', 'perl'), ('/usr', 'bin', 'ruby')]) + => +- /usr/bin/java, /bin/python, /usr/bin/perl, /usr/bin/ruby ++ /bin/python, /usr/bin/java, /usr/bin/perl, /usr/bin/ruby + + + Selecting elements +@@ -837,20 +835,18 @@ + Another group of functions chooses a subset of an iterator's elements based on a + predicate. + +-``itertools.filterfalse(predicate, iter)`` is the opposite, returning all +-elements for which the predicate returns false:: ++:func:`itertools.filterfalse(predicate, iter) ` is the ++opposite, returning all elements for which the predicate returns false:: + + itertools.filterfalse(is_even, itertools.count()) => + 1, 3, 5, 7, 9, 11, 13, 15, ... + +-``itertools.takewhile(predicate, iter)`` returns elements for as long as the +-predicate returns true. Once the predicate returns false, the iterator will +-signal the end of its results. +- +-:: ++:func:`itertools.takewhile(predicate, iter) ` returns ++elements for as long as the predicate returns true. Once the predicate returns ++false, the iterator will signal the end of its results. :: + + def less_than_10(x): +- return (x < 10) ++ return x < 10 + + itertools.takewhile(less_than_10, itertools.count()) => + 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 +@@ -858,10 +854,9 @@ + itertools.takewhile(is_even, itertools.count()) => + 0 + +-``itertools.dropwhile(predicate, iter)`` discards elements while the predicate +-returns true, and then returns the rest of the iterable's results. +- +-:: ++:func:`itertools.dropwhile(predicate, iter) ` discards ++elements while the predicate returns true, and then returns the rest of the ++iterable's results. :: + + itertools.dropwhile(less_than_10, itertools.count()) => + 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, ... +@@ -873,14 +868,14 @@ + Grouping elements + ----------------- + +-The last function I'll discuss, ``itertools.groupby(iter, key_func=None)``, is +-the most complicated. ``key_func(elem)`` is a function that can compute a key +-value for each element returned by the iterable. If you don't supply a key +-function, the key is simply each element itself. ++The last function I'll discuss, :func:`itertools.groupby(iter, key_func=None) ++`, is the most complicated. ``key_func(elem)`` is a function ++that can compute a key value for each element returned by the iterable. If you ++don't supply a key function, the key is simply each element itself. + +-``groupby()`` collects all the consecutive elements from the underlying iterable +-that have the same key value, and returns a stream of 2-tuples containing a key +-value and an iterator for the elements with that key. ++:func:`~itertools.groupby` collects all the consecutive elements from the ++underlying iterable that have the same key value, and returns a stream of ++2-tuples containing a key value and an iterator for the elements with that key. + + :: + +@@ -890,7 +885,7 @@ + ... + ] + +- def get_state (city_state): ++ def get_state(city_state): + return city_state[1] + + itertools.groupby(city_list, get_state) => +@@ -906,9 +901,9 @@ + iterator-3 => + ('Flagstaff', 'AZ'), ('Phoenix', 'AZ'), ('Tucson', 'AZ') + +-``groupby()`` assumes that the underlying iterable's contents will already be +-sorted based on the key. Note that the returned iterators also use the +-underlying iterable, so you have to consume the results of iterator-1 before ++:func:`~itertools.groupby` assumes that the underlying iterable's contents will ++already be sorted based on the key. Note that the returned iterators also use ++the underlying iterable, so you have to consume the results of iterator-1 before + requesting iterator-2 and its corresponding key. + + +@@ -926,33 +921,34 @@ + ``g(b, c)`` that's equivalent to ``f(1, b, c)``; you're filling in a value for + one of ``f()``'s parameters. This is called "partial function application". + +-The constructor for ``partial`` takes the arguments ``(function, arg1, arg2, +-... kwarg1=value1, kwarg2=value2)``. The resulting object is callable, so you +-can just call it to invoke ``function`` with the filled-in arguments. ++The constructor for :func:`~functools.partial` takes the arguments ++``(function, arg1, arg2, ..., kwarg1=value1, kwarg2=value2)``. The resulting ++object is callable, so you can just call it to invoke ``function`` with the ++filled-in arguments. + + Here's a small but realistic example:: + + import functools + +- def log (message, subsystem): +- "Write the contents of 'message' to the specified subsystem." ++ def log(message, subsystem): ++ """Write the contents of 'message' to the specified subsystem.""" + print('%s: %s' % (subsystem, message)) + ... + + server_log = functools.partial(log, subsystem='server') + server_log('Unable to open socket') + +-``functools.reduce(func, iter, [initial_value])`` cumulatively performs an +-operation on all the iterable's elements and, therefore, can't be applied to +-infinite iterables. (Note it is not in :mod:`builtins`, but in the +-:mod:`functools` module.) ``func`` must be a function that takes two elements +-and returns a single value. :func:`functools.reduce` takes the first two +-elements A and B returned by the iterator and calculates ``func(A, B)``. It +-then requests the third element, C, calculates ``func(func(A, B), C)``, combines +-this result with the fourth element returned, and continues until the iterable +-is exhausted. If the iterable returns no values at all, a :exc:`TypeError` +-exception is raised. If the initial value is supplied, it's used as a starting +-point and ``func(initial_value, A)`` is the first calculation. :: ++:func:`functools.reduce(func, iter, [initial_value]) ` ++cumulatively performs an operation on all the iterable's elements and, ++therefore, can't be applied to infinite iterables. *func* must be a function ++that takes two elements and returns a single value. :func:`functools.reduce` ++takes the first two elements A and B returned by the iterator and calculates ++``func(A, B)``. It then requests the third element, C, calculates ++``func(func(A, B), C)``, combines this result with the fourth element returned, ++and continues until the iterable is exhausted. If the iterable returns no ++values at all, a :exc:`TypeError` exception is raised. If the initial value is ++supplied, it's used as a starting point and ``func(initial_value, A)`` is the ++first calculation. :: + + >>> import operator, functools + >>> functools.reduce(operator.concat, ['A', 'BB', 'C']) +@@ -978,8 +974,8 @@ + >>> sum([]) + 0 + +-For many uses of :func:`functools.reduce`, though, it can be clearer to just write the +-obvious :keyword:`for` loop:: ++For many uses of :func:`functools.reduce`, though, it can be clearer to just ++write the obvious :keyword:`for` loop:: + + import functools + # Instead of: +@@ -1023,28 +1019,23 @@ + existing_files = filter(os.path.exists, file_list) + + If the function you need doesn't exist, you need to write it. One way to write +-small functions is to use the ``lambda`` statement. ``lambda`` takes a number +-of parameters and an expression combining these parameters, and creates a small +-function that returns the value of the expression:: ++small functions is to use the :keyword:`lambda` statement. ``lambda`` takes a ++number of parameters and an expression combining these parameters, and creates ++an anonymous function that returns the value of the expression:: + +- lowercase = lambda x: x.lower() ++ adder = lambda x, y: x+y + + print_assign = lambda name, value: name + '=' + str(value) + +- adder = lambda x, y: x+y +- + An alternative is to just use the ``def`` statement and define a function in the + usual way:: + +- def lowercase(x): +- return x.lower() ++ def adder(x, y): ++ return x + y + + def print_assign(name, value): + return name + '=' + str(value) + +- def adder(x,y): +- return x + y +- + Which alternative is preferable? That's a style question; my usual course is to + avoid using ``lambda``. + +@@ -1053,9 +1044,7 @@ + expression, which means you can't have multiway ``if... elif... else`` + comparisons or ``try... except`` statements. If you try to do too much in a + ``lambda`` statement, you'll end up with an overly complicated expression that's +-hard to read. Quick, what's the following code doing? +- +-:: ++hard to read. Quick, what's the following code doing? :: + + import functools + total = functools.reduce(lambda a, b: (0, a[1] + b[1]), items)[1] +@@ -1065,7 +1054,7 @@ + little bit better:: + + import functools +- def combine (a, b): ++ def combine(a, b): + return 0, a[1] + b[1] + + total = functools.reduce(combine, items)[1] +@@ -1085,12 +1074,12 @@ + Fredrik Lundh once suggested the following set of rules for refactoring uses of + ``lambda``: + +-1) Write a lambda function. +-2) Write a comment explaining what the heck that lambda does. +-3) Study the comment for a while, and think of a name that captures the essence ++1. Write a lambda function. ++2. Write a comment explaining what the heck that lambda does. ++3. Study the comment for a while, and think of a name that captures the essence + of the comment. +-4) Convert the lambda to a def statement, using that name. +-5) Remove the comment. ++4. Convert the lambda to a def statement, using that name. ++5. Remove the comment. + + I really like these rules, but you're free to disagree + about whether this lambda-free style is better. +diff -r bd8afb90ebf2 Doc/howto/ipaddress.rst +--- a/Doc/howto/ipaddress.rst ++++ b/Doc/howto/ipaddress.rst +@@ -1,7 +1,7 @@ + .. _ipaddress-howto: + + *************************************** +-An Introduction to the ipaddress module ++An introduction to the ipaddress module + *************************************** + + :author: Peter Moody +@@ -47,7 +47,12 @@ + when working with IP addressing. The simplest way to create addresses is + to use the :func:`ipaddress.ip_address` factory function, which automatically + determines whether to create an IPv4 or IPv6 address based on the passed in +-value:: ++value: ++ ++.. testsetup:: ++ >>> import ipaddress ++ ++:: + + >>> ipaddress.ip_address('192.0.2.1') + IPv4Address('192.0.2.1') +@@ -142,7 +147,7 @@ + + >>> ipaddress.ip_interface('192.0.2.1/24') + IPv4Interface('192.0.2.1/24') +- >>> ipaddress.ip_network('2001:db8::1/96') ++ >>> ipaddress.ip_interface('2001:db8::1/96') + IPv6Interface('2001:db8::1/96') + + Integer inputs are accepted (as with networks), and use of a particular IP +@@ -177,22 +182,22 @@ + Finding out how many individual addresses are in a network:: + + >>> net4 = ipaddress.ip_network('192.0.2.0/24') +- >>> net4.numhosts ++ >>> net4.num_addresses + 256 + >>> net6 = ipaddress.ip_network('2001:db8::0/96') +- >>> net6.numhosts ++ >>> net6.num_addresses + 4294967296 + + Iterating through the "usable" addresses on a network:: + + >>> net4 = ipaddress.ip_network('192.0.2.0/24') + >>> for x in net4.hosts(): +- print(x) ++ ... print(x) # doctest: +ELLIPSIS + 192.0.2.1 + 192.0.2.2 + 192.0.2.3 + 192.0.2.4 +- ++ ... + 192.0.2.252 + 192.0.2.253 + 192.0.2.254 +@@ -216,9 +221,9 @@ + Exploding or compressing the address:: + + >>> addr6.exploded +- '2001:0db8:0000:0000:0000:0000:0000:0000' ++ '2001:0db8:0000:0000:0000:0000:0000:0001' + >>> addr6.compressed +- '2001:db8::' ++ '2001:db8::1' + >>> net6.exploded + '2001:0db8:0000:0000:0000:0000:0000:0000/96' + >>> net6.compressed +@@ -241,9 +246,9 @@ + >>> net4[-1] + IPv4Address('192.0.2.255') + >>> net6[1] +- IPv6Address('2001::1') ++ IPv6Address('2001:db8::1') + >>> net6[-1] +- IPv6Address('2001::ffff:ffff') ++ IPv6Address('2001:db8::ffff:ffff') + + + It also means that network objects lend themselves to using the list +diff -r bd8afb90ebf2 Doc/howto/logging-cookbook.rst +--- a/Doc/howto/logging-cookbook.rst ++++ b/Doc/howto/logging-cookbook.rst +@@ -1615,3 +1615,85 @@ + RFC 5424-compliant messages. If you don't, logging may not complain, but your + messages will not be RFC 5424-compliant, and your syslog daemon may complain. + ++ ++Implementing structured logging ++------------------------------- ++ ++Although most logging messages are intended for reading by humans, and thus not ++readily machine-parseable, there might be cirumstances where you want to output ++messages in a structured format which *is* capable of being parsed by a program ++(without needing complex regular expressions to parse the log message). This is ++straightforward to achieve using the logging package. There are a number of ++ways in which this could be achieved, but the following is a simple approach ++which uses JSON to serialise the event in a machine-parseable manner:: ++ ++ import json ++ import logging ++ ++ class StructuredMessage(object): ++ def __init__(self, message, **kwargs): ++ self.message = message ++ self.kwargs = kwargs ++ ++ def __str__(self): ++ return '%s >>> %s' % (self.message, json.dumps(self.kwargs)) ++ ++ _ = StructuredMessage # optional, to improve readability ++ ++ logging.basicConfig(level=logging.INFO, format='%(message)s') ++ logging.info(_('message 1', foo='bar', bar='baz', num=123, fnum=123.456)) ++ ++If the above script is run, it prints:: ++ ++ message 1 >>> {"fnum": 123.456, "num": 123, "bar": "baz", "foo": "bar"} ++ ++Note that the order of items might be different according to the version of ++Python used. ++ ++If you need more specialised processing, you can use a custom JSON encoder, ++as in the following complete example:: ++ ++ from __future__ import unicode_literals ++ ++ import json ++ import logging ++ ++ # This next bit is to ensure the script runs unchanged on 2.x and 3.x ++ try: ++ unicode ++ except NameError: ++ unicode = str ++ ++ class Encoder(json.JSONEncoder): ++ def default(self, o): ++ if isinstance(o, set): ++ return tuple(o) ++ elif isinstance(o, unicode): ++ return o.encode('unicode_escape').decode('ascii') ++ return super(Encoder, self).default(o) ++ ++ class StructuredMessage(object): ++ def __init__(self, message, **kwargs): ++ self.message = message ++ self.kwargs = kwargs ++ ++ def __str__(self): ++ s = Encoder().encode(self.kwargs) ++ return '%s >>> %s' % (self.message, s) ++ ++ _ = StructuredMessage # optional, to improve readability ++ ++ def main(): ++ logging.basicConfig(level=logging.INFO, format='%(message)s') ++ logging.info(_('message 1', set_value=set([1, 2, 3]), snowman='\u2603')) ++ ++ if __name__ == '__main__': ++ main() ++ ++When the above script is run, it prints:: ++ ++ message 1 >>> {"snowman": "\u2603", "set_value": [1, 2, 3]} ++ ++Note that the order of items might be different according to the version of ++Python used. ++ +diff -r bd8afb90ebf2 Doc/howto/logging.rst +--- a/Doc/howto/logging.rst ++++ b/Doc/howto/logging.rst +@@ -330,6 +330,9 @@ + to output. + * Formatters specify the layout of log records in the final output. + ++Log event information is passed between loggers, handlers, filters and ++formatters in a :class:`LogRecord` instance. ++ + Logging is performed by calling methods on instances of the :class:`Logger` + class (hereafter called :dfn:`loggers`). Each instance has a name, and they are + conceptually arranged in a namespace hierarchy using dots (periods) as +@@ -374,6 +377,13 @@ + *format* keyword argument. For all options regarding how a format string is + constructed, see :ref:`formatter-objects`. + ++Logging Flow ++^^^^^^^^^^^^ ++ ++The flow of log event information in loggers and handlers is illustrated in the ++following diagram. ++ ++.. image:: logging_flow.png + + Loggers + ^^^^^^^ +@@ -780,13 +790,14 @@ + libraries, then the logger name specified can be 'orgname.foo' rather than + just 'foo'. + +-**PLEASE NOTE:** It is strongly advised that you *do not add any handlers other +-than* :class:`~logging.NullHandler` *to your library's loggers*. This is +-because the configuration of handlers is the prerogative of the application +-developer who uses your library. The application developer knows their target +-audience and what handlers are most appropriate for their application: if you +-add handlers 'under the hood', you might well interfere with their ability to +-carry out unit tests and deliver logs which suit their requirements. ++.. note:: It is strongly advised that you *do not add any handlers other ++ than* :class:`~logging.NullHandler` *to your library's loggers*. This is ++ because the configuration of handlers is the prerogative of the application ++ developer who uses your library. The application developer knows their ++ target audience and what handlers are most appropriate for their ++ application: if you add handlers 'under the hood', you might well interfere ++ with their ability to carry out unit tests and deliver logs which suit their ++ requirements. + + + Logging Levels +@@ -969,10 +980,10 @@ + to see if a module-level variable, :data:`raiseExceptions`, is set. If set, a + traceback is printed to :data:`sys.stderr`. If not set, the exception is swallowed. + +-**Note:** The default value of :data:`raiseExceptions` is ``True``. This is because +-during development, you typically want to be notified of any exceptions that +-occur. It's advised that you set :data:`raiseExceptions` to ``False`` for production +-usage. ++.. note:: The default value of :data:`raiseExceptions` is ``True``. This is ++ because during development, you typically want to be notified of any ++ exceptions that occur. It's advised that you set :data:`raiseExceptions` to ++ ``False`` for production usage. + + .. currentmodule:: logging + +diff -r bd8afb90ebf2 Doc/howto/logging_flow.png +Binary file Doc/howto/logging_flow.png has changed +diff -r bd8afb90ebf2 Doc/howto/regex.rst +--- a/Doc/howto/regex.rst ++++ b/Doc/howto/regex.rst +@@ -260,7 +260,7 @@ + + >>> import re + >>> p = re.compile('ab*') +- >>> p ++ >>> p #doctest: +ELLIPSIS + <_sre.SRE_Pattern object at 0x...> + + :func:`re.compile` also accepts an optional *flags* argument, used to enable +@@ -354,9 +354,9 @@ + +------------------+-----------------------------------------------+ + + :meth:`match` and :meth:`search` return ``None`` if no match can be found. If +-they're successful, a ``MatchObject`` instance is returned, containing +-information about the match: where it starts and ends, the substring it matched, +-and more. ++they're successful, a :ref:`match object ` instance is returned, ++containing information about the match: where it starts and ends, the substring ++it matched, and more. + + You can learn about this by interactively experimenting with the :mod:`re` + module. If you have :mod:`tkinter` available, you may also want to look at +@@ -372,7 +372,7 @@ + + >>> import re + >>> p = re.compile('[a-z]+') +- >>> p ++ >>> p #doctest: +ELLIPSIS + <_sre.SRE_Pattern object at 0x...> + + Now, you can try matching various strings against the RE ``[a-z]+``. An empty +@@ -386,16 +386,16 @@ + None + + Now, let's try it on a string that it should match, such as ``tempo``. In this +-case, :meth:`match` will return a :class:`MatchObject`, so you should store the +-result in a variable for later use. :: ++case, :meth:`match` will return a :ref:`match object `, so you ++should store the result in a variable for later use. :: + + >>> m = p.match('tempo') +- >>> m ++ >>> m #doctest: +ELLIPSIS + <_sre.SRE_Match object at 0x...> + +-Now you can query the :class:`MatchObject` for information about the matching +-string. :class:`MatchObject` instances also have several methods and +-attributes; the most important ones are: ++Now you can query the :ref:`match object ` for information ++about the matching string. :ref:`match object ` instances ++also have several methods and attributes; the most important ones are: + + +------------------+--------------------------------------------+ + | Method/Attribute | Purpose | +@@ -429,15 +429,16 @@ + + >>> print(p.match('::: message')) + None +- >>> m = p.search('::: message') ; print(m) ++ >>> m = p.search('::: message'); print(m) #doctest: +ELLIPSIS + <_sre.SRE_Match object at 0x...> + >>> m.group() + 'message' + >>> m.span() + (4, 11) + +-In actual programs, the most common style is to store the :class:`MatchObject` +-in a variable, and then check if it was ``None``. This usually looks like:: ++In actual programs, the most common style is to store the ++:ref:`match object ` in a variable, and then check if it was ++``None``. This usually looks like:: + + p = re.compile( ... ) + m = p.match( 'string goes here' ) +@@ -454,11 +455,11 @@ + ['12', '11', '10'] + + :meth:`findall` has to create the entire list before it can be returned as the +-result. The :meth:`finditer` method returns a sequence of :class:`MatchObject` +-instances as an :term:`iterator`:: ++result. The :meth:`finditer` method returns a sequence of ++:ref:`match object ` instances as an :term:`iterator`:: + + >>> iterator = p.finditer('12 drummers drumming, 11 ... 10 ...') +- >>> iterator ++ >>> iterator #doctest: +ELLIPSIS + + >>> for match in iterator: + ... print(match.span()) +@@ -476,11 +477,11 @@ + :func:`search`, :func:`findall`, :func:`sub`, and so forth. These functions + take the same arguments as the corresponding pattern method, with + the RE string added as the first argument, and still return either ``None`` or a +-:class:`MatchObject` instance. :: ++:ref:`match object ` instance. :: + + >>> print(re.match(r'From\s+', 'Fromage amk')) + None +- >>> re.match(r'From\s+', 'From amk Thu May 14 19:12:10 1998') ++ >>> re.match(r'From\s+', 'From amk Thu May 14 19:12:10 1998') #doctest: +ELLIPSIS + <_sre.SRE_Match object at 0x...> + + Under the hood, these functions simply create a pattern object for you +@@ -682,7 +683,7 @@ + For example, if you wish to match the word ``From`` only at the beginning of a + line, the RE to use is ``^From``. :: + +- >>> print(re.search('^From', 'From Here to Eternity')) ++ >>> print(re.search('^From', 'From Here to Eternity')) #doctest: +ELLIPSIS + <_sre.SRE_Match object at 0x...> + >>> print(re.search('^From', 'Reciting From Memory')) + None +@@ -694,11 +695,11 @@ + Matches at the end of a line, which is defined as either the end of the string, + or any location followed by a newline character. :: + +- >>> print(re.search('}$', '{block}')) ++ >>> print(re.search('}$', '{block}')) #doctest: +ELLIPSIS + <_sre.SRE_Match object at 0x...> + >>> print(re.search('}$', '{block} ')) + None +- >>> print(re.search('}$', '{block}\n')) ++ >>> print(re.search('}$', '{block}\n')) #doctest: +ELLIPSIS + <_sre.SRE_Match object at 0x...> + + To match a literal ``'$'``, use ``\$`` or enclose it inside a character class, +@@ -723,7 +724,7 @@ + match when it's contained inside another word. :: + + >>> p = re.compile(r'\bclass\b') +- >>> print(p.search('no class at all')) ++ >>> print(p.search('no class at all')) #doctest: +ELLIPSIS + <_sre.SRE_Match object at 0x...> + >>> print(p.search('the declassified algorithm')) + None +@@ -741,7 +742,7 @@ + >>> p = re.compile('\bclass\b') + >>> print(p.search('no class at all')) + None +- >>> print(p.search('\b' + 'class' + '\b') ) ++ >>> print(p.search('\b' + 'class' + '\b')) #doctest: +ELLIPSIS + <_sre.SRE_Match object at 0x...> + + Second, inside a character class, where there's no use for this assertion, +@@ -786,9 +787,9 @@ + index of the text that they match; this can be retrieved by passing an argument + to :meth:`group`, :meth:`start`, :meth:`end`, and :meth:`span`. Groups are + numbered starting with 0. Group 0 is always present; it's the whole RE, so +-:class:`MatchObject` methods all have group 0 as their default argument. Later +-we'll see how to express groups that don't capture the span of text that they +-match. :: ++:ref:`match object ` methods all have group 0 as their default ++argument. Later we'll see how to express groups that don't capture the span ++of text that they match. :: + + >>> p = re.compile('(a)b') + >>> m = p.match('ab') +@@ -908,10 +909,10 @@ + The syntax for a named group is one of the Python-specific extensions: + ``(?P...)``. *name* is, obviously, the name of the group. Named groups + also behave exactly like capturing groups, and additionally associate a name +-with a group. The :class:`MatchObject` methods that deal with capturing groups +-all accept either integers that refer to the group by number or strings that +-contain the desired group's name. Named groups are still given numbers, so you +-can retrieve information about a group in two ways:: ++with a group. The :ref:`match object ` methods that deal with ++capturing groups all accept either integers that refer to the group by number ++or strings that contain the desired group's name. Named groups are still ++given numbers, so you can retrieve information about a group in two ways:: + + >>> p = re.compile(r'(?P\b\w+\b)') + >>> m = p.search( '(((( Lots of punctuation )))' ) +@@ -1175,16 +1176,16 @@ + + *replacement* can also be a function, which gives you even more control. If + *replacement* is a function, the function is called for every non-overlapping +-occurrence of *pattern*. On each call, the function is passed a +-:class:`MatchObject` argument for the match and can use this information to +-compute the desired replacement string and return it. ++occurrence of *pattern*. On each call, the function is passed a ++:ref:`match object ` argument for the match and can use this ++information to compute the desired replacement string and return it. + +-In the following example, the replacement function translates decimals into ++In the following example, the replacement function translates decimals into + hexadecimal:: + +- >>> def hexrepl( match ): ++ >>> def hexrepl(match): + ... "Return the hex string for a decimal number" +- ... value = int( match.group() ) ++ ... value = int(match.group()) + ... return hex(value) + ... + >>> p = re.compile(r'\d+') +diff -r bd8afb90ebf2 Doc/howto/unicode.rst +--- a/Doc/howto/unicode.rst ++++ b/Doc/howto/unicode.rst +@@ -44,7 +44,7 @@ + machines had different codes, however, which led to problems exchanging files. + Eventually various commonly used sets of values for the 128--255 range emerged. + Some were true standards, defined by the International Standards Organization, +-and some were **de facto** conventions that were invented by one company or ++and some were *de facto* conventions that were invented by one company or + another and managed to catch on. + + 255 characters aren't very many. For example, you can't fit both the accented +@@ -62,8 +62,8 @@ + to represent many different characters from many different alphabets; an initial + goal was to have Unicode contain the alphabets for every single human language. + It turns out that even 16 bits isn't enough to meet that goal, and the modern +-Unicode specification uses a wider range of codes, 0 through 1,114,111 (0x10ffff +-in base 16). ++Unicode specification uses a wider range of codes, 0 through 1,114,111 ( ++``0x10FFFF`` in base 16). + + There's a related ISO standard, ISO 10646. Unicode and ISO 10646 were + originally separate efforts, but the specifications were merged with the 1.1 +@@ -87,9 +87,11 @@ + + The Unicode standard describes how characters are represented by **code + points**. A code point is an integer value, usually denoted in base 16. In the +-standard, a code point is written using the notation U+12ca to mean the +-character with value 0x12ca (4,810 decimal). The Unicode standard contains a lot +-of tables listing characters and their corresponding code points:: ++standard, a code point is written using the notation ``U+12CA`` to mean the ++character with value ``0x12ca`` (4,810 decimal). The Unicode standard contains ++a lot of tables listing characters and their corresponding code points: ++ ++.. code-block:: none + + 0061 'a'; LATIN SMALL LETTER A + 0062 'b'; LATIN SMALL LETTER B +@@ -98,7 +100,7 @@ + 007B '{'; LEFT CURLY BRACKET + + Strictly, these definitions imply that it's meaningless to say 'this is +-character U+12ca'. U+12ca is a code point, which represents some particular ++character ``U+12CA``'. ``U+12CA`` is a code point, which represents some particular + character; in this case, it represents the character 'ETHIOPIC SYLLABLE WI'. In + informal contexts, this distinction between code points and characters will + sometimes be forgotten. +@@ -115,13 +117,15 @@ + --------- + + To summarize the previous section: a Unicode string is a sequence of code +-points, which are numbers from 0 through 0x10ffff (1,114,111 decimal). This ++points, which are numbers from 0 through ``0x10FFFF`` (1,114,111 decimal). This + sequence needs to be represented as a set of bytes (meaning, values + from 0 through 255) in memory. The rules for translating a Unicode string + into a sequence of bytes are called an **encoding**. + + The first encoding you might think of is an array of 32-bit integers. In this +-representation, the string "Python" would look like this:: ++representation, the string "Python" would look like this: ++ ++.. code-block:: none + + P y t h o n + 0x50 00 00 00 79 00 00 00 74 00 00 00 68 00 00 00 6f 00 00 00 6e 00 00 00 +@@ -133,10 +137,10 @@ + 1. It's not portable; different processors order the bytes differently. + + 2. It's very wasteful of space. In most texts, the majority of the code points +- are less than 127, or less than 255, so a lot of space is occupied by zero ++ are less than 127, or less than 255, so a lot of space is occupied by ``0x00`` + bytes. The above string takes 24 bytes compared to the 6 bytes needed for an + ASCII representation. Increased RAM usage doesn't matter too much (desktop +- computers have megabytes of RAM, and strings aren't usually that large), but ++ computers have gigabytes of RAM, and strings aren't usually that large), but + expanding our usage of disk and network bandwidth by a factor of 4 is + intolerable. + +@@ -175,14 +179,12 @@ + + UTF-8 is one of the most commonly used encodings. UTF stands for "Unicode + Transformation Format", and the '8' means that 8-bit numbers are used in the +-encoding. (There's also a UTF-16 encoding, but it's less frequently used than +-UTF-8.) UTF-8 uses the following rules: ++encoding. (There are also a UTF-16 and UTF-32 encodings, but they are less ++frequently used than UTF-8.) UTF-8 uses the following rules: + +-1. If the code point is <128, it's represented by the corresponding byte value. +-2. If the code point is between 128 and 0x7ff, it's turned into two byte values +- between 128 and 255. +-3. Code points >0x7ff are turned into three- or four-byte sequences, where each +- byte of the sequence is between 128 and 255. ++1. If the code point is < 128, it's represented by the corresponding byte value. ++2. If the code point is >= 128, it's turned into a sequence of two, three, or ++ four bytes, where each byte of the sequence is between 128 and 255. + + UTF-8 has several convenient properties: + +@@ -192,8 +194,8 @@ + processed by C functions such as ``strcpy()`` and sent through protocols that + can't handle zero bytes. + 3. A string of ASCII text is also valid UTF-8 text. +-4. UTF-8 is fairly compact; the majority of code points are turned into two +- bytes, and values less than 128 occupy only a single byte. ++4. UTF-8 is fairly compact; the majority of commonly used characters can be ++ represented with one or two bytes. + 5. If bytes are corrupted or lost, it's possible to determine the start of the + next UTF-8-encoded code point and resynchronize. It's also unlikely that + random 8-bit data will look like valid UTF-8. +@@ -203,25 +205,25 @@ + References + ---------- + +-The Unicode Consortium site at has character charts, a ++The `Unicode Consortium site `_ has character charts, a + glossary, and PDF versions of the Unicode specification. Be prepared for some +-difficult reading. is a chronology of the +-origin and development of Unicode. ++difficult reading. `A chronology `_ of the ++origin and development of Unicode is also available on the site. + +-To help understand the standard, Jukka Korpela has written an introductory guide +-to reading the Unicode character tables, available at +-. ++To help understand the standard, Jukka Korpela has written `an introductory ++guide `_ to reading the ++Unicode character tables. + +-Another good introductory article was written by Joel Spolsky +-. ++Another `good introductory article `_ ++was written by Joel Spolsky. + If this introduction didn't make things clear to you, you should try reading this + alternate article before continuing. + + .. Jason Orendorff XXX http://www.jorendorff.com/articles/unicode/ is broken + +-Wikipedia entries are often helpful; see the entries for "character encoding" +- and UTF-8 +-, for example. ++Wikipedia entries are often helpful; see the entries for "`character encoding ++`_" and `UTF-8 ++`_, for example. + + + Python's Unicode Support +@@ -233,11 +235,11 @@ + The String Type + --------------- + +-Since Python 3.0, the language features a ``str`` type that contain Unicode ++Since Python 3.0, the language features a :class:`str` type that contain Unicode + characters, meaning any string created using ``"unicode rocks!"``, ``'unicode + rocks!'``, or the triple-quoted string syntax is stored as Unicode. + +-To insert a Unicode character that is not part ASCII, e.g., any letters with ++To insert a non-ASCII Unicode character, e.g., any letters with + accents, one can use escape sequences in their string literals as such:: + + >>> "\N{GREEK CAPITAL LETTER DELTA}" # Using the character name +@@ -247,23 +249,24 @@ + >>> "\U00000394" # Using a 32-bit hex value + '\u0394' + +-In addition, one can create a string using the :func:`decode` method of +-:class:`bytes`. This method takes an encoding, such as UTF-8, and, optionally, +-an *errors* argument. ++In addition, one can create a string using the :func:`~bytes.decode` method of ++:class:`bytes`. This method takes an *encoding* argument, such as ``UTF-8``, ++and optionally, an *errors* argument. + + The *errors* argument specifies the response when the input string can't be + converted according to the encoding's rules. Legal values for this argument are +-'strict' (raise a :exc:`UnicodeDecodeError` exception), 'replace' (use U+FFFD, +-'REPLACEMENT CHARACTER'), or 'ignore' (just leave the character out of the +-Unicode result). The following examples show the differences:: ++``'strict'`` (raise a :exc:`UnicodeDecodeError` exception), ``'replace'`` (use ++``U+FFFD``, ``REPLACEMENT CHARACTER``), or ``'ignore'`` (just leave the ++character out of the Unicode result). ++The following examples show the differences:: + +- >>> b'\x80abc'.decode("utf-8", "strict") ++ >>> b'\x80abc'.decode("utf-8", "strict") #doctest: +NORMALIZE_WHITESPACE + Traceback (most recent call last): +- File "", line 1, in ? +- UnicodeDecodeError: 'utf8' codec can't decode byte 0x80 in position 0: +- unexpected code byte ++ ... ++ UnicodeDecodeError: 'utf-8' codec can't decode byte 0x80 in position 0: ++ invalid start byte + >>> b'\x80abc'.decode("utf-8", "replace") +- '?abc' ++ '\ufffdabc' + >>> b'\x80abc'.decode("utf-8", "ignore") + 'abc' + +@@ -273,8 +276,8 @@ + Encodings are specified as strings containing the encoding's name. Python 3.2 + comes with roughly 100 different encodings; see the Python Library Reference at + :ref:`standard-encodings` for a list. Some encodings have multiple names; for +-example, 'latin-1', 'iso_8859_1' and '8859' are all synonyms for the same +-encoding. ++example, ``'latin-1'``, ``'iso_8859_1'`` and ``'8859``' are all synonyms for ++the same encoding. + + One-character Unicode strings can also be created with the :func:`chr` + built-in function, which takes integers and returns a Unicode string of length 1 +@@ -290,22 +293,23 @@ + Converting to Bytes + ------------------- + +-Another important str method is ``.encode([encoding], [errors='strict'])``, +-which returns a ``bytes`` representation of the Unicode string, encoded in the +-requested encoding. The ``errors`` parameter is the same as the parameter of +-the :meth:`decode` method, with one additional possibility; as well as 'strict', +-'ignore', and 'replace' (which in this case inserts a question mark instead of +-the unencodable character), you can also pass 'xmlcharrefreplace' which uses +-XML's character references. The following example shows the different results:: ++The opposite method of :meth:`bytes.decode` is :meth:`str.encode`, ++which returns a :class:`bytes` representation of the Unicode string, encoded in the ++requested *encoding*. The *errors* parameter is the same as the parameter of ++the :meth:`~bytes.decode` method, with one additional possibility; as well as ++``'strict'``, ``'ignore'``, and ``'replace'`` (which in this case inserts a ++question mark instead of the unencodable character), you can also pass ++``'xmlcharrefreplace'`` which uses XML's character references. ++The following example shows the different results:: + + >>> u = chr(40960) + 'abcd' + chr(1972) + >>> u.encode('utf-8') + b'\xea\x80\x80abcd\xde\xb4' +- >>> u.encode('ascii') ++ >>> u.encode('ascii') #doctest: +NORMALIZE_WHITESPACE + Traceback (most recent call last): +- File "", line 1, in ? ++ ... + UnicodeEncodeError: 'ascii' codec can't encode character '\ua000' in +- position 0: ordinal not in range(128) ++ position 0: ordinal not in range(128) + >>> u.encode('ascii', 'ignore') + b'abcd' + >>> u.encode('ascii', 'replace') +@@ -313,6 +317,8 @@ + >>> u.encode('ascii', 'xmlcharrefreplace') + b'ꀀabcd޴' + ++.. XXX mention the surrogate* error handlers ++ + The low-level routines for registering and accessing the available encodings are + found in the :mod:`codecs` module. However, the encoding and decoding functions + returned by this module are usually more low-level than is comfortable, so I'm +@@ -331,12 +337,11 @@ + not four:: + + >>> s = "a\xac\u1234\u20ac\U00008000" +- ^^^^ two-digit hex escape +- ^^^^^ four-digit Unicode escape +- ^^^^^^^^^^ eight-digit Unicode escape +- >>> for c in s: print(ord(c), end=" ") +- ... +- 97 172 4660 8364 32768 ++ ... # ^^^^ two-digit hex escape ++ ... # ^^^^^^ four-digit Unicode escape ++ ... # ^^^^^^^^^^ eight-digit Unicode escape ++ >>> [ord(c) for c in s] ++ [97, 172, 4660, 8364, 32768] + + Using escape sequences for code points greater than 127 is fine in small doses, + but becomes an annoyance if you're using many accented characters, as you would +@@ -366,14 +371,14 @@ + ``coding: name`` or ``coding=name`` in the comment. + + If you don't include such a comment, the default encoding used will be UTF-8 as +-already mentioned. ++already mentioned. See also :pep:`263` for more information. + + + Unicode Properties + ------------------ + + The Unicode specification includes a database of information about code points. +-For each code point that's defined, the information includes the character's ++For each defined code point, the information includes the character's + name, its category, the numeric value if applicable (Unicode has characters + representing the Roman numerals and fractions such as one-third and + four-fifths). There are also properties related to the code point's use in +@@ -393,7 +398,9 @@ + # Get numeric value of second character + print(unicodedata.numeric(u[1])) + +-When run, this prints:: ++When run, this prints: ++ ++.. code-block:: none + + 0 00e9 Ll LATIN SMALL LETTER E WITH ACUTE + 1 0bf2 No TAMIL NUMBER ONE THOUSAND +@@ -414,8 +421,8 @@ + References + ---------- + +-The ``str`` type is described in the Python library reference at +-:ref:`typesseq`. ++The :class:`str` type is described in the Python library reference at ++:ref:`textseq`. + + The documentation for the :mod:`unicodedata` module. + +@@ -444,16 +451,16 @@ + + Unicode data is usually converted to a particular encoding before it gets + written to disk or sent over a socket. It's possible to do all the work +-yourself: open a file, read an 8-bit byte string from it, and convert the string +-with ``str(bytes, encoding)``. However, the manual approach is not recommended. ++yourself: open a file, read an 8-bit bytes object from it, and convert the string ++with ``bytes.decode(encoding)``. However, the manual approach is not recommended. + + One problem is the multi-byte nature of encodings; one Unicode character can be + represented by several bytes. If you want to read the file in arbitrary-sized +-chunks (say, 1K or 4K), you need to write error-handling code to catch the case ++chunks (say, 1k or 4k), you need to write error-handling code to catch the case + where only part of the bytes encoding a single Unicode character are read at the + end of a chunk. One solution would be to read the entire file into memory and + then perform the decoding, but that prevents you from working with files that +-are extremely large; if you need to read a 2Gb file, you need 2Gb of RAM. ++are extremely large; if you need to read a 2GB file, you need 2GB of RAM. + (More, really, since for at least a moment you'd need to have both the encoded + string and its Unicode version in memory.) + +@@ -461,9 +468,9 @@ + of partial coding sequences. The work of implementing this has already been + done for you: the built-in :func:`open` function can return a file-like object + that assumes the file's contents are in a specified encoding and accepts Unicode +-parameters for methods such as ``.read()`` and ``.write()``. This works through ++parameters for methods such as :meth:`read` and :meth:`write`. This works through + :func:`open`\'s *encoding* and *errors* parameters which are interpreted just +-like those in string objects' :meth:`encode` and :meth:`decode` methods. ++like those in :meth:`str.encode` and :meth:`bytes.decode`. + + Reading Unicode from a file is therefore simple:: + +@@ -479,7 +486,7 @@ + f.seek(0) + print(repr(f.readline()[:1])) + +-The Unicode character U+FEFF is used as a byte-order mark (BOM), and is often ++The Unicode character ``U+FEFF`` is used as a byte-order mark (BOM), and is often + written as the first character of a file in order to assist with autodetection + of the file's byte ordering. Some encodings, such as UTF-16, expect a BOM to be + present at the start of a file; when such an encoding is used, the BOM will be +@@ -521,12 +528,12 @@ + filenames. + + Function :func:`os.listdir`, which returns filenames, raises an issue: should it return +-the Unicode version of filenames, or should it return byte strings containing ++the Unicode version of filenames, or should it return bytes containing + the encoded versions? :func:`os.listdir` will do both, depending on whether you +-provided the directory path as a byte string or a Unicode string. If you pass a ++provided the directory path as bytes or a Unicode string. If you pass a + Unicode string as the path, filenames will be decoded using the filesystem's + encoding and a list of Unicode strings will be returned, while passing a byte +-path will return the byte string versions of the filenames. For example, ++path will return the bytes versions of the filenames. For example, + assuming the default filesystem encoding is UTF-8, running the following + program:: + +@@ -560,13 +567,13 @@ + + The most important tip is: + +- Software should only work with Unicode strings internally, converting to a +- particular encoding on output. ++ Software should only work with Unicode strings internally, decoding the input ++ data as soon as possible and encoding the output only at the end. + + If you attempt to write processing functions that accept both Unicode and byte + strings, you will find your program vulnerable to bugs wherever you combine the +-two different kinds of strings. There is no automatic encoding or decoding if +-you do e.g. ``str + bytes``, a :exc:`TypeError` is raised for this expression. ++two different kinds of strings. There is no automatic encoding or decoding: if ++you do e.g. ``str + bytes``, a :exc:`TypeError` will be raised. + + When using data coming from a web browser or some other untrusted source, a + common technique is to check for illegal characters in a string before using the +@@ -611,7 +618,6 @@ + and that the HOWTO only covers 2.x. + + .. comment Describe Python 3.x support (new section? new document?) +-.. comment Additional topic: building Python w/ UCS2 or UCS4 support + .. comment Describe use of codecs.StreamRecoder and StreamReaderWriter + + .. comment +@@ -641,5 +647,3 @@ + - [ ] Writing Unicode programs + - [ ] Do everything in Unicode + - [ ] Declaring source code encodings (PEP 263) +- - [ ] Other issues +- - [ ] Building Python (UCS2, UCS4) +diff -r bd8afb90ebf2 Doc/howto/urllib2.rst +--- a/Doc/howto/urllib2.rst ++++ b/Doc/howto/urllib2.rst +@@ -144,7 +144,7 @@ + >>> data['location'] = 'Northampton' + >>> data['language'] = 'Python' + >>> url_values = urllib.parse.urlencode(data) +- >>> print(url_values) ++ >>> print(url_values) # The order may differ from below. #doctest: +SKIP + name=Somebody+Here&language=Python&location=Northampton + >>> url = 'http://www.example.com/example.cgi' + >>> full_url = url + '?' + url_values +@@ -214,9 +214,9 @@ + + >>> req = urllib.request.Request('http://www.pretend_server.org') + >>> try: urllib.request.urlopen(req) +- >>> except urllib.error.URLError as e: +- >>> print(e.reason) +- >>> ++ ... except urllib.error.URLError as e: ++ ... print(e.reason) #doctest: +SKIP ++ ... + (4, 'getaddrinfo failed') + + +@@ -322,18 +322,17 @@ + + >>> req = urllib.request.Request('http://www.python.org/fish.html') + >>> try: +- >>> urllib.request.urlopen(req) +- >>> except urllib.error.HTTPError as e: +- >>> print(e.code) +- >>> print(e.read()) +- >>> ++ ... urllib.request.urlopen(req) ++ ... except urllib.error.HTTPError as e: ++ ... print(e.code) ++ ... print(e.read()) #doctest: +ELLIPSIS, +NORMALIZE_WHITESPACE ++ ... + 404 +- +- +- Error 404: File Not Found +- ...... etc... ++ b'\n\n\nPage Not Found\n ++ ... + + Wrapping it Up + -------------- +diff -r bd8afb90ebf2 Doc/install/index.rst +--- a/Doc/install/index.rst ++++ b/Doc/install/index.rst +@@ -7,8 +7,6 @@ + ***************************** + + :Author: Greg Ward +-:Release: |version| +-:Date: |today| + + .. TODO: Fill in XXX comments + +diff -r bd8afb90ebf2 Doc/library/2to3.rst +--- a/Doc/library/2to3.rst ++++ b/Doc/library/2to3.rst +@@ -23,7 +23,7 @@ + also located in the :file:`Tools/scripts` directory of the Python root. + + 2to3's basic arguments are a list of files or directories to transform. The +-directories are to recursively traversed for Python sources. ++directories are recursively traversed for Python sources. + + Here is a sample Python 2.x source file, :file:`example.py`:: + +diff -r bd8afb90ebf2 Doc/library/abc.rst +--- a/Doc/library/abc.rst ++++ b/Doc/library/abc.rst +@@ -129,7 +129,7 @@ + + The :mod:`abc` module also provides the following decorators: + +-.. decorator:: abstractmethod(function) ++.. decorator:: abstractmethod + + A decorator indicating abstract methods. + +@@ -203,43 +203,52 @@ + multiple-inheritance. + + +-.. decorator:: abstractclassmethod(function) ++.. decorator:: abstractclassmethod + + A subclass of the built-in :func:`classmethod`, indicating an abstract + classmethod. Otherwise it is similar to :func:`abstractmethod`. + +- Usage:: ++ This special case is deprecated, as the :func:`classmethod` decorator ++ is now correctly identified as abstract when applied to an abstract ++ method:: + + class C(metaclass=ABCMeta): +- @abstractclassmethod ++ @classmethod ++ @abstractmethod + def my_abstract_classmethod(cls, ...): + ... + + .. versionadded:: 3.2 + .. deprecated:: 3.3 +- Use :class:`classmethod` with :func:`abstractmethod` instead. ++ It is now possible to use :class:`classmethod` with ++ :func:`abstractmethod`, making this decorator redundant. + + +-.. decorator:: abstractstaticmethod(function) ++.. decorator:: abstractstaticmethod + + A subclass of the built-in :func:`staticmethod`, indicating an abstract + staticmethod. Otherwise it is similar to :func:`abstractmethod`. + +- Usage:: ++ This special case is deprecated, as the :func:`staticmethod` decorator ++ is now correctly identified as abstract when applied to an abstract ++ method:: + + class C(metaclass=ABCMeta): +- @abstractstaticmethod ++ @staticmethod ++ @abstractmethod + def my_abstract_staticmethod(...): + ... + + .. versionadded:: 3.2 + .. deprecated:: 3.3 +- Use :class:`staticmethod` with :func:`abstractmethod` instead. ++ It is now possible to use :class:`staticmethod` with ++ :func:`abstractmethod`, making this decorator redundant. + + + .. decorator:: abstractproperty(fget=None, fset=None, fdel=None, doc=None) + +- A subclass of the built-in :func:`property`, indicating an abstract property. ++ A subclass of the built-in :func:`property`, indicating an abstract ++ property. + + Using this function requires that the class's metaclass is :class:`ABCMeta` + or is derived from it. A class that has a metaclass derived from +@@ -247,23 +256,43 @@ + and properties are overridden. The abstract properties can be called using + any of the normal 'super' call mechanisms. + +- Usage:: ++ This special case is deprecated, as the :func:`property` decorator ++ is now correctly identified as abstract when applied to an abstract ++ method:: + + class C(metaclass=ABCMeta): +- @abstractproperty ++ @property ++ @abstractmethod + def my_abstract_property(self): + ... + +- This defines a read-only property; you can also define a read-write abstract +- property using the 'long' form of property declaration:: ++ The above example defines a read-only property; you can also define a ++ read-write abstract property by appropriately marking one or more of the ++ underlying methods as abstract:: + + class C(metaclass=ABCMeta): +- def getx(self): ... +- def setx(self, value): ... +- x = abstractproperty(getx, setx) ++ @property ++ def x(self): ++ ... ++ ++ @x.setter ++ @abstractmethod ++ def x(self, val): ++ ... ++ ++ If only some components are abstract, only those components need to be ++ updated to create a concrete property in a subclass:: ++ ++ class D(C): ++ @C.x.setter ++ def x(self, val): ++ ... ++ + + .. deprecated:: 3.3 +- Use :class:`property` with :func:`abstractmethod` instead ++ It is now possible to use :class:`property`, :meth:`property.getter`, ++ :meth:`property.setter` and :meth:`property.deleter` with ++ :func:`abstractmethod`, making this decorator redundant. + + + .. rubric:: Footnotes +diff -r bd8afb90ebf2 Doc/library/argparse.rst +--- a/Doc/library/argparse.rst ++++ b/Doc/library/argparse.rst +@@ -130,9 +130,12 @@ + ArgumentParser objects + ---------------------- + +-.. class:: ArgumentParser([description], [epilog], [prog], [usage], [add_help], \ +- [argument_default], [parents], [prefix_chars], \ +- [conflict_handler], [formatter_class]) ++.. class:: ArgumentParser(prog=None, usage=None, description=None, \ ++ epilog=None, parents=[], \ ++ formatter_class=argparse.HelpFormatter, \ ++ prefix_chars='-', fromfile_prefix_chars=None, \ ++ argument_default=None, conflict_handler='error', \ ++ add_help=True) + + Create a new :class:`ArgumentParser` object. Each parameter has its own more + detailed description below, but in short they are: +@@ -920,6 +923,17 @@ + >>> parser.parse_args(''.split()) + Namespace(foo=42) + ++If the ``default`` value is a string, the parser parses the value as if it ++were a command-line argument. In particular, the parser applies any type_ ++conversion argument, if provided, before setting the attribute on the ++:class:`Namespace` return value. Otherwise, the parser uses the value as is:: ++ ++ >>> parser = argparse.ArgumentParser() ++ >>> parser.add_argument('--length', default='10', type=int) ++ >>> parser.add_argument('--width', default=10.5, type=int) ++ >>> parser.parse_args() ++ Namespace(length=10, width=10.5) ++ + For positional arguments with nargs_ equal to ``?`` or ``*``, the ``default`` value + is used when no command-line argument was present:: + +@@ -958,6 +972,9 @@ + >>> parser.parse_args('2 temp.txt'.split()) + Namespace(bar=<_io.TextIOWrapper name='temp.txt' encoding='UTF-8'>, foo=2) + ++See the section on the default_ keyword argument for information on when the ++``type`` argument is applied to default arguments. ++ + To ease the use of various types of files, the argparse module provides the + factory FileType which takes the ``mode=`` and ``bufsize=`` arguments of the + :func:`open` function. For example, ``FileType('w')`` can be used to create a +@@ -1005,32 +1022,33 @@ + ^^^^^^^ + + Some command-line arguments should be selected from a restricted set of values. +-These can be handled by passing a container object as the ``choices`` keyword ++These can be handled by passing a container object as the *choices* keyword + argument to :meth:`~ArgumentParser.add_argument`. When the command line is +-parsed, argument values will be checked, and an error message will be displayed if +-the argument was not one of the acceptable values:: ++parsed, argument values will be checked, and an error message will be displayed ++if the argument was not one of the acceptable values:: + +- >>> parser = argparse.ArgumentParser(prog='PROG') +- >>> parser.add_argument('foo', choices='abc') +- >>> parser.parse_args('c'.split()) +- Namespace(foo='c') +- >>> parser.parse_args('X'.split()) +- usage: PROG [-h] {a,b,c} +- PROG: error: argument foo: invalid choice: 'X' (choose from 'a', 'b', 'c') ++ >>> parser = argparse.ArgumentParser(prog='game.py') ++ >>> parser.add_argument('move', choices=['rock', 'paper', 'scissors']) ++ >>> parser.parse_args(['rock']) ++ Namespace(move='rock') ++ >>> parser.parse_args(['fire']) ++ usage: game.py [-h] {rock,paper,scissors} ++ game.py: error: argument move: invalid choice: 'fire' (choose from 'rock', ++ 'paper', 'scissors') + +-Note that inclusion in the ``choices`` container is checked after any type_ +-conversions have been performed, so the type of the objects in the ``choices`` ++Note that inclusion in the *choices* container is checked after any type_ ++conversions have been performed, so the type of the objects in the *choices* + container should match the type_ specified:: + +- >>> parser = argparse.ArgumentParser(prog='PROG') +- >>> parser.add_argument('foo', type=complex, choices=[1, 1j]) +- >>> parser.parse_args('1j'.split()) +- Namespace(foo=1j) +- >>> parser.parse_args('-- -4'.split()) +- usage: PROG [-h] {1,1j} +- PROG: error: argument foo: invalid choice: (-4+0j) (choose from 1, 1j) ++ >>> parser = argparse.ArgumentParser(prog='doors.py') ++ >>> parser.add_argument('door', type=int, choices=range(1, 4)) ++ >>> print(parser.parse_args(['3'])) ++ Namespace(door=3) ++ >>> parser.parse_args(['4']) ++ usage: doors.py [-h] {1,2,3} ++ doors.py: error: argument door: invalid choice: 4 (choose from 1, 2, 3) + +-Any object that supports the ``in`` operator can be passed as the ``choices`` ++Any object that supports the ``in`` operator can be passed as the *choices* + value, so :class:`dict` objects, :class:`set` objects, custom containers, + etc. are all supported. + +@@ -1119,7 +1137,7 @@ + metavar + ^^^^^^^ + +-When :class:`ArgumentParser` generates help messages, it need some way to refer ++When :class:`ArgumentParser` generates help messages, it needs some way to refer + to each expected argument. By default, ArgumentParser objects use the dest_ + value as the "name" of each object. By default, for positional argument + actions, the dest_ value is used directly, and for optional argument actions, +@@ -1442,7 +1460,7 @@ + different functions which require different kinds of command-line arguments. + :class:`ArgumentParser` supports the creation of such sub-commands with the + :meth:`add_subparsers` method. The :meth:`add_subparsers` method is normally +- called with no arguments and returns an special action object. This object ++ called with no arguments and returns a special action object. This object + has a single method, :meth:`~ArgumentParser.add_parser`, which takes a + command name and any :class:`ArgumentParser` constructor arguments, and + returns an :class:`ArgumentParser` object that can be modified as usual. +@@ -1488,8 +1506,8 @@ + + positional arguments: + {a,b} sub-command help +- a a help +- b b help ++ a a help ++ b b help + + optional arguments: + -h, --help show this help message and exit +diff -r bd8afb90ebf2 Doc/library/audioop.rst +--- a/Doc/library/audioop.rst ++++ b/Doc/library/audioop.rst +@@ -7,7 +7,7 @@ + + The :mod:`audioop` module contains some useful operations on sound fragments. + It operates on sound fragments consisting of signed integer samples 8, 16 or 32 +-bits wide, stored in Python strings. All scalar items are integers, unless ++bits wide, stored in bytes objects. All scalar items are integers, unless + specified otherwise. + + .. index:: +@@ -126,7 +126,7 @@ + .. function:: lin2alaw(fragment, width) + + Convert samples in the audio fragment to a-LAW encoding and return this as a +- Python string. a-LAW is an audio encoding format whereby you get a dynamic ++ bytes object. a-LAW is an audio encoding format whereby you get a dynamic + range of about 13 bits using only 8 bit samples. It is used by the Sun audio + hardware, among others. + +@@ -151,27 +151,27 @@ + .. function:: lin2ulaw(fragment, width) + + Convert samples in the audio fragment to u-LAW encoding and return this as a +- Python string. u-LAW is an audio encoding format whereby you get a dynamic ++ bytes object. u-LAW is an audio encoding format whereby you get a dynamic + range of about 14 bits using only 8 bit samples. It is used by the Sun audio + hardware, among others. + + ++.. function:: max(fragment, width) ++ ++ Return the maximum of the *absolute value* of all samples in a fragment. ++ ++ ++.. function:: maxpp(fragment, width) ++ ++ Return the maximum peak-peak value in the sound fragment. ++ ++ + .. function:: minmax(fragment, width) + + Return a tuple consisting of the minimum and maximum values of all samples in + the sound fragment. + + +-.. function:: max(fragment, width) +- +- Return the maximum of the *absolute value* of all samples in a fragment. +- +- +-.. function:: maxpp(fragment, width) +- +- Return the maximum peak-peak value in the sound fragment. +- +- + .. function:: mul(fragment, width, factor) + + Return a fragment that has all samples in the original fragment multiplied by +diff -r bd8afb90ebf2 Doc/library/codecs.rst +--- a/Doc/library/codecs.rst ++++ b/Doc/library/codecs.rst +@@ -155,13 +155,16 @@ + when *name* is specified as the errors parameter. + + For encoding *error_handler* will be called with a :exc:`UnicodeEncodeError` +- instance, which contains information about the location of the error. The error +- handler must either raise this or a different exception or return a tuple with a +- replacement for the unencodable part of the input and a position where encoding +- should continue. The encoder will encode the replacement and continue encoding +- the original input at the specified position. Negative position values will be +- treated as being relative to the end of the input string. If the resulting +- position is out of bound an :exc:`IndexError` will be raised. ++ instance, which contains information about the location of the error. The ++ error handler must either raise this or a different exception or return a ++ tuple with a replacement for the unencodable part of the input and a position ++ where encoding should continue. The replacement may be either :class:`str` or ++ :class:`bytes`. If the replacement is bytes, the encoder will simply copy ++ them into the output buffer. If the replacement is a string, the encoder will ++ encode the replacement. Encoding continues on original input at the ++ specified position. Negative position values will be treated as being ++ relative to the end of the input string. If the resulting position is out of ++ bound an :exc:`IndexError` will be raised. + + Decoding and translating works similar, except :exc:`UnicodeDecodeError` or + :exc:`UnicodeTranslateError` will be passed to the handler and that the +diff -r bd8afb90ebf2 Doc/library/collections.abc.rst +--- a/Doc/library/collections.abc.rst ++++ b/Doc/library/collections.abc.rst +@@ -90,7 +90,7 @@ + + .. class:: Iterator + +- ABC for classes that provide the :meth:`__iter__` and :meth:`next` methods. ++ ABC for classes that provide the :meth:`__iter__` and :meth:`__next__` methods. + See also the definition of :term:`iterator`. + + .. class:: Sequence +diff -r bd8afb90ebf2 Doc/library/collections.rst +--- a/Doc/library/collections.rst ++++ b/Doc/library/collections.rst +@@ -159,7 +159,7 @@ + + d['x'] # Get first key in the chain of contexts + d['x'] = 1 # Set value in current context +- del['x'] # Delete from current context ++ del d['x'] # Delete from current context + list(d) # All nested values + k in d # Check all nested values + len(d) # Number of nested values +@@ -279,6 +279,7 @@ + >>> c = Counter(a=4, b=2, c=0, d=-2) + >>> d = Counter(a=1, b=2, c=3, d=4) + >>> c.subtract(d) ++ >>> c + Counter({'a': 3, 'b': 0, 'c': -3, 'd': -6}) + + .. versionadded:: 3.2 +@@ -347,24 +348,24 @@ + this section documents the minimum range and type restrictions. + + * The :class:`Counter` class itself is a dictionary subclass with no +- restrictions on its keys and values. The values are intended to be numbers +- representing counts, but you *could* store anything in the value field. ++ restrictions on its keys and values. The values are intended to be numbers ++ representing counts, but you *could* store anything in the value field. + + * The :meth:`most_common` method requires only that the values be orderable. + + * For in-place operations such as ``c[key] += 1``, the value type need only +- support addition and subtraction. So fractions, floats, and decimals would +- work and negative values are supported. The same is also true for +- :meth:`update` and :meth:`subtract` which allow negative and zero values +- for both inputs and outputs. ++ support addition and subtraction. So fractions, floats, and decimals would ++ work and negative values are supported. The same is also true for ++ :meth:`update` and :meth:`subtract` which allow negative and zero values ++ for both inputs and outputs. + + * The multiset methods are designed only for use cases with positive values. +- The inputs may be negative or zero, but only outputs with positive values +- are created. There are no type restrictions, but the value type needs to +- support addition, subtraction, and comparison. ++ The inputs may be negative or zero, but only outputs with positive values ++ are created. There are no type restrictions, but the value type needs to ++ support addition, subtraction, and comparison. + + * The :meth:`elements` method requires integer counts. It ignores zero and +- negative counts. ++ negative counts. + + .. seealso:: + +@@ -1012,7 +1013,7 @@ + to the end and the sort is not maintained. + + It is also straight-forward to create an ordered dictionary variant +-that the remembers the order the keys were *last* inserted. ++that remembers the order the keys were *last* inserted. + If a new entry overwrites an existing entry, the + original insertion position is changed and moved to the end:: + +diff -r bd8afb90ebf2 Doc/library/colorsys.rst +--- a/Doc/library/colorsys.rst ++++ b/Doc/library/colorsys.rst +@@ -58,7 +58,7 @@ + Example:: + + >>> import colorsys +- >>> colorsys.rgb_to_hsv(.3, .4, .2) +- (0.25, 0.5, 0.4) +- >>> colorsys.hsv_to_rgb(0.25, 0.5, 0.4) +- (0.3, 0.4, 0.2) ++ >>> colorsys.rgb_to_hsv(0.2, 0.4, 0.4) ++ (0.5, 0.5, 0.4) ++ >>> colorsys.hsv_to_rgb(0.5, 0.5, 0.4) ++ (0.2, 0.4, 0.4) +diff -r bd8afb90ebf2 Doc/library/concurrency.rst +--- a/Doc/library/concurrency.rst ++++ b/Doc/library/concurrency.rst +@@ -15,6 +15,7 @@ + + threading.rst + multiprocessing.rst ++ concurrent.rst + concurrent.futures.rst + subprocess.rst + sched.rst +diff -r bd8afb90ebf2 Doc/library/concurrent.futures.rst +--- a/Doc/library/concurrent.futures.rst ++++ b/Doc/library/concurrent.futures.rst +@@ -42,12 +42,13 @@ + + Equivalent to ``map(func, *iterables)`` except *func* is executed + asynchronously and several calls to *func* may be made concurrently. The +- returned iterator raises a :exc:`TimeoutError` if :meth:`__next__()` is +- called and the result isn't available after *timeout* seconds from the +- original call to :meth:`Executor.map`. *timeout* can be an int or a +- float. If *timeout* is not specified or ``None``, there is no limit to +- the wait time. If a call raises an exception, then that exception will +- be raised when its value is retrieved from the iterator. ++ returned iterator raises a :exc:`TimeoutError` if ++ :meth:`~iterator.__next__` is called and the result isn't available ++ after *timeout* seconds from the original call to :meth:`Executor.map`. ++ *timeout* can be an int or a float. If *timeout* is not specified or ++ ``None``, there is no limit to the wait time. If a call raises an ++ exception, then that exception will be raised when its value is ++ retrieved from the iterator. + + .. method:: shutdown(wait=True) + +@@ -135,20 +136,23 @@ + 'http://www.bbc.co.uk/', + 'http://some-made-up-domain.com/'] + ++ # Retrieve a single page and report the url and contents + def load_url(url, timeout): +- return urllib.request.urlopen(url, timeout=timeout).read() ++ conn = urllib.request.urlopen(url, timeout=timeout) ++ return conn.readall() + ++ # We can use a with statement to ensure threads are cleaned up promptly + with concurrent.futures.ThreadPoolExecutor(max_workers=5) as executor: +- future_to_url = dict((executor.submit(load_url, url, 60), url) +- for url in URLS) +- ++ # Start the load operations and mark each future with its URL ++ future_to_url = {executor.submit(load_url, url, 60):url for url in URLS} + for future in concurrent.futures.as_completed(future_to_url): + url = future_to_url[future] +- if future.exception() is not None: +- print('%r generated an exception: %s' % (url, +- future.exception())) ++ try: ++ data = future.result() ++ except Exception as exc: ++ print('%r generated an exception: %s' % (url, exc)) + else: +- print('%r page is %d bytes' % (url, len(future.result()))) ++ print('%r page is %d bytes' % (url, len(data))) + + + ProcessPoolExecutor +@@ -364,10 +368,11 @@ + different :class:`Executor` instances) given by *fs* that yields futures as + they complete (finished or were cancelled). Any futures that completed + before :func:`as_completed` is called will be yielded first. The returned +- iterator raises a :exc:`TimeoutError` if :meth:`__next__` is called and the +- result isn't available after *timeout* seconds from the original call to +- :func:`as_completed`. *timeout* can be an int or float. If *timeout* is not +- specified or ``None``, there is no limit to the wait time. ++ iterator raises a :exc:`TimeoutError` if :meth:`~iterator.__next__` is ++ called and the result isn't available after *timeout* seconds from the ++ original call to :func:`as_completed`. *timeout* can be an int or float. ++ If *timeout* is not specified or ``None``, there is no limit to the wait ++ time. + + + .. seealso:: +diff -r bd8afb90ebf2 Doc/library/concurrent.rst +--- /dev/null ++++ b/Doc/library/concurrent.rst +@@ -0,0 +1,6 @@ ++The :mod:`concurrent` package ++============================= ++ ++Currently, there is only one module in this package: ++ ++* :mod:`concurrent.futures` -- Launching parallel tasks +diff -r bd8afb90ebf2 Doc/library/configparser.rst +--- a/Doc/library/configparser.rst ++++ b/Doc/library/configparser.rst +@@ -389,7 +389,13 @@ + the default value to be visible again. Trying to delete a default value + causes a ``KeyError``. + +-* Trying to delete the ``DEFAULTSECT`` raises ``ValueError``. ++* ``DEFAULTSECT`` cannot be removed from the parser: ++ ++ * trying to delete it raises ``ValueError``, ++ ++ * ``parser.clear()`` leaves it intact, ++ ++ * ``parser.popitem()`` never returns it. + + * ``parser.get(section, option, **kwargs)`` - the second argument is **not** + a fallback value. Note however that the section-level ``get()`` methods are +@@ -770,9 +776,9 @@ + # values using the mapping protocol or ConfigParser's set() does not allow + # such assignments to take place. + config.add_section('Section1') +- config.set('Section1', 'int', '15') +- config.set('Section1', 'bool', 'true') +- config.set('Section1', 'float', '3.1415') ++ config.set('Section1', 'an_int', '15') ++ config.set('Section1', 'a_bool', 'true') ++ config.set('Section1', 'a_float', '3.1415') + config.set('Section1', 'baz', 'fun') + config.set('Section1', 'bar', 'Python') + config.set('Section1', 'foo', '%(bar)s is %(baz)s!') +@@ -790,13 +796,13 @@ + + # getfloat() raises an exception if the value is not a float + # getint() and getboolean() also do this for their respective types +- float = config.getfloat('Section1', 'float') +- int = config.getint('Section1', 'int') +- print(float + int) ++ a_float = config.getfloat('Section1', 'a_float') ++ an_int = config.getint('Section1', 'an_int') ++ print(a_float + an_int) + + # Notice that the next output does not interpolate '%(bar)s' or '%(baz)s'. + # This is because we are using a RawConfigParser(). +- if config.getboolean('Section1', 'bool'): ++ if config.getboolean('Section1', 'a_bool'): + print(config.get('Section1', 'foo')) + + To get interpolation, use :class:`ConfigParser`:: +@@ -1007,7 +1013,7 @@ + .. versionadded:: 3.2 + + +- .. method:: get(section, option, raw=False, [vars, fallback]) ++ .. method:: get(section, option, *, raw=False, vars=None[, fallback]) + + Get an *option* value for the named *section*. If *vars* is provided, it + must be a dictionary. The *option* is looked up in *vars* (if provided), +@@ -1025,21 +1031,21 @@ + (especially when using the mapping protocol). + + +- .. method:: getint(section, option, raw=False, [vars, fallback]) ++ .. method:: getint(section, option, *, raw=False, vars=None[, fallback]) + + A convenience method which coerces the *option* in the specified *section* + to an integer. See :meth:`get` for explanation of *raw*, *vars* and + *fallback*. + + +- .. method:: getfloat(section, option, raw=False, [vars, fallback]) ++ .. method:: getfloat(section, option, *, raw=False, vars=None[, fallback]) + + A convenience method which coerces the *option* in the specified *section* + to a floating point number. See :meth:`get` for explanation of *raw*, + *vars* and *fallback*. + + +- .. method:: getboolean(section, option, raw=False, [vars, fallback]) ++ .. method:: getboolean(section, option, *, raw=False, vars=None[, fallback]) + + A convenience method which coerces the *option* in the specified *section* + to a Boolean value. Note that the accepted values for the option are +@@ -1051,7 +1057,8 @@ + *fallback*. + + +- .. method:: items([section], raw=False, vars=None) ++ .. method:: items(raw=False, vars=None) ++ items(section, raw=False, vars=None) + + When *section* is not given, return a list of *section_name*, + *section_proxy* pairs, including DEFAULTSECT. +@@ -1149,7 +1156,13 @@ + RawConfigParser Objects + ----------------------- + +-.. class:: RawConfigParser(defaults=None, dict_type=collections.OrderedDict, allow_no_value=False, delimiters=('=', ':'), comment_prefixes=('#', ';'), inline_comment_prefixes=None, strict=True, empty_lines_in_values=True, default_section=configaparser.DEFAULTSECT, interpolation=None) ++.. class:: RawConfigParser(defaults=None, dict_type=collections.OrderedDict, \ ++ allow_no_value=False, *, delimiters=('=', ':'), \ ++ comment_prefixes=('#', ';'), \ ++ inline_comment_prefixes=None, strict=True, \ ++ empty_lines_in_values=True, \ ++ default_section=configparser.DEFAULTSECT[, \ ++ interpolation]) + + Legacy variant of the :class:`ConfigParser` with interpolation disabled + by default and unsafe ``add_section`` and ``set`` methods. +diff -r bd8afb90ebf2 Doc/library/contextlib.rst +--- a/Doc/library/contextlib.rst ++++ b/Doc/library/contextlib.rst +@@ -184,7 +184,7 @@ + files = [stack.enter_context(open(fname)) for fname in filenames] + # All opened files will automatically be closed at the end of + # the with statement, even if attempts to open files later +- # in the list throw an exception ++ # in the list raise an exception + + Each instance maintains a stack of registered callbacks that are called in + reverse order when the instance is closed (either explicitly or implicitly +diff -r bd8afb90ebf2 Doc/library/copy.rst +--- a/Doc/library/copy.rst ++++ b/Doc/library/copy.rst +@@ -67,8 +67,8 @@ + + Classes can use the same interfaces to control copying that they use to control + pickling. See the description of module :mod:`pickle` for information on these +-methods. The :mod:`copy` module does not use the :mod:`copyreg` registration +-module. ++methods. In fact, :mod:`copy` module uses the registered pickle functions from ++:mod:`copyreg` module. + + .. index:: + single: __copy__() (copy protocol) +diff -r bd8afb90ebf2 Doc/library/copyreg.rst +--- a/Doc/library/copyreg.rst ++++ b/Doc/library/copyreg.rst +@@ -9,9 +9,10 @@ + module: pickle + module: copy + +-The :mod:`copyreg` module provides support for the :mod:`pickle` module. The +-:mod:`copy` module is likely to use this in the future as well. It provides +-configuration information about object constructors which are not classes. ++The :mod:`copyreg` module offers a way to define fuctions used while pickling ++specific objects. The :mod:`pickle` and :mod:`copy` modules use those functions ++when pickling/copying those objects. The module provides configuration ++information about object constructors which are not classes. + Such constructors may be factory functions or class instances. + + +@@ -37,3 +38,25 @@ + :attr:`~pickle.Pickler.dispatch_table` attribute of a pickler + object or subclass of :class:`pickle.Pickler` can also be used for + declaring reduction functions. ++ ++Example ++------- ++ ++The example below would like to show how to register a pickle function and how ++it will be used: ++ ++ >>> import copyreg, copy, pickle ++ >>> class C(object): ++ ... def __init__(self, a): ++ ... self.a = a ++ ... ++ >>> def pickle_c(c): ++ ... print("pickling a C instance...") ++ ... return C, (c.a,) ++ ... ++ >>> copyreg.pickle(C, pickle_c) ++ >>> c = C(1) ++ >>> d = copy.copy(c) ++ pickling a C instance... ++ >>> p = pickle.dumps(c) ++ pickling a C instance... +diff -r bd8afb90ebf2 Doc/library/crypt.rst +--- a/Doc/library/crypt.rst ++++ b/Doc/library/crypt.rst +@@ -121,11 +121,14 @@ + Examples + -------- + +-A simple example illustrating typical use:: ++A simple example illustrating typical use (a constant-time comparison ++operation is needed to limit exposure to timing attacks. ++:func:`hmac.compare_digest` is suitable for this purpose):: + + import pwd + import crypt + import getpass ++ from hmac import compare_digest as compare_hash + + def login(): + username = input('Python login: ') +@@ -134,7 +137,7 @@ + if cryptedpasswd == 'x' or cryptedpasswd == '*': + raise ValueError('no support for shadow passwords') + cleartext = getpass.getpass() +- return crypt.crypt(cleartext, cryptedpasswd) == cryptedpasswd ++ return compare_hash(crypt.crypt(cleartext, cryptedpasswd), cryptedpasswd) + else: + return True + +@@ -142,7 +145,8 @@ + check it against the original:: + + import crypt ++ from hmac import compare_digest as compare_hash + + hashed = crypt.crypt(plaintext) +- if hashed != crypt.crypt(plaintext, hashed): ++ if not compare_hash(hashed, crypt.crypt(plaintext, hashed)): + raise ValueError("hashed version doesn't validate against original") +diff -r bd8afb90ebf2 Doc/library/crypto.rst +--- a/Doc/library/crypto.rst ++++ b/Doc/library/crypto.rst +@@ -8,6 +8,7 @@ + + The modules described in this chapter implement various algorithms of a + cryptographic nature. They are available at the discretion of the installation. ++On Unix systems, the :mod:`crypt` module may also be available. + Here's an overview: + + +diff -r bd8afb90ebf2 Doc/library/csv.rst +--- a/Doc/library/csv.rst ++++ b/Doc/library/csv.rst +@@ -71,9 +71,10 @@ + A short usage example:: + + >>> import csv +- >>> spamReader = csv.reader(open('eggs.csv', newline=''), delimiter=' ', quotechar='|') +- >>> for row in spamReader: +- ... print(', '.join(row)) ++ >>> with open('eggs.csv', newline='') as csvfile: ++ ... spamreader = csv.reader(csvfile, delimiter=' ', quotechar='|') ++ ... for row in spamreader: ++ ... print(', '.join(row)) + Spam, Spam, Spam, Spam, Spam, Baked Beans + Spam, Lovely Spam, Wonderful Spam + +@@ -99,11 +100,12 @@ + + A short usage example:: + +- >>> import csv +- >>> spamWriter = csv.writer(open('eggs.csv', 'w', newline=''), delimiter=' ', +- ... quotechar='|', quoting=csv.QUOTE_MINIMAL) +- >>> spamWriter.writerow(['Spam'] * 5 + ['Baked Beans']) +- >>> spamWriter.writerow(['Spam', 'Lovely Spam', 'Wonderful Spam']) ++ import csv ++ with open('eggs.csv', 'w', newline='') as csvfile: ++ spamwriter = csv.writer(csvfile, delimiter=' ', ++ quotechar='|', quoting=csv.QUOTE_MINIMAL) ++ spamwriter.writerow(['Spam'] * 5 + ['Baked Beans']) ++ spamwriter.writerow(['Spam', 'Lovely Spam', 'Wonderful Spam']) + + + .. function:: register_dialect(name[, dialect], **fmtparams) +@@ -221,11 +223,11 @@ + + An example for :class:`Sniffer` use:: + +- csvfile = open("example.csv") +- dialect = csv.Sniffer().sniff(csvfile.read(1024)) +- csvfile.seek(0) +- reader = csv.reader(csvfile, dialect) +- # ... process CSV file contents here ... ++ with open('example.csv') as csvfile: ++ dialect = csv.Sniffer().sniff(csvfile.read(1024)) ++ csvfile.seek(0) ++ reader = csv.reader(csvfile, dialect) ++ # ... process CSV file contents here ... + + + The :mod:`csv` module defines the following constants: +@@ -339,6 +341,11 @@ + The default is :const:`False`. + + ++.. attribute:: Dialect.strict ++ ++ When ``True``, raise exception :exc:`Error` on bad CSV input. ++ The default is ``False``. ++ + Reader Objects + -------------- + +diff -r bd8afb90ebf2 Doc/library/ctypes.rst +--- a/Doc/library/ctypes.rst ++++ b/Doc/library/ctypes.rst +@@ -1094,8 +1094,8 @@ + Surprises + ^^^^^^^^^ + +-There are some edges in :mod:`ctypes` where you may be expect something else than +-what actually happens. ++There are some edges in :mod:`ctypes` where you might expect something other ++than what actually happens. + + Consider the following example:: + +diff -r bd8afb90ebf2 Doc/library/curses.rst +--- a/Doc/library/curses.rst ++++ b/Doc/library/curses.rst +@@ -377,7 +377,8 @@ + is to be displayed. + + +-.. function:: newwin([nlines, ncols,] begin_y, begin_x) ++.. function:: newwin(begin_y, begin_x) ++ newwin(nlines, ncols, begin_y, begin_x) + + Return a new window, whose left-upper corner is at ``(begin_y, begin_x)``, and + whose height/width is *nlines*/*ncols*. +@@ -656,7 +657,8 @@ + the following methods and attributes: + + +-.. method:: window.addch([y, x,] ch[, attr]) ++.. method:: window.addch(ch[, attr]) ++ window.addch(y, x, ch[, attr]) + + .. note:: + +@@ -670,13 +672,15 @@ + position and attributes are the current settings for the window object. + + +-.. method:: window.addnstr([y, x,] str, n[, attr]) ++.. method:: window.addnstr(str, n[, attr]) ++ window.addnstr(y, x, str, n[, attr]) + + Paint at most *n* characters of the string *str* at ``(y, x)`` with attributes + *attr*, overwriting anything previously on the display. + + +-.. method:: window.addstr([y, x,] str[, attr]) ++.. method:: window.addstr(str[, attr]) ++ window.addstr(y, x, str[, attr]) + + Paint the string *str* at ``(y, x)`` with attributes *attr*, overwriting + anything previously on the display. +@@ -763,7 +767,10 @@ + *bs* are *horch*. The default corner characters are always used by this function. + + +-.. method:: window.chgat([y, x, ] [num,] attr) ++.. method:: window.chgat(attr) ++ window.chgat(num, attr) ++ window.chgat(y, x, attr) ++ window.chgat(y, x, num, attr) + + Set the attributes of *num* characters at the current cursor position, or at + position ``(y, x)`` if supplied. If no value of *num* is given or *num* = -1, +@@ -812,7 +819,8 @@ + Delete the line under the cursor. All following lines are moved up by one line. + + +-.. method:: window.derwin([nlines, ncols,] begin_y, begin_x) ++.. method:: window.derwin(begin_y, begin_x) ++ window.derwin(nlines, ncols, begin_y, begin_x) + + An abbreviation for "derive window", :meth:`derwin` is the same as calling + :meth:`subwin`, except that *begin_y* and *begin_x* are relative to the origin +@@ -837,7 +845,7 @@ + .. attribute:: window.encoding + + Encoding used to encode method arguments (Unicode strings and characters). +- The encoding attribute is inherited from by parent window when a subwindow ++ The encoding attribute is inherited from the parent window when a subwindow + is created, for example with :meth:`window.subwin`. By default, the locale + encoding is used (see :func:`locale.getpreferredencoding`). + +@@ -906,7 +914,8 @@ + upper-left corner. + + +-.. method:: window.hline([y, x,] ch, n) ++.. method:: window.hline(ch, n) ++ window.hline(y, x, ch, n) + + Display a horizontal line starting at ``(y, x)`` with length *n* consisting of + the character *ch*. +@@ -940,7 +949,8 @@ + the character proper, and upper bits are the attributes. + + +-.. method:: window.insch([y, x,] ch[, attr]) ++.. method:: window.insch(ch[, attr]) ++ window.insch(y, x, ch[, attr]) + + Paint character *ch* at ``(y, x)`` with attributes *attr*, moving the line from + position *x* right by one character. +@@ -961,7 +971,8 @@ + line. + + +-.. method:: window.insnstr([y, x,] str, n [, attr]) ++.. method:: window.insnstr(str, n[, attr]) ++ window.insnstr(y, x, str, n[, attr]) + + Insert a character string (as many characters as will fit on the line) before + the character under the cursor, up to *n* characters. If *n* is zero or +@@ -970,7 +981,8 @@ + The cursor position does not change (after moving to *y*, *x*, if specified). + + +-.. method:: window.insstr([y, x, ] str [, attr]) ++.. method:: window.insstr(str[, attr]) ++ window.insstr(y, x, str[, attr]) + + Insert a character string (as many characters as will fit on the line) before + the character under the cursor. All characters to the right of the cursor are +@@ -978,7 +990,8 @@ + position does not change (after moving to *y*, *x*, if specified). + + +-.. method:: window.instr([y, x] [, n]) ++.. method:: window.instr([n]) ++ window.instr(y, x[, n]) + + Return a string of characters, extracted from the window starting at the + current cursor position, or at *y*, *x* if specified. Attributes are stripped +@@ -1153,13 +1166,15 @@ + Turn on attribute *A_STANDOUT*. + + +-.. method:: window.subpad([nlines, ncols,] begin_y, begin_x) ++.. method:: window.subpad(begin_y, begin_x) ++ window.subpad(nlines, ncols, begin_y, begin_x) + + Return a sub-window, whose upper-left corner is at ``(begin_y, begin_x)``, and + whose width/height is *ncols*/*nlines*. + + +-.. method:: window.subwin([nlines, ncols,] begin_y, begin_x) ++.. method:: window.subwin(begin_y, begin_x) ++ window.subwin(nlines, ncols, begin_y, begin_x) + + Return a sub-window, whose upper-left corner is at ``(begin_y, begin_x)``, and + whose width/height is *ncols*/*nlines*. +@@ -1216,7 +1231,8 @@ + :meth:`refresh`. + + +-.. method:: window.vline([y, x,] ch, n) ++.. method:: window.vline(ch, n) ++ window.vline(y, x, ch, n) + + Display a vertical line starting at ``(y, x)`` with length *n* consisting of the + character *ch*. +diff -r bd8afb90ebf2 Doc/library/datetime.rst +--- a/Doc/library/datetime.rst ++++ b/Doc/library/datetime.rst +@@ -1442,7 +1442,7 @@ + instantiated directly. You need to derive a concrete subclass, and (at least) + supply implementations of the standard :class:`tzinfo` methods needed by the + :class:`.datetime` methods you use. The :mod:`datetime` module supplies +-a simple concrete subclass of :class:`tzinfo` :class:`timezone` which can reprsent ++a simple concrete subclass of :class:`tzinfo` :class:`timezone` which can represent + timezones with fixed offset from UTC such as UTC itself or North American EST and + EDT. + +diff -r bd8afb90ebf2 Doc/library/decimal.rst +--- a/Doc/library/decimal.rst ++++ b/Doc/library/decimal.rst +@@ -400,6 +400,29 @@ + compared, sorted, and coerced to another type (such as :class:`float` or + :class:`int`). + ++ There are some small differences between arithmetic on Decimal objects and ++ arithmetic on integers and floats. When the remainder operator ``%`` is ++ applied to Decimal objects, the sign of the result is the sign of the ++ *dividend* rather than the sign of the divisor:: ++ ++ >>> (-7) % 4 ++ 1 ++ >>> Decimal(-7) % Decimal(4) ++ Decimal('-3') ++ ++ The integer division operator ``//`` behaves analogously, returning the ++ integer part of the true quotient (truncating towards zero) rather than its ++ floor, so as to preserve the usual identity ``x == (x // y) * y + x % y``:: ++ ++ >>> -7 // 4 ++ -2 ++ >>> Decimal(-7) // Decimal(4) ++ Decimal('-1') ++ ++ The ``%`` and ``//`` operators implement the ``remainder`` and ++ ``divide-integer`` operations (respectively) as described in the ++ specification. ++ + Decimal objects cannot generally be combined with floats or + instances of :class:`fractions.Fraction` in arithmetic operations: + an attempt to add a :class:`Decimal` to a :class:`float`, for +@@ -436,7 +459,7 @@ + a :class:`Decimal` instance is always canonical, so this operation returns + its argument unchanged. + +- .. method:: compare(other[, context]) ++ .. method:: compare(other, context=None) + + Compare the values of two Decimal instances. :meth:`compare` returns a + Decimal instance, and if either operand is a NaN then the result is a +@@ -447,13 +470,13 @@ + a == b ==> Decimal('0') + a > b ==> Decimal('1') + +- .. method:: compare_signal(other[, context]) ++ .. method:: compare_signal(other, context=None) + + This operation is identical to the :meth:`compare` method, except that all + NaNs signal. That is, if neither operand is a signaling NaN then any + quiet NaN operand is treated as though it were a signaling NaN. + +- .. method:: compare_total(other) ++ .. method:: compare_total(other, context=None) + + Compare two operands using their abstract representation rather than their + numerical value. Similar to the :meth:`compare` method, but the result +@@ -471,13 +494,21 @@ + higher in the total order than the second operand. See the specification + for details of the total order. + +- .. method:: compare_total_mag(other) ++ This operation is unaffected by context and is quiet: no flags are changed ++ and no rounding is performed. As an exception, the C version may raise ++ InvalidOperation if the second operand cannot be converted exactly. ++ ++ .. method:: compare_total_mag(other, context=None) + + Compare two operands using their abstract representation rather than their + value as in :meth:`compare_total`, but ignoring the sign of each operand. + ``x.compare_total_mag(y)`` is equivalent to + ``x.copy_abs().compare_total(y.copy_abs())``. + ++ This operation is unaffected by context and is quiet: no flags are changed ++ and no rounding is performed. As an exception, the C version may raise ++ InvalidOperation if the second operand cannot be converted exactly. ++ + .. method:: conjugate() + + Just returns self, this method is only to comply with the Decimal +@@ -494,7 +525,7 @@ + Return the negation of the argument. This operation is unaffected by the + context and is quiet: no flags are changed and no rounding is performed. + +- .. method:: copy_sign(other) ++ .. method:: copy_sign(other, context=None) + + Return a copy of the first operand with the sign set to be the same as the + sign of the second operand. For example: +@@ -502,10 +533,11 @@ + >>> Decimal('2.3').copy_sign(Decimal('-1.5')) + Decimal('-2.3') + +- This operation is unaffected by the context and is quiet: no flags are +- changed and no rounding is performed. +- +- .. method:: exp([context]) ++ This operation is unaffected by context and is quiet: no flags are changed ++ and no rounding is performed. As an exception, the C version may raise ++ InvalidOperation if the second operand cannot be converted exactly. ++ ++ .. method:: exp(context=None) + + Return the value of the (natural) exponential function ``e**x`` at the + given number. The result is correctly rounded using the +@@ -542,7 +574,7 @@ + + .. versionadded:: 3.1 + +- .. method:: fma(other, third[, context]) ++ .. method:: fma(other, third, context=None) + + Fused multiply-add. Return self*other+third with no rounding of the + intermediate product self*other. +@@ -571,7 +603,7 @@ + Return :const:`True` if the argument is a (quiet or signaling) NaN and + :const:`False` otherwise. + +- .. method:: is_normal() ++ .. method:: is_normal(context=None) + + Return :const:`True` if the argument is a *normal* finite number. Return + :const:`False` if the argument is zero, subnormal, infinite or a NaN. +@@ -591,7 +623,7 @@ + Return :const:`True` if the argument is a signaling NaN and :const:`False` + otherwise. + +- .. method:: is_subnormal() ++ .. method:: is_subnormal(context=None) + + Return :const:`True` if the argument is subnormal, and :const:`False` + otherwise. +@@ -601,17 +633,17 @@ + Return :const:`True` if the argument is a (positive or negative) zero and + :const:`False` otherwise. + +- .. method:: ln([context]) ++ .. method:: ln(context=None) + + Return the natural (base e) logarithm of the operand. The result is + correctly rounded using the :const:`ROUND_HALF_EVEN` rounding mode. + +- .. method:: log10([context]) ++ .. method:: log10(context=None) + + Return the base ten logarithm of the operand. The result is correctly + rounded using the :const:`ROUND_HALF_EVEN` rounding mode. + +- .. method:: logb([context]) ++ .. method:: logb(context=None) + + For a nonzero number, return the adjusted exponent of its operand as a + :class:`Decimal` instance. If the operand is a zero then +@@ -619,73 +651,73 @@ + is raised. If the operand is an infinity then ``Decimal('Infinity')`` is + returned. + +- .. method:: logical_and(other[, context]) ++ .. method:: logical_and(other, context=None) + + :meth:`logical_and` is a logical operation which takes two *logical + operands* (see :ref:`logical_operands_label`). The result is the + digit-wise ``and`` of the two operands. + +- .. method:: logical_invert([context]) ++ .. method:: logical_invert(context=None) + + :meth:`logical_invert` is a logical operation. The + result is the digit-wise inversion of the operand. + +- .. method:: logical_or(other[, context]) ++ .. method:: logical_or(other, context=None) + + :meth:`logical_or` is a logical operation which takes two *logical + operands* (see :ref:`logical_operands_label`). The result is the + digit-wise ``or`` of the two operands. + +- .. method:: logical_xor(other[, context]) ++ .. method:: logical_xor(other, context=None) + + :meth:`logical_xor` is a logical operation which takes two *logical + operands* (see :ref:`logical_operands_label`). The result is the + digit-wise exclusive or of the two operands. + +- .. method:: max(other[, context]) ++ .. method:: max(other, context=None) + + Like ``max(self, other)`` except that the context rounding rule is applied + before returning and that :const:`NaN` values are either signaled or + ignored (depending on the context and whether they are signaling or + quiet). + +- .. method:: max_mag(other[, context]) ++ .. method:: max_mag(other, context=None) + + Similar to the :meth:`.max` method, but the comparison is done using the + absolute values of the operands. + +- .. method:: min(other[, context]) ++ .. method:: min(other, context=None) + + Like ``min(self, other)`` except that the context rounding rule is applied + before returning and that :const:`NaN` values are either signaled or + ignored (depending on the context and whether they are signaling or + quiet). + +- .. method:: min_mag(other[, context]) ++ .. method:: min_mag(other, context=None) + + Similar to the :meth:`.min` method, but the comparison is done using the + absolute values of the operands. + +- .. method:: next_minus([context]) ++ .. method:: next_minus(context=None) + + Return the largest number representable in the given context (or in the + current thread's context if no context is given) that is smaller than the + given operand. + +- .. method:: next_plus([context]) ++ .. method:: next_plus(context=None) + + Return the smallest number representable in the given context (or in the + current thread's context if no context is given) that is larger than the + given operand. + +- .. method:: next_toward(other[, context]) ++ .. method:: next_toward(other, context=None) + + If the two operands are unequal, return the number closest to the first + operand in the direction of the second operand. If both operands are + numerically equal, return a copy of the first operand with the sign set to + be the same as the sign of the second operand. + +- .. method:: normalize([context]) ++ .. method:: normalize(context=None) + + Normalize the number by stripping the rightmost trailing zeros and + converting any result equal to :const:`Decimal('0')` to +@@ -694,7 +726,7 @@ + ``Decimal('0.321000e+2')`` both normalize to the equivalent value + ``Decimal('32.1')``. + +- .. method:: number_class([context]) ++ .. method:: number_class(context=None) + + Return a string describing the *class* of the operand. The returned value + is one of the following ten strings. +@@ -710,7 +742,7 @@ + * ``"NaN"``, indicating that the operand is a quiet NaN (Not a Number). + * ``"sNaN"``, indicating that the operand is a signaling NaN. + +- .. method:: quantize(exp[, rounding[, context[, watchexp]]]) ++ .. method:: quantize(exp, rounding=None, context=None, watchexp=True) + + Return a value equal to the first operand after rounding and having the + exponent of the second operand. +@@ -748,16 +780,25 @@ + class does all its arithmetic. Included for compatibility with the + specification. + +- .. method:: remainder_near(other[, context]) +- +- Compute the modulo as either a positive or negative value depending on +- which is closest to zero. For instance, ``Decimal(10).remainder_near(6)`` +- returns ``Decimal('-2')`` which is closer to zero than ``Decimal('4')``. +- +- If both are equally close, the one chosen will have the same sign as +- *self*. +- +- .. method:: rotate(other[, context]) ++ .. method:: remainder_near(other, context=None) ++ ++ Return the remainder from dividing *self* by *other*. This differs from ++ ``self % other`` in that the sign of the remainder is chosen so as to ++ minimize its absolute value. More precisely, the return value is ++ ``self - n * other`` where ``n`` is the integer nearest to the exact ++ value of ``self / other``, and if two integers are equally near then the ++ even one is chosen. ++ ++ If the result is zero then its sign will be the sign of *self*. ++ ++ >>> Decimal(18).remainder_near(Decimal(10)) ++ Decimal('-2') ++ >>> Decimal(25).remainder_near(Decimal(10)) ++ Decimal('5') ++ >>> Decimal(35).remainder_near(Decimal(10)) ++ Decimal('-5') ++ ++ .. method:: rotate(other, context=None) + + Return the result of rotating the digits of the first operand by an amount + specified by the second operand. The second operand must be an integer in +@@ -768,18 +809,22 @@ + length precision if necessary. The sign and exponent of the first operand + are unchanged. + +- .. method:: same_quantum(other[, context]) ++ .. method:: same_quantum(other, context=None) + + Test whether self and other have the same exponent or whether both are + :const:`NaN`. + +- .. method:: scaleb(other[, context]) ++ This operation is unaffected by context and is quiet: no flags are changed ++ and no rounding is performed. As an exception, the C version may raise ++ InvalidOperation if the second operand cannot be converted exactly. ++ ++ .. method:: scaleb(other, context=None) + + Return the first operand with exponent adjusted by the second. + Equivalently, return the first operand multiplied by ``10**other``. The + second operand must be an integer. + +- .. method:: shift(other[, context]) ++ .. method:: shift(other, context=None) + + Return the result of shifting the digits of the first operand by an amount + specified by the second operand. The second operand must be an integer in +@@ -789,12 +834,12 @@ + right. Digits shifted into the coefficient are zeros. The sign and + exponent of the first operand are unchanged. + +- .. method:: sqrt([context]) ++ .. method:: sqrt(context=None) + + Return the square root of the argument to full precision. + + +- .. method:: to_eng_string([context]) ++ .. method:: to_eng_string(context=None) + + Convert to an engineering-type string. + +@@ -802,12 +847,12 @@ + are up to 3 digits left of the decimal place. For example, converts + ``Decimal('123E+1')`` to ``Decimal('1.23E+3')`` + +- .. method:: to_integral([rounding[, context]]) ++ .. method:: to_integral(rounding=None, context=None) + + Identical to the :meth:`to_integral_value` method. The ``to_integral`` + name has been kept for compatibility with older versions. + +- .. method:: to_integral_exact([rounding[, context]]) ++ .. method:: to_integral_exact(rounding=None, context=None) + + Round to the nearest integer, signaling :const:`Inexact` or + :const:`Rounded` as appropriate if rounding occurs. The rounding mode is +@@ -815,7 +860,7 @@ + ``context``. If neither parameter is given then the rounding mode of the + current context is used. + +- .. method:: to_integral_value([rounding[, context]]) ++ .. method:: to_integral_value(rounding=None, context=None) + + Round to the nearest integer without signaling :const:`Inexact` or + :const:`Rounded`. If given, applies *rounding*; otherwise, uses the +@@ -861,10 +906,10 @@ + You can also use the :keyword:`with` statement and the :func:`localcontext` + function to temporarily change the active context. + +-.. function:: localcontext([c]) ++.. function:: localcontext(ctx=None) + + Return a context manager that will set the current context for the active thread +- to a copy of *c* on entry to the with-statement and restore the previous context ++ to a copy of *ctx* on entry to the with-statement and restore the previous context + when exiting the with-statement. If no context is specified, a copy of the + current context is used. + +@@ -1283,7 +1328,7 @@ + identity operation. + + +- .. method:: power(x, y[, modulo]) ++ .. method:: power(x, y, modulo=None) + + Return ``x`` to the power of ``y``, reduced modulo ``modulo`` if given. + +diff -r bd8afb90ebf2 Doc/library/dis.rst +--- a/Doc/library/dis.rst ++++ b/Doc/library/dis.rst +@@ -660,10 +660,10 @@ + + .. opcode:: FOR_ITER (delta) + +- ``TOS`` is an :term:`iterator`. Call its :meth:`__next__` method. If this +- yields a new value, push it on the stack (leaving the iterator below it). If +- the iterator indicates it is exhausted ``TOS`` is popped, and the byte code +- counter is incremented by *delta*. ++ ``TOS`` is an :term:`iterator`. Call its :meth:`~iterator.__next__` method. ++ If this yields a new value, push it on the stack (leaving the iterator below ++ it). If the iterator indicates it is exhausted ``TOS`` is popped, and the ++ byte code counter is incremented by *delta*. + + + .. opcode:: LOAD_GLOBAL (namei) +@@ -763,9 +763,10 @@ + .. opcode:: MAKE_CLOSURE (argc) + + Creates a new function object, sets its *__closure__* slot, and pushes it on +- the stack. TOS is the code associated with the function, TOS1 the tuple +- containing cells for the closure's free variables. The function also has +- *argc* default parameters, which are found below the cells. ++ the stack. TOS is the :term:`qualified name` of the function, TOS1 is the ++ code associated with the function, and TOS2 is the tuple containing cells for ++ the closure's free variables. The function also has *argc* default parameters, ++ which are found below the cells. + + + .. opcode:: BUILD_SLICE (argc) +diff -r bd8afb90ebf2 Doc/library/doctest.rst +--- a/Doc/library/doctest.rst ++++ b/Doc/library/doctest.rst +@@ -1,3 +1,5 @@ ++:keepdoctest: ++ + :mod:`doctest` --- Test interactive Python examples + =================================================== + +@@ -318,7 +320,8 @@ + Tabs in output generated by the tested code are not modified. Because any + hard tabs in the sample output *are* expanded, this means that if the code + output includes hard tabs, the only way the doctest can pass is if the +- :const:`NORMALIZE_WHITESPACE` option or directive is in effect. ++ :const:`NORMALIZE_WHITESPACE` option or :ref:`directive ` ++ is in effect. + Alternatively, the test can be rewritten to capture the output and compare it + to an expected value as part of the test. This handling of tabs in the + source was arrived at through trial and error, and has proven to be the least +@@ -338,7 +341,7 @@ + Backslashes in a raw docstring: m\n + + Otherwise, the backslash will be interpreted as part of the string. For example, +- the "\\" above would be interpreted as a newline character. Alternatively, you ++ the ``\n`` above would be interpreted as a newline character. Alternatively, you + can double each backslash in the doctest version (and not use a raw string):: + + >>> def f(x): +@@ -483,15 +486,16 @@ + SyntaxError: invalid syntax + + ++.. _option-flags-and-directives: + .. _doctest-options: + +-Option Flags and Directives +-^^^^^^^^^^^^^^^^^^^^^^^^^^^ ++Option Flags ++^^^^^^^^^^^^ + + A number of option flags control various aspects of doctest's behavior. + Symbolic names for the flags are supplied as module constants, which can be + or'ed together and passed to various functions. The names can also be used in +-doctest directives (see below). ++:ref:`doctest directives `. + + The first group of options define test semantics, controlling aspects of how + doctest decides whether actual output matches an example's expected output: +@@ -545,14 +549,14 @@ + :exc:`TypeError` is raised. + + It will also ignore the module name used in Python 3 doctest reports. Hence +- both these variations will work regardless of whether the test is run under +- Python 2.7 or Python 3.2 (or later versions): ++ both of these variations will work with the flag specified, regardless of ++ whether the test is run under Python 2.7 or Python 3.2 (or later versions):: + +- >>> raise CustomError('message') #doctest: +IGNORE_EXCEPTION_DETAIL ++ >>> raise CustomError('message') + Traceback (most recent call last): + CustomError: message + +- >>> raise CustomError('message') #doctest: +IGNORE_EXCEPTION_DETAIL ++ >>> raise CustomError('message') + Traceback (most recent call last): + my_module.CustomError: message + +@@ -562,15 +566,16 @@ + exception name. Using :const:`IGNORE_EXCEPTION_DETAIL` and the details + from Python 2.3 is also the only clear way to write a doctest that doesn't + care about the exception detail yet continues to pass under Python 2.3 or +- earlier (those releases do not support doctest directives and ignore them +- as irrelevant comments). For example, :: ++ earlier (those releases do not support :ref:`doctest directives ++ ` and ignore them as irrelevant comments). For example:: + +- >>> (1, 2)[3] = 'moo' #doctest: +IGNORE_EXCEPTION_DETAIL ++ >>> (1, 2)[3] = 'moo' + Traceback (most recent call last): + File "", line 1, in ? + TypeError: object doesn't support item assignment + +- passes under Python 2.3 and later Python versions, even though the detail ++ passes under Python 2.3 and later Python versions with the flag specified, ++ even though the detail + changed in Python 2.4 to say "does not" instead of "doesn't". + + .. versionchanged:: 3.2 +@@ -632,9 +637,30 @@ + + A bitmask or'ing together all the reporting flags above. + +-"Doctest directives" may be used to modify the option flags for individual +-examples. Doctest directives are expressed as a special Python comment +-following an example's source code: ++ ++There is also a way to register new option flag names, though this isn't ++useful unless you intend to extend :mod:`doctest` internals via subclassing: ++ ++ ++.. function:: register_optionflag(name) ++ ++ Create a new option flag with a given name, and return the new flag's integer ++ value. :func:`register_optionflag` can be used when subclassing ++ :class:`OutputChecker` or :class:`DocTestRunner` to create new options that are ++ supported by your subclasses. :func:`register_optionflag` should always be ++ called using the following idiom:: ++ ++ MY_FLAG = register_optionflag('MY_FLAG') ++ ++ ++.. _doctest-directives: ++ ++Directives ++^^^^^^^^^^ ++ ++Doctest directives may be used to modify the :ref:`option flags ++` for an individual example. Doctest directives are ++special Python comments following an example's source code: + + .. productionlist:: doctest + directive: "#" "doctest:" `directive_options` +@@ -652,7 +678,7 @@ + + For example, this test passes:: + +- >>> print(list(range(20))) #doctest: +NORMALIZE_WHITESPACE ++ >>> print(list(range(20))) # doctest: +NORMALIZE_WHITESPACE + [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, + 10, 11, 12, 13, 14, 15, 16, 17, 18, 19] + +@@ -664,7 +690,8 @@ + >>> print(list(range(20))) # doctest: +ELLIPSIS + [0, 1, ..., 18, 19] + +-Multiple directives can be used on a single physical line, separated by commas:: ++Multiple directives can be used on a single physical line, separated by ++commas:: + + >>> print(list(range(20))) # doctest: +ELLIPSIS, +NORMALIZE_WHITESPACE + [0, 1, ..., 18, 19] +@@ -690,20 +717,6 @@ + functions that run doctests, establishing different defaults. In such cases, + disabling an option via ``-`` in a directive can be useful. + +-There's also a way to register new option flag names, although this isn't useful +-unless you intend to extend :mod:`doctest` internals via subclassing: +- +- +-.. function:: register_optionflag(name) +- +- Create a new option flag with a given name, and return the new flag's integer +- value. :func:`register_optionflag` can be used when subclassing +- :class:`OutputChecker` or :class:`DocTestRunner` to create new options that are +- supported by your subclasses. :func:`register_optionflag` should always be +- called using the following idiom:: +- +- MY_FLAG = register_optionflag('MY_FLAG') +- + + .. _doctest-warnings: + +@@ -1024,6 +1037,16 @@ + + This function uses the same search technique as :func:`testmod`. + ++ .. note:: ++ Unlike :func:`testmod` and :class:`DocTestFinder`, this function raises ++ a :exc:`ValueError` if *module* contains no docstrings. You can prevent ++ this error by passing a :class:`DocTestFinder` instance as the ++ *test_finder* argument with its *exclude_empty* keyword argument set ++ to ``False``:: ++ ++ >>> finder = doctest.DocTestFinder(exclude_empty=False) ++ >>> suite = doctest.DocTestSuite(test_finder=finder) ++ + + Under the covers, :func:`DocTestSuite` creates a :class:`unittest.TestSuite` out + of :class:`doctest.DocTestCase` instances, and :class:`DocTestCase` is a +diff -r bd8afb90ebf2 Doc/library/dummy_threading.rst +--- a/Doc/library/dummy_threading.rst ++++ b/Doc/library/dummy_threading.rst +@@ -17,7 +17,7 @@ + try: + import threading + except ImportError: +- import dummy_threading ++ import dummy_threading as threading + + Be careful to not use this module where deadlock might occur from a thread being + created that blocks waiting for another thread to be created. This often occurs +diff -r bd8afb90ebf2 Doc/library/exceptions.rst +--- a/Doc/library/exceptions.rst ++++ b/Doc/library/exceptions.rst +@@ -39,17 +39,31 @@ + new exception is not handled the traceback that is eventually displayed will + include the originating exception(s) and the final exception. + +-This implicit exception chain can be made explicit by using :keyword:`from` with +-:keyword:`raise`. The single argument to :keyword:`from` must be an exception +-or ``None``. It will be set as :attr:`__cause__` on the raised exception. +-Setting :attr:`__cause__` implicitly sets the :attr:`__suppress_context__` to +-``True``. If :attr:`__cause__` is an exception, it will be displayed. If +-:attr:`__cause__` is present or :attr:`__suppress_context__` has a true value, +-:attr:`__context__` will not be displayed. ++When raising a new exception (rather than using a bare ``raise`` to re-raise ++the exception currently being handled), the implicit exception context can be ++supplemented with an explicit cause by using :keyword:`from` with ++:keyword:`raise`:: + +-In either case, the default exception handling code will not display any of the +-remaining links in the :attr:`__context__` chain if :attr:`__cause__` has been +-set. ++ raise new_exc from original_exc ++ ++The expression following :keyword:`from` must be an exception or ``None``. It ++will be set as :attr:`__cause__` on the raised exception. Setting ++:attr:`__cause__` also implicitly sets the :attr:`__suppress_context__` ++attribute to ``True``, so that using ``raise new_exc from None`` ++effectively replaces the old exception with the new one for display ++purposes (e.g. converting :exc:`KeyError` to :exc:`AttributeError`, while ++leaving the old exception available in :attr:`__context__` for introspection ++when debugging. ++ ++The default traceback display code shows these chained exceptions in ++addition to the traceback for the exception itself. An explicitly chained ++exception in :attr:`__cause__` is always shown when present. An implicitly ++chained exception in :attr:`__context__` is shown only if :attr:`__cause__` ++is :const:`None` and :attr:`__suppress_context__` is false. ++ ++In either case, the exception itself is always shown after any chained ++exceptions so that the final line of the traceback always shows the last ++exception that was raised. + + + Base classes +@@ -275,8 +289,8 @@ + .. exception:: StopIteration + + Raised by built-in function :func:`next` and an :term:`iterator`\'s +- :meth:`__next__` method to signal that there are no further items to be +- produced by the iterator. ++ :meth:`~iterator.__next__` method to signal that there are no further ++ items produced by the iterator. + + The exception object has a single attribute :attr:`value`, which is + given as an argument when constructing the exception, and defaults +@@ -371,6 +385,30 @@ + Raised when a Unicode-related encoding or decoding error occurs. It is a + subclass of :exc:`ValueError`. + ++ :exc:`UnicodeError` has attributes that describe the encoding or decoding ++ error. For example, ``err.object[err.start:err.end]`` gives the particular ++ invalid input that the codec failed on. ++ ++ .. attribute:: encoding ++ ++ The name of the encoding that raised the error. ++ ++ .. attribute:: reason ++ ++ A string describing the specific codec error. ++ ++ .. attribute:: object ++ ++ The object the codec was attempting to encode or decode. ++ ++ .. attribute:: start ++ ++ The first index of invalid data in :attr:`object`. ++ ++ .. attribute:: end ++ ++ The index after the last invalid data in :attr:`object`. ++ + + .. exception:: UnicodeEncodeError + +@@ -449,34 +487,35 @@ + + .. exception:: ConnectionError + +- A base class for connection-related issues. Subclasses are +- :exc:`BrokenPipeError`, :exc:`ConnectionAbortedError`, ++ A base class for connection-related issues. ++ ++ Subclasses are :exc:`BrokenPipeError`, :exc:`ConnectionAbortedError`, + :exc:`ConnectionRefusedError` and :exc:`ConnectionResetError`. + +- .. exception:: BrokenPipeError ++.. exception:: BrokenPipeError + +- A subclass of :exc:`ConnectionError`, raised when trying to write on a +- pipe while the other end has been closed, or trying to write on a socket +- which has been shutdown for writing. +- Corresponds to :c:data:`errno` ``EPIPE`` and ``ESHUTDOWN``. ++ A subclass of :exc:`ConnectionError`, raised when trying to write on a ++ pipe while the other end has been closed, or trying to write on a socket ++ which has been shutdown for writing. ++ Corresponds to :c:data:`errno` ``EPIPE`` and ``ESHUTDOWN``. + +- .. exception:: ConnectionAbortedError ++.. exception:: ConnectionAbortedError + +- A subclass of :exc:`ConnectionError`, raised when a connection attempt +- is aborted by the peer. +- Corresponds to :c:data:`errno` ``ECONNABORTED``. ++ A subclass of :exc:`ConnectionError`, raised when a connection attempt ++ is aborted by the peer. ++ Corresponds to :c:data:`errno` ``ECONNABORTED``. + +- .. exception:: ConnectionRefusedError ++.. exception:: ConnectionRefusedError + +- A subclass of :exc:`ConnectionError`, raised when a connection attempt +- is refused by the peer. +- Corresponds to :c:data:`errno` ``ECONNREFUSED``. ++ A subclass of :exc:`ConnectionError`, raised when a connection attempt ++ is refused by the peer. ++ Corresponds to :c:data:`errno` ``ECONNREFUSED``. + +- .. exception:: ConnectionResetError ++.. exception:: ConnectionResetError + +- A subclass of :exc:`ConnectionError`, raised when a connection is +- reset by the peer. +- Corresponds to :c:data:`errno` ``ECONNRESET``. ++ A subclass of :exc:`ConnectionError`, raised when a connection is ++ reset by the peer. ++ Corresponds to :c:data:`errno` ``ECONNRESET``. + + .. exception:: FileExistsError + +@@ -491,7 +530,7 @@ + .. exception:: InterruptedError + + Raised when a system call is interrupted by an incoming signal. +- Corresponds to :c:data:`errno` ``EEINTR``. ++ Corresponds to :c:data:`errno` ``EINTR``. + + .. exception:: IsADirectoryError + +diff -r bd8afb90ebf2 Doc/library/filecmp.rst +--- a/Doc/library/filecmp.rst ++++ b/Doc/library/filecmp.rst +@@ -176,6 +176,6 @@ + ... for sub_dcmp in dcmp.subdirs.values(): + ... print_diff_files(sub_dcmp) + ... +- >>> dcmp = dircmp('dir1', 'dir2') +- >>> print_diff_files(dcmp) ++ >>> dcmp = dircmp('dir1', 'dir2') # doctest: +SKIP ++ >>> print_diff_files(dcmp) # doctest: +SKIP + +diff -r bd8afb90ebf2 Doc/library/fnmatch.rst +--- a/Doc/library/fnmatch.rst ++++ b/Doc/library/fnmatch.rst +@@ -29,6 +29,9 @@ + | ``[!seq]`` | matches any character not in *seq* | + +------------+------------------------------------+ + ++For a literal match, wrap the meta-characters in brackets. ++For example, ``'[?]'`` matches the character ``'?'``. ++ + .. index:: module: glob + + Note that the filename separator (``'/'`` on Unix) is *not* special to this +@@ -74,8 +77,6 @@ + + Return the shell-style *pattern* converted to a regular expression. + +- Be aware there is no way to quote meta-characters. +- + Example: + + >>> import fnmatch, re +diff -r bd8afb90ebf2 Doc/library/fractions.rst +--- a/Doc/library/fractions.rst ++++ b/Doc/library/fractions.rst +@@ -56,7 +56,6 @@ + Fraction(0, 1) + >>> Fraction('3/7') + Fraction(3, 7) +- [40794 refs] + >>> Fraction(' -3/7 ') + Fraction(-3, 7) + >>> Fraction('1.414213 \t\n') +diff -r bd8afb90ebf2 Doc/library/ftplib.rst +--- a/Doc/library/ftplib.rst ++++ b/Doc/library/ftplib.rst +@@ -270,12 +270,12 @@ + .. method:: FTP.storbinary(cmd, file, blocksize=8192, callback=None, rest=None) + + Store a file in binary transfer mode. *cmd* should be an appropriate +- ``STOR`` command: ``"STOR filename"``. *file* is an open :term:`file object` +- which is read until EOF using its :meth:`read` method in blocks of size +- *blocksize* to provide the data to be stored. The *blocksize* argument +- defaults to 8192. *callback* is an optional single parameter callable that +- is called on each block of data after it is sent. *rest* means the same thing +- as in the :meth:`transfercmd` method. ++ ``STOR`` command: ``"STOR filename"``. *file* is a :term:`file object` ++ (opened in binary mode) which is read until EOF using its :meth:`read` ++ method in blocks of size *blocksize* to provide the data to be stored. ++ The *blocksize* argument defaults to 8192. *callback* is an optional single ++ parameter callable that is called on each block of data after it is sent. ++ *rest* means the same thing as in the :meth:`transfercmd` method. + + .. versionchanged:: 3.2 + *rest* parameter added. +@@ -285,9 +285,9 @@ + + Store a file in ASCII transfer mode. *cmd* should be an appropriate + ``STOR`` command (see :meth:`storbinary`). Lines are read until EOF from the +- open :term:`file object` *file* using its :meth:`readline` method to provide +- the data to be stored. *callback* is an optional single parameter callable +- that is called on each line after it is sent. ++ :term:`file object` *file* (opened in binary mode) using its :meth:`readline` ++ method to provide the data to be stored. *callback* is an optional single ++ parameter callable that is called on each line after it is sent. + + + .. method:: FTP.transfercmd(cmd, rest=None) +@@ -406,10 +406,10 @@ + .. method:: FTP.close() + + Close the connection unilaterally. This should not be applied to an already +- closed connection such as after a successful call to :meth:`quit`. After this +- call the :class:`FTP` instance should not be used any more (after a call to +- :meth:`close` or :meth:`quit` you cannot reopen the connection by issuing +- another :meth:`login` method). ++ closed connection such as after a successful call to :meth:`~FTP.quit`. ++ After this call the :class:`FTP` instance should not be used any more (after ++ a call to :meth:`close` or :meth:`~FTP.quit` you cannot reopen the ++ connection by issuing another :meth:`login` method). + + + FTP_TLS Objects +diff -r bd8afb90ebf2 Doc/library/functions.rst +--- a/Doc/library/functions.rst ++++ b/Doc/library/functions.rst +@@ -14,7 +14,7 @@ + :func:`all` :func:`dir` :func:`hex` :func:`next` :func:`slice` + :func:`any` :func:`divmod` :func:`id` :func:`object` :func:`sorted` + :func:`ascii` :func:`enumerate` :func:`input` :func:`oct` :func:`staticmethod` +-:func:`bin` :func:`eval` :func:`int` :func:`open` :func:`str` ++:func:`bin` :func:`eval` :func:`int` :func:`open` |func-str|_ + :func:`bool` :func:`exec` :func:`isinstance` :func:`ord` :func:`sum` + :func:`bytearray` :func:`filter` :func:`issubclass` :func:`pow` :func:`super` + :func:`bytes` :func:`float` :func:`iter` :func:`print` |func-tuple|_ +@@ -34,6 +34,7 @@ + .. |func-memoryview| replace:: ``memoryview()`` + .. |func-set| replace:: ``set()`` + .. |func-list| replace:: ``list()`` ++.. |func-str| replace:: ``str()`` + .. |func-tuple| replace:: ``tuple()`` + .. |func-range| replace:: ``range()`` + +@@ -122,6 +123,8 @@ + + Without an argument, an array of size 0 is created. + ++ See also :ref:`binaryseq` and :ref:`typebytearray`. ++ + + .. _func-bytes: + .. function:: bytes([source[, encoding[, errors]]]) +@@ -135,6 +138,8 @@ + + Bytes objects can also be created with literals, see :ref:`strings`. + ++ See also :ref:`binaryseq`, :ref:`typebytes`, and :ref:`bytes-methods`. ++ + + .. function:: callable(object) + +@@ -267,14 +272,17 @@ + + + .. _func-dict: +-.. function:: dict([arg]) ++.. function:: dict(**kwarg) ++ dict(mapping, **kwarg) ++ dict(iterable, **kwarg) + :noindex: + +- Create a new data dictionary, optionally with items taken from *arg*. +- The dictionary type is described in :ref:`typesmapping`. ++ Create a new dictionary. The :class:`dict` object is the dictionary class. ++ See :class:`dict` and :ref:`typesmapping` for documentation about this ++ class. + +- For other containers see the built in :class:`list`, :class:`set`, and +- :class:`tuple` classes, and the :mod:`collections` module. ++ For other containers see the built-in :class:`list`, :class:`set`, and ++ :class:`tuple` classes, as well as the :mod:`collections` module. + + + .. function:: dir([object]) +@@ -348,10 +356,10 @@ + .. function:: enumerate(iterable, start=0) + + Return an enumerate object. *iterable* must be a sequence, an +- :term:`iterator`, or some other object which supports iteration. The +- :meth:`__next__` method of the iterator returned by :func:`enumerate` returns a +- tuple containing a count (from *start* which defaults to 0) and the +- values obtained from iterating over *iterable*. ++ :term:`iterator`, or some other object which supports iteration. ++ The :meth:`~iterator.__next__` method of the iterator returned by ++ :func:`enumerate` returns a tuple containing a count (from *start* which ++ defaults to 0) and the values obtained from iterating over *iterable*. + + >>> seasons = ['Spring', 'Summer', 'Fall', 'Winter'] + >>> list(enumerate(seasons)) +@@ -514,20 +522,20 @@ + + The float type is described in :ref:`typesnumeric`. + ++ .. index:: ++ single: __format__ ++ single: string; format() (built-in function) ++ + + .. function:: format(value[, format_spec]) + +- .. index:: +- pair: str; format +- single: __format__ +- + Convert a *value* to a "formatted" representation, as controlled by + *format_spec*. The interpretation of *format_spec* will depend on the type + of the *value* argument, however there is a standard formatting syntax that + is used by most built-in types: :ref:`formatspec`. + + The default *format_spec* is an empty string which usually gives the same +- effect as calling ``str(value)``. ++ effect as calling :func:`str(value) `. + + A call to ``format(value, format_spec)`` is translated to + ``type(value).__format__(format_spec)`` which bypasses the instance +@@ -540,11 +548,13 @@ + .. function:: frozenset([iterable]) + :noindex: + +- Return a frozenset object, optionally with elements taken from *iterable*. +- The frozenset type is described in :ref:`types-set`. ++ Return a new :class:`frozenset` object, optionally with elements taken from ++ *iterable*. ``frozenset`` is a built-in class. See :class:`frozenset` and ++ :ref:`types-set` for documentation about this class. + +- For other containers see the built in :class:`dict`, :class:`list`, and +- :class:`tuple` classes, and the :mod:`collections` module. ++ For other containers see the built-in :class:`set`, :class:`list`, ++ :class:`tuple`, and :class:`dict` classes, as well as the :mod:`collections` ++ module. + + + .. function:: getattr(object, name[, default]) +@@ -629,14 +639,19 @@ + to provide elaborate line editing and history features. + + +-.. function:: int([number | string[, base]]) ++.. function:: int(x=0) ++ int(x, base=10) + +- Convert a number or string to an integer. If no arguments are given, return +- ``0``. If a number is given, return ``number.__int__()``. Conversion of +- floating point numbers to integers truncates towards zero. A string must be +- a base-radix integer literal optionally preceded by '+' or '-' (with no space +- in between) and optionally surrounded by whitespace. A base-n literal +- consists of the digits 0 to n-1, with 'a' to 'z' (or 'A' to 'Z') having ++ Convert a number or string *x* to an integer, or return ``0`` if no ++ arguments are given. If *x* is a number, return :meth:`x.__int__() ++ `. For floating point numbers, this truncates towards zero. ++ ++ If *x* is not a number or if *base* is given, then *x* must be a string, ++ :class:`bytes`, or :class:`bytearray` instance representing an :ref:`integer ++ literal ` in radix *base*. Optionally, the literal can be ++ preceded by ``+`` or ``-`` (with no space in between) and surrounded by ++ whitespace. A base-n literal consists of the digits 0 to n-1, with ``a`` ++ to ``z`` (or ``A`` to ``Z``) having + values 10 to 35. The default *base* is 10. The allowed values are 0 and 2-36. + Base-2, -8, and -16 literals can be optionally prefixed with ``0b``/``0B``, + ``0o``/``0O``, or ``0x``/``0X``, as with integer literals in code. Base 0 +@@ -678,9 +693,12 @@ + starting at ``0``). If it does not support either of those protocols, + :exc:`TypeError` is raised. If the second argument, *sentinel*, is given, + then *object* must be a callable object. The iterator created in this case +- will call *object* with no arguments for each call to its :meth:`__next__` +- method; if the value returned is equal to *sentinel*, :exc:`StopIteration` +- will be raised, otherwise the value will be returned. ++ will call *object* with no arguments for each call to its ++ :meth:`~iterator.__next__` method; if the value returned is equal to ++ *sentinel*, :exc:`StopIteration` will be raised, otherwise the value will ++ be returned. ++ ++ See also :ref:`typeiter`. + + One useful application of the second form of :func:`iter` is to read lines of + a file until a certain line is reached. The following example reads a file +@@ -702,7 +720,7 @@ + :noindex: + + Rather than being a function, :class:`list` is actually a mutable +- sequence type, as documented in :ref:`typesseq`. ++ sequence type, as documented in :ref:`typesseq-list` and :ref:`typesseq`. + + + .. function:: locals() +@@ -725,11 +743,16 @@ + already arranged into argument tuples, see :func:`itertools.starmap`\. + + +-.. function:: max(iterable[, args...], *[, key]) ++.. function:: max(iterable, *[, key]) ++ max(arg1, arg2, *args[, key]) + +- With a single argument *iterable*, return the largest item of a non-empty +- iterable (such as a string, tuple or list). With more than one argument, return +- the largest of the arguments. ++ Return the largest item in an iterable or the largest of two or more ++ arguments. ++ ++ If one positional argument is provided, *iterable* must be a non-empty ++ iterable (such as a non-empty string, tuple or list). The largest item ++ in the iterable is returned. If two or more positional arguments are ++ provided, the largest of the positional arguments is returned. + + The optional keyword-only *key* argument specifies a one-argument ordering + function like that used for :meth:`list.sort`. +@@ -748,11 +771,16 @@ + :ref:`typememoryview` for more information. + + +-.. function:: min(iterable[, args...], *[, key]) ++.. function:: min(iterable, *[, key]) ++ min(arg1, arg2, *args[, key]) + +- With a single argument *iterable*, return the smallest item of a non-empty +- iterable (such as a string, tuple or list). With more than one argument, return +- the smallest of the arguments. ++ Return the smallest item in an iterable or the smallest of two or more ++ arguments. ++ ++ If one positional argument is provided, *iterable* must be a non-empty ++ iterable (such as a non-empty string, tuple or list). The smallest item ++ in the iterable is returned. If two or more positional arguments are ++ provided, the smallest of the positional arguments is returned. + + The optional keyword-only *key* argument specifies a one-argument ordering + function like that used for :meth:`list.sort`. +@@ -764,9 +792,9 @@ + + .. function:: next(iterator[, default]) + +- Retrieve the next item from the *iterator* by calling its :meth:`__next__` +- method. If *default* is given, it is returned if the iterator is exhausted, +- otherwise :exc:`StopIteration` is raised. ++ Retrieve the next item from the *iterator* by calling its ++ :meth:`~iterator.__next__` method. If *default* is given, it is returned ++ if the iterator is exhausted, otherwise :exc:`StopIteration` is raised. + + + .. function:: object() +@@ -910,6 +938,19 @@ + :mod:`os.open` as *opener* results in functionality similar to passing + ``None``). + ++ The following example uses the :ref:`dir_fd ` parameter of the ++ :func:`os.open` function to open a file relative to a given directory:: ++ ++ >>> import os ++ >>> dir_fd = os.open('somedir', os.O_RDONLY) ++ >>> def opener(path, flags): ++ ... return os.open(path, flags, dir_fd=dir_fd) ++ ... ++ >>> with open('spamspam.txt', 'w', opener=opener) as f: ++ ... print('This will be written to somedir/spamspam.txt', file=f) ++ ... ++ >>> os.close(dir_fd) # don't leak a file descriptor ++ + .. versionchanged:: 3.3 + The *opener* parameter was added. + The ``'x'`` mode was added. +@@ -970,16 +1011,16 @@ + must be of integer types, and *y* must be non-negative. + + +-.. function:: print([object, ...], *, sep=' ', end='\\n', file=sys.stdout, flush=False) ++.. function:: print(*objects, sep=' ', end='\\n', file=sys.stdout, flush=False) + +- Print *object*\(s) to the stream *file*, separated by *sep* and followed by ++ Print *objects* to the stream *file*, separated by *sep* and followed by + *end*. *sep*, *end* and *file*, if present, must be given as keyword + arguments. + + All non-keyword arguments are converted to strings like :func:`str` does and + written to the stream, separated by *sep* and followed by *end*. Both *sep* + and *end* must be strings; they can also be ``None``, which means to use the +- default values. If no *object* is given, :func:`print` will just write ++ default values. If no *objects* are given, :func:`print` will just write + *end*. + + The *file* argument must be an object with a ``write(string)`` method; if it +@@ -1061,11 +1102,12 @@ + + + .. _func-range: +-.. function:: range([start,] stop[, step]) ++.. function:: range(stop) ++ range(start, stop[, step]) + :noindex: + + Rather than being a function, :class:`range` is actually an immutable +- sequence type, as documented in :ref:`typesseq`. ++ sequence type, as documented in :ref:`typesseq-range` and :ref:`typesseq`. + + + .. function:: repr(object) +@@ -1087,18 +1129,18 @@ + arguments starting at ``0``). + + +-.. function:: round(x[, n]) ++.. function:: round(number[, ndigits]) + +- Return the floating point value *x* rounded to *n* digits after the decimal +- point. If *n* is omitted, it defaults to zero. Delegates to +- ``x.__round__(n)``. ++ Return the floating point value *number* rounded to *ndigits* digits after ++ the decimal point. If *ndigits* is omitted, it defaults to zero. Delegates ++ to ``number.__round__(ndigits)``. + + For the built-in types supporting :func:`round`, values are rounded to the +- closest multiple of 10 to the power minus *n*; if two multiples are equally +- close, rounding is done toward the even choice (so, for example, both +- ``round(0.5)`` and ``round(-0.5)`` are ``0``, and ``round(1.5)`` is ``2``). +- The return value is an integer if called with one argument, otherwise of the +- same type as *x*. ++ closest multiple of 10 to the power minus *ndigits*; if two multiples are ++ equally close, rounding is done toward the even choice (so, for example, ++ both ``round(0.5)`` and ``round(-0.5)`` are ``0``, and ``round(1.5)`` is ++ ``2``). The return value is an integer if called with one argument, ++ otherwise of the same type as *number*. + + .. note:: + +@@ -1113,8 +1155,13 @@ + .. function:: set([iterable]) + :noindex: + +- Return a new set, optionally with elements taken from *iterable*. +- The set type is described in :ref:`types-set`. ++ Return a new :class:`set` object, optionally with elements taken from ++ *iterable*. ``set`` is a built-in class. See :class:`set` and ++ :ref:`types-set` for documentation about this class. ++ ++ For other containers see the built-in :class:`frozenset`, :class:`list`, ++ :class:`tuple`, and :class:`dict` classes, as well as the :mod:`collections` ++ module. + + + .. function:: setattr(object, name, value) +@@ -1126,7 +1173,8 @@ + ``x.foobar = 123``. + + +-.. function:: slice([start,] stop[, step]) ++.. function:: slice(stop) ++ slice(start, stop[, step]) + + .. index:: single: Numerical Python + +@@ -1184,38 +1232,19 @@ + For more information on static methods, consult the documentation on the + standard type hierarchy in :ref:`types`. + ++ .. index:: ++ single: string; str() (built-in function) ++ + + .. _func-str: +-.. function:: str([object[, encoding[, errors]]]) ++.. function:: str(object='') ++ str(object=b'', encoding='utf-8', errors='strict') ++ :noindex: + +- Return a string version of an object, using one of the following modes: ++ Return a :class:`str` version of *object*. See :func:`str` for details. + +- If *encoding* and/or *errors* are given, :func:`str` will decode the +- *object* which can either be a byte string or a character buffer using +- the codec for *encoding*. The *encoding* parameter is a string giving +- the name of an encoding; if the encoding is not known, :exc:`LookupError` +- is raised. Error handling is done according to *errors*; this specifies the +- treatment of characters which are invalid in the input encoding. If +- *errors* is ``'strict'`` (the default), a :exc:`ValueError` is raised on +- errors, while a value of ``'ignore'`` causes errors to be silently ignored, +- and a value of ``'replace'`` causes the official Unicode replacement character, +- U+FFFD, to be used to replace input characters which cannot be decoded. +- See also the :mod:`codecs` module. +- +- When only *object* is given, this returns its nicely printable representation. +- For strings, this is the string itself. The difference with ``repr(object)`` +- is that ``str(object)`` does not always attempt to return a string that is +- acceptable to :func:`eval`; its goal is to return a printable string. +- With no arguments, this returns the empty string. +- +- Objects can specify what ``str(object)`` returns by defining a :meth:`__str__` +- special method. +- +- For more information on strings see :ref:`typesseq` which describes sequence +- functionality (strings are sequences), and also the string-specific methods +- described in the :ref:`string-methods` section. To output formatted strings, +- see the :ref:`string-formatting` section. In addition see the +- :ref:`stringservices` section. ++ ``str`` is the built-in string :term:`class`. For general information ++ about strings, see :ref:`textseq`. + + + .. function:: sum(iterable[, start]) +@@ -1292,39 +1321,37 @@ + :noindex: + + Rather than being a function, :class:`tuple` is actually an immutable +- sequence type, as documented in :ref:`typesseq`. ++ sequence type, as documented in :ref:`typesseq-tuple` and :ref:`typesseq`. + + + .. function:: type(object) ++ type(name, bases, dict) + + .. index:: object: type + +- Return the type of an *object*. The return value is a type object and +- generally the same object as returned by ``object.__class__``. ++ ++ With one argument, return the type of an *object*. The return value is a ++ type object and generally the same object as returned by ``object.__class__``. + + The :func:`isinstance` built-in function is recommended for testing the type + of an object, because it takes subclasses into account. + +- With three arguments, :func:`type` functions as a constructor as detailed +- below. + +- +-.. function:: type(name, bases, dict) +- :noindex: +- +- Return a new type object. This is essentially a dynamic form of the +- :keyword:`class` statement. The *name* string is the class name and becomes the +- :attr:`__name__` attribute; the *bases* tuple itemizes the base classes and +- becomes the :attr:`__bases__` attribute; and the *dict* dictionary is the +- namespace containing definitions for class body and becomes the :attr:`__dict__` +- attribute. For example, the following two statements create identical +- :class:`type` objects: ++ With three arguments, return a new type object. This is essentially a ++ dynamic form of the :keyword:`class` statement. The *name* string is the ++ class name and becomes the :attr:`__name__` attribute; the *bases* tuple ++ itemizes the base classes and becomes the :attr:`__bases__` attribute; ++ and the *dict* dictionary is the namespace containing definitions for class ++ body and becomes the :attr:`__dict__` attribute. For example, the ++ following two statements create identical :class:`type` objects: + + >>> class X: + ... a = 1 + ... + >>> X = type('X', (object,), dict(a=1)) + ++ See also :ref:`bltin-type-objects`. ++ + + .. function:: vars([object]) + +diff -r bd8afb90ebf2 Doc/library/gc.rst +--- a/Doc/library/gc.rst ++++ b/Doc/library/gc.rst +@@ -189,13 +189,13 @@ + after collection. The callbacks will be called with two arguments, + *phase* and *info*. + +- *phase* can one of two values: ++ *phase* can be one of two values: + + "start": The garbage collection is about to start. + + "stop": The garbage collection has finished. + +- *info* provides more information for the callback. The following ++ *info* is a dict providing more information for the callback. The following + keys are currently defined: + + "generation": The oldest generation being collected. +@@ -203,7 +203,7 @@ + "collected": When *phase* is "stop", the number of objects + successfully collected. + +- "uncollectable": when *phase* is "stop", the number of objects ++ "uncollectable": When *phase* is "stop", the number of objects + that could not be collected and were put in :data:`garbage`. + + Applications can add their own callbacks to this list. The primary +diff -r bd8afb90ebf2 Doc/library/glob.rst +--- a/Doc/library/glob.rst ++++ b/Doc/library/glob.rst +@@ -19,6 +19,9 @@ + subshell. (For tilde and shell variable expansion, use + :func:`os.path.expanduser` and :func:`os.path.expandvars`.) + ++For a literal match, wrap the meta-characters in brackets. ++For example, ``'[?]'`` matches the character ``'?'``. ++ + + .. function:: glob(pathname) + +diff -r bd8afb90ebf2 Doc/library/gzip.rst +--- a/Doc/library/gzip.rst ++++ b/Doc/library/gzip.rst +@@ -38,7 +38,7 @@ + ``'w'``, or ``'wb'`` for binary mode, or ``'rt'``, ``'at'``, or ``'wt'`` for + text mode. The default is ``'rb'``. + +- The *compresslevel* argument is an integer from 1 to 9, as for the ++ The *compresslevel* argument is an integer from 0 to 9, as for the + :class:`GzipFile` constructor. + + For binary mode, this function is equivalent to the :class:`GzipFile` +@@ -80,9 +80,10 @@ + in text mode, use :func:`.open` (or wrap your :class:`GzipFile` with an + :class:`io.TextIOWrapper`). + +- The *compresslevel* argument is an integer from ``1`` to ``9`` controlling the +- level of compression; ``1`` is fastest and produces the least compression, and +- ``9`` is slowest and produces the most compression. The default is ``9``. ++ The *compresslevel* argument is an integer from ``0`` to ``9`` controlling ++ the level of compression; ``1`` is fastest and produces the least ++ compression, and ``9`` is slowest and produces the most compression. ``0`` ++ is no compression. The default is ``9``. + + The *mtime* argument is an optional numeric timestamp to be written to + the stream when compressing. All :program:`gzip` compressed streams are +diff -r bd8afb90ebf2 Doc/library/hashlib.rst +--- a/Doc/library/hashlib.rst ++++ b/Doc/library/hashlib.rst +@@ -40,12 +40,12 @@ + + .. note:: + +- For better multithreading performance, the Python GIL is released for ++ For better multithreading performance, the Python :term:`GIL` is released for + strings of more than 2047 bytes at object creation or on update. + + .. note:: + +- Feeding string objects is to :meth:`update` is not supported, as hashes work ++ Feeding string objects into :meth:`update` is not supported, as hashes work + on bytes, not on characters. + + .. index:: single: OpenSSL; (use in module hashlib) +diff -r bd8afb90ebf2 Doc/library/html.rst +--- a/Doc/library/html.rst ++++ b/Doc/library/html.rst +@@ -19,3 +19,10 @@ + attribute value delimited by quotes, as in ````. + + .. versionadded:: 3.2 ++ ++-------------- ++ ++Submodules in the ``html`` package are: ++ ++* :mod:`html.parser` -- HTML/XHTML parser with lenient parsing mode ++* :mod:`html.entities` -- HTML entity definitions +diff -r bd8afb90ebf2 Doc/library/http.client.rst +--- a/Doc/library/http.client.rst ++++ b/Doc/library/http.client.rst +@@ -27,7 +27,8 @@ + The module provides the following classes: + + +-.. class:: HTTPConnection(host, port=None[, strict[, timeout[, source_address]]]) ++.. class:: HTTPConnection(host, port=None[, strict][, timeout], \ ++ source_address=None) + + An :class:`HTTPConnection` instance represents one transaction with an HTTP + server. It should be instantiated passing it a host and optional port +@@ -55,7 +56,10 @@ + are not supported anymore. + + +-.. class:: HTTPSConnection(host, port=None, key_file=None, cert_file=None[, strict[, timeout[, source_address]]], *, context=None, check_hostname=None) ++.. class:: HTTPSConnection(host, port=None, key_file=None, \ ++ cert_file=None[, strict][, timeout], \ ++ source_address=None, *, context=None, \ ++ check_hostname=None) + + A subclass of :class:`HTTPConnection` that uses SSL for communication with + secure servers. Default port is ``443``. If *context* is specified, it +diff -r bd8afb90ebf2 Doc/library/http.rst +--- /dev/null ++++ b/Doc/library/http.rst +@@ -0,0 +1,11 @@ ++:mod:`http` --- HTTP modules ++============================ ++ ++``http`` is a package that collects several modules for working with the ++HyperText Transfer Protocol: ++ ++* :mod:`http.client` is a low-level HTTP protocol client; for high-level URL ++ opening use :mod:`urllib.request` ++* :mod:`http.server` contains basic HTTP server classes based on :mod:`socketserver` ++* :mod:`http.cookies` has utilities for implementing state management with cookies ++* :mod:`http.cookiejar` provides persistence of cookies +diff -r bd8afb90ebf2 Doc/library/idle.rst +--- a/Doc/library/idle.rst ++++ b/Doc/library/idle.rst +@@ -154,27 +154,77 @@ + it to the foreground (deiconifying it if necessary). + + +-Debug menu (in the Python Shell window only) +-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ++Debug menu ++^^^^^^^^^^ ++ ++* in the Python Shell window only + + Go to file/line +- look around the insert point for a filename and linenumber, open the file, and +- show the line. ++ Look around the insert point for a filename and line number, open the file, ++ and show the line. Useful to view the source lines referenced in an ++ exception traceback. + +-Open stack viewer +- show the stack traceback of the last exception ++Debugger ++ Run commands in the shell under the debugger. + +-Debugger toggle +- Run commands in the shell under the debugger ++Stack viewer ++ Show the stack traceback of the last exception. + +-JIT Stack viewer toggle +- Open stack viewer on traceback ++Auto-open Stack Viewer ++ Open stack viewer on traceback. + + .. index:: + single: stack viewer + single: debugger + + ++Edit context menu ++^^^^^^^^^^^^^^^^^ ++ ++* Right-click in Edit window (Control-click on OS X) ++ ++Cut ++ Copy selection into system-wide clipboard; then delete selection ++ ++Copy ++ Copy selection into system-wide clipboard ++ ++Paste ++ Insert system-wide clipboard into window ++ ++Set Breakpoint ++ Sets a breakpoint. Breakpoints are only enabled when the debugger is open. ++ ++Clear Breakpoint ++ Clears the breakpoint on that line. ++ ++.. index:: ++ single: Cut ++ single: Copy ++ single: Paste ++ single: Set Breakpoint ++ single: Clear Breakpoint ++ single: breakpoints ++ ++ ++Shell context menu ++^^^^^^^^^^^^^^^^^^ ++ ++* Right-click in Python Shell window (Control-click on OS X) ++ ++Cut ++ Copy selection into system-wide clipboard; then delete selection ++ ++Copy ++ Copy selection into system-wide clipboard ++ ++Paste ++ Insert system-wide clipboard into window ++ ++Go to file/line ++ Same as in Debug menu. ++ ++ + Basic editing and navigation + ---------------------------- + +diff -r bd8afb90ebf2 Doc/library/imaplib.rst +--- a/Doc/library/imaplib.rst ++++ b/Doc/library/imaplib.rst +@@ -75,7 +75,7 @@ + :class:`ssl.SSLContext` object which allows bundling SSL configuration + options, certificates and private keys into a single (potentially long-lived) + structure. Note that the *keyfile*/*certfile* parameters are mutually exclusive with *ssl_context*, +- a :class:`ValueError` is thrown if *keyfile*/*certfile* is provided along with *ssl_context*. ++ a :class:`ValueError` is raised if *keyfile*/*certfile* is provided along with *ssl_context*. + + .. versionchanged:: 3.3 + *ssl_context* parameter added. +diff -r bd8afb90ebf2 Doc/library/importlib.rst +--- a/Doc/library/importlib.rst ++++ b/Doc/library/importlib.rst +@@ -94,11 +94,10 @@ + :exc:`ValueError` is raised). Otherwise a search using :attr:`sys.meta_path` + is done. ``None`` is returned if no loader is found. + +- A dotted name does not have its parent's implicitly imported. If that is +- desired (although not nessarily required to find the loader, it will most +- likely be needed if the loader actually is used to load the module), then +- you will have to import the packages containing the module prior to calling +- this function. ++ A dotted name does not have its parent's implicitly imported as that requires ++ loading them and that may not be desired. To properly import a submodule you ++ will need to import all parent packages of the submodule and use the correct ++ argument to *path*. + + .. function:: invalidate_caches() + +@@ -162,7 +161,7 @@ + + An abstract method for finding a :term:`loader` for the specified + module. If this is a top-level import, *path* will be ``None``. +- Otheriwse, this is a search for a subpackage or module and *path* ++ Otherwise, this is a search for a subpackage or module and *path* + will be the value of :attr:`__path__` from the parent + package. If a loader cannot be found, ``None`` is returned. + +diff -r bd8afb90ebf2 Doc/library/index.rst +--- a/Doc/library/index.rst ++++ b/Doc/library/index.rst +@@ -4,9 +4,6 @@ + The Python Standard Library + ############################### + +-:Release: |version| +-:Date: |today| +- + While :ref:`reference-index` describes the exact syntax and + semantics of the Python language, this library reference manual + describes the standard library that is distributed with Python. It also +diff -r bd8afb90ebf2 Doc/library/inspect.rst +--- a/Doc/library/inspect.rst ++++ b/Doc/library/inspect.rst +@@ -471,7 +471,7 @@ + Returns :class:`BoundArguments`, or raises a :exc:`TypeError` if the + passed arguments do not match the signature. + +- .. method:: Signature.replace([parameters], *, [return_annotation]) ++ .. method:: Signature.replace(*[, parameters][, return_annotation]) + + Create a new Signature instance based on the instance replace was invoked + on. It is possible to pass different ``parameters`` and/or +@@ -565,7 +565,7 @@ + ... print('Parameter:', param) + Parameter: c + +- .. method:: Parameter.replace(*, [name], [kind], [default], [annotation]) ++ .. method:: Parameter.replace(*[, name][, kind][, default][, annotation]) + + Create a new Parameter instance based on the instance replaced was invoked + on. To override a :class:`Parameter` attribute, pass the corresponding +@@ -716,7 +716,7 @@ + locals dictionary of the given frame. + + +-.. function:: formatargspec(args[, varargs, varkw, defaults, kwonlyargs, kwonlydefaults, annotations, formatarg, formatvarargs, formatvarkw, formatvalue, formatreturns, formatannotations]) ++.. function:: formatargspec(args[, varargs, varkw, defaults, kwonlyargs, kwonlydefaults, annotations[, formatarg, formatvarargs, formatvarkw, formatvalue, formatreturns, formatannotations]]) + + Format a pretty argument spec from the values returned by + :func:`getargspec` or :func:`getfullargspec`. +@@ -725,7 +725,14 @@ + ``defaults``, ``kwonlyargs``, ``kwonlydefaults``, ``annotations``). The + other five arguments are the corresponding optional formatting functions + that are called to turn names and values into strings. The last argument +- is an optional function to format the sequence of arguments. ++ is an optional function to format the sequence of arguments. For example:: ++ ++ >>> from inspect import formatargspec, getfullargspec ++ >>> def f(a: int, b: float): ++ ... pass ++ ... ++ >>> formatargspec(*getfullargspec(f)) ++ '(a: int, b: float)' + + + .. function:: formatargvalues(args[, varargs, varkw, locals, formatarg, formatvarargs, formatvarkw, formatvalue]) +diff -r bd8afb90ebf2 Doc/library/internet.rst +--- a/Doc/library/internet.rst ++++ b/Doc/library/internet.rst +@@ -23,10 +23,12 @@ + cgi.rst + cgitb.rst + wsgiref.rst ++ urllib.rst + urllib.request.rst + urllib.parse.rst + urllib.error.rst + urllib.robotparser.rst ++ http.rst + http.client.rst + ftplib.rst + poplib.rst +@@ -40,6 +42,7 @@ + http.server.rst + http.cookies.rst + http.cookiejar.rst ++ xmlrpc.rst + xmlrpc.client.rst + xmlrpc.server.rst + ipaddress.rst +diff -r bd8afb90ebf2 Doc/library/io.rst +--- a/Doc/library/io.rst ++++ b/Doc/library/io.rst +@@ -185,6 +185,25 @@ + Argument names are not part of the specification, and only the arguments of + :func:`open` are intended to be used as keyword arguments. + ++The following table summarizes the ABCs provided by the :mod:`io` module: ++ ++========================= ================== ======================== ================================================== ++ABC Inherits Stub Methods Mixin Methods and Properties ++========================= ================== ======================== ================================================== ++:class:`IOBase` ``fileno``, ``seek``, ``close``, ``closed``, ``__enter__``, ++ and ``truncate`` ``__exit__``, ``flush``, ``isatty``, ``__iter__``, ++ ``__next__``, ``readable``, ``readline``, ++ ``readlines``, ``seekable``, ``tell``, ++ ``writable``, and ``writelines`` ++:class:`RawIOBase` :class:`IOBase` ``readinto`` and Inherited :class:`IOBase` methods, ``read``, ++ ``write`` and ``readall`` ++:class:`BufferedIOBase` :class:`IOBase` ``detach``, ``read``, Inherited :class:`IOBase` methods, ``readinto`` ++ ``read1``, and ``write`` ++:class:`TextIOBase` :class:`IOBase` ``detach``, ``read``, Inherited :class:`IOBase` methods, ``encoding``, ++ ``readline``, and ``errors``, and ``newlines`` ++ ``write`` ++========================= ================== ======================== ================================================== ++ + + I/O Base Classes + ^^^^^^^^^^^^^^^^ +@@ -213,7 +232,7 @@ + Note that calling any method (even inquiries) on a closed stream is + undefined. Implementations may raise :exc:`ValueError` in this case. + +- :class:`IOBase` (and its subclasses) support the iterator protocol, meaning ++ :class:`IOBase` (and its subclasses) supports the iterator protocol, meaning + that an :class:`IOBase` object can be iterated over yielding the lines in a + stream. Lines are defined slightly differently depending on whether the + stream is a binary stream (yielding bytes), or a text stream (yielding +@@ -498,6 +517,9 @@ + :mod:`os.open` as *opener* results in functionality similar to passing + ``None``). + ++ See the :func:`open` built-in function for examples on using the *opener* ++ parameter. ++ + .. versionchanged:: 3.3 + The *opener* parameter was added. + The ``'x'`` mode was added. +diff -r bd8afb90ebf2 Doc/library/ipaddress.rst +--- a/Doc/library/ipaddress.rst ++++ b/Doc/library/ipaddress.rst +@@ -42,8 +42,15 @@ + Return an :class:`IPv4Address` or :class:`IPv6Address` object depending on + the IP address passed as argument. Either IPv4 or IPv6 addresses may be + supplied; integers less than 2**32 will be considered to be IPv4 by default. +- A :exc:`ValueError` is raised if *address* does not represent a valid IPv4 or +- IPv6 address. ++ A :exc:`ValueError` is raised if *address* does not represent a valid IPv4 ++ or IPv6 address. ++ ++.. testsetup:: ++ >>> import ipaddress ++ >>> from ipaddress import (ip_network, IPv4Address, IPv4Interface, ++ ... IPv4Network) ++ ++:: + + >>> ipaddress.ip_address('192.168.0.1') + IPv4Address('192.168.0.1') +@@ -111,7 +118,7 @@ + + >>> ipaddress.IPv4Address('192.168.0.1') + IPv4Address('192.168.0.1') +- >>> ipaddress.IPv4Address(3221225985) ++ >>> ipaddress.IPv4Address(3232235521) + IPv4Address('192.168.0.1') + >>> ipaddress.IPv4Address(b'\xC0\xA8\x00\x01') + IPv4Address('192.168.0.1') +@@ -437,7 +444,7 @@ + hosts are all the IP addresses that belong to the network, except the + network address itself and the network broadcast address. + +- >>> list(ip_network('192.0.2.0/29').hosts()) ++ >>> list(ip_network('192.0.2.0/29').hosts()) #doctest: +NORMALIZE_WHITESPACE + [IPv4Address('192.0.2.1'), IPv4Address('192.0.2.2'), + IPv4Address('192.0.2.3'), IPv4Address('192.0.2.4'), + IPv4Address('192.0.2.5'), IPv4Address('192.0.2.6')] +@@ -456,7 +463,7 @@ + + >>> n1 = ip_network('192.0.2.0/28') + >>> n2 = ip_network('192.0.2.1/32') +- >>> list(n1.address_exclude(n2)) ++ >>> list(n1.address_exclude(n2)) #doctest: +NORMALIZE_WHITESPACE + [IPv4Network('192.0.2.8/29'), IPv4Network('192.0.2.4/30'), + IPv4Network('192.0.2.2/31'), IPv4Network('192.0.2.0/32')] + +@@ -471,10 +478,10 @@ + + >>> list(ip_network('192.0.2.0/24').subnets()) + [IPv4Network('192.0.2.0/25'), IPv4Network('192.0.2.128/25')] +- >>> list(ip_network('192.0.2.0/24').subnets(prefixlen_diff=2)) ++ >>> list(ip_network('192.0.2.0/24').subnets(prefixlen_diff=2)) #doctest: +NORMALIZE_WHITESPACE + [IPv4Network('192.0.2.0/26'), IPv4Network('192.0.2.64/26'), + IPv4Network('192.0.2.128/26'), IPv4Network('192.0.2.192/26')] +- >>> list(ip_network('192.0.2.0/24').subnets(new_prefix=26)) ++ >>> list(ip_network('192.0.2.0/24').subnets(new_prefix=26)) #doctest: +NORMALIZE_WHITESPACE + [IPv4Network('192.0.2.0/26'), IPv4Network('192.0.2.64/26'), + IPv4Network('192.0.2.128/26'), IPv4Network('192.0.2.192/26')] + >>> list(ip_network('192.0.2.0/24').subnets(new_prefix=23)) +diff -r bd8afb90ebf2 Doc/library/itertools.rst +--- a/Doc/library/itertools.rst ++++ b/Doc/library/itertools.rst +@@ -401,7 +401,8 @@ + self.currkey = self.keyfunc(self.currvalue) + + +-.. function:: islice(iterable, [start,] stop [, step]) ++.. function:: islice(iterable, stop) ++ islice(iterable, start, stop[, step]) + + Make an iterator that returns selected elements from the iterable. If *start* is + non-zero, then elements from the iterable are skipped until start is reached. +diff -r bd8afb90ebf2 Doc/library/json.rst +--- a/Doc/library/json.rst ++++ b/Doc/library/json.rst +@@ -42,7 +42,8 @@ + Pretty printing:: + + >>> import json +- >>> print(json.dumps({'4': 5, '6': 7}, sort_keys=True, indent=4)) ++ >>> print(json.dumps({'4': 5, '6': 7}, sort_keys=True, ++ ... indent=4, separators=(',', ': '))) + { + "4": 5, + "6": 7 +@@ -116,7 +117,10 @@ + Basic Usage + ----------- + +-.. function:: dump(obj, fp, skipkeys=False, ensure_ascii=True, check_circular=True, allow_nan=True, cls=None, indent=None, separators=None, default=None, **kw) ++.. function:: dump(obj, fp, skipkeys=False, ensure_ascii=True, \ ++ check_circular=True, allow_nan=True, cls=None, \ ++ indent=None, separators=None, default=None, \ ++ sort_keys=False, **kw) + + Serialize *obj* as a JSON formatted stream to *fp* (a ``.write()``-supporting + :term:`file-like object`). +@@ -146,9 +150,18 @@ + object members will be pretty-printed with that indent level. An indent level + of 0, negative, or ``""`` will only insert newlines. ``None`` (the default) + selects the most compact representation. Using a positive integer indent +- indents that many spaces per level. If *indent* is a string (such at '\t'), ++ indents that many spaces per level. If *indent* is a string (such as ``"\t"``), + that string is used to indent each level. + ++ .. versionchanged:: 3.2 ++ Allow strings for *indent* in addition to integers. ++ ++ .. note:: ++ ++ Since the default item separator is ``', '``, the output might include ++ trailing whitespace when *indent* is specified. You can use ++ ``separators=(',', ': ')`` to avoid this. ++ + If *separators* is an ``(item_separator, dict_separator)`` tuple, then it + will be used instead of the default ``(', ', ': ')`` separators. ``(',', + ':')`` is the most compact JSON representation. +@@ -156,12 +169,18 @@ + *default(obj)* is a function that should return a serializable version of + *obj* or raise :exc:`TypeError`. The default simply raises :exc:`TypeError`. + ++ If *sort_keys* is ``True`` (default: ``False``), then the output of ++ dictionaries will be sorted by key. ++ + To use a custom :class:`JSONEncoder` subclass (e.g. one that overrides the + :meth:`default` method to serialize additional types), specify it with the + *cls* kwarg; otherwise :class:`JSONEncoder` is used. + + +-.. function:: dumps(obj, skipkeys=False, ensure_ascii=True, check_circular=True, allow_nan=True, cls=None, indent=None, separators=None, default=None, **kw) ++.. function:: dumps(obj, skipkeys=False, ensure_ascii=True, \ ++ check_circular=True, allow_nan=True, cls=None, \ ++ indent=None, separators=None, default=None, \ ++ sort_keys=False, **kw) + + Serialize *obj* to a JSON formatted :class:`str`. The arguments have the + same meaning as in :func:`dump`. +@@ -371,10 +390,21 @@ + will be sorted by key; this is useful for regression tests to ensure that + JSON serializations can be compared on a day-to-day basis. + +- If *indent* is a non-negative integer (it is ``None`` by default), then JSON +- array elements and object members will be pretty-printed with that indent +- level. An indent level of 0 will only insert newlines. ``None`` is the most +- compact representation. ++ If *indent* is a non-negative integer or string, then JSON array elements and ++ object members will be pretty-printed with that indent level. An indent level ++ of 0, negative, or ``""`` will only insert newlines. ``None`` (the default) ++ selects the most compact representation. Using a positive integer indent ++ indents that many spaces per level. If *indent* is a string (such as ``"\t"``), ++ that string is used to indent each level. ++ ++ .. versionchanged:: 3.2 ++ Allow strings for *indent* in addition to integers. ++ ++ .. note:: ++ ++ Since the default item separator is ``', '``, the output might include ++ trailing whitespace when *indent* is specified. You can use ++ ``separators=(',', ': ')`` to avoid this. + + If specified, *separators* should be an ``(item_separator, key_separator)`` + tuple. The default is ``(', ', ': ')``. To get the most compact JSON +diff -r bd8afb90ebf2 Doc/library/logging.rst +--- a/Doc/library/logging.rst ++++ b/Doc/library/logging.rst +@@ -70,16 +70,25 @@ + + .. attribute:: Logger.propagate + +- If this evaluates to true, logging messages are passed by this logger and by +- its child loggers to the handlers of higher level (ancestor) loggers. +- Messages are passed directly to the ancestor loggers' handlers - neither the +- level nor filters of the ancestor loggers in question are considered. ++ If this evaluates to true, events logged to this logger will be passed to the ++ handlers of higher level (ancestor) loggers, in addition to any handlers ++ attached to this logger. Messages are passed directly to the ancestor ++ loggers' handlers - neither the level nor filters of the ancestor loggers in ++ question are considered. + + If this evaluates to false, logging messages are not passed to the handlers + of ancestor loggers. + + The constructor sets this attribute to ``True``. + ++ .. note:: If you attach a handler to a logger *and* one or more of its ++ ancestors, it may emit the same record multiple times. In general, you ++ should not need to attach a handler to more than one logger - if you just ++ attach it to the appropriate logger which is highest in the logger ++ hierarchy, then it will see all events logged by all descendant loggers, ++ provided that their propagate setting is left set to ``True``. A common ++ scenario is to attach handlers only to the root logger, and to let ++ propagation take care of the rest. + + .. method:: Logger.setLevel(lvl) + +@@ -255,7 +264,10 @@ + .. method:: Logger.filter(record) + + Applies this logger's filters to the record and returns a true value if the +- record is to be processed. ++ record is to be processed. The filters are consulted in turn, until one of ++ them returns a false value. If none of them return a false value, the record ++ will be processed (passed to handlers). If one returns a false value, no ++ further processing of the record occurs. + + + .. method:: Logger.addHandler(hdlr) +@@ -364,7 +376,10 @@ + .. method:: Handler.filter(record) + + Applies this handler's filters to the record and returns a true value if the +- record is to be processed. ++ record is to be processed. The filters are consulted in turn, until one of ++ them returns a false value. If none of them return a false value, the record ++ will be emitted. If one returns a false value, the handler will not emit the ++ record. + + + .. method:: Handler.flush() +@@ -547,12 +562,12 @@ + yes. If deemed appropriate, the record may be modified in-place by this + method. + +-Note that filters attached to handlers are consulted whenever an event is ++Note that filters attached to handlers are consulted before an event is + emitted by the handler, whereas filters attached to loggers are consulted +-whenever an event is logged to the handler (using :meth:`debug`, :meth:`info`, +-etc.) This means that events which have been generated by descendant loggers +-will not be filtered by a logger's filter setting, unless the filter has also +-been applied to those descendant loggers. ++whenever an event is logged (using :meth:`debug`, :meth:`info`, ++etc.), before sending an event to handlers. This means that events which have ++been generated by descendant loggers will not be filtered by a logger's filter ++setting, unless the filter has also been applied to those descendant loggers. + + You don't actually need to subclass ``Filter``: you can pass any instance + which has a ``filter`` method with the same semantics. +@@ -596,7 +611,9 @@ + record. + + :param name: The name of the logger used to log the event represented by +- this LogRecord. ++ this LogRecord. Note that this name will always have this ++ value, even though it may be emitted by a handler attached to ++ a different (ancestor) logger. + :param level: The numeric level of the logging event (one of DEBUG, INFO etc.) + Note that this is converted to *two* attributes of the LogRecord: + ``levelno`` for the numeric value and ``levelname`` for the +@@ -948,14 +965,14 @@ + Logs a message with level *level* on the root logger. The other arguments are + interpreted as for :func:`debug`. + +- PLEASE NOTE: The above module-level functions which delegate to the root +- logger should *not* be used in threads, in versions of Python earlier than +- 2.7.1 and 3.2, unless at least one handler has been added to the root +- logger *before* the threads are started. These convenience functions call +- :func:`basicConfig` to ensure that at least one handler is available; in +- earlier versions of Python, this can (under rare circumstances) lead to +- handlers being added multiple times to the root logger, which can in turn +- lead to multiple messages for the same event. ++ .. note:: The above module-level functions which delegate to the root ++ logger should *not* be used in threads, in versions of Python earlier ++ than 2.7.1 and 3.2, unless at least one handler has been added to the ++ root logger *before* the threads are started. These convenience functions ++ call :func:`basicConfig` to ensure that at least one handler is ++ available; in earlier versions of Python, this can (under rare ++ circumstances) lead to handlers being added multiple times to the root ++ logger, which can in turn lead to multiple messages for the same event. + + .. function:: disable(lvl) + +@@ -978,8 +995,8 @@ + registered using this function, levels should be positive integers and they + should increase in increasing order of severity. + +- NOTE: If you are thinking of defining your own levels, please see the section +- on :ref:`custom-levels`. ++ .. note:: If you are thinking of defining your own levels, please see the ++ section on :ref:`custom-levels`. + + .. function:: getLevelName(lvl) + +@@ -1011,12 +1028,12 @@ + This function does nothing if the root logger already has handlers + configured for it. + +- PLEASE NOTE: This function should be called from the main thread +- before other threads are started. In versions of Python prior to +- 2.7.1 and 3.2, if this function is called from multiple threads, +- it is possible (in rare circumstances) that a handler will be added +- to the root logger more than once, leading to unexpected results +- such as messages being duplicated in the log. ++ .. note:: This function should be called from the main thread ++ before other threads are started. In versions of Python prior to ++ 2.7.1 and 3.2, if this function is called from multiple threads, ++ it is possible (in rare circumstances) that a handler will be added ++ to the root logger more than once, leading to unexpected results ++ such as messages being duplicated in the log. + + The following keyword arguments are supported. + +@@ -1115,6 +1132,21 @@ + :kwargs: Additional keyword arguments. + + ++Module-Level Attributes ++----------------------- ++ ++.. attribute:: lastResort ++ ++ A "handler of last resort" is available through this attribute. This ++ is a :class:`StreamHandler` writing to ``sys.stderr`` with a level of ++ ``WARNING``, and is used to handle logging events in the absence of any ++ logging configuration. The end result is to just print the message to ++ ``sys.stderr``. This replaces the earlier error message saying that ++ "no handlers could be found for logger XYZ". If you need the earlier ++ behaviour for some reason, ``lastResort`` can be set to ``None``. ++ ++ .. versionadded:: 3.2 ++ + Integration with the warnings module + ------------------------------------ + +diff -r bd8afb90ebf2 Doc/library/lzma.rst +--- a/Doc/library/lzma.rst ++++ b/Doc/library/lzma.rst +@@ -335,15 +335,15 @@ + Reading in a compressed file:: + + import lzma +- with lzma.LZMAFile("file.xz") as f: +- file_content = f.read() ++ with lzma.open("file.xz") as f: ++ file_content = f.read() + + Creating a compressed file:: + + import lzma + data = b"Insert Data Here" +- with lzma.LZMAFile("file.xz", "w") as f: +- f.write(data) ++ with lzma.open("file.xz", "w") as f: ++ f.write(data) + + Compressing data in memory:: + +@@ -367,7 +367,7 @@ + import lzma + with open("file.xz", "wb") as f: + f.write(b"This data will not be compressed\n") +- with lzma.LZMAFile(f, "w") as lzf: ++ with lzma.open(f, "w") as lzf: + lzf.write(b"This *will* be compressed\n") + f.write(b"Not compressed\n") + +@@ -378,5 +378,5 @@ + {"id": lzma.FILTER_DELTA, "dist": 5}, + {"id": lzma.FILTER_LZMA2, "preset": 7 | lzma.PRESET_EXTREME}, + ] +- with lzma.LZMAFile("file.xz", "w", filters=my_filters) as f: ++ with lzma.open("file.xz", "w", filters=my_filters) as f: + f.write(b"blah blah blah") +diff -r bd8afb90ebf2 Doc/library/mailbox.rst +--- a/Doc/library/mailbox.rst ++++ b/Doc/library/mailbox.rst +@@ -10,9 +10,9 @@ + This module defines two classes, :class:`Mailbox` and :class:`Message`, for + accessing and manipulating on-disk mailboxes and the messages they contain. + :class:`Mailbox` offers a dictionary-like mapping from keys to messages. +-:class:`Message` extends the :mod:`email.Message` module's :class:`Message` +-class with format-specific state and behavior. Supported mailbox formats are +-Maildir, mbox, MH, Babyl, and MMDF. ++:class:`Message` extends the :mod:`email.message` module's ++:class:`~email.message.Message` class with format-specific state and behavior. ++Supported mailbox formats are Maildir, mbox, MH, Babyl, and MMDF. + + + .. seealso:: +@@ -81,7 +81,7 @@ + it. + + Parameter *message* may be a :class:`Message` instance, an +- :class:`email.Message.Message` instance, a string, a byte string, or a ++ :class:`email.message.Message` instance, a string, a byte string, or a + file-like object (which should be open in binary mode). If *message* is + an instance of the + appropriate format-specific :class:`Message` subclass (e.g., if it's an +@@ -112,7 +112,7 @@ + :exc:`KeyError` exception if no message already corresponds to *key*. + + As with :meth:`add`, parameter *message* may be a :class:`Message` +- instance, an :class:`email.Message.Message` instance, a string, a byte ++ instance, an :class:`email.message.Message` instance, a string, a byte + string, or a file-like object (which should be open in binary mode). If + *message* is an + instance of the appropriate format-specific :class:`Message` subclass +@@ -757,11 +757,12 @@ + + .. class:: Message(message=None) + +- A subclass of the :mod:`email.Message` module's :class:`Message`. Subclasses of +- :class:`mailbox.Message` add mailbox-format-specific state and behavior. ++ A subclass of the :mod:`email.message` module's ++ :class:`~email.message.Message`. Subclasses of :class:`mailbox.Message` add ++ mailbox-format-specific state and behavior. + + If *message* is omitted, the new instance is created in a default, empty state. +- If *message* is an :class:`email.Message.Message` instance, its contents are ++ If *message* is an :class:`email.message.Message` instance, its contents are + copied; furthermore, any format-specific information is converted insofar as + possible if *message* is a :class:`Message` instance. If *message* is a string, + a byte string, +@@ -1267,7 +1268,7 @@ + + Set the message's visible headers to be the same as the headers in + *message*. Parameter *visible* should be a :class:`Message` instance, an +- :class:`email.Message.Message` instance, a string, or a file-like object ++ :class:`email.message.Message` instance, a string, or a file-like object + (which should be open in text mode). + + +diff -r bd8afb90ebf2 Doc/library/markup.rst +--- a/Doc/library/markup.rst ++++ b/Doc/library/markup.rst +@@ -9,20 +9,13 @@ + Language (SGML) and the Hypertext Markup Language (HTML), and several interfaces + for working with the Extensible Markup Language (XML). + +-It is important to note that modules in the :mod:`xml` package require that +-there be at least one SAX-compliant XML parser available. The Expat parser is +-included with Python, so the :mod:`xml.parsers.expat` module will always be +-available. +- +-The documentation for the :mod:`xml.dom` and :mod:`xml.sax` packages are the +-definition of the Python bindings for the DOM and SAX interfaces. +- + + .. toctree:: + + html.rst + html.parser.rst + html.entities.rst ++ xml.rst + xml.etree.elementtree.rst + xml.dom.rst + xml.dom.minidom.rst +diff -r bd8afb90ebf2 Doc/library/math.rst +--- a/Doc/library/math.rst ++++ b/Doc/library/math.rst +@@ -4,6 +4,9 @@ + .. module:: math + :synopsis: Mathematical functions (sin() etc.). + ++.. testsetup:: ++ ++ from math import fsum + + This module is always available. It provides access to the mathematical + functions defined by the C standard. +diff -r bd8afb90ebf2 Doc/library/multiprocessing.rst +--- a/Doc/library/multiprocessing.rst ++++ b/Doc/library/multiprocessing.rst +@@ -29,7 +29,7 @@ + Functionality within this package requires that the ``__main__`` module be + importable by the children. This is covered in :ref:`multiprocessing-programming` + however it is worth pointing out here. This means that some examples, such +- as the :class:`multiprocessing.Pool` examples will not work in the ++ as the :class:`multiprocessing.pool.Pool` examples will not work in the + interactive interpreter. For example:: + + >>> from multiprocessing import Pool +@@ -279,7 +279,7 @@ + return x*x + + if __name__ == '__main__': +- with Pool(processes=4) as pool # start 4 worker processes ++ with Pool(processes=4) as pool: # start 4 worker processes + result = pool.apply_async(f, [10]) # evaluate "f(10)" asynchronously + print(result.get(timeout=1)) # prints "100" unless your computer is *very* slow + print(pool.map(f, range(10))) # prints "[0, 1, 4,..., 81]" +@@ -295,7 +295,8 @@ + :class:`Process` and exceptions + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +-.. class:: Process([group[, target[, name[, args[, kwargs]]]]], *, daemon=None) ++.. class:: Process(group=None, target=None, name=None, args=(), kwargs={}, \ ++ *, daemon=None) + + Process objects represent activity that is run in a separate process. The + :class:`Process` class has equivalents of all the methods of +@@ -915,7 +916,7 @@ + + .. class:: Condition([lock]) + +- A condition variable: a clone of :class:`threading.Condition`. ++ A condition variable: an alias for :class:`threading.Condition`. + + If *lock* is specified then it should be a :class:`Lock` or :class:`RLock` + object from :mod:`multiprocessing`. +@@ -1147,7 +1148,7 @@ + + n = Value('i', 7) + x = Value(c_double, 1.0/3.0, lock=False) +- s = Array('c', 'hello world', lock=lock) ++ s = Array('c', b'hello world', lock=lock) + A = Array(Point, [(1.875,-6.25), (-5.75,2.0), (2.375,9.5)], lock=lock) + + p = Process(target=modify, args=(n, x, s, A)) +@@ -1637,7 +1638,7 @@ + One can create a pool of processes which will carry out tasks submitted to it + with the :class:`Pool` class. + +-.. class:: multiprocessing.Pool([processes[, initializer[, initargs[, maxtasksperchild]]]]) ++.. class:: Pool([processes[, initializer[, initargs[, maxtasksperchild]]]]) + + A process pool object which controls a pool of worker processes to which jobs + can be submitted. It supports asynchronous results with timeouts and +diff -r bd8afb90ebf2 Doc/library/nntplib.rst +--- a/Doc/library/nntplib.rst ++++ b/Doc/library/nntplib.rst +@@ -487,10 +487,10 @@ + them have been superseded by newer commands in :rfc:`3977`. + + +-.. method:: NNTP.xhdr(header, string, *, file=None) ++.. method:: NNTP.xhdr(hdr, str, *, file=None) + +- Send an ``XHDR`` command. The *header* argument is a header keyword, e.g. +- ``'subject'``. The *string* argument should have the form ``'first-last'`` ++ Send an ``XHDR`` command. The *hdr* argument is a header keyword, e.g. ++ ``'subject'``. The *str* argument should have the form ``'first-last'`` + where *first* and *last* are the first and last article numbers to search. + Return a pair ``(response, list)``, where *list* is a list of pairs ``(id, + text)``, where *id* is an article number (as a string) and *text* is the text of +diff -r bd8afb90ebf2 Doc/library/optparse.rst +--- a/Doc/library/optparse.rst ++++ b/Doc/library/optparse.rst +@@ -273,7 +273,8 @@ + strings as you like (including zero), as long as there is at least one option + string overall. + +-The option strings passed to :meth:`add_option` are effectively labels for the ++The option strings passed to :meth:`OptionParser.add_option` are effectively ++labels for the + option defined by that call. For brevity, we will frequently refer to + *encountering an option* on the command line; in reality, :mod:`optparse` + encounters *option strings* and looks up options from them. +@@ -892,7 +893,8 @@ + The canonical way to create an :class:`Option` instance is with the + :meth:`add_option` method of :class:`OptionParser`. + +-.. method:: OptionParser.add_option(opt_str[, ...], attr=value, ...) ++.. method:: OptionParser.add_option(option) ++ OptionParser.add_option(*opt_str, attr=value, ...) + + To define an option with only a short option string:: + +@@ -1165,6 +1167,17 @@ + + options.tracks.append(int("4")) + ++ The ``append`` action calls the ``append`` method on the current value of the ++ option. This means that any default value specified must have an ``append`` ++ method. It also means that if the default value is non-empty, the default ++ elements will be present in the parsed value for the option, with any values ++ from the command line appended after those default values:: ++ ++ >>> parser.add_option("--files", action="append", default=['~/.mypkg/defaults']) ++ >>> opts, args = parser.parse_args(['--files', 'overrides.mypkg']) ++ >>> opts.files ++ ['~/.mypkg/defaults', 'overrides.mypkg'] ++ + * ``"append_const"`` [required: :attr:`~Option.const`; relevant: + :attr:`~Option.dest`] + +diff -r bd8afb90ebf2 Doc/library/os.path.rst +--- a/Doc/library/os.path.rst ++++ b/Doc/library/os.path.rst +@@ -17,6 +17,11 @@ + names on Windows (in the standard ``mbcs`` encoding), hence Windows + applications should use string objects to access all files. + ++Unlike a unix shell, Python does not do any *automatic* path expansions. ++Functions such as :func:`expanduser` and :func:`expandvars` can be invoked ++explicitly when an application desires shell-like path expansion. (See also ++the :mod:`glob` module.) ++ + .. note:: + + All of these functions accept either only bytes or only string objects as +@@ -43,13 +48,15 @@ + .. function:: abspath(path) + + Return a normalized absolutized version of the pathname *path*. On most +- platforms, this is equivalent to ``normpath(join(os.getcwd(), path))``. ++ platforms, this is equivalent to calling the function :func:`normpath` as ++ follows: ``normpath(join(os.getcwd(), path))``. + + + .. function:: basename(path) + +- Return the base name of pathname *path*. This is the second half of the pair +- returned by ``split(path)``. Note that the result of this function is different ++ Return the base name of pathname *path*. This is the second element of the ++ pair returned by passing *path* to the function :func:`split`. Note that ++ the result of this function is different + from the Unix :program:`basename` program; where :program:`basename` for + ``'/foo/bar/'`` returns ``'bar'``, the :func:`basename` function returns an + empty string (``''``). +@@ -64,8 +71,8 @@ + + .. function:: dirname(path) + +- Return the directory name of pathname *path*. This is the first half of the +- pair returned by ``split(path)``. ++ Return the directory name of pathname *path*. This is the first element of ++ the pair returned by passing *path* to the function :func:`split`. + + + .. function:: exists(path) +@@ -124,7 +131,7 @@ + + Return the time of last access of *path*. The return value is a number giving + the number of seconds since the epoch (see the :mod:`time` module). Raise +- :exc:`os.error` if the file does not exist or is inaccessible. ++ :exc:`OSError` if the file does not exist or is inaccessible. + + If :func:`os.stat_float_times` returns True, the result is a floating point + number. +@@ -134,7 +141,7 @@ + + Return the time of last modification of *path*. The return value is a number + giving the number of seconds since the epoch (see the :mod:`time` module). +- Raise :exc:`os.error` if the file does not exist or is inaccessible. ++ Raise :exc:`OSError` if the file does not exist or is inaccessible. + + If :func:`os.stat_float_times` returns True, the result is a floating point + number. +@@ -145,13 +152,13 @@ + Return the system's ctime which, on some systems (like Unix) is the time of the + last change, and, on others (like Windows), is the creation time for *path*. + The return value is a number giving the number of seconds since the epoch (see +- the :mod:`time` module). Raise :exc:`os.error` if the file does not exist or ++ the :mod:`time` module). Raise :exc:`OSError` if the file does not exist or + is inaccessible. + + + .. function:: getsize(path) + +- Return the size, in bytes, of *path*. Raise :exc:`os.error` if the file does ++ Return the size, in bytes, of *path*. Raise :exc:`OSError` if the file does + not exist or is inaccessible. + + +@@ -282,7 +289,8 @@ + *path* is empty, both *head* and *tail* are empty. Trailing slashes are + stripped from *head* unless it is the root (one or more slashes only). In + all cases, ``join(head, tail)`` returns a path to the same location as *path* +- (but the strings may differ). ++ (but the strings may differ). Also see the functions :func:`dirname` and ++ :func:`basename`. + + + .. function:: splitdrive(path) +diff -r bd8afb90ebf2 Doc/library/os.rst +--- a/Doc/library/os.rst ++++ b/Doc/library/os.rst +@@ -105,7 +105,7 @@ + + .. data:: environ + +- A mapping object representing the string environment. For example, ++ A :term:`mapping` object representing the string environment. For example, + ``environ['HOME']`` is the pathname of your home directory (on some platforms), + and is equivalent to ``getenv("HOME")`` in C. + +@@ -145,7 +145,7 @@ + + .. data:: environb + +- Bytes version of :data:`environ`: a mapping object representing the ++ Bytes version of :data:`environ`: a :term:`mapping` object representing the + environment as byte strings. :data:`environ` and :data:`environb` are + synchronized (modify :data:`environb` updates :data:`environ`, and vice + versa). +@@ -1171,7 +1171,7 @@ + output) specifies which file descriptor should be queried. + + If the file descriptor is not connected to a terminal, an :exc:`OSError` +- is thrown. ++ is raised. + + :func:`shutil.get_terminal_size` is the high-level function which + should normally be used, ``os.get_terminal_size`` is the low-level +@@ -1555,18 +1555,21 @@ + single: UNC paths; and os.makedirs() + + Recursive directory creation function. Like :func:`mkdir`, but makes all +- intermediate-level directories needed to contain the leaf directory. If +- the target directory with the same mode as specified already exists, +- raises an :exc:`OSError` exception if *exist_ok* is False, otherwise no +- exception is raised. If the directory cannot be created in other cases, +- raises an :exc:`OSError` exception. The default *mode* is ``0o777`` (octal). +- On some systems, *mode* is ignored. Where it is used, the current umask +- value is first masked out. ++ intermediate-level directories needed to contain the leaf directory. ++ ++ The default *mode* is ``0o777`` (octal). On some systems, *mode* is ++ ignored. Where it is used, the current umask value is first masked out. ++ ++ If *exists_ok* is ``False`` (the default), an :exc:`OSError` is raised if ++ the target directory already exists. If *exists_ok* is ``True`` an ++ :exc:`OSError` is still raised if the umask-masked *mode* is different from ++ the existing mode, on systems where the mode is used. :exc:`OSError` will ++ also be raised if the directory creation fails. + + .. note:: + + :func:`makedirs` will become confused if the path elements to create +- include :data:`pardir`. ++ include :data:`pardir` (eg. ".." on UNIX systems). + + This function handles UNC paths correctly. + +@@ -1855,9 +1858,8 @@ + :attr:`st_mtime`, :attr:`st_ctime`. More items may be added at the end by + some implementations. + +- This function can support :ref:`specifying a file descriptor +- `, :ref:`specifying a file descriptor ` and :ref:`not +- following symlinks `. ++ This function can support :ref:`specifying a file descriptor ` and ++ :ref:`not following symlinks `. + + .. index:: module: stat + +@@ -1943,7 +1945,7 @@ + :mod:`os` module permit use of their *dir_fd* parameter. Different platforms + provide different functionality, and an option that might work on one might + be unsupported on another. For consistency's sakes, functions that support +- *dir_fd* always allow specifying the parameter, but will throw an exception ++ *dir_fd* always allow specifying the parameter, but will raise an exception + if the functionality is not actually available. + + To check whether a particular function permits use of its *dir_fd* +@@ -1984,7 +1986,7 @@ + descriptor. Different platforms provide different functionality, and an + option that might work on one might be unsupported on another. For + consistency's sakes, functions that support *fd* always allow specifying +- the parameter, but will throw an exception if the functionality is not ++ the parameter, but will raise an exception if the functionality is not + actually available. + + To check whether a particular function permits specifying an open file +@@ -2005,7 +2007,7 @@ + platforms provide different functionality, and an option that might work on + one might be unsupported on another. For consistency's sakes, functions that + support *follow_symlinks* always allow specifying the parameter, but will +- throw an exception if the functionality is not actually available. ++ raise an exception if the functionality is not actually available. + + To check whether a particular function permits use of its *follow_symlinks* + parameter, use the ``in`` operator on ``supports_follow_symlinks``. As an +@@ -2923,7 +2925,7 @@ + with :const:`P_NOWAIT` return suitable process handles. + + +-.. function:: wait3([options]) ++.. function:: wait3(options) + + Similar to :func:`waitpid`, except no process id argument is given and a + 3-element tuple containing the child's process id, exit status indication, and +@@ -3307,3 +3309,6 @@ + though its exact quality depends on the OS implementation. On a Unix-like + system this will query /dev/urandom, and on Windows it will use CryptGenRandom. + If a randomness source is not found, :exc:`NotImplementedError` will be raised. ++ ++ For an easy-to-use interface to the random number generator ++ provided by your platform, please see :class:`random.SystemRandom`. +diff -r bd8afb90ebf2 Doc/library/ossaudiodev.rst +--- a/Doc/library/ossaudiodev.rst ++++ b/Doc/library/ossaudiodev.rst +@@ -67,7 +67,8 @@ + ``ossaudiodev.error``.) + + +-.. function:: open([device, ]mode) ++.. function:: open(mode) ++ open(device, mode) + + Open an audio device and return an OSS audio device object. This object + supports many file-like methods, such as :meth:`read`, :meth:`write`, and +diff -r bd8afb90ebf2 Doc/library/pickle.rst +--- a/Doc/library/pickle.rst ++++ b/Doc/library/pickle.rst +@@ -390,8 +390,9 @@ + + * classes that are defined at the top level of a module + +-* instances of such classes whose :attr:`__dict__` or :meth:`__setstate__` is +- picklable (see section :ref:`pickle-inst` for details) ++* instances of such classes whose :attr:`__dict__` or the result of calling ++ :meth:`__getstate__` is picklable (see section :ref:`pickle-inst` for ++ details). + + Attempts to pickle unpicklable objects will raise the :exc:`PicklingError` + exception; when this happens, an unspecified number of bytes may have already +@@ -402,8 +403,8 @@ + + Note that functions (built-in and user-defined) are pickled by "fully qualified" + name reference, not by value. This means that only the function name is +-pickled, along with the name of the module the function is defined in. Neither the +-function's code, nor any of its function attributes are pickled. Thus the ++pickled, along with the name of the module the function is defined in. Neither ++the function's code, nor any of its function attributes are pickled. Thus the + defining module must be importable in the unpickling environment, and the module + must contain the named object, otherwise an exception will be raised. [#]_ + +diff -r bd8afb90ebf2 Doc/library/poplib.rst +--- a/Doc/library/poplib.rst ++++ b/Doc/library/poplib.rst +@@ -24,7 +24,7 @@ + mailserver supports IMAP, you would be better off using the + :class:`imaplib.IMAP4` class, as IMAP servers tend to be better implemented. + +-A single class is provided by the :mod:`poplib` module: ++The :mod:`poplib` module provides two classes: + + + .. class:: POP3(host, port=POP3_PORT[, timeout]) +@@ -105,7 +105,7 @@ + .. method:: POP3.pass_(password) + + Send password, response includes message count and mailbox size. Note: the +- mailbox on the server is locked until :meth:`quit` is called. ++ mailbox on the server is locked until :meth:`~poplib.quit` is called. + + + .. method:: POP3.apop(user, secret) +diff -r bd8afb90ebf2 Doc/library/profile.rst +--- a/Doc/library/profile.rst ++++ b/Doc/library/profile.rst +@@ -240,11 +240,12 @@ + 43/3 0.533 0.012 0.749 0.250 pobject.py:99(evaluate) + ... + +- The first line indicates that 2706 calls were monitored. Of those calls, 2004 +- were :dfn:`primitive`. We define :dfn:`primitive` to mean that the call was not +- induced via recursion. The next line: ``Ordered by: standard name``, indicates +- that the text string in the far right column was used to sort the output. The +- column headings include: ++ The first line indicates that 2706 calls were monitored. Of those ++ calls, 2004 were :dfn:`primitive`. We define :dfn:`primitive` to ++ mean that the call was not induced via recursion. The next line: ++ ``Ordered by: standard name``, indicates that the text string in ++ the far right column was used to sort the output. The column ++ headings include: + + ncalls + for the number of calls, +@@ -266,14 +267,14 @@ + filename:lineno(function) + provides the respective data of each function + +- When there are two numbers in the first column (for example, ``43/3``), then the +- latter is the number of primitive calls, and the former is the actual number of +- calls. Note that when the function does not recurse, these two values are the +- same, and only the single figure is printed. ++ When there are two numbers in the first column (for example, ++ ``43/3``), then the latter is the number of primitive calls, and ++ the former is the actual number of calls. Note that when the ++ function does not recurse, these two values are the same, and only ++ the single figure is printed. + +- If *sort* is given, it can be one of ``'stdname'`` (sort by filename:lineno), +- ``'calls'`` (sort by number of calls), ``'time'`` (sort by total time) or +- ``'cumulative'`` (sort by cumulative time). The default is ``'stdname'``. ++ If *sort* is given, it can be one of values allowed for *key* ++ parameter from :meth:`pstats.Stats.sort_stats`. + + + .. function:: runctx(command, globals, locals, filename=None) +@@ -291,19 +292,22 @@ + + .. class:: Stats(*filenames, stream=sys.stdout) + +- This class constructor creates an instance of a "statistics object" from a +- *filename* (or set of filenames). :class:`Stats` objects are manipulated by +- methods, in order to print useful reports. You may specify an alternate output +- stream by giving the keyword argument, ``stream``. ++ This class constructor creates an instance of a "statistics object" ++ from a *filename* (or set of filenames). :class:`Stats` objects ++ are manipulated by methods, in order to print useful reports. You ++ may specify an alternate output stream by giving the keyword ++ argument, ``stream``. + +- The file selected by the above constructor must have been created by the +- corresponding version of :mod:`profile` or :mod:`cProfile`. To be specific, +- there is *no* file compatibility guaranteed with future versions of this +- profiler, and there is no compatibility with files produced by other profilers. +- If several files are provided, all the statistics for identical functions will +- be coalesced, so that an overall view of several processes can be considered in +- a single report. If additional files need to be combined with data in an +- existing :class:`Stats` object, the :meth:`add` method can be used. ++ The file selected by the above constructor must have been created ++ by the corresponding version of :mod:`profile` or :mod:`cProfile`. ++ To be specific, there is *no* file compatibility guaranteed with ++ future versions of this profiler, and there is no compatibility ++ with files produced by other profilers. If several files are ++ provided, all the statistics for identical functions will be ++ coalesced, so that an overall view of several processes can be ++ considered in a single report. If additional files need to be ++ combined with data in an existing :class:`Stats` object, the ++ :meth:`add` method can be used. + + .. (such as the old system profiler). + +@@ -318,15 +322,17 @@ + + .. method:: Stats.strip_dirs() + +- This method for the :class:`Stats` class removes all leading path information +- from file names. It is very useful in reducing the size of the printout to fit +- within (close to) 80 columns. This method modifies the object, and the stripped +- information is lost. After performing a strip operation, the object is +- considered to have its entries in a "random" order, as it was just after object +- initialization and loading. If :meth:`strip_dirs` causes two function names to +- be indistinguishable (they are on the same line of the same filename, and have +- the same function name), then the statistics for these two entries are +- accumulated into a single entry. ++ This method for the :class:`Stats` class removes all leading path ++ information from file names. It is very useful in reducing the ++ size of the printout to fit within (close to) 80 columns. This ++ method modifies the object, and the stripped information is lost. ++ After performing a strip operation, the object is considered to ++ have its entries in a "random" order, as it was just after object ++ initialization and loading. If :meth:`strip_dirs` causes two ++ function names to be indistinguishable (they are on the same line ++ of the same filename, and have the same function name), then the ++ statistics for these two entries are accumulated into a single ++ entry. + + + .. method:: Stats.add(*filenames) +@@ -340,23 +346,25 @@ + + .. method:: Stats.dump_stats(filename) + +- Save the data loaded into the :class:`Stats` object to a file named *filename*. +- The file is created if it does not exist, and is overwritten if it already +- exists. This is equivalent to the method of the same name on the +- :class:`profile.Profile` and :class:`cProfile.Profile` classes. ++ Save the data loaded into the :class:`Stats` object to a file named ++ *filename*. The file is created if it does not exist, and is ++ overwritten if it already exists. This is equivalent to the method ++ of the same name on the :class:`profile.Profile` and ++ :class:`cProfile.Profile` classes. + + + .. method:: Stats.sort_stats(*keys) + +- This method modifies the :class:`Stats` object by sorting it according to the +- supplied criteria. The argument is typically a string identifying the basis of +- a sort (example: ``'time'`` or ``'name'``). ++ This method modifies the :class:`Stats` object by sorting it ++ according to the supplied criteria. The argument is typically a ++ string identifying the basis of a sort (example: ``'time'`` or ++ ``'name'``). + +- When more than one key is provided, then additional keys are used as secondary +- criteria when there is equality in all keys selected before them. For example, +- ``sort_stats('name', 'file')`` will sort all the entries according to their +- function name, and resolve all ties (identical function names) by sorting by +- file name. ++ When more than one key is provided, then additional keys are used ++ as secondary criteria when there is equality in all keys selected ++ before them. For example, ``sort_stats('name', 'file')`` will sort ++ all the entries according to their function name, and resolve all ++ ties (identical function names) by sorting by file name. + + Abbreviations can be used for any key names, as long as the abbreviation is + unambiguous. The following are the keys currently defined: +@@ -368,10 +376,16 @@ + +------------------+----------------------+ + | ``'cumulative'`` | cumulative time | + +------------------+----------------------+ ++ | ``'cumtime'`` | cumulative time | ++ +------------------+----------------------+ + | ``'file'`` | file name | + +------------------+----------------------+ ++ | ``'filename'`` | file name | ++ +------------------+----------------------+ + | ``'module'`` | file name | + +------------------+----------------------+ ++ | ``'ncalls'`` | call count | ++ +------------------+----------------------+ + | ``'pcalls'`` | primitive call count | + +------------------+----------------------+ + | ``'line'`` | line number | +@@ -384,51 +398,60 @@ + +------------------+----------------------+ + | ``'time'`` | internal time | + +------------------+----------------------+ ++ | ``'tottime'`` | internal time | ++ +------------------+----------------------+ + +- Note that all sorts on statistics are in descending order (placing most time +- consuming items first), where as name, file, and line number searches are in +- ascending order (alphabetical). The subtle distinction between ``'nfl'`` and +- ``'stdname'`` is that the standard name is a sort of the name as printed, which +- means that the embedded line numbers get compared in an odd way. For example, +- lines 3, 20, and 40 would (if the file names were the same) appear in the string +- order 20, 3 and 40. In contrast, ``'nfl'`` does a numeric compare of the line +- numbers. In fact, ``sort_stats('nfl')`` is the same as ``sort_stats('name', +- 'file', 'line')``. ++ Note that all sorts on statistics are in descending order (placing ++ most time consuming items first), where as name, file, and line ++ number searches are in ascending order (alphabetical). The subtle ++ distinction between ``'nfl'`` and ``'stdname'`` is that the ++ standard name is a sort of the name as printed, which means that ++ the embedded line numbers get compared in an odd way. For example, ++ lines 3, 20, and 40 would (if the file names were the same) appear ++ in the string order 20, 3 and 40. In contrast, ``'nfl'`` does a ++ numeric compare of the line numbers. In fact, ++ ``sort_stats('nfl')`` is the same as ``sort_stats('name', 'file', ++ 'line')``. + +- For backward-compatibility reasons, the numeric arguments ``-1``, ``0``, ``1``, +- and ``2`` are permitted. They are interpreted as ``'stdname'``, ``'calls'``, +- ``'time'``, and ``'cumulative'`` respectively. If this old style format +- (numeric) is used, only one sort key (the numeric key) will be used, and +- additional arguments will be silently ignored. ++ For backward-compatibility reasons, the numeric arguments ``-1``, ++ ``0``, ``1``, and ``2`` are permitted. They are interpreted as ++ ``'stdname'``, ``'calls'``, ``'time'``, and ``'cumulative'`` ++ respectively. If this old style format (numeric) is used, only one ++ sort key (the numeric key) will be used, and additional arguments ++ will be silently ignored. + + .. For compatibility with the old profiler, + + + .. method:: Stats.reverse_order() + +- This method for the :class:`Stats` class reverses the ordering of the basic list +- within the object. Note that by default ascending vs descending order is +- properly selected based on the sort key of choice. ++ This method for the :class:`Stats` class reverses the ordering of ++ the basic list within the object. Note that by default ascending ++ vs descending order is properly selected based on the sort key of ++ choice. + + .. This method is provided primarily for compatibility with the old profiler. + + + .. method:: Stats.print_stats(*restrictions) + +- This method for the :class:`Stats` class prints out a report as described in the +- :func:`profile.run` definition. ++ This method for the :class:`Stats` class prints out a report as ++ described in the :func:`profile.run` definition. + +- The order of the printing is based on the last :meth:`sort_stats` operation done +- on the object (subject to caveats in :meth:`add` and :meth:`strip_dirs`). ++ The order of the printing is based on the last :meth:`sort_stats` ++ operation done on the object (subject to caveats in :meth:`add` and ++ :meth:`strip_dirs`). + +- The arguments provided (if any) can be used to limit the list down to the +- significant entries. Initially, the list is taken to be the complete set of +- profiled functions. Each restriction is either an integer (to select a count of +- lines), or a decimal fraction between 0.0 and 1.0 inclusive (to select a +- percentage of lines), or a regular expression (to pattern match the standard +- name that is printed; as of Python 1.5b1, this uses the Perl-style regular +- expression syntax defined by the :mod:`re` module). If several restrictions are +- provided, then they are applied sequentially. For example:: ++ The arguments provided (if any) can be used to limit the list down ++ to the significant entries. Initially, the list is taken to be the ++ complete set of profiled functions. Each restriction is either an ++ integer (to select a count of lines), or a decimal fraction between ++ 0.0 and 1.0 inclusive (to select a percentage of lines), or a ++ regular expression (to pattern match the standard name that is ++ printed; as of Python 1.5b1, this uses the Perl-style regular ++ expression syntax defined by the :mod:`re` module). If several ++ restrictions are provided, then they are applied sequentially. For ++ example:: + + print_stats(.1, 'foo:') + +@@ -455,17 +478,19 @@ + non-parenthesized number repeats the cumulative time spent in the function + at the right. + +- * With :mod:`cProfile`, each caller is preceded by three numbers: the number of +- times this specific call was made, and the total and cumulative times spent in +- the current function while it was invoked by this specific caller. ++ * With :mod:`cProfile`, each caller is preceded by three numbers: ++ the number of times this specific call was made, and the total ++ and cumulative times spent in the current function while it was ++ invoked by this specific caller. + + + .. method:: Stats.print_callees(*restrictions) + +- This method for the :class:`Stats` class prints a list of all function that were +- called by the indicated function. Aside from this reversal of direction of +- calls (re: called vs was called by), the arguments and ordering are identical to +- the :meth:`print_callers` method. ++ This method for the :class:`Stats` class prints a list of all ++ function that were called by the indicated function. Aside from ++ this reversal of direction of calls (re: called vs was called by), ++ the arguments and ordering are identical to the ++ :meth:`print_callers` method. + + + .. _profile-limits: +@@ -566,29 +591,33 @@ + The resulting profiler will then call :func:`your_time_func`. + + :class:`profile.Profile` +- :func:`your_time_func` should return a single number, or a list of numbers whose +- sum is the current time (like what :func:`os.times` returns). If the function +- returns a single time number, or the list of returned numbers has length 2, then +- you will get an especially fast version of the dispatch routine. ++ :func:`your_time_func` should return a single number, or a list of ++ numbers whose sum is the current time (like what :func:`os.times` ++ returns). If the function returns a single time number, or the ++ list of returned numbers has length 2, then you will get an ++ especially fast version of the dispatch routine. + +- Be warned that you should calibrate the profiler class for the timer function +- that you choose. For most machines, a timer that returns a lone integer value +- will provide the best results in terms of low overhead during profiling. +- (:func:`os.times` is *pretty* bad, as it returns a tuple of floating point +- values). If you want to substitute a better timer in the cleanest fashion, +- derive a class and hardwire a replacement dispatch method that best handles your +- timer call, along with the appropriate calibration constant. ++ Be warned that you should calibrate the profiler class for the ++ timer function that you choose. For most machines, a timer that ++ returns a lone integer value will provide the best results in terms ++ of low overhead during profiling. (:func:`os.times` is *pretty* ++ bad, as it returns a tuple of floating point values). If you want ++ to substitute a better timer in the cleanest fashion, derive a ++ class and hardwire a replacement dispatch method that best handles ++ your timer call, along with the appropriate calibration constant. + + :class:`cProfile.Profile` +- :func:`your_time_func` should return a single number. If it returns +- integers, you can also invoke the class constructor with a second argument +- specifying the real duration of one unit of time. For example, if +- :func:`your_integer_time_func` returns times measured in thousands of seconds, +- you would construct the :class:`Profile` instance as follows:: ++ :func:`your_time_func` should return a single number. If it ++ returns integers, you can also invoke the class constructor with a ++ second argument specifying the real duration of one unit of time. ++ For example, if :func:`your_integer_time_func` returns times ++ measured in thousands of seconds, you would construct the ++ :class:`Profile` instance as follows:: + + pr = profile.Profile(your_integer_time_func, 0.001) + +- As the :mod:`cProfile.Profile` class cannot be calibrated, custom timer +- functions should be used with care and should be as fast as possible. For the +- best results with a custom timer, it might be necessary to hard-code it in the C +- source of the internal :mod:`_lsprof` module. ++ As the :mod:`cProfile.Profile` class cannot be calibrated, custom ++ timer functions should be used with care and should be as fast as ++ possible. For the best results with a custom timer, it might be ++ necessary to hard-code it in the C source of the internal ++ :mod:`_lsprof` module. +diff -r bd8afb90ebf2 Doc/library/pyexpat.rst +--- a/Doc/library/pyexpat.rst ++++ b/Doc/library/pyexpat.rst +@@ -402,7 +402,7 @@ + .. method:: xmlparser.CommentHandler(data) + + Called for comments. *data* is the text of the comment, excluding the leading +- '````'. ++ ``''``. + + + .. method:: xmlparser.StartCdataSectionHandler() +diff -r bd8afb90ebf2 Doc/library/random.rst +--- a/Doc/library/random.rst ++++ b/Doc/library/random.rst +@@ -52,20 +52,20 @@ + + Bookkeeping functions: + +-.. function:: seed([x], version=2) ++.. function:: seed(a=None, version=2) + + Initialize the random number generator. + +- If *x* is omitted or ``None``, the current system time is used. If ++ If *a* is omitted or ``None``, the current system time is used. If + randomness sources are provided by the operating system, they are used + instead of the system time (see the :func:`os.urandom` function for details + on availability). + +- If *x* is an int, it is used directly. ++ If *a* is an int, it is used directly. + + With version 2 (the default), a :class:`str`, :class:`bytes`, or :class:`bytearray` + object gets converted to an :class:`int` and all of its bits are used. With version 1, +- the :func:`hash` of *x* is used instead. ++ the :func:`hash` of *a* is used instead. + + .. versionchanged:: 3.2 + Moved to the version 2 scheme which uses all of the bits in a string seed. +@@ -93,7 +93,8 @@ + + Functions for integers: + +-.. function:: randrange([start,] stop[, step]) ++.. function:: randrange(stop) ++ randrange(start, stop[, step]) + + Return a randomly selected element from ``range(start, stop, step)``. This is + equivalent to ``choice(range(start, stop, step))``, but doesn't actually build a +diff -r bd8afb90ebf2 Doc/library/re.rst +--- a/Doc/library/re.rst ++++ b/Doc/library/re.rst +@@ -824,9 +824,16 @@ + Match Objects + ------------- + +-Match objects always have a boolean value of :const:`True`. This lets you +-use a simple if-statement to test whether a match was found. Match objects +-support the following methods and attributes: ++Match objects always have a boolean value of ``True``. ++Since :meth:`~regex.match` and :meth:`~regex.search` return ``None`` ++when there is no match, you can test whether there was a match with a simple ++``if`` statement:: ++ ++ match = re.search(pattern, string) ++ if match: ++ process(match) ++ ++Match objects support the following methods and attributes: + + + .. method:: match.expand(template) +diff -r bd8afb90ebf2 Doc/library/sched.rst +--- a/Doc/library/sched.rst ++++ b/Doc/library/sched.rst +@@ -27,6 +27,7 @@ + + .. versionchanged:: 3.3 + *timefunc* and *delayfunc* parameters are optional. ++ + .. versionchanged:: 3.3 + :class:`scheduler` class can be safely used in multi-threaded + environments. +@@ -35,19 +36,22 @@ + + >>> import sched, time + >>> s = sched.scheduler(time.time, time.sleep) +- >>> def print_time(): print("From print_time", time.time()) ++ >>> def print_time(a='default'): ++ ... print("From print_time", time.time(), a) + ... + >>> def print_some_times(): + ... print(time.time()) +- ... s.enter(5, 1, print_time, ()) +- ... s.enter(10, 1, print_time, ()) ++ ... s.enter(10, 1, print_time) ++ ... s.enter(5, 2, print_time, argument=('positional',)) ++ ... s.enter(5, 1, print_time, kwargs={'a': 'keyword'}) + ... s.run() + ... print(time.time()) + ... + >>> print_some_times() + 930343690.257 +- From print_time 930343695.274 +- From print_time 930343700.273 ++ From print_time 930343695.274 positional ++ From print_time 930343695.275 keyword ++ From print_time 930343700.273 default + 930343700.276 + + .. _scheduler-objects: +@@ -58,7 +62,7 @@ + :class:`scheduler` instances have the following methods and attributes: + + +-.. method:: scheduler.enterabs(time, priority, action, argument=[], kwargs={}) ++.. method:: scheduler.enterabs(time, priority, action, argument=(), kwargs={}) + + Schedule a new event. The *time* argument should be a numeric type compatible + with the return value of the *timefunc* function passed to the constructor. +@@ -66,8 +70,8 @@ + *priority*. + + Executing the event means executing ``action(*argument, **kwargs)``. +- *argument* must be a sequence holding the parameters for *action*. +- *kwargs* must be a dictionary holding the keyword parameters for *action*. ++ *argument* is a sequence holding the positional arguments for *action*. ++ *kwargs* is a dictionary holding the keyword arguments for *action*. + + Return value is an event which may be used for later cancellation of the event + (see :meth:`cancel`). +@@ -79,7 +83,7 @@ + *kwargs* parameter was added. + + +-.. method:: scheduler.enter(delay, priority, action, argument=[], kwargs={}) ++.. method:: scheduler.enter(delay, priority, action, argument=(), kwargs={}) + + Schedule an event for *delay* more time units. Other than the relative time, the + other arguments, the effect and the return value are the same as those for +@@ -129,4 +133,4 @@ + + Read-only attribute returning a list of upcoming events in the order they + will be run. Each event is shown as a :term:`named tuple` with the +- following fields: time, priority, action, argument. ++ following fields: time, priority, action, argument, kwargs. +diff -r bd8afb90ebf2 Doc/library/shutil.rst +--- a/Doc/library/shutil.rst ++++ b/Doc/library/shutil.rst +@@ -335,7 +335,7 @@ + directories. For example, on Windows:: + + >>> shutil.which("python") +- 'c:\\python33\\python.exe' ++ 'C:\\Python33\\python.EXE' + + .. versionadded:: 3.3 + +@@ -372,7 +372,7 @@ + else: + copy2(srcname, dstname) + # XXX What about devices, sockets etc.? +- except (IOError, os.error) as why: ++ except OSError as why: + errors.append((srcname, dstname, str(why))) + # catch the Error from the recursive copytree so that we can + # continue with other files +diff -r bd8afb90ebf2 Doc/library/site.rst +--- a/Doc/library/site.rst ++++ b/Doc/library/site.rst +@@ -33,7 +33,7 @@ + For the head part, it uses ``sys.prefix`` and ``sys.exec_prefix``; empty heads + are skipped. For the tail part, it uses the empty string and then + :file:`lib/site-packages` (on Windows) or +-:file:`lib/python|version|/site-packages` and then :file:`lib/site-python` (on ++:file:`lib/python{X.Y}/site-packages` and then :file:`lib/site-python` (on + Unix and Macintosh). For each of the distinct head-tail combinations, it sees + if it refers to an existing directory, and if so, adds it to ``sys.path`` and + also inspects the newly added path for configuration files. +diff -r bd8afb90ebf2 Doc/library/smtpd.rst +--- a/Doc/library/smtpd.rst ++++ b/Doc/library/smtpd.rst +@@ -111,12 +111,13 @@ + .. attribute:: addr + + Holds the address of the client, the second value returned by +- socket.accept() ++ :func:`socket.accept ` + + .. attribute:: received_lines + + Holds a list of the line strings (decoded using UTF-8) received from +- the client. The lines have their "\\r\\n" line ending translated to "\\n". ++ the client. The lines have their ``"\r\n"`` line ending translated to ++ ``"\n"``. + + .. attribute:: smtp_state + +@@ -141,12 +142,12 @@ + .. attribute:: received_data + + Holds a string containing all of the data sent by the client during the +- DATA state, up to but not including the terminating "\r\n.\r\n". ++ DATA state, up to but not including the terminating ``"\r\n.\r\n"``. + + .. attribute:: fqdn + + Holds the fully-qualified domain name of the server as returned by +- ``socket.getfqdn()``. ++ :func:`socket.getfqdn`. + + .. attribute:: peer + +@@ -170,14 +171,14 @@ + MAIL Accepts the "MAIL FROM:" syntax and stores the supplied address as + :attr:`mailfrom`. In extended command mode, accepts the + :rfc:`1870` SIZE attribute and responds appropriately based on the +- value of ``data_size_limit``. ++ value of *data_size_limit*. + RCPT Accepts the "RCPT TO:" syntax and stores the supplied addresses in + the :attr:`rcpttos` list. + RSET Resets the :attr:`mailfrom`, :attr:`rcpttos`, and + :attr:`received_data`, but not the greeting. + DATA Sets the internal state to :attr:`DATA` and stores remaining lines + from the client in :attr:`received_data` until the terminator +- "\r\n.\r\n" is received. ++ ``"\r\n.\r\n"`` is received. + HELP Returns minimal information on command syntax + VRFY Returns code 252 (the server doesn't know if the address is valid) + EXPN Reports that the command is not implemented. +diff -r bd8afb90ebf2 Doc/library/smtplib.rst +--- a/Doc/library/smtplib.rst ++++ b/Doc/library/smtplib.rst +@@ -37,7 +37,8 @@ + behavior will be used. + + For normal use, you should only require the initialization/connect, +- :meth:`sendmail`, and :meth:`quit` methods. An example is included below. ++ :meth:`sendmail`, and :meth:`~smtplib.quit` methods. ++ An example is included below. + + The :class:`SMTP` class supports the :keyword:`with` statement. When used + like this, the SMTP ``QUIT`` command is issued automatically when the +diff -r bd8afb90ebf2 Doc/library/socket.rst +--- a/Doc/library/socket.rst ++++ b/Doc/library/socket.rst +@@ -1005,7 +1005,8 @@ + much data, if any, was successfully sent. + + +-.. method:: socket.sendto(bytes[, flags], address) ++.. method:: socket.sendto(bytes, address) ++ socket.sendto(bytes, flags, address) + + Send data to the socket. The socket should not be connected to a remote socket, + since the destination socket is specified by *address*. The optional *flags* +diff -r bd8afb90ebf2 Doc/library/socketserver.rst +--- a/Doc/library/socketserver.rst ++++ b/Doc/library/socketserver.rst +@@ -153,20 +153,22 @@ + + .. method:: BaseServer.serve_forever(poll_interval=0.5) + +- Handle requests until an explicit :meth:`shutdown` request. +- Poll for shutdown every *poll_interval* seconds. Ignores :attr:`self.timeout`. It also calls +- :meth:`service_actions` which may be used by a subclass or Mixin to provide +- various cleanup actions. For e.g. ForkingMixin class uses +- :meth:`service_actions` to cleanup the zombie child processes. ++ Handle requests until an explicit :meth:`shutdown` request. Poll for ++ shutdown every *poll_interval* seconds. Ignores :attr:`self.timeout`. It ++ also calls :meth:`service_actions`, which may be used by a subclass or mixin ++ to provide actions specific to a given service. For example, the ++ :class:`ForkingMixIn` class uses :meth:`service_actions` to clean up zombie ++ child processes. + + .. versionchanged:: 3.3 +- Added service_actions call to the serve_forever method. ++ Added ``service_actions`` call to the ``serve_forever`` method. + + + .. method:: BaseServer.service_actions() + +- This is called by the serve_forever loop. This method is can be overridden +- by Mixin's to add cleanup or service specific actions. ++ This is called in the :meth:`serve_forever` loop. This method is can be ++ overridden by subclasses or mixin classes to perform actions specific to ++ a given service, such as cleanup actions. + + .. versionadded:: 3.3 + +@@ -311,8 +313,8 @@ + .. method:: RequestHandler.finish() + + Called after the :meth:`handle` method to perform any clean-up actions +- required. The default implementation does nothing. If :meth:`setup` or +- :meth:`handle` raise an exception, this function will not be called. ++ required. The default implementation does nothing. If :meth:`setup` ++ raises an exception, this function will not be called. + + + .. method:: RequestHandler.handle() +diff -r bd8afb90ebf2 Doc/library/sqlite3.rst +--- a/Doc/library/sqlite3.rst ++++ b/Doc/library/sqlite3.rst +@@ -109,6 +109,28 @@ + ------------------------------ + + ++.. data:: version ++ ++ The version number of this module, as a string. This is not the version of ++ the SQLite library. ++ ++ ++.. data:: version_info ++ ++ The version number of this module, as a tuple of integers. This is not the ++ version of the SQLite library. ++ ++ ++.. data:: sqlite_version ++ ++ The version number of the run-time SQLite library, as a string. ++ ++ ++.. data:: sqlite_version_info ++ ++ The version number of the run-time SQLite library, as a tuple of integers. ++ ++ + .. data:: PARSE_DECLTYPES + + This constant is meant to be used with the *detect_types* parameter of the +@@ -222,250 +244,254 @@ + + A SQLite database connection has the following attributes and methods: + +-.. attribute:: Connection.isolation_level ++ .. attribute:: isolation_level + +- Get or set the current isolation level. :const:`None` for autocommit mode or +- one of "DEFERRED", "IMMEDIATE" or "EXCLUSIVE". See section +- :ref:`sqlite3-controlling-transactions` for a more detailed explanation. ++ Get or set the current isolation level. :const:`None` for autocommit mode or ++ one of "DEFERRED", "IMMEDIATE" or "EXCLUSIVE". See section ++ :ref:`sqlite3-controlling-transactions` for a more detailed explanation. + +-.. attribute:: Connection.in_transaction ++ .. attribute:: in_transaction + +- :const:`True` if a transaction is active (there are uncommitted changes), +- :const:`False` otherwise. Read-only attribute. ++ :const:`True` if a transaction is active (there are uncommitted changes), ++ :const:`False` otherwise. Read-only attribute. + +- .. versionadded:: 3.2 ++ .. versionadded:: 3.2 + +-.. method:: Connection.cursor([cursorClass]) ++ .. method:: cursor([cursorClass]) + +- The cursor method accepts a single optional parameter *cursorClass*. If +- supplied, this must be a custom cursor class that extends +- :class:`sqlite3.Cursor`. ++ The cursor method accepts a single optional parameter *cursorClass*. If ++ supplied, this must be a custom cursor class that extends ++ :class:`sqlite3.Cursor`. + +-.. method:: Connection.commit() ++ .. method:: commit() + +- This method commits the current transaction. If you don't call this method, +- anything you did since the last call to ``commit()`` is not visible from +- other database connections. If you wonder why you don't see the data you've +- written to the database, please check you didn't forget to call this method. ++ This method commits the current transaction. If you don't call this method, ++ anything you did since the last call to ``commit()`` is not visible from ++ other database connections. If you wonder why you don't see the data you've ++ written to the database, please check you didn't forget to call this method. + +-.. method:: Connection.rollback() ++ .. method:: rollback() + +- This method rolls back any changes to the database since the last call to +- :meth:`commit`. ++ This method rolls back any changes to the database since the last call to ++ :meth:`commit`. + +-.. method:: Connection.close() ++ .. method:: close() + +- This closes the database connection. Note that this does not automatically +- call :meth:`commit`. If you just close your database connection without +- calling :meth:`commit` first, your changes will be lost! ++ This closes the database connection. Note that this does not automatically ++ call :meth:`commit`. If you just close your database connection without ++ calling :meth:`commit` first, your changes will be lost! + +-.. method:: Connection.execute(sql, [parameters]) ++ .. method:: execute(sql, [parameters]) + +- This is a nonstandard shortcut that creates an intermediate cursor object by +- calling the cursor method, then calls the cursor's :meth:`execute +- ` method with the parameters given. ++ This is a nonstandard shortcut that creates an intermediate cursor object by ++ calling the cursor method, then calls the cursor's :meth:`execute ++ ` method with the parameters given. + + +-.. method:: Connection.executemany(sql, [parameters]) ++ .. method:: executemany(sql, [parameters]) + +- This is a nonstandard shortcut that creates an intermediate cursor object by +- calling the cursor method, then calls the cursor's :meth:`executemany +- ` method with the parameters given. ++ This is a nonstandard shortcut that creates an intermediate cursor object by ++ calling the cursor method, then calls the cursor's :meth:`executemany ++ ` method with the parameters given. + +-.. method:: Connection.executescript(sql_script) ++ .. method:: executescript(sql_script) + +- This is a nonstandard shortcut that creates an intermediate cursor object by +- calling the cursor method, then calls the cursor's :meth:`executescript +- ` method with the parameters given. ++ This is a nonstandard shortcut that creates an intermediate cursor object by ++ calling the cursor method, then calls the cursor's :meth:`executescript ++ ` method with the parameters given. + + +-.. method:: Connection.create_function(name, num_params, func) ++ .. method:: create_function(name, num_params, func) + +- Creates a user-defined function that you can later use from within SQL +- statements under the function name *name*. *num_params* is the number of +- parameters the function accepts, and *func* is a Python callable that is called +- as the SQL function. ++ Creates a user-defined function that you can later use from within SQL ++ statements under the function name *name*. *num_params* is the number of ++ parameters the function accepts, and *func* is a Python callable that is called ++ as the SQL function. + +- The function can return any of the types supported by SQLite: bytes, str, int, +- float and None. ++ The function can return any of the types supported by SQLite: bytes, str, int, ++ float and None. + +- Example: ++ Example: + +- .. literalinclude:: ../includes/sqlite3/md5func.py ++ .. literalinclude:: ../includes/sqlite3/md5func.py + + +-.. method:: Connection.create_aggregate(name, num_params, aggregate_class) ++ .. method:: create_aggregate(name, num_params, aggregate_class) + +- Creates a user-defined aggregate function. ++ Creates a user-defined aggregate function. + +- The aggregate class must implement a ``step`` method, which accepts the number +- of parameters *num_params*, and a ``finalize`` method which will return the +- final result of the aggregate. ++ The aggregate class must implement a ``step`` method, which accepts the number ++ of parameters *num_params*, and a ``finalize`` method which will return the ++ final result of the aggregate. + +- The ``finalize`` method can return any of the types supported by SQLite: +- bytes, str, int, float and None. ++ The ``finalize`` method can return any of the types supported by SQLite: ++ bytes, str, int, float and None. + +- Example: ++ Example: + +- .. literalinclude:: ../includes/sqlite3/mysumaggr.py ++ .. literalinclude:: ../includes/sqlite3/mysumaggr.py + + +-.. method:: Connection.create_collation(name, callable) ++ .. method:: create_collation(name, callable) + +- Creates a collation with the specified *name* and *callable*. The callable will +- be passed two string arguments. It should return -1 if the first is ordered +- lower than the second, 0 if they are ordered equal and 1 if the first is ordered +- higher than the second. Note that this controls sorting (ORDER BY in SQL) so +- your comparisons don't affect other SQL operations. ++ Creates a collation with the specified *name* and *callable*. The callable will ++ be passed two string arguments. It should return -1 if the first is ordered ++ lower than the second, 0 if they are ordered equal and 1 if the first is ordered ++ higher than the second. Note that this controls sorting (ORDER BY in SQL) so ++ your comparisons don't affect other SQL operations. + +- Note that the callable will get its parameters as Python bytestrings, which will +- normally be encoded in UTF-8. ++ Note that the callable will get its parameters as Python bytestrings, which will ++ normally be encoded in UTF-8. + +- The following example shows a custom collation that sorts "the wrong way": ++ The following example shows a custom collation that sorts "the wrong way": + +- .. literalinclude:: ../includes/sqlite3/collation_reverse.py ++ .. literalinclude:: ../includes/sqlite3/collation_reverse.py + +- To remove a collation, call ``create_collation`` with None as callable:: ++ To remove a collation, call ``create_collation`` with None as callable:: + +- con.create_collation("reverse", None) ++ con.create_collation("reverse", None) + + +-.. method:: Connection.interrupt() ++ .. method:: interrupt() + +- You can call this method from a different thread to abort any queries that might +- be executing on the connection. The query will then abort and the caller will +- get an exception. ++ You can call this method from a different thread to abort any queries that might ++ be executing on the connection. The query will then abort and the caller will ++ get an exception. + + +-.. method:: Connection.set_authorizer(authorizer_callback) ++ .. method:: set_authorizer(authorizer_callback) + +- This routine registers a callback. The callback is invoked for each attempt to +- access a column of a table in the database. The callback should return +- :const:`SQLITE_OK` if access is allowed, :const:`SQLITE_DENY` if the entire SQL +- statement should be aborted with an error and :const:`SQLITE_IGNORE` if the +- column should be treated as a NULL value. These constants are available in the +- :mod:`sqlite3` module. ++ This routine registers a callback. The callback is invoked for each attempt to ++ access a column of a table in the database. The callback should return ++ :const:`SQLITE_OK` if access is allowed, :const:`SQLITE_DENY` if the entire SQL ++ statement should be aborted with an error and :const:`SQLITE_IGNORE` if the ++ column should be treated as a NULL value. These constants are available in the ++ :mod:`sqlite3` module. + +- The first argument to the callback signifies what kind of operation is to be +- authorized. The second and third argument will be arguments or :const:`None` +- depending on the first argument. The 4th argument is the name of the database +- ("main", "temp", etc.) if applicable. The 5th argument is the name of the +- inner-most trigger or view that is responsible for the access attempt or +- :const:`None` if this access attempt is directly from input SQL code. ++ The first argument to the callback signifies what kind of operation is to be ++ authorized. The second and third argument will be arguments or :const:`None` ++ depending on the first argument. The 4th argument is the name of the database ++ ("main", "temp", etc.) if applicable. The 5th argument is the name of the ++ inner-most trigger or view that is responsible for the access attempt or ++ :const:`None` if this access attempt is directly from input SQL code. + +- Please consult the SQLite documentation about the possible values for the first +- argument and the meaning of the second and third argument depending on the first +- one. All necessary constants are available in the :mod:`sqlite3` module. ++ Please consult the SQLite documentation about the possible values for the first ++ argument and the meaning of the second and third argument depending on the first ++ one. All necessary constants are available in the :mod:`sqlite3` module. + + +-.. method:: Connection.set_progress_handler(handler, n) ++ .. method:: set_progress_handler(handler, n) + +- This routine registers a callback. The callback is invoked for every *n* +- instructions of the SQLite virtual machine. This is useful if you want to +- get called from SQLite during long-running operations, for example to update +- a GUI. ++ This routine registers a callback. The callback is invoked for every *n* ++ instructions of the SQLite virtual machine. This is useful if you want to ++ get called from SQLite during long-running operations, for example to update ++ a GUI. + +- If you want to clear any previously installed progress handler, call the +- method with :const:`None` for *handler*. ++ If you want to clear any previously installed progress handler, call the ++ method with :const:`None` for *handler*. + + +-.. method:: Connection.set_trace_callback(trace_callback) ++ .. method:: set_trace_callback(trace_callback) + +- Registers *trace_callback* to be called for each SQL statement that is +- actually executed by the SQLite backend. ++ Registers *trace_callback* to be called for each SQL statement that is ++ actually executed by the SQLite backend. + +- The only argument passed to the callback is the statement (as string) that +- is being executed. The return value of the callback is ignored. Note that +- the backend does not only run statements passed to the :meth:`Cursor.execute` +- methods. Other sources include the transaction management of the Python +- module and the execution of triggers defined in the current database. ++ The only argument passed to the callback is the statement (as string) that ++ is being executed. The return value of the callback is ignored. Note that ++ the backend does not only run statements passed to the :meth:`Cursor.execute` ++ methods. Other sources include the transaction management of the Python ++ module and the execution of triggers defined in the current database. + +- Passing :const:`None` as *trace_callback* will disable the trace callback. ++ Passing :const:`None` as *trace_callback* will disable the trace callback. + +- .. versionadded:: 3.3 ++ .. versionadded:: 3.3 + + +-.. method:: Connection.enable_load_extension(enabled) ++ .. method:: enable_load_extension(enabled) + +- This routine allows/disallows the SQLite engine to load SQLite extensions +- from shared libraries. SQLite extensions can define new functions, +- aggregates or whole new virtual table implementations. One well-known +- extension is the fulltext-search extension distributed with SQLite. ++ This routine allows/disallows the SQLite engine to load SQLite extensions ++ from shared libraries. SQLite extensions can define new functions, ++ aggregates or whole new virtual table implementations. One well-known ++ extension is the fulltext-search extension distributed with SQLite. + +- Loadable extensions are disabled by default. See [#f1]_. ++ Loadable extensions are disabled by default. See [#f1]_. + +- .. versionadded:: 3.2 ++ .. versionadded:: 3.2 + +- .. literalinclude:: ../includes/sqlite3/load_extension.py ++ .. literalinclude:: ../includes/sqlite3/load_extension.py + +-.. method:: Connection.load_extension(path) ++ .. method:: load_extension(path) + +- This routine loads a SQLite extension from a shared library. You have to +- enable extension loading with :meth:`enable_load_extension` before you can +- use this routine. ++ This routine loads a SQLite extension from a shared library. You have to ++ enable extension loading with :meth:`enable_load_extension` before you can ++ use this routine. + +- Loadable extensions are disabled by default. See [#f1]_. ++ Loadable extensions are disabled by default. See [#f1]_. + +- .. versionadded:: 3.2 ++ .. versionadded:: 3.2 + +-.. attribute:: Connection.row_factory ++ .. attribute:: row_factory + +- You can change this attribute to a callable that accepts the cursor and the +- original row as a tuple and will return the real result row. This way, you can +- implement more advanced ways of returning results, such as returning an object +- that can also access columns by name. ++ You can change this attribute to a callable that accepts the cursor and the ++ original row as a tuple and will return the real result row. This way, you can ++ implement more advanced ways of returning results, such as returning an object ++ that can also access columns by name. + +- Example: ++ Example: + +- .. literalinclude:: ../includes/sqlite3/row_factory.py ++ .. literalinclude:: ../includes/sqlite3/row_factory.py + +- If returning a tuple doesn't suffice and you want name-based access to +- columns, you should consider setting :attr:`row_factory` to the +- highly-optimized :class:`sqlite3.Row` type. :class:`Row` provides both +- index-based and case-insensitive name-based access to columns with almost no +- memory overhead. It will probably be better than your own custom +- dictionary-based approach or even a db_row based solution. ++ If returning a tuple doesn't suffice and you want name-based access to ++ columns, you should consider setting :attr:`row_factory` to the ++ highly-optimized :class:`sqlite3.Row` type. :class:`Row` provides both ++ index-based and case-insensitive name-based access to columns with almost no ++ memory overhead. It will probably be better than your own custom ++ dictionary-based approach or even a db_row based solution. + +- .. XXX what's a db_row-based solution? ++ .. XXX what's a db_row-based solution? + + +-.. attribute:: Connection.text_factory ++ .. attribute:: text_factory + +- Using this attribute you can control what objects are returned for the ``TEXT`` +- data type. By default, this attribute is set to :class:`str` and the +- :mod:`sqlite3` module will return Unicode objects for ``TEXT``. If you want to +- return bytestrings instead, you can set it to :class:`bytes`. ++ Using this attribute you can control what objects are returned for the ``TEXT`` ++ data type. By default, this attribute is set to :class:`str` and the ++ :mod:`sqlite3` module will return Unicode objects for ``TEXT``. If you want to ++ return bytestrings instead, you can set it to :class:`bytes`. + +- You can also set it to any other callable that accepts a single bytestring +- parameter and returns the resulting object. ++ For efficiency reasons, there's also a way to return :class:`str` objects ++ only for non-ASCII data, and :class:`bytes` otherwise. To activate it, set ++ this attribute to :const:`sqlite3.OptimizedUnicode`. + +- See the following example code for illustration: ++ You can also set it to any other callable that accepts a single bytestring ++ parameter and returns the resulting object. + +- .. literalinclude:: ../includes/sqlite3/text_factory.py ++ See the following example code for illustration: + ++ .. literalinclude:: ../includes/sqlite3/text_factory.py + +-.. attribute:: Connection.total_changes + +- Returns the total number of database rows that have been modified, inserted, or +- deleted since the database connection was opened. ++ .. attribute:: total_changes + ++ Returns the total number of database rows that have been modified, inserted, or ++ deleted since the database connection was opened. + +-.. attribute:: Connection.iterdump + +- Returns an iterator to dump the database in an SQL text format. Useful when +- saving an in-memory database for later restoration. This function provides +- the same capabilities as the :kbd:`.dump` command in the :program:`sqlite3` +- shell. ++ .. attribute:: iterdump + +- Example:: ++ Returns an iterator to dump the database in an SQL text format. Useful when ++ saving an in-memory database for later restoration. This function provides ++ the same capabilities as the :kbd:`.dump` command in the :program:`sqlite3` ++ shell. + +- # Convert file existing_db.db to SQL dump file dump.sql +- import sqlite3, os ++ Example:: + +- con = sqlite3.connect('existing_db.db') +- with open('dump.sql', 'w') as f: +- for line in con.iterdump(): +- f.write('%s\n' % line) ++ # Convert file existing_db.db to SQL dump file dump.sql ++ import sqlite3, os ++ ++ con = sqlite3.connect('existing_db.db') ++ with open('dump.sql', 'w') as f: ++ for line in con.iterdump(): ++ f.write('%s\n' % line) + + + .. _sqlite3-cursor-objects: +@@ -477,110 +503,110 @@ + + A :class:`Cursor` instance has the following attributes and methods. + +-.. method:: Cursor.execute(sql, [parameters]) ++ .. method:: execute(sql, [parameters]) + +- Executes an SQL statement. The SQL statement may be parametrized (i. e. +- placeholders instead of SQL literals). The :mod:`sqlite3` module supports two +- kinds of placeholders: question marks (qmark style) and named placeholders +- (named style). ++ Executes an SQL statement. The SQL statement may be parametrized (i. e. ++ placeholders instead of SQL literals). The :mod:`sqlite3` module supports two ++ kinds of placeholders: question marks (qmark style) and named placeholders ++ (named style). + +- Here's an example of both styles: ++ Here's an example of both styles: + +- .. literalinclude:: ../includes/sqlite3/execute_1.py ++ .. literalinclude:: ../includes/sqlite3/execute_1.py + +- :meth:`execute` will only execute a single SQL statement. If you try to execute +- more than one statement with it, it will raise a Warning. Use +- :meth:`executescript` if you want to execute multiple SQL statements with one +- call. ++ :meth:`execute` will only execute a single SQL statement. If you try to execute ++ more than one statement with it, it will raise a Warning. Use ++ :meth:`executescript` if you want to execute multiple SQL statements with one ++ call. + + +-.. method:: Cursor.executemany(sql, seq_of_parameters) ++ .. method:: executemany(sql, seq_of_parameters) + +- Executes an SQL command against all parameter sequences or mappings found in +- the sequence *sql*. The :mod:`sqlite3` module also allows using an +- :term:`iterator` yielding parameters instead of a sequence. ++ Executes an SQL command against all parameter sequences or mappings found in ++ the sequence *sql*. The :mod:`sqlite3` module also allows using an ++ :term:`iterator` yielding parameters instead of a sequence. + +- .. literalinclude:: ../includes/sqlite3/executemany_1.py ++ .. literalinclude:: ../includes/sqlite3/executemany_1.py + +- Here's a shorter example using a :term:`generator`: ++ Here's a shorter example using a :term:`generator`: + +- .. literalinclude:: ../includes/sqlite3/executemany_2.py ++ .. literalinclude:: ../includes/sqlite3/executemany_2.py + + +-.. method:: Cursor.executescript(sql_script) ++ .. method:: executescript(sql_script) + +- This is a nonstandard convenience method for executing multiple SQL statements +- at once. It issues a ``COMMIT`` statement first, then executes the SQL script it +- gets as a parameter. ++ This is a nonstandard convenience method for executing multiple SQL statements ++ at once. It issues a ``COMMIT`` statement first, then executes the SQL script it ++ gets as a parameter. + +- *sql_script* can be an instance of :class:`str` or :class:`bytes`. ++ *sql_script* can be an instance of :class:`str` or :class:`bytes`. + +- Example: ++ Example: + +- .. literalinclude:: ../includes/sqlite3/executescript.py ++ .. literalinclude:: ../includes/sqlite3/executescript.py + + +-.. method:: Cursor.fetchone() ++ .. method:: fetchone() + +- Fetches the next row of a query result set, returning a single sequence, +- or :const:`None` when no more data is available. ++ Fetches the next row of a query result set, returning a single sequence, ++ or :const:`None` when no more data is available. + + +-.. method:: Cursor.fetchmany(size=cursor.arraysize) ++ .. method:: fetchmany(size=cursor.arraysize) + +- Fetches the next set of rows of a query result, returning a list. An empty +- list is returned when no more rows are available. ++ Fetches the next set of rows of a query result, returning a list. An empty ++ list is returned when no more rows are available. + +- The number of rows to fetch per call is specified by the *size* parameter. +- If it is not given, the cursor's arraysize determines the number of rows +- to be fetched. The method should try to fetch as many rows as indicated by +- the size parameter. If this is not possible due to the specified number of +- rows not being available, fewer rows may be returned. ++ The number of rows to fetch per call is specified by the *size* parameter. ++ If it is not given, the cursor's arraysize determines the number of rows ++ to be fetched. The method should try to fetch as many rows as indicated by ++ the size parameter. If this is not possible due to the specified number of ++ rows not being available, fewer rows may be returned. + +- Note there are performance considerations involved with the *size* parameter. +- For optimal performance, it is usually best to use the arraysize attribute. +- If the *size* parameter is used, then it is best for it to retain the same +- value from one :meth:`fetchmany` call to the next. ++ Note there are performance considerations involved with the *size* parameter. ++ For optimal performance, it is usually best to use the arraysize attribute. ++ If the *size* parameter is used, then it is best for it to retain the same ++ value from one :meth:`fetchmany` call to the next. + +-.. method:: Cursor.fetchall() ++ .. method:: fetchall() + +- Fetches all (remaining) rows of a query result, returning a list. Note that +- the cursor's arraysize attribute can affect the performance of this operation. +- An empty list is returned when no rows are available. ++ Fetches all (remaining) rows of a query result, returning a list. Note that ++ the cursor's arraysize attribute can affect the performance of this operation. ++ An empty list is returned when no rows are available. + + +-.. attribute:: Cursor.rowcount ++ .. attribute:: rowcount + +- Although the :class:`Cursor` class of the :mod:`sqlite3` module implements this +- attribute, the database engine's own support for the determination of "rows +- affected"/"rows selected" is quirky. ++ Although the :class:`Cursor` class of the :mod:`sqlite3` module implements this ++ attribute, the database engine's own support for the determination of "rows ++ affected"/"rows selected" is quirky. + +- For :meth:`executemany` statements, the number of modifications are summed up +- into :attr:`rowcount`. ++ For :meth:`executemany` statements, the number of modifications are summed up ++ into :attr:`rowcount`. + +- As required by the Python DB API Spec, the :attr:`rowcount` attribute "is -1 in +- case no ``executeXX()`` has been performed on the cursor or the rowcount of the +- last operation is not determinable by the interface". This includes ``SELECT`` +- statements because we cannot determine the number of rows a query produced +- until all rows were fetched. ++ As required by the Python DB API Spec, the :attr:`rowcount` attribute "is -1 in ++ case no ``executeXX()`` has been performed on the cursor or the rowcount of the ++ last operation is not determinable by the interface". This includes ``SELECT`` ++ statements because we cannot determine the number of rows a query produced ++ until all rows were fetched. + +- With SQLite versions before 3.6.5, :attr:`rowcount` is set to 0 if +- you make a ``DELETE FROM table`` without any condition. ++ With SQLite versions before 3.6.5, :attr:`rowcount` is set to 0 if ++ you make a ``DELETE FROM table`` without any condition. + +-.. attribute:: Cursor.lastrowid ++ .. attribute:: lastrowid + +- This read-only attribute provides the rowid of the last modified row. It is +- only set if you issued a ``INSERT`` statement using the :meth:`execute` +- method. For operations other than ``INSERT`` or when :meth:`executemany` is +- called, :attr:`lastrowid` is set to :const:`None`. ++ This read-only attribute provides the rowid of the last modified row. It is ++ only set if you issued a ``INSERT`` statement using the :meth:`execute` ++ method. For operations other than ``INSERT`` or when :meth:`executemany` is ++ called, :attr:`lastrowid` is set to :const:`None`. + +-.. attribute:: Cursor.description ++ .. attribute:: description + +- This read-only attribute provides the column names of the last query. To +- remain compatible with the Python DB API, it returns a 7-tuple for each +- column where the last six items of each tuple are :const:`None`. ++ This read-only attribute provides the column names of the last query. To ++ remain compatible with the Python DB API, it returns a 7-tuple for each ++ column where the last six items of each tuple are :const:`None`. + +- It is set for ``SELECT`` statements without any matching rows as well. ++ It is set for ``SELECT`` statements without any matching rows as well. + + .. _sqlite3-row-objects: + +diff -r bd8afb90ebf2 Doc/library/stat.rst +--- a/Doc/library/stat.rst ++++ b/Doc/library/stat.rst +@@ -182,10 +182,6 @@ + + Use of the functions above is more portable than use of the first set of flags: + +-.. data:: S_IFMT +- +- Bit mask for the file type bit fields. +- + .. data:: S_IFSOCK + + Socket. +diff -r bd8afb90ebf2 Doc/library/stdtypes.rst +--- a/Doc/library/stdtypes.rst ++++ b/Doc/library/stdtypes.rst +@@ -779,9 +779,9 @@ + specific types are not important beyond their implementation of the iterator + protocol. + +-Once an iterator's :meth:`__next__` method raises :exc:`StopIteration`, it must +-continue to do so on subsequent calls. Implementations that do not obey this +-property are deemed broken. ++Once an iterator's :meth:`~iterator.__next__` method raises ++:exc:`StopIteration`, it must continue to do so on subsequent calls. ++Implementations that do not obey this property are deemed broken. + + + .. _generator-types: +@@ -792,7 +792,8 @@ + Python's :term:`generator`\s provide a convenient way to implement the iterator + protocol. If a container object's :meth:`__iter__` method is implemented as a + generator, it will automatically return an iterator object (technically, a +-generator object) supplying the :meth:`__iter__` and :meth:`__next__` methods. ++generator object) supplying the :meth:`__iter__` and :meth:`~generator.__next__` ++methods. + More information about generators can be found in :ref:`the documentation for + the yield expression `. + +@@ -1235,7 +1236,8 @@ + commonly used for looping a specific number of times in :keyword:`for` + loops. + +-.. class:: range([start, ]stop[, step]) ++.. class:: range(stop) ++ range(start, stop[, step]) + + The arguments to the range constructor must be integers (either built-in + :class:`int` or any object that implements the ``__index__`` special +@@ -1344,20 +1346,19 @@ + The :attr:`start`, :attr:`stop` and :attr:`step` attributes. + + ++.. index:: ++ single: string; text sequence type ++ single: str (built-in class); (see also string) ++ object: string ++ + .. _textseq: + + Text Sequence Type --- :class:`str` + =================================== + +-.. index:: +- object: string +- object: bytes +- object: bytearray +- object: io.StringIO +- +- +-Textual data in Python is handled with :class:`str` objects, which are +-immutable sequences of Unicode code points. String literals are ++Textual data in Python is handled with :class:`str` objects, or :dfn:`strings`. ++Strings are immutable ++:ref:`sequences ` of Unicode code points. String literals are + written in a variety of ways: + + * Single quotes: ``'allows embedded "double" quotes'`` +@@ -1375,12 +1376,15 @@ + including supported escape sequences, and the ``r`` ("raw") prefix that + disables most escape sequence processing. + +-Strings may also be created from other objects with the :ref:`str ` +-built-in. ++Strings may also be created from other objects using the :class:`str` ++constructor. + + Since there is no separate "character" type, indexing a string produces + strings of length 1. That is, for a non-empty string *s*, ``s[0] == s[0:1]``. + ++.. index:: ++ object: io.StringIO ++ + There is also no mutable string type, but :meth:`str.join` or + :class:`io.StringIO` can be used to efficiently construct strings from + multiple fragments. +@@ -1390,13 +1394,61 @@ + once again permitted on string literals. It has no effect on the meaning + of string literals and cannot be combined with the ``r`` prefix. + ++ ++.. index:: ++ single: string; str (built-in class) ++ ++.. class:: str(object='') ++ str(object=b'', encoding='utf-8', errors='strict') ++ ++ Return a :ref:`string ` version of *object*. If *object* is not ++ provided, returns the empty string. Otherwise, the behavior of ``str()`` ++ depends on whether *encoding* or *errors* is given, as follows. ++ ++ If neither *encoding* nor *errors* is given, ``str(object)`` returns ++ :meth:`object.__str__() `, which is the "informal" or nicely ++ printable string representation of *object*. For string objects, this is ++ the string itself. If *object* does not have a :meth:`~object.__str__` ++ method, then :func:`str` falls back to returning ++ :meth:`repr(object) `. ++ ++ .. index:: ++ single: buffer protocol; str (built-in class) ++ single: bytes; str (built-in class) ++ ++ If at least one of *encoding* or *errors* is given, *object* should be a ++ :class:`bytes` or :class:`bytearray` object, or more generally any object ++ that supports the :ref:`buffer protocol `. In this case, if ++ *object* is a :class:`bytes` (or :class:`bytearray`) object, then ++ ``str(bytes, encoding, errors)`` is equivalent to ++ :meth:`bytes.decode(encoding, errors) `. Otherwise, the bytes ++ object underlying the buffer object is obtained before calling ++ :meth:`bytes.decode`. See :ref:`binaryseq` and ++ :ref:`bufferobjects` for information on buffer objects. ++ ++ Passing a :class:`bytes` object to :func:`str` without the *encoding* ++ or *errors* arguments falls under the first case of returning the informal ++ string representation (see also the :option:`-b` command-line option to ++ Python). For example:: ++ ++ >>> str(b'Zoot!') ++ "b'Zoot!'" ++ ++ For more information on the ``str`` class and its methods, see ++ :ref:`textseq` and the :ref:`string-methods` section below. To output ++ formatted strings, see the :ref:`string-formatting` section. In addition, ++ see the :ref:`stringservices` section. ++ ++ ++.. index:: ++ pair: string; methods ++ + .. _string-methods: + + String Methods + -------------- + + .. index:: +- pair: string; methods + module: re + + Strings implement all of the :ref:`common ` sequence +@@ -1830,11 +1882,11 @@ + + >>> import re + >>> def titlecase(s): +- return re.sub(r"[A-Za-z]+('[A-Za-z]+)?", +- lambda mo: mo.group(0)[0].upper() + +- mo.group(0)[1:].lower(), +- s) +- ++ ... return re.sub(r"[A-Za-z]+('[A-Za-z]+)?", ++ ... lambda mo: mo.group(0)[0].upper() + ++ ... mo.group(0)[1:].lower(), ++ ... s) ++ ... + >>> titlecase("they're bill's friends.") + "They're Bill's Friends." + +@@ -2062,6 +2114,9 @@ + longer replaced by ``%g`` conversions. + + ++.. index:: ++ single: buffer protocol; binary sequence types ++ + .. _binaryseq: + + Binary Sequence Types --- :class:`bytes`, :class:`bytearray`, :class:`memoryview` +@@ -2075,8 +2130,8 @@ + + The core built-in types for manipulating binary data are :class:`bytes` and + :class:`bytearray`. They are supported by :class:`memoryview` which uses +-the buffer protocol to access the memory of other binary objects without +-needing to make a copy. ++the :ref:`buffer protocol ` to access the memory of other ++binary objects without needing to make a copy. + + The :mod:`array` module supports efficient storage of basic data types like + 32-bit integers and IEEE754 double-precision floating values. +@@ -2162,7 +2217,7 @@ + * Creating an empty instance: ``bytearray()`` + * Creating a zero-filled instance with a given length: ``bytearray(10)`` + * From an iterable of integers: ``bytearray(range(20))`` +-* Copying existing binary data via the buffer protocol: ``bytearray(b'Hi!)`` ++* Copying existing binary data via the buffer protocol: ``bytearray(b'Hi!')`` + + As bytearray objects are mutable, they support the + :ref:`mutable ` sequence operations in addition to the +@@ -2391,12 +2446,6 @@ + .. versionchanged:: 3.3 + One-dimensional memoryviews with formats 'B', 'b' or 'c' are now hashable. + +- .. note:: +- Hashing of memoryviews with formats other than 'B', 'b' or 'c' as well +- as hashing of multi-dimensional memoryviews is possible in version 3.3.0, +- but will raise an error in 3.3.1 in order to be compatible with the new +- memoryview equality definition. +- + :class:`memoryview` has several methods: + + .. method:: __eq__(exporter) +@@ -2687,13 +2736,19 @@ + .. attribute:: shape + + A tuple of integers the length of :attr:`ndim` giving the shape of the +- memory as a N-dimensional array. ++ memory as an N-dimensional array. ++ ++ .. versionchanged:: 3.3 ++ An empty tuple instead of None when ndim = 0. + + .. attribute:: strides + + A tuple of integers the length of :attr:`ndim` giving the size in bytes to + access each element for each dimension of the array. + ++ .. versionchanged:: 3.3 ++ An empty tuple instead of None when ndim = 0. ++ + .. attribute:: suboffsets + + Used internally for PIL-style arrays. The value is informational only. +@@ -2785,7 +2840,7 @@ + + .. method:: set < other + +- Test whether the set is a true subset of *other*, that is, ++ Test whether the set is a proper subset of *other*, that is, + ``set <= other and set != other``. + + .. method:: issuperset(other) +@@ -2795,7 +2850,7 @@ + + .. method:: set > other + +- Test whether the set is a true superset of *other*, that is, ``set >= ++ Test whether the set is a proper superset of *other*, that is, ``set >= + other and set != other``. + + .. method:: union(other, ...) +@@ -2926,7 +2981,7 @@ + statement: del + builtin: len + +-A :dfn:`mapping` object maps :term:`hashable` values to arbitrary objects. ++A :term:`mapping` object maps :term:`hashable` values to arbitrary objects. + Mappings are mutable objects. There is currently only one standard mapping + type, the :dfn:`dictionary`. (For other containers see the built-in + :class:`list`, :class:`set`, and :class:`tuple` classes, and the +@@ -2945,33 +3000,41 @@ + pairs within braces, for example: ``{'jack': 4098, 'sjoerd': 4127}`` or ``{4098: + 'jack', 4127: 'sjoerd'}``, or by the :class:`dict` constructor. + +-.. class:: dict([arg]) +- +- Return a new dictionary initialized from an optional positional argument or +- from a set of keyword arguments. If no arguments are given, return a new +- empty dictionary. If the positional argument *arg* is a mapping object, +- return a dictionary mapping the same keys to the same values as does the +- mapping object. Otherwise the positional argument must be a sequence, a +- container that supports iteration, or an iterator object. The elements of +- the argument must each also be of one of those kinds, and each must in turn +- contain exactly two objects. The first is used as a key in the new +- dictionary, and the second as the key's value. If a given key is seen more +- than once, the last value associated with it is retained in the new ++.. class:: dict(**kwarg) ++ dict(mapping, **kwarg) ++ dict(iterable, **kwarg) ++ ++ Return a new dictionary initialized from an optional positional argument ++ and a possibly empty set of keyword arguments. ++ ++ If no positional argument is given, an empty dictionary is created. ++ If a positional argument is given and it is a mapping object, a dictionary ++ is created with the same key-value pairs as the mapping object. Otherwise, ++ the positional argument must be an :term:`iterator` object. Each item in ++ the iterable must itself be an iterator with exactly two objects. The ++ first object of each item becomes a key in the new dictionary, and the ++ second object the corresponding value. If a key occurs more than once, the ++ last value for that key becomes the corresponding value in the new + dictionary. + +- If keyword arguments are given, the keywords themselves with their associated +- values are added as items to the dictionary. If a key is specified both in +- the positional argument and as a keyword argument, the value associated with +- the keyword is retained in the dictionary. For example, these all return a +- dictionary equal to ``{"one": 1, "two": 2}``: +- +- * ``dict(one=1, two=2)`` +- * ``dict({'one': 1, 'two': 2})`` +- * ``dict(zip(('one', 'two'), (1, 2)))`` +- * ``dict([['two', 2], ['one', 1]])`` +- +- The first example only works for keys that are valid Python identifiers; the +- others work with any valid keys. ++ If keyword arguments are given, the keyword arguments and their values are ++ added to the dictionary created from the positional argument. If a key ++ being added is already present, the value from the keyword argument ++ replaces the value from the positional argument. ++ ++ To illustrate, the following examples all return a dictionary equal to ++ ``{"one": 1, "two": 2, "three": 3}``:: ++ ++ >>> a = dict(one=1, two=2, three=3) ++ >>> b = {'one': 1, 'two': 2, 'three': 3} ++ >>> c = dict(zip(['one', 'two', 'three'], [1, 2, 3])) ++ >>> d = dict([('two', 2), ('one', 1), ('three', 3)]) ++ >>> e = dict({'three': 3, 'one': 1, 'two': 2}) ++ >>> a == b == c == d == e ++ True ++ ++ Providing keyword arguments as in the first example only works for keys that ++ are valid Python identifiers. Otherwise, any valid keys can be used. + + + These are the operations that dictionaries support (and therefore, custom +@@ -3333,16 +3396,22 @@ + Like function objects, bound method objects support getting arbitrary + attributes. However, since method attributes are actually stored on the + underlying function object (``meth.__func__``), setting method attributes on +-bound methods is disallowed. Attempting to set a method attribute results in a +-:exc:`TypeError` being raised. In order to set a method attribute, you need to +-explicitly set it on the underlying function object:: +- +- class C: +- def method(self): +- pass +- +- c = C() +- c.method.__func__.whoami = 'my name is c' ++bound methods is disallowed. Attempting to set an attribute on a method ++results in an :exc:`AttributeError` being raised. In order to set a method ++attribute, you need to explicitly set it on the underlying function object:: ++ ++ >>> class C: ++ ... def method(self): ++ ... pass ++ ... ++ >>> c = C() ++ >>> c.method.whoami = 'my name is method' # can't set on the method ++ Traceback (most recent call last): ++ File "", line 1, in ++ AttributeError: 'method' object has no attribute 'whoami' ++ >>> c.method.__func__.whoami = 'my name is method' ++ >>> c.method.whoami ++ 'my name is method' + + See :ref:`types` for more information. + +diff -r bd8afb90ebf2 Doc/library/string.rst +--- a/Doc/library/string.rst ++++ b/Doc/library/string.rst +@@ -10,7 +10,7 @@ + + .. seealso:: + +- :ref:`typesseq` ++ :ref:`textseq` + + :ref:`string-methods` + +@@ -100,7 +100,7 @@ + This function does the actual work of formatting. It is exposed as a + separate function for cases where you want to pass in a predefined + dictionary of arguments, rather than unpacking and repacking the +- dictionary as individual arguments using the ``*args`` and ``**kwds`` ++ dictionary as individual arguments using the ``*args`` and ``**kwargs`` + syntax. :meth:`vformat` does the work of breaking up the format string + into character data and replacement fields. It calls the various + methods described below. +@@ -610,7 +610,7 @@ + 3232235521 + >>> + >>> width = 5 +- >>> for num in range(5,12): ++ >>> for num in range(5,12): #doctest: +NORMALIZE_WHITESPACE + ... for base in 'dXob': + ... print('{0:{width}{base}}'.format(num, base=base, width=width), end=' ') + ... print() +@@ -698,7 +698,7 @@ + >>> Template('Give $who $100').substitute(d) + Traceback (most recent call last): + [...] +- ValueError: Invalid placeholder in string: line 1, col 10 ++ ValueError: Invalid placeholder in string: line 1, col 11 + >>> Template('$who likes $what').substitute(d) + Traceback (most recent call last): + [...] +diff -r bd8afb90ebf2 Doc/library/subprocess.rst +--- a/Doc/library/subprocess.rst ++++ b/Doc/library/subprocess.rst +@@ -22,8 +22,8 @@ + :pep:`324` -- PEP proposing the subprocess module + + +-Using the subprocess Module +---------------------------- ++Using the :mod:`subprocess` Module ++---------------------------------- + + The recommended approach to invoking subprocesses is to use the following + convenience functions for all use cases they can handle. For more advanced +@@ -307,10 +307,14 @@ + :meth:`Popen.communicate` method. + + If *shell* is ``True``, the specified command will be executed through +- the shell. This can be useful if you are using Python primarily for the ++ the shell. This can be useful if you are using Python primarily for the + enhanced control flow it offers over most system shells and still want +- access to other shell features such as filename wildcards, shell pipes and +- environment variable expansion. ++ convenient access to other shell features such as shell pipes, filename ++ wildcards, environment variable expansion, and expansion of ``~`` to a ++ user's home directory. However, note that Python itself offers ++ implementations of many shell-like features (in particular, :mod:`glob`, ++ :mod:`fnmatch`, :func:`os.walk`, :func:`os.path.expandvars`, ++ :func:`os.path.expanduser`, and :mod:`shutil`). + + .. versionchanged:: 3.3 + When *universal_newlines* is ``True``, the class uses the encoding +@@ -324,8 +328,8 @@ + untrusted source makes a program vulnerable to `shell injection + `_, + a serious security flaw which can result in arbitrary command execution. +- For this reason, the use of *shell=True* is **strongly discouraged** in cases +- where the command string is constructed from external input:: ++ For this reason, the use of ``shell=True`` is **strongly discouraged** ++ in cases where the command string is constructed from external input:: + + >>> from subprocess import call + >>> filename = input("What file would you like to display?\n") +@@ -337,6 +341,10 @@ + from this vulnerability; see the Note in the :class:`Popen` constructor + documentation for helpful hints in getting ``shell=False`` to work. + ++ When using ``shell=True``, :func:`shlex.quote` can be used to properly ++ escape whitespace and shell metacharacters in strings that are going to ++ be used to construct shell commands. ++ + These options, along with all of the other options, are described in more + detail in the :class:`Popen` constructor documentation. + +@@ -350,24 +358,27 @@ + functions. + + +-.. class:: Popen(args, bufsize=0, executable=None, stdin=None, stdout=None, stderr=None, preexec_fn=None, close_fds=True, shell=False, cwd=None, env=None, universal_newlines=False, startupinfo=None, creationflags=0, restore_signals=True, start_new_session=False, pass_fds=()) ++.. class:: Popen(args, bufsize=0, executable=None, stdin=None, stdout=None, \ ++ stderr=None, preexec_fn=None, close_fds=True, shell=False, \ ++ cwd=None, env=None, universal_newlines=False, \ ++ startupinfo=None, creationflags=0, restore_signals=True, \ ++ start_new_session=False, pass_fds=()) + +- Arguments are: ++ Execute a child program in a new process. On Unix, the class uses ++ :meth:`os.execvp`-like behavior to execute the child program. On Windows, ++ the class uses the Windows ``CreateProcess()`` function. The arguments to ++ :class:`Popen` are as follows. + +- *args* should be a string, or a sequence of program arguments. The program +- to execute is normally the first item in the args sequence or the string if +- a string is given, but can be explicitly set by using the *executable* +- argument. When *executable* is given, the first item in the args sequence +- is still treated by most programs as the command name, which can then be +- different from the actual executable name. On Unix, it becomes the display +- name for the executing program in utilities such as :program:`ps`. ++ *args* should be a sequence of program arguments or else a single string. ++ By default, the program to execute is the first item in *args* if *args* is ++ a sequence. If *args* is a string, the interpretation is ++ platform-dependent and described below. See the *shell* and *executable* ++ arguments for additional differences from the default behavior. Unless ++ otherwise stated, it is recommended to pass *args* as a sequence. + +- On Unix, with *shell=False* (default): In this case, the Popen class uses +- :meth:`os.execvp` like behavior to execute the child program. +- *args* should normally be a +- sequence. If a string is specified for *args*, it will be used as the name +- or path of the program to execute; this will only work if the program is +- being given no arguments. ++ On Unix, if *args* is a string, the string is interpreted as the name or ++ path of the program to execute. However, this can only be done if not ++ passing arguments to the program. + + .. note:: + +@@ -388,27 +399,37 @@ + used in the shell (such as filenames containing spaces or the *echo* command + shown above) are single list elements. + +- On Unix, with *shell=True*: If args is a string, it specifies the command +- string to execute through the shell. This means that the string must be ++ On Windows, if *args* is a sequence, it will be converted to a string in a ++ manner described in :ref:`converting-argument-sequence`. This is because ++ the underlying ``CreateProcess()`` operates on strings. ++ ++ The *shell* argument (which defaults to *False*) specifies whether to use ++ the shell as the program to execute. If *shell* is *True*, it is ++ recommended to pass *args* as a string rather than as a sequence. ++ ++ On Unix with ``shell=True``, the shell defaults to :file:`/bin/sh`. If ++ *args* is a string, the string specifies the command ++ to execute through the shell. This means that the string must be + formatted exactly as it would be when typed at the shell prompt. This + includes, for example, quoting or backslash escaping filenames with spaces in + them. If *args* is a sequence, the first item specifies the command string, and + any additional items will be treated as additional arguments to the shell +- itself. That is to say, *Popen* does the equivalent of:: ++ itself. That is to say, :class:`Popen` does the equivalent of:: + + Popen(['/bin/sh', '-c', args[0], args[1], ...]) + ++ On Windows with ``shell=True``, the :envvar:`COMSPEC` environment variable ++ specifies the default shell. The only time you need to specify ++ ``shell=True`` on Windows is when the command you wish to execute is built ++ into the shell (e.g. :command:`dir` or :command:`copy`). You do not need ++ ``shell=True`` to run a batch file or console-based executable. ++ + .. warning:: + +- Enabling this option can be a security hazard if combined with untrusted +- input. See the warning under :ref:`frequently-used-arguments` ++ Passing ``shell=True`` can be a security hazard if combined with ++ untrusted input. See the warning under :ref:`frequently-used-arguments` + for details. + +- On Windows: the :class:`Popen` class uses CreateProcess() to execute the +- child program, which operates on strings. If *args* is a sequence, it will +- be converted to a string in a manner described in +- :ref:`converting-argument-sequence`. +- + *bufsize*, if given, has the same meaning as the corresponding argument to the + built-in open() function: :const:`0` means unbuffered, :const:`1` means line + buffered, any other positive value means use a buffer of (approximately) that +@@ -421,15 +442,15 @@ + enable buffering by setting *bufsize* to either -1 or a large enough + positive value (such as 4096). + +- The *executable* argument specifies the program to execute. It is very seldom +- needed: Usually, the program to execute is defined by the *args* argument. If +- ``shell=True``, the *executable* argument specifies which shell to use. On Unix, +- the default shell is :file:`/bin/sh`. On Windows, the default shell is +- specified by the :envvar:`COMSPEC` environment variable. The only reason you +- would need to specify ``shell=True`` on Windows is where the command you +- wish to execute is actually built in to the shell, eg ``dir``, ``copy``. +- You don't need ``shell=True`` to run a batch file, nor to run a console-based +- executable. ++ The *executable* argument specifies a replacement program to execute. It ++ is very seldom needed. When ``shell=False``, *executable* replaces the ++ program to execute specified by *args*. However, the original *args* is ++ still passed to the program. Most programs treat the program specified ++ by *args* as the command name, which can then be different from the program ++ actually executed. On Unix, the *args* name ++ becomes the display name for the executable in utilities such as ++ :program:`ps`. If ``shell=True``, on Unix the *executable* argument ++ specifies a replacement shell for the default :file:`/bin/sh`. + + *stdin*, *stdout* and *stderr* specify the executed program's standard input, + standard output and standard error file handles, respectively. Valid values +@@ -480,10 +501,10 @@ + .. versionadded:: 3.2 + The *pass_fds* parameter was added. + +- If *cwd* is not ``None``, the child's current directory will be changed to *cwd* +- before it is executed. Note that this directory is not considered when +- searching the executable, so you can't specify the program's path relative to +- *cwd*. ++ If *cwd* is not ``None``, the function changes the working directory to ++ *cwd* before executing the child. In particular, the function looks for ++ *executable* (or for the first item in *args*) relative to *cwd* if the ++ executable path is a relative path. + + If *restore_signals* is True (the default) all signals that Python has set to + SIG_IGN are restored to SIG_DFL in the child process before the exec. +@@ -669,8 +690,8 @@ + + .. warning:: + +- Use :meth:`communicate` rather than :attr:`.stdin.write `, +- :attr:`.stdout.read ` or :attr:`.stderr.read ` to avoid ++ Use :meth:`~Popen.communicate` rather than :attr:`.stdin.write `, ++ :attr:`.stdout.read ` or :attr:`.stderr.read ` to avoid + deadlocks due to any of the other OS pipe buffers filling up and blocking the + child process. + +@@ -818,8 +839,8 @@ + + .. _subprocess-replacements: + +-Replacing Older Functions with the subprocess Module +----------------------------------------------------- ++Replacing Older Functions with the :mod:`subprocess` Module ++----------------------------------------------------------- + + In this section, "a becomes b" means that b can be used as a replacement for a. + +@@ -835,7 +856,7 @@ + the raised exception. + + In the following examples, we assume that the relevant functions have already +-been imported from the subprocess module. ++been imported from the :mod:`subprocess` module. + + + Replacing /bin/sh shell backquote +diff -r bd8afb90ebf2 Doc/library/sys.rst +--- a/Doc/library/sys.rst ++++ b/Doc/library/sys.rst +@@ -215,21 +215,6 @@ + a traceback object (see the Reference Manual) which encapsulates the call + stack at the point where the exception originally occurred. + +- .. warning:: +- +- Assigning the *traceback* return value to a local variable in a function +- that is handling an exception will cause a circular reference. Since most +- functions don't need access to the traceback, the best solution is to use +- something like ``exctype, value = sys.exc_info()[:2]`` to extract only the +- exception type and value. If you do need the traceback, make sure to +- delete it after use (best done with a :keyword:`try` +- ... :keyword:`finally` statement) or to call :func:`exc_info` in a +- function that does not itself handle an exception. +- +- Such cycles are normally automatically reclaimed when garbage collection +- is enabled and they become unreachable, but it remains more efficient to +- avoid creating cycles. +- + + .. data:: exec_prefix + +@@ -783,7 +768,9 @@ + current directory first. Notice that the script directory is inserted *before* + the entries inserted as a result of :envvar:`PYTHONPATH`. + +- A program is free to modify this list for its own purposes. ++ A program is free to modify this list for its own purposes. Only strings ++ and bytes should be added to :data:`sys.path`; all other data types are ++ ignored during import. + + + .. seealso:: +@@ -831,7 +818,7 @@ + For other systems, the values are: + + ================ =========================== +- System :data:`platform` value ++ System ``platform`` value + ================ =========================== + Linux ``'linux'`` + Windows ``'win32'`` +diff -r bd8afb90ebf2 Doc/library/syslog.rst +--- a/Doc/library/syslog.rst ++++ b/Doc/library/syslog.rst +@@ -17,7 +17,8 @@ + The module defines the following functions: + + +-.. function:: syslog([priority,] message) ++.. function:: syslog(message) ++ syslog(priority, message) + + Send the string *message* to the system logger. A trailing newline is added + if necessary. Each message is tagged with a priority composed of a +diff -r bd8afb90ebf2 Doc/library/tempfile.rst +--- a/Doc/library/tempfile.rst ++++ b/Doc/library/tempfile.rst +@@ -86,6 +86,9 @@ + whether :func:`rollover` has been called. This file-like object can be + used in a :keyword:`with` statement, just like a normal file. + ++ .. versionchanged:: 3.3 ++ the truncate method now accepts a ``size`` argument. ++ + + .. function:: TemporaryDirectory(suffix='', prefix='tmp', dir=None) + +diff -r bd8afb90ebf2 Doc/library/textwrap.rst +--- a/Doc/library/textwrap.rst ++++ b/Doc/library/textwrap.rst +@@ -25,6 +25,9 @@ + Optional keyword arguments correspond to the instance attributes of + :class:`TextWrapper`, documented below. *width* defaults to ``70``. + ++ See the :meth:`TextWrapper.wrap` method for additional details on how ++ :func:`wrap` behaves. ++ + + .. function:: fill(text, width=70, **kwargs) + +@@ -167,15 +170,18 @@ + + .. attribute:: drop_whitespace + +- (default: ``True``) If true, whitespace that, after wrapping, happens to +- end up at the beginning or end of a line is dropped (leading whitespace in +- the first line is always preserved, though). ++ (default: ``True``) If true, whitespace at the beginning and ending of ++ every line (after wrapping but before indenting) is dropped. ++ Whitespace at the beginning of the paragraph, however, is not dropped ++ if non-whitespace follows it. If whitespace being dropped takes up an ++ entire line, the whole line is dropped. + + + .. attribute:: initial_indent + + (default: ``''``) String that will be prepended to the first line of +- wrapped output. Counts towards the length of the first line. ++ wrapped output. Counts towards the length of the first line. The empty ++ string is not indented. + + + .. attribute:: subsequent_indent +@@ -236,8 +242,9 @@ + + Wraps the single paragraph in *text* (a string) so every line is at most + :attr:`width` characters long. All wrapping options are taken from +- instance attributes of the :class:`TextWrapper` instance. Returns a list +- of output lines, without final newlines. ++ instance attributes of the :class:`TextWrapper` instance. Returns a list ++ of output lines, without final newlines. If the wrapped output has no ++ content, the returned list is empty. + + + .. method:: fill(text) +diff -r bd8afb90ebf2 Doc/library/threading.rst +--- a/Doc/library/threading.rst ++++ b/Doc/library/threading.rst +@@ -21,7 +21,7 @@ + supported by this module. + + +-This module defines the following functions and objects: ++This module defines the following functions: + + + .. function:: active_count() +@@ -30,16 +30,6 @@ + count is equal to the length of the list returned by :func:`.enumerate`. + + +-.. function:: Condition() +- :noindex: +- +- A factory function that returns a new condition variable object. A condition +- variable allows one or more threads to wait until they are notified by another +- thread. +- +- See :ref:`condition-objects`. +- +- + .. function:: current_thread() + + Return the current :class:`Thread` object, corresponding to the caller's thread +@@ -67,88 +57,6 @@ + and threads that have not yet been started. + + +-.. function:: Event() +- :noindex: +- +- A factory function that returns a new event object. An event manages a flag +- that can be set to true with the :meth:`~Event.set` method and reset to false +- with the :meth:`clear` method. The :meth:`wait` method blocks until the flag +- is true. +- +- See :ref:`event-objects`. +- +- +-.. class:: local +- +- A class that represents thread-local data. Thread-local data are data whose +- values are thread specific. To manage thread-local data, just create an +- instance of :class:`local` (or a subclass) and store attributes on it:: +- +- mydata = threading.local() +- mydata.x = 1 +- +- The instance's values will be different for separate threads. +- +- For more details and extensive examples, see the documentation string of the +- :mod:`_threading_local` module. +- +- +-.. function:: Lock() +- +- A factory function that returns a new primitive lock object. Once a thread has +- acquired it, subsequent attempts to acquire it block, until it is released; any +- thread may release it. +- +- See :ref:`lock-objects`. +- +- +-.. function:: RLock() +- +- A factory function that returns a new reentrant lock object. A reentrant lock +- must be released by the thread that acquired it. Once a thread has acquired a +- reentrant lock, the same thread may acquire it again without blocking; the +- thread must release it once for each time it has acquired it. +- +- See :ref:`rlock-objects`. +- +- +-.. function:: Semaphore(value=1) +- :noindex: +- +- A factory function that returns a new semaphore object. A semaphore manages a +- counter representing the number of :meth:`release` calls minus the number of +- :meth:`acquire` calls, plus an initial value. The :meth:`acquire` method blocks +- if necessary until it can return without making the counter negative. If not +- given, *value* defaults to 1. +- +- See :ref:`semaphore-objects`. +- +- +-.. function:: BoundedSemaphore(value=1) +- +- A factory function that returns a new bounded semaphore object. A bounded +- semaphore checks to make sure its current value doesn't exceed its initial +- value. If it does, :exc:`ValueError` is raised. In most situations semaphores +- are used to guard resources with limited capacity. If the semaphore is released +- too many times it's a sign of a bug. If not given, *value* defaults to 1. +- +- +-.. class:: Thread +- +- A class that represents a thread of control. This class can be safely +- subclassed in a limited fashion. +- +- See :ref:`thread-objects`. +- +- +-.. class:: Timer +- :noindex: +- +- A thread that executes a function after a specified interval has passed. +- +- See :ref:`timer-objects`. +- +- + .. function:: settrace(func) + + .. index:: single: trace function +@@ -197,7 +105,8 @@ + .. versionadded:: 3.2 + + +-Detailed interfaces for the objects are documented below. ++This module defines a number of classes, which are detailed in the sections ++below. + + The design of this module is loosely based on Java's threading model. However, + where Java makes locks and condition variables basic behavior of every object, +@@ -210,17 +119,38 @@ + All of the methods described below are executed atomically. + + ++Thread-Local Data ++----------------- ++ ++Thread-local data is data whose values are thread specific. To manage ++thread-local data, just create an instance of :class:`local` (or a ++subclass) and store attributes on it:: ++ ++ mydata = threading.local() ++ mydata.x = 1 ++ ++The instance's values will be different for separate threads. ++ ++ ++.. class:: local() ++ ++ A class that represents thread-local data. ++ ++ For more details and extensive examples, see the documentation string of the ++ :mod:`_threading_local` module. ++ ++ + .. _thread-objects: + + Thread Objects + -------------- + +-This class represents an activity that is run in a separate thread of control. +-There are two ways to specify the activity: by passing a callable object to the +-constructor, or by overriding the :meth:`~Thread.run` method in a subclass. +-No other methods (except for the constructor) should be overridden in a +-subclass. In other words, *only* override the :meth:`~Thread.__init__` +-and :meth:`~Thread.run` methods of this class. ++The :class:`Thread` class represents an activity that is run in a separate ++thread of control. There are two ways to specify the activity: by passing a ++callable object to the constructor, or by overriding the :meth:`~Thread.run` ++method in a subclass. No other methods (except for the constructor) should be ++overridden in a subclass. In other words, *only* override the ++:meth:`~Thread.__init__` and :meth:`~Thread.run` methods of this class. + + Once a thread object is created, its activity must be started by calling the + thread's :meth:`~Thread.start` method. This invokes the :meth:`~Thread.run` +@@ -255,8 +185,8 @@ + since it is impossible to detect the termination of alien threads. + + +-.. class:: Thread(group=None, target=None, name=None, args=(), kwargs={}, +- verbose=None, *, daemon=None) ++.. class:: Thread(group=None, target=None, name=None, args=(), kwargs={}, *, \ ++ daemon=None) + + This constructor should always be called with keyword arguments. Arguments + are: +@@ -275,8 +205,6 @@ + *kwargs* is a dictionary of keyword arguments for the target invocation. + Defaults to ``{}``. + +- *verbose* is a flag used for debugging messages. +- + If not ``None``, *daemon* explicitly sets whether the thread is daemonic. + If ``None`` (the default), the daemonic property is inherited from the + current thread. +@@ -380,10 +308,10 @@ + + .. impl-detail:: + +- Due to the :term:`Global Interpreter Lock`, in CPython only one thread ++ In CPython, due to the :term:`Global Interpreter Lock`, only one thread + can execute Python code at once (even though certain performance-oriented + libraries might overcome this limitation). +- If you want your application to make better of use of the computational ++ If you want your application to make better use of the computational + resources of multi-core machines, you are advised to use + :mod:`multiprocessing` or :class:`concurrent.futures.ProcessPoolExecutor`. + However, threading is still an appropriate model if you want to run +@@ -421,45 +349,55 @@ + All methods are executed atomically. + + +-.. method:: Lock.acquire(blocking=True, timeout=-1) ++.. class:: Lock() + +- Acquire a lock, blocking or non-blocking. ++ The class implementing primitive lock objects. Once a thread has acquired a ++ lock, subsequent attempts to acquire it block, until it is released; any ++ thread may release it. + +- When invoked with the *blocking* argument set to ``True`` (the default), +- block until the lock is unlocked, then set it to locked and return ``True``. ++ .. versionchanged:: 3.3 ++ Changed from a factory function to a class. + +- When invoked with the *blocking* argument set to ``False``, do not block. +- If a call with *blocking* set to ``True`` would block, return ``False`` +- immediately; otherwise, set the lock to locked and return ``True``. + +- When invoked with the floating-point *timeout* argument set to a positive +- value, block for at most the number of seconds specified by *timeout* +- and as long as the lock cannot be acquired. A negative *timeout* argument +- specifies an unbounded wait. It is forbidden to specify a *timeout* +- when *blocking* is false. ++ .. method:: acquire(blocking=True, timeout=-1) + +- The return value is ``True`` if the lock is acquired successfully, +- ``False`` if not (for example if the *timeout* expired). ++ Acquire a lock, blocking or non-blocking. + +- .. versionchanged:: 3.2 +- The *timeout* parameter is new. ++ When invoked with the *blocking* argument set to ``True`` (the default), ++ block until the lock is unlocked, then set it to locked and return ``True``. + +- .. versionchanged:: 3.2 +- Lock acquires can now be interrupted by signals on POSIX. ++ When invoked with the *blocking* argument set to ``False``, do not block. ++ If a call with *blocking* set to ``True`` would block, return ``False`` ++ immediately; otherwise, set the lock to locked and return ``True``. + ++ When invoked with the floating-point *timeout* argument set to a positive ++ value, block for at most the number of seconds specified by *timeout* ++ and as long as the lock cannot be acquired. A negative *timeout* argument ++ specifies an unbounded wait. It is forbidden to specify a *timeout* ++ when *blocking* is false. + +-.. method:: Lock.release() ++ The return value is ``True`` if the lock is acquired successfully, ++ ``False`` if not (for example if the *timeout* expired). + +- Release a lock. This can be called from any thread, not only the thread +- which has acquired the lock. ++ .. versionchanged:: 3.2 ++ The *timeout* parameter is new. + +- When the lock is locked, reset it to unlocked, and return. If any other threads +- are blocked waiting for the lock to become unlocked, allow exactly one of them +- to proceed. ++ .. versionchanged:: 3.2 ++ Lock acquires can now be interrupted by signals on POSIX. + +- When invoked on an unlocked lock, a :exc:`RuntimeError` is raised. + +- There is no return value. ++ .. method:: release() ++ ++ Release a lock. This can be called from any thread, not only the thread ++ which has acquired the lock. ++ ++ When the lock is locked, reset it to unlocked, and return. If any other threads ++ are blocked waiting for the lock to become unlocked, allow exactly one of them ++ to proceed. ++ ++ When invoked on an unlocked lock, a :exc:`RuntimeError` is raised. ++ ++ There is no return value. + + + .. _rlock-objects: +@@ -483,47 +421,59 @@ + Reentrant locks also support the :ref:`context manager protocol `. + + +-.. method:: RLock.acquire(blocking=True, timeout=-1) ++.. class:: RLock() + +- Acquire a lock, blocking or non-blocking. ++ This class implements reentrant lock objects. A reentrant lock must be ++ released by the thread that acquired it. Once a thread has acquired a ++ reentrant lock, the same thread may acquire it again without blocking; the ++ thread must release it once for each time it has acquired it. + +- When invoked without arguments: if this thread already owns the lock, increment +- the recursion level by one, and return immediately. Otherwise, if another +- thread owns the lock, block until the lock is unlocked. Once the lock is +- unlocked (not owned by any thread), then grab ownership, set the recursion level +- to one, and return. If more than one thread is blocked waiting until the lock +- is unlocked, only one at a time will be able to grab ownership of the lock. +- There is no return value in this case. ++ Note that ``RLock`` is actually a factory function which returns an instance ++ of the most efficient version of the concrete RLock class that is supported ++ by the platform. + +- When invoked with the *blocking* argument set to true, do the same thing as when +- called without arguments, and return true. + +- When invoked with the *blocking* argument set to false, do not block. If a call +- without an argument would block, return false immediately; otherwise, do the +- same thing as when called without arguments, and return true. ++ .. method:: acquire(blocking=True, timeout=-1) + +- When invoked with the floating-point *timeout* argument set to a positive +- value, block for at most the number of seconds specified by *timeout* +- and as long as the lock cannot be acquired. Return true if the lock has +- been acquired, false if the timeout has elapsed. ++ Acquire a lock, blocking or non-blocking. + +- .. versionchanged:: 3.2 +- The *timeout* parameter is new. ++ When invoked without arguments: if this thread already owns the lock, increment ++ the recursion level by one, and return immediately. Otherwise, if another ++ thread owns the lock, block until the lock is unlocked. Once the lock is ++ unlocked (not owned by any thread), then grab ownership, set the recursion level ++ to one, and return. If more than one thread is blocked waiting until the lock ++ is unlocked, only one at a time will be able to grab ownership of the lock. ++ There is no return value in this case. + ++ When invoked with the *blocking* argument set to true, do the same thing as when ++ called without arguments, and return true. + +-.. method:: RLock.release() ++ When invoked with the *blocking* argument set to false, do not block. If a call ++ without an argument would block, return false immediately; otherwise, do the ++ same thing as when called without arguments, and return true. + +- Release a lock, decrementing the recursion level. If after the decrement it is +- zero, reset the lock to unlocked (not owned by any thread), and if any other +- threads are blocked waiting for the lock to become unlocked, allow exactly one +- of them to proceed. If after the decrement the recursion level is still +- nonzero, the lock remains locked and owned by the calling thread. ++ When invoked with the floating-point *timeout* argument set to a positive ++ value, block for at most the number of seconds specified by *timeout* ++ and as long as the lock cannot be acquired. Return true if the lock has ++ been acquired, false if the timeout has elapsed. + +- Only call this method when the calling thread owns the lock. A +- :exc:`RuntimeError` is raised if this method is called when the lock is +- unlocked. ++ .. versionchanged:: 3.2 ++ The *timeout* parameter is new. + +- There is no return value. ++ ++ .. method:: release() ++ ++ Release a lock, decrementing the recursion level. If after the decrement it is ++ zero, reset the lock to unlocked (not owned by any thread), and if any other ++ threads are blocked waiting for the lock to become unlocked, allow exactly one ++ of them to proceed. If after the decrement the recursion level is still ++ nonzero, the lock remains locked and owned by the calling thread. ++ ++ Only call this method when the calling thread owns the lock. A ++ :exc:`RuntimeError` is raised if this method is called when the lock is ++ unlocked. ++ ++ There is no return value. + + + .. _condition-objects: +@@ -558,10 +508,6 @@ + the thread that called :meth:`~Condition.notify` or :meth:`~Condition.notify_all` + finally relinquishes ownership of the lock. + +- +-Usage +-^^^^^ +- + The typical programming style using condition variables uses the lock to + synchronize access to some shared state; threads that are interested in a + particular change of state call :meth:`~Condition.wait` repeatedly until they +@@ -600,15 +546,18 @@ + item to the buffer only needs to wake up one consumer thread. + + +-Interface +-^^^^^^^^^ ++.. class:: Condition(lock=None) + +-.. class:: Condition(lock=None) ++ This class implements condition variable objects. A condition variable ++ allows one or more threads to wait until they are notified by another thread. + + If the *lock* argument is given and not ``None``, it must be a :class:`Lock` + or :class:`RLock` object, and it is used as the underlying lock. Otherwise, + a new :class:`RLock` object is created and used as the underlying lock. + ++ .. versionchanged:: 3.3 ++ changed from a factory function to a class. ++ + .. method:: acquire(*args) + + Acquire the underlying lock. This method calls the corresponding method on +@@ -718,10 +667,19 @@ + + .. class:: Semaphore(value=1) + ++ This class implements semaphore objects. A semaphore manages a counter ++ representing the number of :meth:`release` calls minus the number of ++ :meth:`acquire` calls, plus an initial value. The :meth:`acquire` method ++ blocks if necessary until it can return without making the counter negative. ++ If not given, *value* defaults to 1. ++ + The optional argument gives the initial *value* for the internal counter; it + defaults to ``1``. If the *value* given is less than 0, :exc:`ValueError` is + raised. + ++ .. versionchanged:: 3.3 ++ changed from a factory function to a class. ++ + .. method:: acquire(blocking=True, timeout=None) + + Acquire a semaphore. +@@ -754,6 +712,18 @@ + than zero again, wake up that thread. + + ++.. class:: BoundedSemaphore(value=1) ++ ++ Class implementing bounded semaphore objects. A bounded semaphore checks to ++ make sure its current value doesn't exceed its initial value. If it does, ++ :exc:`ValueError` is raised. In most situations semaphores are used to guard ++ resources with limited capacity. If the semaphore is released too many times ++ it's a sign of a bug. If not given, *value* defaults to 1. ++ ++ .. versionchanged:: 3.3 ++ changed from a factory function to a class. ++ ++ + .. _semaphore-examples: + + :class:`Semaphore` Example +@@ -765,7 +735,7 @@ + main thread would initialize the semaphore:: + + maxconnections = 5 +- ... ++ # ... + pool_sema = BoundedSemaphore(value=maxconnections) + + Once spawned, worker threads call the semaphore's acquire and release methods +@@ -774,7 +744,7 @@ + with pool_sema: + conn = connectdb() + try: +- ... use connection ... ++ # ... use connection ... + finally: + conn.close() + +@@ -797,7 +767,13 @@ + + .. class:: Event() + +- The internal flag is initially false. ++ Class implementing event objects. An event manages a flag that can be set to ++ true with the :meth:`~Event.set` method and reset to false with the ++ :meth:`clear` method. The :meth:`wait` method blocks until the flag is true. ++ The flag is initially false. ++ ++ .. versionchanged:: 3.3 ++ changed from a factory function to a class. + + .. method:: is_set() + +@@ -862,6 +838,9 @@ + Create a timer that will run *function* with arguments *args* and keyword + arguments *kwargs*, after *interval* seconds have passed. + ++ .. versionchanged:: 3.3 ++ changed from a factory function to a class. ++ + .. method:: cancel() + + Stop the timer, and cancel the execution of the timer's action. This will +diff -r bd8afb90ebf2 Doc/library/time.rst +--- a/Doc/library/time.rst ++++ b/Doc/library/time.rst +@@ -309,7 +309,7 @@ + + On Windows versions older than Vista, :func:`monotonic` detects + :c:func:`GetTickCount` integer overflow (32 bits, roll-over after 49.7 days). +- It increases an internal epoch (reference time by) 2\ :sup:`32` each time ++ It increases an internal epoch (reference time) by 2\ :sup:`32` each time + that an overflow is detected. The epoch is stored in the process-local state + and so the value of :func:`monotonic` may be different in two Python + processes running for more than 49 days. On more recent versions of Windows +@@ -557,7 +557,7 @@ + :exc:`TypeError` is raised. + + .. versionchanged:: 3.3 +- :attr:`tm_gmtoff` and :attr:`tm_zone` attributes are avaliable on platforms ++ :attr:`tm_gmtoff` and :attr:`tm_zone` attributes are available on platforms + with C library supporting the corresponding fields in ``struct tm``. + + .. function:: time() +diff -r bd8afb90ebf2 Doc/library/timeit.rst +--- a/Doc/library/timeit.rst ++++ b/Doc/library/timeit.rst +@@ -14,113 +14,154 @@ + -------------- + + This module provides a simple way to time small bits of Python code. It has both +-command line as well as callable interfaces. It avoids a number of common traps +-for measuring execution times. See also Tim Peters' introduction to the +-"Algorithms" chapter in the Python Cookbook, published by O'Reilly. ++a :ref:`command-line-interface` as well as a :ref:`callable ` ++one. It avoids a number of common traps for measuring execution times. ++See also Tim Peters' introduction to the "Algorithms" chapter in the *Python ++Cookbook*, published by O'Reilly. + +-The module defines the following public class: ++ ++Basic Examples ++-------------- ++ ++The following example shows how the :ref:`command-line-interface` ++can be used to compare three different expressions: ++ ++.. code-block:: sh ++ ++ $ python -m timeit '"-".join(str(n) for n in range(100))' ++ 10000 loops, best of 3: 40.3 usec per loop ++ $ python -m timeit '"-".join([str(n) for n in range(100)])' ++ 10000 loops, best of 3: 33.4 usec per loop ++ $ python -m timeit '"-".join(map(str, range(100)))' ++ 10000 loops, best of 3: 25.2 usec per loop ++ ++This can be achieved from the :ref:`python-interface` with:: ++ ++ >>> import timeit ++ >>> timeit.timeit('"-".join(str(n) for n in range(100))', number=10000) ++ 0.8187260627746582 ++ >>> timeit.timeit('"-".join([str(n) for n in range(100)])', number=10000) ++ 0.7288308143615723 ++ >>> timeit.timeit('"-".join(map(str, range(100)))', number=10000) ++ 0.5858950614929199 ++ ++Note however that :mod:`timeit` will automatically determine the number of ++repetitions only when the command-line interface is used. In the ++:ref:`timeit-examples` section you can find more advanced examples. ++ ++ ++.. _python-interface: ++ ++Python Interface ++---------------- ++ ++The module defines three convenience functions and a public class: ++ ++ ++.. function:: timeit(stmt='pass', setup='pass', timer=, number=1000000) ++ ++ Create a :class:`Timer` instance with the given statement, *setup* code and ++ *timer* function and run its :meth:`.timeit` method with *number* executions. ++ ++ ++.. function:: repeat(stmt='pass', setup='pass', timer=, repeat=3, number=1000000) ++ ++ Create a :class:`Timer` instance with the given statement, *setup* code and ++ *timer* function and run its :meth:`.repeat` method with the given *repeat* ++ count and *number* executions. ++ ++ ++.. function:: default_timer() ++ ++ The default timer, which is always :func:`time.perf_counter`. ++ ++ .. versionchanged:: 3.3 ++ :func:`time.perf_counter` is now the default timer. + + + .. class:: Timer(stmt='pass', setup='pass', timer=) + + Class for timing execution speed of small code snippets. + +- The constructor takes a statement to be timed, an additional statement used for +- setup, and a timer function. Both statements default to ``'pass'``; the timer +- function is platform-dependent (see the module doc string). *stmt* and *setup* +- may also contain multiple statements separated by ``;`` or newlines, as long as +- they don't contain multi-line string literals. ++ The constructor takes a statement to be timed, an additional statement used ++ for setup, and a timer function. Both statements default to ``'pass'``; ++ the timer function is platform-dependent (see the module doc string). ++ *stmt* and *setup* may also contain multiple statements separated by ``;`` ++ or newlines, as long as they don't contain multi-line string literals. + +- To measure the execution time of the first statement, use the :meth:`timeit` +- method. The :meth:`repeat` method is a convenience to call :meth:`timeit` ++ To measure the execution time of the first statement, use the :meth:`.timeit` ++ method. The :meth:`.repeat` method is a convenience to call :meth:`.timeit` + multiple times and return a list of results. + + The *stmt* and *setup* parameters can also take objects that are callable +- without arguments. This will embed calls to them in a timer function that +- will then be executed by :meth:`timeit`. Note that the timing overhead is a ++ without arguments. This will embed calls to them in a timer function that ++ will then be executed by :meth:`.timeit`. Note that the timing overhead is a + little larger in this case because of the extra function calls. + + +-.. method:: Timer.print_exc(file=None) ++ .. method:: Timer.timeit(number=1000000) + +- Helper to print a traceback from the timed code. ++ Time *number* executions of the main statement. This executes the setup ++ statement once, and then returns the time it takes to execute the main ++ statement a number of times, measured in seconds as a float. ++ The argument is the number of times through the loop, defaulting to one ++ million. The main statement, the setup statement and the timer function ++ to be used are passed to the constructor. + +- Typical use:: ++ .. note:: + +- t = Timer(...) # outside the try/except +- try: +- t.timeit(...) # or t.repeat(...) +- except: +- t.print_exc() ++ By default, :meth:`.timeit` temporarily turns off :term:`garbage ++ collection` during the timing. The advantage of this approach is that ++ it makes independent timings more comparable. This disadvantage is ++ that GC may be an important component of the performance of the ++ function being measured. If so, GC can be re-enabled as the first ++ statement in the *setup* string. For example:: + +- The advantage over the standard traceback is that source lines in the compiled +- template will be displayed. The optional *file* argument directs where the +- traceback is sent; it defaults to ``sys.stderr``. ++ timeit.Timer('for i in range(10): oct(i)', 'gc.enable()').timeit() + + +-.. method:: Timer.repeat(repeat=3, number=1000000) ++ .. method:: Timer.repeat(repeat=3, number=1000000) + +- Call :meth:`timeit` a few times. ++ Call :meth:`.timeit` a few times. + +- This is a convenience function that calls the :meth:`timeit` repeatedly, +- returning a list of results. The first argument specifies how many times to +- call :meth:`timeit`. The second argument specifies the *number* argument for +- :func:`timeit`. ++ This is a convenience function that calls the :meth:`.timeit` repeatedly, ++ returning a list of results. The first argument specifies how many times ++ to call :meth:`.timeit`. The second argument specifies the *number* ++ argument for :meth:`.timeit`. + +- .. note:: ++ .. note:: + +- It's tempting to calculate mean and standard deviation from the result vector +- and report these. However, this is not very useful. In a typical case, the +- lowest value gives a lower bound for how fast your machine can run the given +- code snippet; higher values in the result vector are typically not caused by +- variability in Python's speed, but by other processes interfering with your +- timing accuracy. So the :func:`min` of the result is probably the only number +- you should be interested in. After that, you should look at the entire vector +- and apply common sense rather than statistics. ++ It's tempting to calculate mean and standard deviation from the result ++ vector and report these. However, this is not very useful. ++ In a typical case, the lowest value gives a lower bound for how fast ++ your machine can run the given code snippet; higher values in the ++ result vector are typically not caused by variability in Python's ++ speed, but by other processes interfering with your timing accuracy. ++ So the :func:`min` of the result is probably the only number you ++ should be interested in. After that, you should look at the entire ++ vector and apply common sense rather than statistics. + + +-.. method:: Timer.timeit(number=1000000) ++ .. method:: Timer.print_exc(file=None) + +- Time *number* executions of the main statement. This executes the setup +- statement once, and then returns the time it takes to execute the main statement +- a number of times, measured in seconds as a float. The argument is the number +- of times through the loop, defaulting to one million. The main statement, the +- setup statement and the timer function to be used are passed to the constructor. ++ Helper to print a traceback from the timed code. + +- .. note:: ++ Typical use:: + +- By default, :meth:`timeit` temporarily turns off :term:`garbage collection` +- during the timing. The advantage of this approach is that it makes +- independent timings more comparable. This disadvantage is that GC may be +- an important component of the performance of the function being measured. +- If so, GC can be re-enabled as the first statement in the *setup* string. +- For example:: ++ t = Timer(...) # outside the try/except ++ try: ++ t.timeit(...) # or t.repeat(...) ++ except: ++ t.print_exc() + +- timeit.Timer('for i in range(10): oct(i)', 'gc.enable()').timeit() ++ The advantage over the standard traceback is that source lines in the ++ compiled template will be displayed. The optional *file* argument directs ++ where the traceback is sent; it defaults to :data:`sys.stderr`. + + +-The module also defines three convenience functions: ++.. _command-line-interface: + +- +-.. function:: default_timer() +- +- The default timer, which is always :func:`time.perf_counter`. +- +- +-.. function:: repeat(stmt='pass', setup='pass', timer=, repeat=3, number=1000000) +- +- Create a :class:`Timer` instance with the given statement, setup code and timer +- function and run its :meth:`repeat` method with the given repeat count and +- *number* executions. +- +- +-.. function:: timeit(stmt='pass', setup='pass', timer=, number=1000000) +- +- Create a :class:`Timer` instance with the given statement, setup code and timer +- function and run its :meth:`timeit` method with *number* executions. +- +- +-Command Line Interface ++Command-Line Interface + ---------------------- + + When called as a program from the command line, the following form is used:: +@@ -184,25 +225,53 @@ + + There is a certain baseline overhead associated with executing a pass statement. + The code here doesn't try to hide it, but you should be aware of it. The +- baseline overhead can be measured by invoking the program without arguments. ++ baseline overhead can be measured by invoking the program without arguments, ++ and it might differ between Python versions. + +-The baseline overhead differs between Python versions! Also, to fairly compare +-older Python versions to Python 2.3, you may want to use Python's :option:`-O` +-option for the older versions to avoid timing ``SET_LINENO`` instructions. + ++.. _timeit-examples: + + Examples + -------- + +-Here are two example sessions (one using the command line, one using the module +-interface) that compare the cost of using :func:`hasattr` vs. +-:keyword:`try`/:keyword:`except` to test for missing and present object +-attributes. :: ++It is possible to provide a setup statement that is executed only once at the beginning: ++ ++.. code-block:: sh ++ ++ $ python -m timeit -s 'text = "sample string"; char = "g"' 'char in text' ++ 10000000 loops, best of 3: 0.0877 usec per loop ++ $ python -m timeit -s 'text = "sample string"; char = "g"' 'text.find(char)' ++ 1000000 loops, best of 3: 0.342 usec per loop ++ ++:: ++ ++ >>> import timeit ++ >>> timeit.timeit('char in text', setup='text = "sample string"; char = "g"') ++ 0.41440500499993504 ++ >>> timeit.timeit('text.find(char)', setup='text = "sample string"; char = "g"') ++ 1.7246671520006203 ++ ++The same can be done using the :class:`Timer` class and its methods:: ++ ++ >>> import timeit ++ >>> t = timeit.Timer('char in text', setup='text = "sample string"; char = "g"') ++ >>> t.timeit() ++ 0.3955516149999312 ++ >>> t.repeat() ++ [0.40193588800002544, 0.3960157959998014, 0.39594301399984033] ++ ++ ++The following examples show how to time expressions that contain multiple lines. ++Here we compare the cost of using :func:`hasattr` vs. :keyword:`try`/:keyword:`except` ++to test for missing and present object attributes: ++ ++.. code-block:: sh + + $ python -m timeit 'try:' ' str.__bool__' 'except AttributeError:' ' pass' + 100000 loops, best of 3: 15.7 usec per loop + $ python -m timeit 'if hasattr(str, "__bool__"): pass' + 100000 loops, best of 3: 4.26 usec per loop ++ + $ python -m timeit 'try:' ' int.__bool__' 'except AttributeError:' ' pass' + 1000000 loops, best of 3: 1.43 usec per loop + $ python -m timeit 'if hasattr(int, "__bool__"): pass' +@@ -211,46 +280,40 @@ + :: + + >>> import timeit ++ >>> # attribute is missing + >>> s = """\ + ... try: + ... str.__bool__ + ... except AttributeError: + ... pass + ... """ +- >>> t = timeit.Timer(stmt=s) +- >>> print("%.2f usec/pass" % (1000000 * t.timeit(number=100000)/100000)) +- 17.09 usec/pass +- >>> s = """\ +- ... if hasattr(str, '__bool__'): pass +- ... """ +- >>> t = timeit.Timer(stmt=s) +- >>> print("%.2f usec/pass" % (1000000 * t.timeit(number=100000)/100000)) +- 4.85 usec/pass ++ >>> timeit.timeit(stmt=s, number=100000) ++ 0.9138244460009446 ++ >>> s = "if hasattr(str, '__bool__'): pass" ++ >>> timeit.timeit(stmt=s, number=100000) ++ 0.5829014980008651 ++ >>> ++ >>> # attribute is present + >>> s = """\ + ... try: + ... int.__bool__ + ... except AttributeError: + ... pass + ... """ +- >>> t = timeit.Timer(stmt=s) +- >>> print("%.2f usec/pass" % (1000000 * t.timeit(number=100000)/100000)) +- 1.97 usec/pass +- >>> s = """\ +- ... if hasattr(int, '__bool__'): pass +- ... """ +- >>> t = timeit.Timer(stmt=s) +- >>> print("%.2f usec/pass" % (1000000 * t.timeit(number=100000)/100000)) +- 3.15 usec/pass ++ >>> timeit.timeit(stmt=s, number=100000) ++ 0.04215312199994514 ++ >>> s = "if hasattr(int, '__bool__'): pass" ++ >>> timeit.timeit(stmt=s, number=100000) ++ 0.08588060699912603 ++ + + To give the :mod:`timeit` module access to functions you define, you can pass a +-``setup`` parameter which contains an import statement:: ++*setup* parameter which contains an import statement:: + + def test(): + """Stupid test function""" + L = [i for i in range(100)] + + if __name__ == '__main__': +- from timeit import Timer +- t = Timer("test()", "from __main__ import test") +- print(t.timeit()) +- ++ import timeit ++ print(timeit.timeit("test()", setup="from __main__ import test")) +diff -r bd8afb90ebf2 Doc/library/tkinter.tix.rst +--- a/Doc/library/tkinter.tix.rst ++++ b/Doc/library/tkinter.tix.rst +@@ -504,7 +504,7 @@ + print(root.tix_configure()) + + +-.. method:: tixCommand.tix_configure([cnf,] **kw) ++.. method:: tixCommand.tix_configure(cnf=None, **kw) + + Query or modify the configuration options of the Tix application context. If no + option is specified, returns a dictionary all of the available options. If +diff -r bd8afb90ebf2 Doc/library/types.rst +--- a/Doc/library/types.rst ++++ b/Doc/library/types.rst +@@ -69,7 +69,7 @@ + the types that arise only incidentally during processing such as the + ``listiterator`` type. + +-Typical use is of these names is for :func:`isinstance` or ++Typical use of these names is for :func:`isinstance` or + :func:`issubclass` checks. + + Standard names are defined for the following types: +diff -r bd8afb90ebf2 Doc/library/unicodedata.rst +--- a/Doc/library/unicodedata.rst ++++ b/Doc/library/unicodedata.rst +@@ -69,7 +69,7 @@ + + .. function:: bidirectional(chr) + +- Returns the bidirectional category assigned to the character *chr* as ++ Returns the bidirectional class assigned to the character *chr* as + string. If no such value is defined, an empty string is returned. + + +diff -r bd8afb90ebf2 Doc/library/unittest.mock-examples.rst +--- a/Doc/library/unittest.mock-examples.rst ++++ b/Doc/library/unittest.mock-examples.rst +@@ -372,8 +372,8 @@ + ... @patch('package.module.ClassName1') + ... @patch('package.module.ClassName2') + ... def test_something(self, MockClass2, MockClass1): +- ... self.assertTrue(package.module.ClassName1 is MockClass1) +- ... self.assertTrue(package.module.ClassName2 is MockClass2) ++ ... self.assertIs(package.module.ClassName1, MockClass1) ++ ... self.assertIs(package.module.ClassName2, MockClass2) + ... + >>> MyTest('test_something').test_something() + +@@ -595,10 +595,10 @@ + ... class MyTest(TestCase): + ... + ... def test_one(self, MockSomeClass): +- ... self.assertTrue(mymodule.SomeClass is MockSomeClass) ++ ... self.assertIs(mymodule.SomeClass, MockSomeClass) + ... + ... def test_two(self, MockSomeClass): +- ... self.assertTrue(mymodule.SomeClass is MockSomeClass) ++ ... self.assertIs(mymodule.SomeClass, MockSomeClass) + ... + ... def not_a_test(self): + ... return 'something' +@@ -617,7 +617,7 @@ + ... self.mock_foo = self.patcher.start() + ... + ... def test_foo(self): +- ... self.assertTrue(mymodule.foo is self.mock_foo) ++ ... self.assertIs(mymodule.foo, self.mock_foo) + ... + ... def tearDown(self): + ... self.patcher.stop() +@@ -636,7 +636,7 @@ + ... self.mock_foo = patcher.start() + ... + ... def test_foo(self): +- ... self.assertTrue(mymodule.foo is self.mock_foo) ++ ... self.assertIs(mymodule.foo, self.mock_foo) + ... + >>> MyTest('test_foo').run() + +diff -r bd8afb90ebf2 Doc/library/unittest.mock.rst +--- a/Doc/library/unittest.mock.rst ++++ b/Doc/library/unittest.mock.rst +@@ -1,3 +1,4 @@ ++ + :mod:`unittest.mock` --- mock object library + ============================================ + +@@ -276,7 +277,7 @@ + >>> mock.assert_called_once_with('foo', bar='baz') + Traceback (most recent call last): + ... +- AssertionError: Expected to be called once. Called 2 times. ++ AssertionError: Expected 'mock' to be called once. Called 2 times. + + + .. method:: assert_any_call(*args, **kwargs) +@@ -646,7 +647,7 @@ + which have no meaning on a non-callable mock. + + Mock objects that use a class or an instance as a `spec` or `spec_set` are able +-to pass `isintance` tests: ++to pass `isinstance` tests: + + >>> mock = Mock(spec=SomeClass) + >>> isinstance(mock, SomeClass) +@@ -2020,7 +2021,7 @@ + >>> mock.assert_called_once_with(1, 2, 3) + Traceback (most recent call last): + ... +- AssertionError: Expected to be called once. Called 2 times. ++ AssertionError: Expected 'mock' to be called once. Called 2 times. + + Because mocks auto-create attributes on demand, and allow you to call them + with arbitrary arguments, if you misspell one of these assert methods then +diff -r bd8afb90ebf2 Doc/library/unittest.rst +--- a/Doc/library/unittest.rst ++++ b/Doc/library/unittest.rst +@@ -11,17 +11,14 @@ + (If you are already familiar with the basic concepts of testing, you might want + to skip to :ref:`the list of assert methods `.) + +-The Python unit testing framework, sometimes referred to as "PyUnit," is a +-Python language version of JUnit, by Kent Beck and Erich Gamma. JUnit is, in +-turn, a Java version of Kent's Smalltalk testing framework. Each is the de +-facto standard unit testing framework for its respective language. +- +-:mod:`unittest` supports test automation, sharing of setup and shutdown code for +-tests, aggregation of tests into collections, and independence of the tests from +-the reporting framework. The :mod:`unittest` module provides classes that make +-it easy to support these qualities for a set of tests. +- +-To achieve this, :mod:`unittest` supports some important concepts: ++The :mod:`unittest` unit testing framework was originally inspired by JUnit ++and has a similar flavor as major unit testing frameworks in other ++languages. It supports test automation, sharing of setup and shutdown code ++for tests, aggregation of tests into collections, and independence of the ++tests from the reporting framework. ++ ++To achieve this, :mod:`unittest` supports some important concepts in an ++object-oriented way: + + test fixture + A :dfn:`test fixture` represents the preparation needed to perform one or more +@@ -30,7 +27,7 @@ + process. + + test case +- A :dfn:`test case` is the smallest unit of testing. It checks for a specific ++ A :dfn:`test case` is the individual unit of testing. It checks for a specific + response to a particular set of inputs. :mod:`unittest` provides a base class, + :class:`TestCase`, which may be used to create new test cases. + +@@ -44,43 +41,12 @@ + a textual interface, or return a special value to indicate the results of + executing the tests. + +-The test case and test fixture concepts are supported through the +-:class:`TestCase` and :class:`FunctionTestCase` classes; the former should be +-used when creating new tests, and the latter can be used when integrating +-existing test code with a :mod:`unittest`\ -driven framework. When building test +-fixtures using :class:`TestCase`, the :meth:`~TestCase.setUp` and +-:meth:`~TestCase.tearDown` methods can be overridden to provide initialization +-and cleanup for the fixture. With :class:`FunctionTestCase`, existing functions +-can be passed to the constructor for these purposes. When the test is run, the +-fixture initialization is run first; if it succeeds, the cleanup method is run +-after the test has been executed, regardless of the outcome of the test. Each +-instance of the :class:`TestCase` will only be used to run a single test method, +-so a new fixture is created for each test. +- +-Test suites are implemented by the :class:`TestSuite` class. This class allows +-individual tests and test suites to be aggregated; when the suite is executed, +-all tests added directly to the suite and in "child" test suites are run. +- +-A test runner is an object that provides a single method, +-:meth:`~TestRunner.run`, which accepts a :class:`TestCase` or :class:`TestSuite` +-object as a parameter, and returns a result object. The class +-:class:`TestResult` is provided for use as the result object. :mod:`unittest` +-provides the :class:`TextTestRunner` as an example test runner which reports +-test results on the standard error stream by default. Alternate runners can be +-implemented for other environments (such as graphical environments) without any +-need to derive from a specific class. +- + + .. seealso:: + + Module :mod:`doctest` + Another test-support module with a very different flavor. + +- `unittest2: A backport of new unittest features for Python 2.4-2.6 `_ +- Many new features were added to unittest in Python 2.7, including test +- discovery. unittest2 allows you to use these features with earlier +- versions of Python. +- + `Simple Smalltalk Testing: With Patterns `_ + Kent Beck's original paper on testing frameworks using the pattern shared + by :mod:`unittest`. +@@ -89,7 +55,7 @@ + Third-party unittest frameworks with a lighter-weight syntax for writing + tests. For example, ``assert func(10) == 42``. + +- `The Python Testing Tools Taxonomy `_ ++ `The Python Testing Tools Taxonomy `_ + An extensive list of Python testing tools including functional testing + frameworks and mock object libraries. + +@@ -99,9 +65,10 @@ + + The script :file:`Tools/unittestgui/unittestgui.py` in the Python source distribution is + a GUI tool for test discovery and execution. This is intended largely for ease of use +- for those new to unit testing. For production environments it is recommended that +- tests be driven by a continuous integration system such as `Hudson `_ +- or `Buildbot `_. ++ for those new to unit testing. For production environments it is ++ recommended that tests be driven by a continuous integration system such as ++ `Buildbot `_, `Jenkins `_ ++ or `Hudson `_. + + + .. _unittest-minimal-example: +@@ -172,15 +139,8 @@ + + OK + +-Instead of :func:`unittest.main`, there are other ways to run the tests with a +-finer level of control, less terse output, and no requirement to be run from the +-command line. For example, the last two lines may be replaced with:: +- +- suite = unittest.TestLoader().loadTestsFromTestCase(TestSequenceFunctions) +- unittest.TextTestRunner(verbosity=2).run(suite) +- +-Running the revised script from the interpreter or another script produces the +-following output:: ++Passing the ``-v`` option to your test script will instruct :func:`unittest.main` ++to enable a higher level of verbosity, and produce the following output:: + + test_choice (__main__.TestSequenceFunctions) ... ok + test_sample (__main__.TestSequenceFunctions) ... ok +@@ -358,45 +318,30 @@ + To make your own test cases you must write subclasses of + :class:`TestCase` or use :class:`FunctionTestCase`. + +-An instance of a :class:`TestCase`\ -derived class is an object that can +-completely run a single test method, together with optional set-up and tidy-up +-code. +- + The testing code of a :class:`TestCase` instance should be entirely self + contained, such that it can be run either in isolation or in arbitrary + combination with any number of other test cases. + +-The simplest :class:`TestCase` subclass will simply override the +-:meth:`~TestCase.runTest` method in order to perform specific testing code:: ++The simplest :class:`TestCase` subclass will simply implement a test method ++(i.e. a method whose name starts with ``test``) in order to perform specific ++testing code:: + + import unittest + + class DefaultWidgetSizeTestCase(unittest.TestCase): +- def runTest(self): ++ def test_default_widget_size(self): + widget = Widget('The widget') +- self.assertEqual(widget.size(), (50, 50), 'incorrect default size') ++ self.assertEqual(widget.size(), (50, 50)) + + Note that in order to test something, we use one of the :meth:`assert\*` + methods provided by the :class:`TestCase` base class. If the test fails, an + exception will be raised, and :mod:`unittest` will identify the test case as a +-:dfn:`failure`. Any other exceptions will be treated as :dfn:`errors`. This +-helps you identify where the problem is: :dfn:`failures` are caused by incorrect +-results - a 5 where you expected a 6. :dfn:`Errors` are caused by incorrect +-code - e.g., a :exc:`TypeError` caused by an incorrect function call. +- +-The way to run a test case will be described later. For now, note that to +-construct an instance of such a test case, we call its constructor without +-arguments:: +- +- testCase = DefaultWidgetSizeTestCase() +- +-Now, such test cases can be numerous, and their set-up can be repetitive. In +-the above case, constructing a :class:`Widget` in each of 100 Widget test case +-subclasses would mean unsightly duplication. +- +-Luckily, we can factor out such set-up code by implementing a method called +-:meth:`~TestCase.setUp`, which the testing framework will automatically call for +-us when we run the test:: ++:dfn:`failure`. Any other exceptions will be treated as :dfn:`errors`. ++ ++Tests can be numerous, and their set-up can be repetitive. Luckily, we ++can factor out set-up code by implementing a method called ++:meth:`~TestCase.setUp`, which the testing framework will automatically ++call for every single test we run:: + + import unittest + +@@ -404,23 +349,26 @@ + def setUp(self): + self.widget = Widget('The widget') + +- class DefaultWidgetSizeTestCase(SimpleWidgetTestCase): +- def runTest(self): ++ def test_default_widget_size(self): + self.assertEqual(self.widget.size(), (50,50), + 'incorrect default size') + +- class WidgetResizeTestCase(SimpleWidgetTestCase): +- def runTest(self): ++ def test_widget_resize(self): + self.widget.resize(100,150) + self.assertEqual(self.widget.size(), (100,150), + 'wrong size after resize') + ++.. note:: ++ The order in which the various tests will be run is determined ++ by sorting the test method names with respect to the built-in ++ ordering for strings. ++ + If the :meth:`~TestCase.setUp` method raises an exception while the test is +-running, the framework will consider the test to have suffered an error, and the +-:meth:`~TestCase.runTest` method will not be executed. ++running, the framework will consider the test to have suffered an error, and ++the test method will not be executed. + + Similarly, we can provide a :meth:`~TestCase.tearDown` method that tidies up +-after the :meth:`~TestCase.runTest` method has been run:: ++after the test method has been run:: + + import unittest + +@@ -430,59 +378,20 @@ + + def tearDown(self): + self.widget.dispose() +- self.widget = None +- +-If :meth:`~TestCase.setUp` succeeded, the :meth:`~TestCase.tearDown` method will +-be run whether :meth:`~TestCase.runTest` succeeded or not. ++ ++If :meth:`~TestCase.setUp` succeeded, :meth:`~TestCase.tearDown` will be ++run whether the test method succeeded or not. + + Such a working environment for the testing code is called a :dfn:`fixture`. + +-Often, many small test cases will use the same fixture. In this case, we would +-end up subclassing :class:`SimpleWidgetTestCase` into many small one-method +-classes such as :class:`DefaultWidgetSizeTestCase`. This is time-consuming and +-discouraging, so in the same vein as JUnit, :mod:`unittest` provides a simpler +-mechanism:: +- +- import unittest +- +- class WidgetTestCase(unittest.TestCase): +- def setUp(self): +- self.widget = Widget('The widget') +- +- def tearDown(self): +- self.widget.dispose() +- self.widget = None +- +- def test_default_size(self): +- self.assertEqual(self.widget.size(), (50,50), +- 'incorrect default size') +- +- def test_resize(self): +- self.widget.resize(100,150) +- self.assertEqual(self.widget.size(), (100,150), +- 'wrong size after resize') +- +-Here we have not provided a :meth:`~TestCase.runTest` method, but have instead +-provided two different test methods. Class instances will now each run one of +-the :meth:`test_\*` methods, with ``self.widget`` created and destroyed +-separately for each instance. When creating an instance we must specify the +-test method it is to run. We do this by passing the method name in the +-constructor:: +- +- defaultSizeTestCase = WidgetTestCase('test_default_size') +- resizeTestCase = WidgetTestCase('test_resize') +- + Test case instances are grouped together according to the features they test. + :mod:`unittest` provides a mechanism for this: the :dfn:`test suite`, +-represented by :mod:`unittest`'s :class:`TestSuite` class:: +- +- widgetTestSuite = unittest.TestSuite() +- widgetTestSuite.addTest(WidgetTestCase('test_default_size')) +- widgetTestSuite.addTest(WidgetTestCase('test_resize')) +- +-For the ease of running tests, as we will see later, it is a good idea to +-provide in each test module a callable object that returns a pre-built test +-suite:: ++represented by :mod:`unittest`'s :class:`TestSuite` class. In most cases, ++calling :func:`unittest.main` will do the right thing and collect all the ++module's test cases for you, and then execute them. ++ ++However, should you want to customize the building of your test suite, ++you can do it yourself:: + + def suite(): + suite = unittest.TestSuite() +@@ -490,37 +399,6 @@ + suite.addTest(WidgetTestCase('test_resize')) + return suite + +-or even:: +- +- def suite(): +- tests = ['test_default_size', 'test_resize'] +- +- return unittest.TestSuite(map(WidgetTestCase, tests)) +- +-Since it is a common pattern to create a :class:`TestCase` subclass with many +-similarly named test functions, :mod:`unittest` provides a :class:`TestLoader` +-class that can be used to automate the process of creating a test suite and +-populating it with individual tests. For example, :: +- +- suite = unittest.TestLoader().loadTestsFromTestCase(WidgetTestCase) +- +-will create a test suite that will run ``WidgetTestCase.test_default_size()`` and +-``WidgetTestCase.test_resize``. :class:`TestLoader` uses the ``'test'`` method +-name prefix to identify test methods automatically. +- +-Note that the order in which the various test cases will be run is +-determined by sorting the test function names with respect to the +-built-in ordering for strings. +- +-Often it is desirable to group suites of test cases together, so as to run tests +-for the whole system at once. This is easy, since :class:`TestSuite` instances +-can be added to a :class:`TestSuite` just as :class:`TestCase` instances can be +-added to a :class:`TestSuite`:: +- +- suite1 = module1.TheTestSuite() +- suite2 = module2.TheTestSuite() +- alltests = unittest.TestSuite([suite1, suite2]) +- + You can place the definitions of test cases and test suites in the same modules + as the code they are to test (such as :file:`widget.py`), but there are several + advantages to placing the test code in a separate module, such as +@@ -563,23 +441,13 @@ + assert something.name is not None + # ... + +-one can create an equivalent test case instance as follows:: +- +- testcase = unittest.FunctionTestCase(testSomething) +- +-If there are additional set-up and tear-down methods that should be called as +-part of the test case's operation, they can also be provided like so:: ++one can create an equivalent test case instance as follows, with optional ++set-up and tear-down methods:: + + testcase = unittest.FunctionTestCase(testSomething, + setUp=makeSomethingDB, + tearDown=deleteSomethingDB) + +-To make migrating existing test suites easier, :mod:`unittest` supports tests +-raising :exc:`AssertionError` to indicate test failure. However, it is +-recommended that you use the explicit :meth:`TestCase.fail\*` and +-:meth:`TestCase.assert\*` methods instead, as future versions of :mod:`unittest` +-may treat :exc:`AssertionError` differently. +- + .. note:: + + Even though :class:`FunctionTestCase` can be used to quickly convert an +@@ -703,32 +571,24 @@ + + .. class:: TestCase(methodName='runTest') + +- Instances of the :class:`TestCase` class represent the smallest testable units ++ Instances of the :class:`TestCase` class represent the logical test units + in the :mod:`unittest` universe. This class is intended to be used as a base + class, with specific tests being implemented by concrete subclasses. This class + implements the interface needed by the test runner to allow it to drive the +- test, and methods that the test code can use to check for and report various ++ tests, and methods that the test code can use to check for and report various + kinds of failure. + +- Each instance of :class:`TestCase` will run a single test method: the method +- named *methodName*. If you remember, we had an earlier example that went +- something like this:: +- +- def suite(): +- suite = unittest.TestSuite() +- suite.addTest(WidgetTestCase('test_default_size')) +- suite.addTest(WidgetTestCase('test_resize')) +- return suite +- +- Here, we create two instances of :class:`WidgetTestCase`, each of which runs a +- single test. ++ Each instance of :class:`TestCase` will run a single base method: the method ++ named *methodName*. However, the standard implementation of the default ++ *methodName*, ``runTest()``, will run every method starting with ``test`` ++ as an individual test, and count successes and failures accordingly. ++ Therefore, in most uses of :class:`TestCase`, you will neither change ++ the *methodName* nor reimplement the default ``runTest()`` method. + + .. versionchanged:: 3.2 +- :class:`TestCase` can be instantiated successfully without providing a method +- name. This makes it easier to experiment with :class:`TestCase` from the +- interactive interpreter. +- +- *methodName* defaults to :meth:`runTest`. ++ :class:`TestCase` can be instantiated successfully without providing a ++ *methodName*. This makes it easier to experiment with :class:`TestCase` ++ from the interactive interpreter. + + :class:`TestCase` instances provide three groups of methods: one group used + to run the test, another used by the test implementation to check conditions +@@ -737,7 +597,6 @@ + + Methods in the first group (running the test) are: + +- + .. method:: setUp() + + Method called to prepare the test fixture. This is called immediately +@@ -789,10 +648,11 @@ + + .. method:: run(result=None) + +- Run the test, collecting the result into the test result object passed as +- *result*. If *result* is omitted or ``None``, a temporary result +- object is created (by calling the :meth:`defaultTestResult` method) and +- used. The result object is returned to :meth:`run`'s caller. ++ Run the test, collecting the result into the :class:`TestResult` object ++ passed as *result*. If *result* is omitted or ``None``, a temporary ++ result object is created (by calling the :meth:`defaultTestResult` ++ method) and used. The result object is returned to :meth:`run`'s ++ caller. + + The same effect may be had by simply calling the :class:`TestCase` + instance. +@@ -1265,7 +1125,7 @@ + .. method:: assertListEqual(first, second, msg=None) + assertTupleEqual(first, second, msg=None) + +- Tests that two lists or tuples are equal. If not an error message is ++ Tests that two lists or tuples are equal. If not, an error message is + constructed that shows only the differences between the two. An error + is also raised if either of the parameters are of the wrong type. + These methods are used by default when comparing lists or tuples with +diff -r bd8afb90ebf2 Doc/library/urllib.error.rst +--- a/Doc/library/urllib.error.rst ++++ b/Doc/library/urllib.error.rst +@@ -41,6 +41,10 @@ + to a value found in the dictionary of codes as found in + :attr:`http.server.BaseHTTPRequestHandler.responses`. + ++ .. attribute:: reason ++ ++ This is usually a string explaining the reason for this error. ++ + .. exception:: ContentTooShortError(msg, content) + + This exception is raised when the :func:`urlretrieve` function detects that +diff -r bd8afb90ebf2 Doc/library/urllib.parse.rst +--- a/Doc/library/urllib.parse.rst ++++ b/Doc/library/urllib.parse.rst +@@ -145,8 +145,9 @@ + percent-encoded sequences into Unicode characters, as accepted by the + :meth:`bytes.decode` method. + +- Use the :func:`urllib.parse.urlencode` function to convert such +- dictionaries into query strings. ++ Use the :func:`urllib.parse.urlencode` function (with the ``doseq`` ++ parameter set to ``True``) to convert such dictionaries into query ++ strings. + + + .. versionchanged:: 3.2 +diff -r bd8afb90ebf2 Doc/library/urllib.request.rst +--- a/Doc/library/urllib.request.rst ++++ b/Doc/library/urllib.request.rst +@@ -1305,7 +1305,8 @@ + *filename* is not given, the filename is the output of :func:`tempfile.mktemp` + with a suffix that matches the suffix of the last path component of the input + URL. If *reporthook* is given, it must be a function accepting three numeric +- parameters. It will be called after each chunk of data is read from the ++ parameters: A chunk number, the maximum size chunks are read in and the total size of the download ++ (-1 if unknown). It will be called once at the start and after each chunk of data is read from the + network. *reporthook* is ignored for local URLs. + + If the *url* uses the :file:`http:` scheme identifier, the optional *data* +diff -r bd8afb90ebf2 Doc/library/urllib.rst +--- /dev/null ++++ b/Doc/library/urllib.rst +@@ -0,0 +1,9 @@ ++:mod:`urllib` --- URL handling modules ++====================================== ++ ++``urllib`` is a package that collects several modules for working with URLs: ++ ++* :mod:`urllib.request` for opening and reading URLs ++* :mod:`urllib.error` containing the exceptions raised by :mod:`urllib.request` ++* :mod:`urllib.parse` for parsing URLs ++* :mod:`urllib.robotparser` for parsing ``robots.txt`` files +diff -r bd8afb90ebf2 Doc/library/winreg.rst +--- a/Doc/library/winreg.rst ++++ b/Doc/library/winreg.rst +@@ -12,6 +12,17 @@ + to ensure that the handles are closed correctly, even if the programmer neglects + to explicitly close them. + ++.. _exception-changed: ++ ++.. versionchanged:: 3.3 ++ Several functions in this module used to raise a ++ :exc:`WindowsError`, which is now an alias of :exc:`OSError`. ++ ++.. _functions: ++ ++Functions ++------------------ ++ + This module offers the following functions: + + +@@ -37,12 +48,11 @@ + + *key* is the predefined handle to connect to. + +- The return value is the handle of the opened key. If the function fails, a ++ The return value is the handle of the opened key. If the function fails, an + :exc:`OSError` exception is raised. + + .. versionchanged:: 3.3 +- This function used to raise a :exc:`WindowsError`, which is now an +- alias of :exc:`OSError`. ++ See :ref:`above `. + + + .. function:: CreateKey(key, sub_key) +@@ -60,15 +70,14 @@ + + If the key already exists, this function opens the existing key. + +- The return value is the handle of the opened key. If the function fails, a ++ The return value is the handle of the opened key. If the function fails, an + :exc:`OSError` exception is raised. + + .. versionchanged:: 3.3 +- This function used to raise a :exc:`WindowsError`, which is now an +- alias of :exc:`OSError`. ++ See :ref:`above `. + + +-.. function:: CreateKeyEx(key, sub_key, reserved=0, access=KEY_ALL_ACCESS) ++.. function:: CreateKeyEx(key, sub_key, reserved=0, access=KEY_WRITE) + + Creates or opens the specified key, returning a + :ref:`handle object `. +@@ -78,10 +87,10 @@ + + *sub_key* is a string that names the key this method opens or creates. + +- *res* is a reserved integer, and must be zero. The default is zero. ++ *reserved* is a reserved integer, and must be zero. The default is zero. + +- *sam* is an integer that specifies an access mask that describes the desired +- security access for the key. Default is :const:`KEY_ALL_ACCESS`. See ++ *access* is an integer that specifies an access mask that describes the desired ++ security access for the key. Default is :const:`KEY_WRITE`. See + :ref:`Access Rights ` for other allowed values. + + If *key* is one of the predefined keys, *sub_key* may be ``None``. In that +@@ -89,14 +98,13 @@ + + If the key already exists, this function opens the existing key. + +- The return value is the handle of the opened key. If the function fails, a ++ The return value is the handle of the opened key. If the function fails, an + :exc:`OSError` exception is raised. + + .. versionadded:: 3.2 + + .. versionchanged:: 3.3 +- This function used to raise a :exc:`WindowsError`, which is now an +- alias of :exc:`OSError`. ++ See :ref:`above `. + + + .. function:: DeleteKey(key, sub_key) +@@ -112,14 +120,13 @@ + *This method can not delete keys with subkeys.* + + If the method succeeds, the entire key, including all of its values, is removed. +- If the method fails, a :exc:`OSError` exception is raised. ++ If the method fails, an :exc:`OSError` exception is raised. + + .. versionchanged:: 3.3 +- This function used to raise a :exc:`WindowsError`, which is now an +- alias of :exc:`OSError`. ++ See :ref:`above `. + + +-.. function:: DeleteKeyEx(key, sub_key, access=KEY_ALL_ACCESS, reserved=0) ++.. function:: DeleteKeyEx(key, sub_key, access=KEY_WOW64_64KEY, reserved=0) + + Deletes the specified key. + +@@ -136,24 +143,23 @@ + *key* parameter. This value must not be ``None``, and the key may not have + subkeys. + +- *res* is a reserved integer, and must be zero. The default is zero. ++ *reserved* is a reserved integer, and must be zero. The default is zero. + +- *sam* is an integer that specifies an access mask that describes the desired ++ *access* is an integer that specifies an access mask that describes the desired + security access for the key. Default is :const:`KEY_ALL_ACCESS`. See + :ref:`Access Rights ` for other allowed values. + + *This method can not delete keys with subkeys.* + + If the method succeeds, the entire key, including all of its values, is +- removed. If the method fails, a :exc:`OSError` exception is raised. ++ removed. If the method fails, an :exc:`OSError` exception is raised. + + On unsupported Windows versions, :exc:`NotImplementedError` is raised. + + .. versionadded:: 3.2 + + .. versionchanged:: 3.3 +- This function used to raise a :exc:`WindowsError`, which is now an +- alias of :exc:`OSError`. ++ See :ref:`above `. + + + .. function:: DeleteValue(key, value) +@@ -176,12 +182,11 @@ + *index* is an integer that identifies the index of the key to retrieve. + + The function retrieves the name of one subkey each time it is called. It is +- typically called repeatedly until a :exc:`OSError` exception is ++ typically called repeatedly until an :exc:`OSError` exception is + raised, indicating, no more values are available. + + .. versionchanged:: 3.3 +- This function used to raise a :exc:`WindowsError`, which is now an +- alias of :exc:`OSError`. ++ See :ref:`above `. + + + .. function:: EnumValue(key, index) +@@ -194,7 +199,7 @@ + *index* is an integer that identifies the index of the value to retrieve. + + The function retrieves the name of one subkey each time it is called. It is +- typically called repeatedly, until a :exc:`OSError` exception is ++ typically called repeatedly, until an :exc:`OSError` exception is + raised, indicating no more values. + + The result is a tuple of 3 items: +@@ -214,8 +219,7 @@ + +-------+--------------------------------------------+ + + .. versionchanged:: 3.3 +- This function used to raise a :exc:`WindowsError`, which is now an +- alias of :exc:`OSError`. ++ See :ref:`above `. + + + .. function:: ExpandEnvironmentStrings(str) +@@ -272,6 +276,7 @@ + + + .. function:: OpenKey(key, sub_key, reserved=0, access=KEY_READ) ++ OpenKeyEx(key, sub_key, reserved=0, access=KEY_READ) + + Opens the specified key, returning a :ref:`handle object `. + +@@ -294,14 +299,7 @@ + Allow the use of named arguments. + + .. versionchanged:: 3.3 +- This function used to raise a :exc:`WindowsError`, which is now an +- alias of :exc:`OSError`. +- +- +-.. function:: OpenKeyEx() +- +- The functionality of :func:`OpenKeyEx` is provided via :func:`OpenKey`, +- by the use of default arguments. ++ See :ref:`above `. + + + .. function:: QueryInfoKey(key) +@@ -427,11 +425,11 @@ + *value_name* is a string that names the subkey with which the value is + associated. + ++ *reserved* can be anything -- zero is always passed to the API. ++ + *type* is an integer that specifies the type of the data. See + :ref:`Value Types ` for the available types. + +- *reserved* can be anything -- zero is always passed to the API. +- + *value* is a string that specifies the new value. + + This method can also set additional value and type information for the specified +diff -r bd8afb90ebf2 Doc/library/xml.dom.minidom.rst +--- a/Doc/library/xml.dom.minidom.rst ++++ b/Doc/library/xml.dom.minidom.rst +@@ -1,8 +1,8 @@ +-:mod:`xml.dom.minidom` --- Lightweight DOM implementation +-========================================================= ++:mod:`xml.dom.minidom` --- Minimal DOM implementation ++===================================================== + + .. module:: xml.dom.minidom +- :synopsis: Lightweight Document Object Model (DOM) implementation. ++ :synopsis: Minimal Document Object Model (DOM) implementation. + .. moduleauthor:: Paul Prescod + .. sectionauthor:: Paul Prescod + .. sectionauthor:: Martin v. Löwis +@@ -11,17 +11,11 @@ + + -------------- + +-:mod:`xml.dom.minidom` is a light-weight implementation of the Document Object +-Model interface. It is intended to be simpler than the full DOM and also +-significantly smaller. +- +-.. note:: +- +- The :mod:`xml.dom.minidom` module provides an implementation of the W3C-DOM, +- with an API similar to that in other programming languages. Users who are +- unfamiliar with the W3C-DOM interface or who would like to write less code +- for processing XML files should consider using the +- :mod:`xml.etree.ElementTree` module instead. ++:mod:`xml.dom.minidom` is a minimal implementation of the Document Object ++Model interface, with an API similar to that in other languages. It is intended ++to be simpler than the full DOM and also significantly smaller. Users who are ++not already proficient with the DOM should consider using the ++:mod:`xml.etree.ElementTree` module for their XML processing instead + + DOM applications typically start by parsing some XML into a DOM. With + :mod:`xml.dom.minidom`, this is done through the parse functions:: +diff -r bd8afb90ebf2 Doc/library/xml.etree.elementtree.rst +--- a/Doc/library/xml.etree.elementtree.rst ++++ b/Doc/library/xml.etree.elementtree.rst +@@ -291,7 +291,9 @@ + | | current element. For example, ``.//egg`` selects | + | | all ``egg`` elements in the entire tree. | + +-----------------------+------------------------------------------------------+ +-| ``..`` | Selects the parent element. | ++| ``..`` | Selects the parent element. Returns ``None`` if the | ++| | path attempts to reach the ancestors of the start | ++| | element (the element ``find`` was called on). | + +-----------------------+------------------------------------------------------+ + | ``[@attrib]`` | Selects all elements that have the given attribute. | + +-----------------------+------------------------------------------------------+ +@@ -431,9 +433,9 @@ + Generates a string representation of an XML element, including all + subelements. *element* is an :class:`Element` instance. *encoding* [1]_ is + the output encoding (default is US-ASCII). Use ``encoding="unicode"`` to +- generate a Unicode string. *method* is either ``"xml"``, +- ``"html"`` or ``"text"`` (default is ``"xml"``). Returns an (optionally) +- encoded string containing the XML data. ++ generate a Unicode string (otherwise, a bytestring is generated). *method* ++ is either ``"xml"``, ``"html"`` or ``"text"`` (default is ``"xml"``). ++ Returns an (optionally) encoded string containing the XML data. + + + .. function:: tostringlist(element, encoding="us-ascii", method="xml") +@@ -441,11 +443,11 @@ + Generates a string representation of an XML element, including all + subelements. *element* is an :class:`Element` instance. *encoding* [1]_ is + the output encoding (default is US-ASCII). Use ``encoding="unicode"`` to +- generate a Unicode string. *method* is either ``"xml"``, +- ``"html"`` or ``"text"`` (default is ``"xml"``). Returns a list of +- (optionally) encoded strings containing the XML data. It does not guarantee +- any specific sequence, except that ``"".join(tostringlist(element)) == +- tostring(element)``. ++ generate a Unicode string (otherwise, a bytestring is generated). *method* ++ is either ``"xml"``, ``"html"`` or ``"text"`` (default is ``"xml"``). ++ Returns a list of (optionally) encoded strings containing the XML data. ++ It does not guarantee any specific sequence, except that ++ ``"".join(tostringlist(element)) == tostring(element)``. + + .. versionadded:: 3.2 + +@@ -521,7 +523,7 @@ + .. method:: clear() + + Resets an element. This function removes all subelements, clears all +- attributes, and sets the text and tail attributes to None. ++ attributes, and sets the text and tail attributes to ``None``. + + + .. method:: get(key, default=None) +@@ -740,7 +742,7 @@ + + + .. method:: write(file, encoding="us-ascii", xml_declaration=None, \ +- method="xml") ++ default_namespace=None, method="xml") + + Writes the element tree to a file, as XML. *file* is a file name, or a + :term:`file object` opened for writing. *encoding* [1]_ is the output +@@ -748,6 +750,7 @@ + *xml_declaration* controls if an XML declaration should be added to the + file. Use ``False`` for never, ``True`` for always, ``None`` + for only if not US-ASCII or UTF-8 or Unicode (default is ``None``). ++ *default_namespace* sets the default XML namespace (for "xmlns"). + *method* is either ``"xml"``, ``"html"`` or ``"text"`` (default is + ``"xml"``). + +diff -r bd8afb90ebf2 Doc/library/xml.rst +--- /dev/null ++++ b/Doc/library/xml.rst +@@ -0,0 +1,29 @@ ++.. _xml: ++ ++XML Processing Modules ++====================== ++ ++Python's interfaces for processing XML are grouped in the ``xml`` package. ++ ++It is important to note that modules in the :mod:`xml` package require that ++there be at least one SAX-compliant XML parser available. The Expat parser is ++included with Python, so the :mod:`xml.parsers.expat` module will always be ++available. ++ ++The documentation for the :mod:`xml.dom` and :mod:`xml.sax` packages are the ++definition of the Python bindings for the DOM and SAX interfaces. ++ ++The XML handling submodules are: ++ ++* :mod:`xml.etree.ElementTree`: the ElementTree API, a simple and lightweight ++ ++.. ++ ++* :mod:`xml.dom`: the DOM API definition ++* :mod:`xml.dom.minidom`: a lightweight DOM implementation ++* :mod:`xml.dom.pulldom`: support for building partial DOM trees ++ ++.. ++ ++* :mod:`xml.sax`: SAX2 base classes and convenience functions ++* :mod:`xml.parsers.expat`: the Expat parser binding +diff -r bd8afb90ebf2 Doc/library/xmlrpc.rst +--- /dev/null ++++ b/Doc/library/xmlrpc.rst +@@ -0,0 +1,12 @@ ++:mod:`xmlrpc` --- XMLRPC server and client modules ++================================================== ++ ++XML-RPC is a Remote Procedure Call method that uses XML passed via HTTP as a ++transport. With it, a client can call methods with parameters on a remote ++server (the server is named by a URI) and get back structured data. ++ ++``xmlrpc`` is a package that collects server and client modules implementing ++XML-RPC. The modules are: ++ ++* :mod:`xmlrpc.client` ++* :mod:`xmlrpc.server` +diff -r bd8afb90ebf2 Doc/library/zipfile.rst +--- a/Doc/library/zipfile.rst ++++ b/Doc/library/zipfile.rst +@@ -61,7 +61,7 @@ + .. class:: ZipInfo(filename='NoName', date_time=(1980,1,1,0,0,0)) + + Class used to represent information about a member of an archive. Instances +- of this class are returned by the :meth:`getinfo` and :meth:`infolist` ++ of this class are returned by the :meth:`.getinfo` and :meth:`.infolist` + methods of :class:`ZipFile` objects. Most users of the :mod:`zipfile` module + will not need to create these, but only use those created by this + module. *filename* should be the full name of the archive member, and +@@ -87,20 +87,20 @@ + .. data:: ZIP_DEFLATED + + The numeric constant for the usual ZIP compression method. This requires the +- zlib module. ++ :mod:`zlib` module. + + + .. data:: ZIP_BZIP2 + + The numeric constant for the BZIP2 compression method. This requires the +- bz2 module. ++ :mod:`bz2` module. + + .. versionadded:: 3.3 + + .. data:: ZIP_LZMA + + The numeric constant for the LZMA compression method. This requires the +- lzma module. ++ :mod:`lzma` module. + + .. versionadded:: 3.3 + +@@ -155,7 +155,7 @@ + these extensions. + + If the file is created with mode ``'a'`` or ``'w'`` and then +- :meth:`close`\ d without adding any files to the archive, the appropriate ++ :meth:`closed ` without adding any files to the archive, the appropriate + ZIP structures for an empty archive will be written to the file. + + ZipFile is also a context manager and therefore supports the +@@ -169,7 +169,7 @@ + Added the ability to use :class:`ZipFile` as a context manager. + + .. versionchanged:: 3.3 +- Added support for :mod:`bzip2` and :mod:`lzma` compression. ++ Added support for :mod:`bzip2 ` and :mod:`lzma` compression. + + + .. method:: ZipFile.close() +@@ -207,7 +207,7 @@ + *mode* parameter, if included, must be one of the following: ``'r'`` (the + default), ``'U'``, or ``'rU'``. Choosing ``'U'`` or ``'rU'`` will enable + :term:`universal newlines` support in the read-only object. *pwd* is the +- password used for encrypted files. Calling :meth:`open` on a closed ++ password used for encrypted files. Calling :meth:`.open` on a closed + ZipFile will raise a :exc:`RuntimeError`. + + .. note:: +@@ -229,7 +229,7 @@ + + .. note:: + +- The :meth:`open`, :meth:`read` and :meth:`extract` methods can take a filename ++ The :meth:`.open`, :meth:`read` and :meth:`extract` methods can take a filename + or a :class:`ZipInfo` object. You will appreciate this when trying to read a + ZIP file that contains members with duplicate names. + +@@ -335,7 +335,7 @@ + :class:`ZipInfo` constructor sets this member to :const:`ZIP_STORED`. + + .. versionchanged:: 3.2 +- The *compression_type* argument. ++ The *compress_type* argument. + + The following data attributes are also available: + +@@ -351,7 +351,7 @@ + The comment text associated with the ZIP file. If assigning a comment to a + :class:`ZipFile` instance created with mode 'a' or 'w', this should be a + string no longer than 65535 bytes. Comments longer than this will be +- truncated in the written archive when :meth:`ZipFile.close` is called. ++ truncated in the written archive when :meth:`close` is called. + + + .. _pyzipfile-objects: +@@ -407,8 +407,8 @@ + ZipInfo Objects + --------------- + +-Instances of the :class:`ZipInfo` class are returned by the :meth:`getinfo` and +-:meth:`infolist` methods of :class:`ZipFile` objects. Each object stores ++Instances of the :class:`ZipInfo` class are returned by the :meth:`.getinfo` and ++:meth:`.infolist` methods of :class:`ZipFile` objects. Each object stores + information about a single member of the ZIP archive. + + Instances have the following attributes: +diff -r bd8afb90ebf2 Doc/library/zlib.rst +--- a/Doc/library/zlib.rst ++++ b/Doc/library/zlib.rst +@@ -52,10 +52,10 @@ + .. function:: compress(data[, level]) + + Compresses the bytes in *data*, returning a bytes object containing compressed data. +- *level* is an integer from ``1`` to ``9`` controlling the level of compression; ++ *level* is an integer from ``0`` to ``9`` controlling the level of compression; + ``1`` is fastest and produces the least compression, ``9`` is slowest and +- produces the most. The default value is ``6``. Raises the :exc:`error` +- exception if any error occurs. ++ produces the most. ``0`` is no compression. The default value is ``6``. ++ Raises the :exc:`error` exception if any error occurs. + + + .. function:: compressobj(level=-1, method=DEFLATED, wbits=15, memlevel=8, strategy=Z_DEFAULT_STRATEGY[, zdict]) +@@ -63,9 +63,10 @@ + Returns a compression object, to be used for compressing data streams that won't + fit into memory at once. + +- *level* is the compression level -- an integer from ``1`` to ``9``. A value ++ *level* is the compression level -- an integer from ``0`` to ``9``. A value + of ``1`` is fastest and produces the least compression, while a value of +- ``9`` is slowest and produces the most. The default value is ``6``. ++ ``9`` is slowest and produces the most. ``0`` is no compression. The default ++ value is ``6``. + + *method* is the compression algorithm. Currently, the only supported value is + ``DEFLATED``. +diff -r bd8afb90ebf2 Doc/license.rst +--- a/Doc/license.rst ++++ b/Doc/license.rst +@@ -150,7 +150,7 @@ + analyze, test, perform and/or display publicly, prepare derivative works, + distribute, and otherwise use Python |release| alone or in any derivative + version, provided, however, that PSF's License Agreement and PSF's notice of +- copyright, i.e., "Copyright © 2001-2012 Python Software Foundation; All Rights ++ copyright, i.e., "Copyright © 2001-2013 Python Software Foundation; All Rights + Reserved" are retained in Python |release| alone or in any derivative version + prepared by Licensee. + +@@ -327,7 +327,7 @@ + ---------------- + + The :mod:`_random` module includes code based on a download from +-http://www.math.keio.ac.jp/ matumoto/MT2002/emt19937ar.html. The following are ++http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/MT2002/emt19937ar.html. The following are + the verbatim comments from the original code:: + + A C-program for MT19937, with initialization improved 2002/1/26. +@@ -368,8 +368,8 @@ + + + Any feedback is very welcome. +- http://www.math.keio.ac.jp/matumoto/emt.html +- email: matumoto@math.keio.ac.jp ++ http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/emt.html ++ email: m-mat @ math.sci.hiroshima-u.ac.jp (remove space) + + + Sockets +diff -r bd8afb90ebf2 Doc/make.bat +--- a/Doc/make.bat ++++ b/Doc/make.bat +@@ -37,7 +37,7 @@ + svn co %SVNROOT%/external/Sphinx-1.0.7/sphinx tools/sphinx + svn co %SVNROOT%/external/docutils-0.6/docutils tools/docutils + svn co %SVNROOT%/external/Jinja-2.3.1/jinja2 tools/jinja2 +-svn co %SVNROOT%/external/Pygments-1.3.1/pygments tools/pygments ++svn co %SVNROOT%/external/Pygments-1.5dev-20120930/pygments tools/pygments + goto end + + :update +diff -r bd8afb90ebf2 Doc/reference/compound_stmts.rst +--- a/Doc/reference/compound_stmts.rst ++++ b/Doc/reference/compound_stmts.rst +@@ -307,11 +307,11 @@ + :keyword:`try` clause is executed, including any :keyword:`except` and + :keyword:`else` clauses. If an exception occurs in any of the clauses and is + not handled, the exception is temporarily saved. The :keyword:`finally` clause +-is executed. If there is a saved exception or :keyword:`break` statement, +-it is re-raised at the end of the :keyword:`finally` clause. If the +-:keyword:`finally` clause raises another exception the saved exception +-is set as the context of the new exception; if the :keyword:`finally` clause +-executes a :keyword:`return` statement, the saved exception is discarded:: ++is executed. If there is a saved exception it is re-raised at the end of the ++:keyword:`finally` clause. If the :keyword:`finally` clause raises another ++exception, the saved exception is set as the context of the new exception. ++If the :keyword:`finally` clause executes a :keyword:`return` or :keyword:`break` ++statement, the saved exception is discarded:: + + def f(): + try: +@@ -417,6 +417,9 @@ + statement. + + ++.. index:: ++ single: parameter; function definition ++ + .. _function: + .. _def: + +@@ -442,8 +445,7 @@ + decorator: "@" `dotted_name` ["(" [`parameter_list` [","]] ")"] NEWLINE + dotted_name: `identifier` ("." `identifier`)* + parameter_list: (`defparameter` ",")* +- : ( "*" [`parameter`] ("," `defparameter`)* +- : [, "**" `parameter`] ++ : ( "*" [`parameter`] ("," `defparameter`)* ["," "**" `parameter`] + : | "**" `parameter` + : | `defparameter` [","] ) + parameter: `identifier` [":" `expression`] +@@ -479,11 +481,14 @@ + def func(): pass + func = f1(arg)(f2(func)) + +-.. index:: triple: default; parameter; value ++.. index:: ++ triple: default; parameter; value ++ single: argument; function definition + +-When one or more parameters have the form *parameter* ``=`` *expression*, the +-function is said to have "default parameter values." For a parameter with a +-default value, the corresponding argument may be omitted from a call, in which ++When one or more :term:`parameters ` have the form *parameter* ``=`` ++*expression*, the function is said to have "default parameter values." For a ++parameter with a default value, the corresponding :term:`argument` may be ++omitted from a call, in which + case the parameter's default value is substituted. If a parameter has a default + value, all following parameters up until the "``*``" must also have a default + value --- this is a syntactic restriction that is not expressed by the grammar. +diff -r bd8afb90ebf2 Doc/reference/datamodel.rst +--- a/Doc/reference/datamodel.rst ++++ b/Doc/reference/datamodel.rst +@@ -274,11 +274,13 @@ + + The following types are immutable sequences: + ++ .. index:: ++ single: string; immutable sequences ++ + Strings + .. index:: + builtin: chr + builtin: ord +- builtin: str + single: character + single: integer + single: Unicode +@@ -312,7 +314,7 @@ + + A bytes object is an immutable array. The items are 8-bit bytes, + represented by integers in the range 0 <= x < 256. Bytes literals +- (like ``b'abc'`` and the built-in function :func:`bytes` can be used to ++ (like ``b'abc'``) and the built-in function :func:`bytes` can be used to + construct bytes objects. Also, bytes objects can be decoded to strings + via the :meth:`decode` method. + +@@ -600,9 +602,9 @@ + A function or method which uses the :keyword:`yield` statement (see section + :ref:`yield`) is called a :dfn:`generator function`. Such a function, when + called, always returns an iterator object which can be used to execute the +- body of the function: calling the iterator's :meth:`__next__` method will +- cause the function to execute until it provides a value using the +- :keyword:`yield` statement. When the function executes a ++ body of the function: calling the iterator's :meth:`iterator__next__` ++ method will cause the function to execute until it provides a value ++ using the :keyword:`yield` statement. When the function executes a + :keyword:`return` statement or falls off the end, a :exc:`StopIteration` + exception is raised and the iterator will have reached the end of the set of + values to be returned. +@@ -1140,11 +1142,12 @@ + modules are still available at the time when the :meth:`__del__` method is + called. + ++ .. index:: ++ single: repr() (built-in function); __repr__() (object method) ++ + + .. method:: object.__repr__(self) + +- .. index:: builtin: repr +- + Called by the :func:`repr` built-in function to compute the "official" string + representation of an object. If at all possible, this should look like a + valid Python expression that could be used to recreate an object with the +@@ -1157,18 +1160,25 @@ + This is typically used for debugging, so it is important that the representation + is information-rich and unambiguous. + ++ .. index:: ++ single: string; __str__() (object method) ++ single: format() (built-in function); __str__() (object method) ++ single: print() (built-in function); __str__() (object method) ++ + + .. method:: object.__str__(self) + +- .. index:: +- builtin: str +- builtin: print +- +- Called by the :func:`str` built-in function and by the :func:`print` function +- to compute the "informal" string representation of an object. This differs +- from :meth:`__repr__` in that it does not have to be a valid Python +- expression: a more convenient or concise representation may be used instead. +- The return value must be a string object. ++ Called by :func:`str(object) ` and the built-in functions ++ :func:`format` and :func:`print` to compute the "informal" or nicely ++ printable string representation of an object. The return value must be a ++ :ref:`string ` object. ++ ++ This method differs from :meth:`object.__repr__` in that there is no ++ expectation that :meth:`__str__` return a valid Python expression: a more ++ convenient or concise representation can be used. ++ ++ The default implementation defined by the built-in type :class:`object` ++ calls :meth:`object.__repr__`. + + .. XXX what about subclasses of string? + +@@ -1180,16 +1190,16 @@ + Called by :func:`bytes` to compute a byte-string representation of an + object. This should return a ``bytes`` object. + ++ .. index:: ++ single: string; __format__() (object method) ++ pair: string; conversion ++ builtin: print ++ + + .. method:: object.__format__(self, format_spec) + +- .. index:: +- pair: string; conversion +- builtin: str +- builtin: print +- + Called by the :func:`format` built-in function (and by extension, the +- :meth:`format` method of class :class:`str`) to produce a "formatted" ++ :meth:`str.format` method of class :class:`str`) to produce a "formatted" + string representation of an object. The ``format_spec`` argument is + a string that contains a description of the formatting options desired. + The interpretation of the ``format_spec`` argument is up to the type +@@ -1271,22 +1281,22 @@ + and ``x.__hash__()`` returns an appropriate value such that ``x == y`` + implies both that ``x is y`` and ``hash(x) == hash(y)``. + +- Classes which inherit a :meth:`__hash__` method from a parent class but +- change the meaning of :meth:`__eq__` such that the hash value returned is no +- longer appropriate (e.g. by switching to a value-based concept of equality +- instead of the default identity based equality) can explicitly flag +- themselves as being unhashable by setting ``__hash__ = None`` in the class +- definition. Doing so means that not only will instances of the class raise an +- appropriate :exc:`TypeError` when a program attempts to retrieve their hash +- value, but they will also be correctly identified as unhashable when checking +- ``isinstance(obj, collections.Hashable)`` (unlike classes which define their +- own :meth:`__hash__` to explicitly raise :exc:`TypeError`). ++ A class that overrides :meth:`__eq__` and does not define :meth:`__hash__` ++ will have its :meth:`__hash__` implicitly set to ``None``. When the ++ :meth:`__hash__` method of a class is ``None``, instances of the class will ++ raise an appropriate :exc:`TypeError` when a program attempts to retrieve ++ their hash value, and will also be correctly identified as unhashable when ++ checking ``isinstance(obj, collections.Hashable``). + + If a class that overrides :meth:`__eq__` needs to retain the implementation + of :meth:`__hash__` from a parent class, the interpreter must be told this +- explicitly by setting ``__hash__ = .__hash__``. Otherwise the +- inheritance of :meth:`__hash__` will be blocked, just as if :attr:`__hash__` +- had been explicitly set to :const:`None`. ++ explicitly by setting ``__hash__ = .__hash__``. ++ ++ If a class that does not override :meth:`__eq__` wishes to suppress hash ++ support, it should include ``__hash__ = None`` in the class definition. ++ A class which defines its own :meth:`__hash__` that explicitly raises ++ a :exc:`TypeError` would be incorrectly identified as hashable by ++ an ``isinstance(obj, collections.Hashable)`` call. + + + .. note:: +diff -r bd8afb90ebf2 Doc/reference/expressions.rst +--- a/Doc/reference/expressions.rst ++++ b/Doc/reference/expressions.rst +@@ -294,13 +294,13 @@ + brackets or curly braces. + + Variables used in the generator expression are evaluated lazily when the +-:meth:`__next__` method is called for generator object (in the same fashion as +-normal generators). However, the leftmost :keyword:`for` clause is immediately +-evaluated, so that an error produced by it can be seen before any other possible +-error in the code that handles the generator expression. Subsequent +-:keyword:`for` clauses cannot be evaluated immediately since they may depend on +-the previous :keyword:`for` loop. For example: ``(x*y for x in range(10) for y +-in bar(x))``. ++:meth:`~generator.__next__` method is called for generator object (in the same ++fashion as normal generators). However, the leftmost :keyword:`for` clause is ++immediately evaluated, so that an error produced by it can be seen before any ++other possible error in the code that handles the generator expression. ++Subsequent :keyword:`for` clauses cannot be evaluated immediately since they ++may depend on the previous :keyword:`for` loop. For example: ``(x*y for x in ++range(10) for y in bar(x))``. + + The parentheses can be omitted on calls with only one argument. See section + :ref:`calls` for the detail. +@@ -320,7 +320,8 @@ + yield_atom: "(" `yield_expression` ")" + yield_expression: "yield" [`expression_list` | "from" `expression`] + +-The :keyword:`yield` expression is only used when defining a generator function, ++The :keyword:`yield` expression is only used when defining a :term:`generator` ++function, + and can only be used in the body of a function definition. Using a + :keyword:`yield` expression in a function definition is sufficient to cause that + definition to create a generator function instead of a normal function. +@@ -394,10 +395,11 @@ + + Starts the execution of a generator function or resumes it at the last + executed :keyword:`yield` expression. When a generator function is resumed +- with a :meth:`__next__` method, the current :keyword:`yield` expression +- always evaluates to :const:`None`. The execution then continues to the next +- :keyword:`yield` expression, where the generator is suspended again, and the +- value of the :token:`expression_list` is returned to :meth:`next`'s caller. ++ with a :meth:`~generator.__next__` method, the current :keyword:`yield` ++ expression always evaluates to :const:`None`. The execution then continues ++ to the next :keyword:`yield` expression, where the generator is suspended ++ again, and the value of the :token:`expression_list` is returned to ++ :meth:`next`'s caller. + If the generator exits without yielding another value, a :exc:`StopIteration` + exception is raised. + +@@ -437,6 +439,12 @@ + other exception, it is propagated to the caller. :meth:`close` does nothing + if the generator has already exited due to an exception or normal exit. + ++ ++.. index:: single: yield; examples ++ ++Examples ++^^^^^^^^ ++ + Here is a simple example that demonstrates the behavior of generators and + generator functions:: + +@@ -464,6 +472,9 @@ + >>> generator.close() + Don't forget to clean up when 'close()' is called. + ++For examples using ``yield from``, see :ref:`pep-380` in "What's New in ++Python." ++ + + .. seealso:: + +@@ -626,17 +637,18 @@ + expressions. + + ++.. index:: ++ object: callable ++ single: call ++ single: argument; call semantics ++ + .. _calls: + + Calls + ----- + +-.. index:: single: call +- +-.. index:: object: callable +- +-A call calls a callable object (e.g., a function) with a possibly empty series +-of arguments: ++A call calls a callable object (e.g., a :term:`function`) with a possibly empty ++series of :term:`arguments `: + + .. productionlist:: + call: `primary` "(" [`argument_list` [","] | `comprehension`] ")" +@@ -654,11 +666,14 @@ + A trailing comma may be present after the positional and keyword arguments but + does not affect the semantics. + ++.. index:: ++ single: parameter; call semantics ++ + The primary must evaluate to a callable object (user-defined functions, built-in + functions, methods of built-in objects, class objects, methods of class + instances, and all objects having a :meth:`__call__` method are callable). All + argument expressions are evaluated before the call is attempted. Please refer +-to section :ref:`function` for the syntax of formal parameter lists. ++to section :ref:`function` for the syntax of formal :term:`parameter` lists. + + .. XXX update with kwonly args PEP + +@@ -1094,16 +1109,10 @@ + another one is made arbitrarily but consistently within one execution of a + program. + +-Comparison of objects of the differing types depends on whether either +-of the types provide explicit support for the comparison. Most numeric types +-can be compared with one another, but comparisons of :class:`float` and +-:class:`Decimal` are not supported to avoid the inevitable confusion arising +-from representation issues such as ``float('1.1')`` being inexactly represented +-and therefore not exactly equal to ``Decimal('1.1')`` which is. When +-cross-type comparison is not supported, the comparison method returns +-``NotImplemented``. This can create the illusion of non-transitivity between +-supported cross-type comparisons and unsupported comparisons. For example, +-``Decimal(2) == 2`` and ``2 == float(2)`` but ``Decimal(2) != float(2)``. ++Comparison of objects of the differing types depends on whether either of the ++types provide explicit support for the comparison. Most numeric types can be ++compared with one another. When cross-type comparison is not supported, the ++comparison method returns ``NotImplemented``. + + .. _membership-test-details: + +@@ -1298,8 +1307,8 @@ + + .. _operator-summary: + +-Summary +-======= ++Operator precedence ++=================== + + .. index:: pair: operator; precedence + +@@ -1323,9 +1332,9 @@ + +-----------------------------------------------+-------------------------------------+ + | :keyword:`and` | Boolean AND | + +-----------------------------------------------+-------------------------------------+ +-| :keyword:`not` *x* | Boolean NOT | ++| :keyword:`not` ``x`` | Boolean NOT | + +-----------------------------------------------+-------------------------------------+ +-| :keyword:`in`, :keyword:`not` :keyword:`in`, | Comparisons, including membership | ++| :keyword:`in`, :keyword:`not in`, | Comparisons, including membership | + | :keyword:`is`, :keyword:`is not`, ``<``, | tests and identity tests, | + | ``<=``, ``>``, ``>=``, ``!=``, ``==`` | | + +-----------------------------------------------+-------------------------------------+ +@@ -1351,7 +1360,7 @@ + +-----------------------------------------------+-------------------------------------+ + | ``(expressions...)``, | Binding or tuple display, | + | ``[expressions...]``, | list display, | +-| ``{key:datum...}``, | dictionary display, | ++| ``{key: value...}``, | dictionary display, | + | ``{expressions...}`` | set display | + +-----------------------------------------------+-------------------------------------+ + +diff -r bd8afb90ebf2 Doc/reference/import.rst +--- a/Doc/reference/import.rst ++++ b/Doc/reference/import.rst +@@ -44,9 +44,9 @@ + + .. versionchanged:: 3.3 + The import system has been updated to fully implement the second phase +- of PEP 302. There is no longer any implicit import machinery - the full ++ of :pep:`302`. There is no longer any implicit import machinery - the full + import system is exposed through :data:`sys.meta_path`. In addition, +- native namespace package support has been implemented (see PEP 420). ++ native namespace package support has been implemented (see :pep:`420`). + + + :mod:`importlib` +@@ -219,9 +219,9 @@ + interfaces are referred to as :term:`importers ` - they return + themselves when they find that they can load the requested module. + +-Python includes a number of default finders and importers. One +-knows how to locate frozen modules, and another knows how to locate +-built-in modules. A third default finder searches an :term:`import path` ++Python includes a number of default finders and importers. The first one ++knows how to locate built-in modules, and the second knows how to locate ++frozen modules. A third default finder searches an :term:`import path` + for modules. The :term:`import path` is a list of locations that may + name file system paths or zip files. It can also be extended to search + for any locatable resource, such as those identified by URLs. +@@ -540,7 +540,10 @@ + implementation-specific defaults. Entries in :data:`sys.path` can name + directories on the file system, zip files, and potentially other "locations" + (see the :mod:`site` module) that should be searched for modules, such as +-URLs, or database queries. ++URLs, or database queries. Only strings and bytes should be present on ++:data:`sys.path`; all other data types are ignored. The encoding of bytes ++entries is determined by the individual :term:`path entry finders `. + + The :term:`path based finder` is a :term:`meta path finder`, so the import + machinery begins the :term:`import path` search by calling the path +@@ -563,14 +566,17 @@ + the path based finder to perform the path entry search again [#fnpic]_. + + If the path entry is not present in the cache, the path based finder iterates +-over every callable in :data:`sys.path_hooks`. Each of the +-:term:`path entry hooks ` in this list is called with a +-single argument, the path entry to be searched. This callable may either +-return a :term:`path entry finder` that can handle the path entry, or it may +-raise :exc:`ImportError`. +-An :exc:`ImportError` is used by the path based finder to signal that the hook +-cannot find a :term:`path entry finder` for that :term:`path entry`. The +-exception is ignored and :term:`import path` iteration continues. ++over every callable in :data:`sys.path_hooks`. Each of the :term:`path entry ++hooks ` in this list is called with a single argument, the ++path entry to be searched. This callable may either return a :term:`path ++entry finder` that can handle the path entry, or it may raise ++:exc:`ImportError`. An :exc:`ImportError` is used by the path based finder to ++signal that the hook cannot find a :term:`path entry finder` for that ++:term:`path entry`. The exception is ignored and :term:`import path` ++iteration continues. The hook should expect either a string or bytes object; ++the encoding of bytes objects is up to the hook (e.g. it may be a file system ++encoding, UTF-8, or something else), and if the hook cannot decode the ++argument, it should raise :exc:`ImportError`. + + If :data:`sys.path_hooks` iteration ends with no :term:`path entry finder` + being returned, then the path based finder's :meth:`find_module()` method +diff -r bd8afb90ebf2 Doc/reference/index.rst +--- a/Doc/reference/index.rst ++++ b/Doc/reference/index.rst +@@ -4,9 +4,6 @@ + The Python Language Reference + ################################# + +-:Release: |version| +-:Date: |today| +- + This reference manual describes the syntax and "core semantics" of the + language. It is terse, but attempts to be exact and complete. The semantics of + non-essential built-in object types and of the built-in functions and modules +diff -r bd8afb90ebf2 Doc/reference/lexical_analysis.rst +--- a/Doc/reference/lexical_analysis.rst ++++ b/Doc/reference/lexical_analysis.rst +@@ -538,9 +538,7 @@ + this escape sequence. Exactly four hex digits are required. + + (6) +- Any Unicode character can be encoded this way, but characters outside the Basic +- Multilingual Plane (BMP) will be encoded using a surrogate pair if Python is +- compiled to use 16-bit code units (the default). Exactly eight hex digits ++ Any Unicode character can be encoded this way. Exactly eight hex digits + are required. + + +diff -r bd8afb90ebf2 Doc/tools/sphinxext/indexsidebar.html +--- a/Doc/tools/sphinxext/indexsidebar.html ++++ b/Doc/tools/sphinxext/indexsidebar.html +@@ -3,7 +3,7 @@ +

Docs for other versions

+
+ +diff -r bd8afb90ebf2 Doc/tools/sphinxext/layout.html +--- a/Doc/tools/sphinxext/layout.html ++++ b/Doc/tools/sphinxext/layout.html +@@ -3,18 +3,83 @@ +
  • +
  • Python{{ reldelim1 }}
  • +-
  • {{ shorttitle }}{{ reldelim1 }}
  • ++
  • ++ {%- if versionswitcher is defined %} ++ {{ release }} ++ Documentation{{ reldelim1 }} ++ {%- else %} ++ {{ shorttitle }}{{ reldelim1 }} ++ {%- endif %} ++
  • + {% endblock %} + {% block extrahead %} + + {% if not embedded %}{% endif %} ++ {% if versionswitcher is defined and not embedded %}{% endif %} ++ {% if pagename == 'whatsnew/changelog' %} ++ ++ {% endif %} + {{ super() }} + {% endblock %} + {% block footer %} +