Mailman 3 May 2004 - Python-checkins

python/nondist/peps pep-0003.txt,1.4,1.5
by akuchling＠users.sourceforge.net May 26, 2004

May 26, 2004

Update of /cvsroot/python/python/nondist/peps In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv5157 Modified Files: pep-0003.txt Log Message: Typo fix Index: pep-0003.txt =================================================================== RCS file: /cvsroot/python/python/nondist/peps/pep-0003.txt,v retrieving revision 1.4 retrieving revision 1.5 diff -C2 -d -r1.4 -r1.5 *** pep-0003.txt 26 May 2004 16:10:30 -0000 1.4 --- pep-0003.txt 26 May 2004 17:02:35 -0000 1.5 *************** *** 15,19 **** expertise. ! These are guidlines for the developers of Python, not the submitters of bugs. Those are at --- 15,19 ---- expertise. ! These are guidelines for the developers of Python, not the submitters of bugs. Those are at

1 0

python/nondist/peps pep-0042.txt,1.76,1.77
by mwh＠users.sourceforge.net May 26, 2004

May 26, 2004

Update of /cvsroot/python/python/nondist/peps In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv28569 Modified Files: pep-0042.txt Log Message: Remove an implemented request. Index: pep-0042.txt =================================================================== RCS file: /cvsroot/python/python/nondist/peps/pep-0042.txt,v retrieving revision 1.76 retrieving revision 1.77 diff -C2 -d -r1.76 -r1.77 *** pep-0042.txt 8 Jan 2004 01:58:29 -0000 1.76 --- pep-0042.txt 26 May 2004 16:17:39 -0000 1.77 *************** *** 296,308 **** http://www.python.org/sf/216326 - - There's a name conflict on case insensitive filesystems (in - particular Mac OSX) between the directory "Python" and the key - build target "python". That's currently solved by abusing the - --with-suffix option, but that's not ideal (since that also - causes the binary to be *installed* as python.exe). What should - be the solution? - - http://www.python.org/sf/222215 - - Building from source should not attempt to overwrite the Include/graminit.h and Parser/graminit.c files, at least for --- 296,299 ----

1 0

python/nondist/peps pep-0003.txt,1.3,1.4
by mwh＠users.sourceforge.net May 26, 2004

May 26, 2004

Update of /cvsroot/python/python/nondist/peps In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv27052 Modified Files: pep-0003.txt Log Message: Make this a little bit less hilariously out of date. Index: pep-0003.txt =================================================================== RCS file: /cvsroot/python/python/nondist/peps/pep-0003.txt,v retrieving revision 1.3 retrieving revision 1.4 diff -C2 -d -r1.3 -r1.4 *** pep-0003.txt 30 Sep 2002 01:55:41 -0000 1.3 --- pep-0003.txt 26 May 2004 16:10:30 -0000 1.4 *************** *** 15,18 **** --- 15,25 ---- expertise. + These are guidlines for the developers of Python, not the + submitters of bugs. Those are at + + http://docs.python.org/lib/reporting-bugs.html + + (though this hardly seems the best place). + Guidelines *************** *** 28,31 **** --- 35,40 ---- saying that this is the case (mentioning the PEP explicitly). + XXX do we prefer the feature request tracker or PEP 42? + 3. Assign the bug a reasonable priority. We don't yet have a clear sense of what each priority should mean, except than 9 is *************** *** 34,41 **** 4. If a bug report doesn't have enough information to allow you to ! reproduce or diagnose it, send email to the original submittor ! and ask for more information. If the original report is really ! thin and your email doesn't get a response after a reasonable ! waiting period, you can close the bug. 5. If you fix a bug, mark the status as "Fixed" and close it. In --- 43,50 ---- 4. If a bug report doesn't have enough information to allow you to ! reproduce or diagnose it, ask the original submitter for more ! information. If the original report is really thin and your ! email doesn't get a response after a reasonable waiting period, ! you can close the bug. 5. If you fix a bug, mark the status as "Fixed" and close it. In *************** *** 45,52 **** change. ! 6. If you are assigned a bug that you are unable to deal with ! assign it to someone else. The guys at PythonLabs get paid to ! fix these bugs, so pick one of them if there is no other ! obvious candidate. --- 54,60 ---- change. ! 6. If you are assigned a bug that you are unable to deal with, ! assign it to someone else if you think they will be able to ! deal with it, otherwise it's probably best to unassign it.

1 0

python/dist/src/Doc/tut tut.tex,1.230,1.231
by rhettinger＠users.sourceforge.net May 26, 2004

May 26, 2004

Update of /cvsroot/python/python/dist/src/Doc/tut In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv31172 Modified Files: tut.tex Log Message: Fill-in the introductory paragraph for the library tour. Index: tut.tex =================================================================== RCS file: /cvsroot/python/python/dist/src/Doc/tut/tut.tex,v retrieving revision 1.230 retrieving revision 1.231 diff -C2 -d -r1.230 -r1.231 *** tut.tex 26 May 2004 13:52:59 -0000 1.230 --- tut.tex 26 May 2004 13:57:54 -0000 1.231 *************** *** 4766,4769 **** --- 4766,4772 ---- \chapter{Brief Tour of the Standard Library -- Part II\label{briefTourTwo}} + This second tour covers more advanced modules that support professional + programming needs. These modules rarely occur in small scripts. + \section{Output Formatting\label{output-formatting}}

1 0

python/dist/src/Doc/tut tut.tex,1.229,1.230
by rhettinger＠users.sourceforge.net May 26, 2004

May 26, 2004

Update of /cvsroot/python/python/dist/src/Doc/tut In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv30188 Modified Files: tut.tex Log Message: Add a further tour of the standard library. Index: tut.tex =================================================================== RCS file: /cvsroot/python/python/dist/src/Doc/tut/tut.tex,v retrieving revision 1.229 retrieving revision 1.230 diff -C2 -d -r1.229 -r1.230 *** tut.tex 25 May 2004 16:08:28 -0000 1.229 --- tut.tex 26 May 2004 13:52:59 -0000 1.230 *************** *** 4764,4767 **** --- 4764,5057 ---- + \chapter{Brief Tour of the Standard Library -- Part II\label{briefTourTwo}} + + + \section{Output Formatting\label{output-formatting}} + + The \ulink{\module{repr}}{../lib/module-repr.html} module provides an + version of \function{repr()} for abbreviated displays of large or deeply + nested containers: + + \begin{verbatim} + >>> import repr + >>> repr.repr(set('supercalifragilisticexpialidocious')) + "set(['a', 'c', 'd', 'e', 'f', 'g', ...])" + \end{verbatim} + + The \ulink{\module{pprint}}{../lib/module-pprint.html} module offers + more sophisticated control over printing both built-in and user defined + objects in a way that is readable by the interpreter. When the result + is longer than one line, the ``pretty printer'' adds line breaks and + indentation to more clearly reveal data structure: + + \begin{verbatim} + >>> import pprint + >>> t = [[[['black', 'cyan'], 'white', ['green', 'red']], [['magenta', + ... 'yellow'], 'blue']]] + ... + >>> pprint.pprint(t, width=30) + [[[['black', 'cyan'], + 'white', + ['green', 'red']], + [['magenta', 'yellow'], + 'blue']]] + \end{verbatim} + + The \ulink{\module{textwrap}}{../lib/module-textwrap.html} module + formats paragraphs of text to fit a given screen width: + + \begin{verbatim} + >>> import textwrap + >>> doc = """The wrap() method is just like fill() except that it returns + ... a list of strings instead of one big string with newlines to separate + ... the wrapped lines.""" + ... + >>> print textwrap.fill(doc, width=40) + The wrap() method is just like fill() + except that it returns a list of strings + instead of one big string with newlines + to separate the wrapped lines. + \end{verbatim} + + The \ulink{\module{locale}}{../lib/module-locale.html} module accesses + a database of culture specific data formats. The grouping attribute + of locale's format function provides a direct way of formatting numbers + with group separators: + + \begin{verbatim} + >>> import locale + >>> locale.setlocale(locale.LC_ALL, 'English_United States.1252') + 'English_United States.1252' + >>> conv = locale.localeconv() # get a mapping of conventions + >>> x = 1234567.8 + >>> locale.format("%d", x, grouping=True) + '1,234,567' + >>> locale.format("%s%.*f", (conv['currency_symbol'], + ... conv['int_frac_digits'], x), grouping=True) + '$1,234,567.80' + \end{verbatim} + + + \section{Working with Binary Data Record Layouts\label{binary-formats}} + + The \ulink{\module{struct}}{../lib/module-struct.html} module provides + \function{pack()} and \function{unpack()} functions for working with + variable length binary record formats. The following example shows how + to loop through header information in a ZIP file (with pack codes + \code{"H"} and \code{"L"} representing two and four byte unsigned + numbers respectively): + + \begin{verbatim} + import struct + + data = open('myfile.zip', 'rb').read() + start = 0 + for i in range(3): # show the first 3 file headers + start += 14 + fields = struct.unpack('LLLHH', data[start:start+16]) + crc32, comp_size, uncomp_size, filenamesize, extra_size = fields + + start += 16 + filename = data[start:start+filenamesize] + start += filenamesize + extra = data[start:start+extra_size] + print filename, hex(crc32), comp_size, uncomp_size + + start += extra_size + comp_size # skip to the next header + \end{verbatim} + + + \section{Multi-threading\label{multi-threading}} + + Threading is a technique for decoupling tasks which are not sequentially + dependent. Python threads are driven by the operating system and run + in a single process and share memory space in a single interpreter. + + Threads can be used to improve the responsiveness of applications that + accept user input while other tasks run in the background. The + following code shows how the high level + \ulink{\module{threading}}{../lib/module-threading.html} module can run + tasks in background while the main program continues to run: + + \begin{verbatim} + import threading, zipfile + + class AsyncZip(threading.Thread): + def __init__(self, infile, outfile): + threading.Thread.__init__(self) + self.infile = infile + self.outfile = outfile + def run(self): + f = zipfile.ZipFile(self.outfile, 'w', zipfile.ZIP_DEFLATED) + f.write(self.infile) + f.close() + print 'Finished background zip of: ', self.infile + + AsyncZip('mydata.txt', 'myarchive.zip').start() + print 'The main program continues to run' + \end{verbatim} + + The principal challenge of multi-thread applications is coordinating + threads that share data or other resources. To that end, the threading + module provides a number of synchronization primitives including locks, + events, condition variables, and semaphores. + + While those tools are powerful, minor design errors can result in + problems that are difficult to reproduce. A simpler and more robust + approach to task coordination is concentrating all access to a resource + in a single thread and then using the + \ulink{\module{Queue}}{../lib/module-Queue.html} module to feed that + thread with requests from other threads. Applications that use + \class{Queue} objects for inter-thread communication and coordination + tend to be easier to design, more readable, and more reliable. + + + \section{Logging\label{logging}} + + The \ulink{\module{logging}}{../lib/module-logging.html} module offers + a full featured and flexible logging system. At its simplest, log + messages are sent to a file or to \code{sys.stderr}: + + \begin{verbatim} + import logging + logging.debug('Debugging information') + logging.info('Informational message') + logging.warning('Warning:config file %s not found', 'server.conf') + logging.error('Error occurred') + logging.critical('Critical error -- shutting down') + \end{verbatim} + + This produces the following output: + + \begin{verbatim} + WARNING:root:Warning:config file server.conf not found + ERROR:root:Error occurred + CRITICAL:root:Critical error -- shutting down + \end{verbatim} + + By default, informational and debugging messages are suppressed and the + output is sent to standard error. Other output options include routing + messages through email, datagrams, sockets, or to an HTTP Server. New + filters select different routing based on message priority: DEBUG, + INFO, WARNING, ERROR, and CRITICAL. + + The logging system can be configured directly from Python or can be + loaded from a user editable configuration file for customized logging + without altering the application. + + + \section{Weak References\label{weak-references}} + + Python does automatic memory management (reference counting for most + objects and garbage collection to eliminate cycles). The memory is + freed shortly after the last reference to it has been eliminated. + + This approach works fine for most applications but occasionally there + is a need to track objects only as long as they are being used by + something else. Unfortunately, just tracking them creates a reference + that makes them permanent. The + \ulink{\module{weakref}}{../lib/module-weakref.html} module provides + tools for tracking objects without creating a reference. When the + object is no longer needed, it is automatically removed from a weakref + table and a callback is triggered for weakref objects. Typical + applications include caching objects that are expensive to create: + + \begin{verbatim} + >>> import weakref, gc + >>> class A: + ... def __init__(self, value): + ... self.value = value + ... def __repr__(self): + ... return str(self.value) + ... + >>> a = A(10) # create a reference + >>> d = weakref.WeakValueDictionary() + >>> d['primary'] = a # does not create a reference + >>> d['primary'] # fetch the object if it is still alive + 10 + >>> del a # remove the one reference + >>> gc.collect() # run garbage collection right away + 0 + >>> d['primary'] # entry was automatically removed + Traceback (most recent call last): + File "<pyshell#108>", line 1, in -toplevel- + d['primary'] # entry was automatically removed + File "C:/PY24/lib/weakref.py", line 46, in __getitem__ + o = self.data[key]() + KeyError: 'primary' + \end{verbatim} + + \section{Tools for Working with Lists\label{list-tools}} + + Many data structure needs can be met with the built-in list type. + However, sometimes there is a need for alternative implementations + with different performance trade-offs. + + The \ulink{\module{array}}{../lib/module-array.html} module provides an + \class{array()} object that is like a list that stores only homogenous + data but stores it more compactly. The following example shows an array + of numbers stored as two byte unsigned binary numbers (typecode + \code{"H"}) rather than the usual 16 bytes per entry for regular lists + of python int objects: + + \begin{verbatim} + >>> from array import array + >>> a = array('H', [4000, 10, 700, 22222]) + >>> sum(a) + 26932 + >>> a[1:3] + array('H', [10, 700]) + \end{verbatim} + + The \ulink{\module{collections}}{../lib/module-collections.html} module + provides a \class{deque()} object that is like a list with faster + appends and pops from the left side but slower lookups in the middle. + These objects are well suited for implementing queues and breadth first + tree searches: + + \begin{verbatim} + >>> from collections import deque + >>> d = deque(["task1", "task2", "task3"]) + >>> d.append("task4") + >>> print "Handling", d.popleft() + Handling task1 + + unsearched = deque([starting_node]) + def breadth_first_search(unsearched): + node = unsearched.popleft() + for m in gen_moves(node): + if is_goal(m): + return m + unsearched.append(m) + \end{verbatim} + + In addition to alternative list implementations, the library also offers + other tools such as the \ulink{\module{bisect}}{../lib/module-bisect.html} + module with functions for manipulating sorted lists: + + \begin{verbatim} + >>> import bisect + >>> scores = [(100, 'perl'), (200, 'tcl'), (400, 'lua'), (500, 'python')] + >>> bisect.insort(scores, (300, 'ruby')) + >>> scores + [(100, 'perl'), (200, 'tcl'), (300, 'ruby'), (400, 'lua'), (500, 'python')] + \end{verbatim} + + The \ulink{\module{heapq}}{../lib/module-heapq.html} module provides + functions for implementing heaps based on regular lists. The lowest + valued entry is always kept at position zero. This is useful for + applications which repeatedly access the smallest element but do not + want to run a full list sort: + + \begin{verbatim} + >>> from heapq import heapify, heappop, heappush + >>> data = [1, 3, 5, 7, 9, 2, 4, 6, 8, 0] + >>> heapify(data) # rearrange the list into heap order + >>> heappush(data, -5) # add a new entry + >>> [heappop(data) for i in range(3)] # fetch the three smallest entries + [-5, 0, 1] + \end{verbatim} + + \chapter{What Now? \label{whatNow}}

1 0

python/nondist/peps pep-0320.txt,1.11,1.12
by fdrake＠users.sourceforge.net May 26, 2004

May 26, 2004

Update of /cvsroot/python/python/nondist/peps In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv28481 Modified Files: pep-0320.txt Log Message: Features planned for 2.4 aren't being pushed off to 2.4. Index: pep-0320.txt =================================================================== RCS file: /cvsroot/python/python/nondist/peps/pep-0320.txt,v retrieving revision 1.11 retrieving revision 1.12 diff -C2 -d -r1.11 -r1.12 *** pep-0320.txt 19 May 2004 21:18:55 -0000 1.11 --- pep-0320.txt 26 May 2004 00:11:02 -0000 1.12 *************** *** 61,67 **** PEP 327: A Decimal package for fixed precision arithmetic. ! PEP 328: Imports: Multi-line and Absolute/Relative. (Possibly ! the absolute/relative stuff is too controversial and will be ! pushed off to 2.4.) Deprecate and/or remove the modules listed in PEP 4 (posixfile, --- 61,66 ---- PEP 327: A Decimal package for fixed precision arithmetic. ! PEP 328: Imports: Multi-line and Absolute/Relative. (Still quite ! controversial.) Deprecate and/or remove the modules listed in PEP 4 (posixfile,

1 0

python/dist/src/PCbuild python20.wse, 1.133.4.8, 1.133.4.9
by theller＠users.sourceforge.net May 25, 2004

May 25, 2004

Update of /cvsroot/python/python/dist/src/PCbuild In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv31309 Modified Files: Tag: release23-maint python20.wse Log Message: Changes for Python 2.3.4. Index: python20.wse =================================================================== RCS file: /cvsroot/python/python/dist/src/PCbuild/python20.wse,v retrieving revision 1.133.4.8 retrieving revision 1.133.4.9 diff -C2 -d -r1.133.4.8 -r1.133.4.9 *** python20.wse 12 May 2004 20:04:18 -0000 1.133.4.8 --- python20.wse 25 May 2004 18:50:10 -0000 1.133.4.9 *************** *** 2,6 **** item: Global Version=9.0 ! Title=Python 2.3.4c1 Flags=00010100 Languages=65 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 --- 2,6 ---- item: Global Version=9.0 ! Title=Python 2.3.4 Flags=00010100 Languages=65 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 *************** *** 21,27 **** MIF PDF Version=1.0 MIF SMS Version=2.0 ! EXE Filename=Python-2.3.4c1.exe Dialogs Version=8 ! Version File=2.3.4c1 Version Description=Python Programming Language Version Copyright=©2001-2004 Python Software Foundation --- 21,27 ---- MIF PDF Version=1.0 MIF SMS Version=2.0 ! EXE Filename=Python-2.3.4.exe Dialogs Version=8 ! Version File=2.3.4 Version Description=Python Programming Language Version Copyright=©2001-2004 Python Software Foundation *************** *** 82,86 **** item: Set Variable Variable=PYVER_STRING ! Value=2.3.4c1 end item: Remark --- 82,86 ---- item: Set Variable Variable=PYVER_STRING ! Value=2.3.4 end item: Remark

1 0

[Python-checkins] python/dist/src/Lib/distutils/command wininst.exe, 1.1.16.1, 1.1.16.2
by theller＠users.sourceforge.net May 25, 2004

May 25, 2004

Update of /cvsroot/python/python/dist/src/Lib/distutils/command In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv30771 Modified Files: Tag: release23-maint wininst.exe Log Message: This file no longer compressed with upx. Index: wininst.exe =================================================================== RCS file: /cvsroot/python/python/dist/src/Lib/distutils/command/Attic/wininst.exe,v retrieving revision 1.1.16.1 retrieving revision 1.1.16.2 diff -C2 -d -r1.1.16.1 -r1.1.16.2 Binary files /tmp/cvsC1AU1W and /tmp/cvsi7WOcD differ

1 0

python/dist/src/PCbuild pythoncore.dsp, 1.48.4.6, 1.48.4.7 BUILDno.txt, 1.51.4.6, 1.51.4.7
by theller＠users.sourceforge.net May 25, 2004

May 25, 2004

Update of /cvsroot/python/python/dist/src/PCbuild In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv29976 Modified Files: Tag: release23-maint pythoncore.dsp BUILDno.txt Log Message: Set release date for Python 2.3.4 (final). Windows build number is 53. Index: pythoncore.dsp =================================================================== RCS file: /cvsroot/python/python/dist/src/PCbuild/Attic/pythoncore.dsp,v retrieving revision 1.48.4.6 retrieving revision 1.48.4.7 diff -C2 -d -r1.48.4.6 -r1.48.4.7 *** pythoncore.dsp 12 May 2004 19:51:26 -0000 1.48.4.6 --- pythoncore.dsp 25 May 2004 18:43:54 -0000 1.48.4.7 *************** *** 259,263 **** SOURCE=..\Modules\getbuildinfo.c ! # ADD CPP /D BUILD=52 # End Source File # Begin Source File --- 259,263 ---- SOURCE=..\Modules\getbuildinfo.c ! # ADD CPP /D BUILD=53 # End Source File # Begin Source File Index: BUILDno.txt =================================================================== RCS file: /cvsroot/python/python/dist/src/PCbuild/BUILDno.txt,v retrieving revision 1.51.4.6 retrieving revision 1.51.4.7 diff -C2 -d -r1.51.4.6 -r1.51.4.7 *** BUILDno.txt 12 May 2004 19:51:26 -0000 1.51.4.6 --- BUILDno.txt 25 May 2004 18:43:54 -0000 1.51.4.7 *************** *** 34,37 **** --- 34,39 ---- Windows Python BUILD numbers ---------------------------- + 53 2.3.4 (final) + 27-May-2004 52 2.3.4c1 13-May-2004

1 0

python/dist/src/Misc/RPM python-2.3.spec, 1.2.12.10, 1.2.12.11
by theller＠users.sourceforge.net May 25, 2004

May 25, 2004

Update of /cvsroot/python/python/dist/src/Misc/RPM In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv29950 Modified Files: Tag: release23-maint python-2.3.spec Log Message: Set release date for Python 2.3.4 (final). Windows build number is 53. Index: python-2.3.spec =================================================================== RCS file: /cvsroot/python/python/dist/src/Misc/RPM/python-2.3.spec,v retrieving revision 1.2.12.10 retrieving revision 1.2.12.11 diff -C2 -d -r1.2.12.10 -r1.2.12.11 *** python-2.3.spec 19 May 2004 13:42:31 -0000 1.2.12.10 --- python-2.3.spec 25 May 2004 18:43:41 -0000 1.2.12.11 *************** *** 31,35 **** %define name python ! %define version 2.3.4c1 %define libvers 2.3 %define release 3pydotorg --- 31,35 ---- %define name python ! %define version 2.3.4 %define libvers 2.3 %define release 3pydotorg

1 0