Mailman 3 September 2003 - Python-checkins

python/nondist/peps pep-0008.txt, 1.19, 1.20 pep-0290.txt, 1.9, 1.10
by rhettinger＠users.sourceforge.net 26 Sep '03

26 Sep '03

Update of /cvsroot/python/python/nondist/peps In directory sc8-pr-cvs1:/tmp/cvs-serv4933 Modified Files: pep-0008.txt pep-0290.txt Log Message: * str.startwith() is less errorprone that slice comparisons but not as fast. * Fix minor typos. Index: pep-0008.txt =================================================================== RCS file: /cvsroot/python/python/nondist/peps/pep-0008.txt,v retrieving revision 1.19 retrieving revision 1.20 diff -C2 -d -r1.19 -r1.20 *** pep-0008.txt 22 Sep 2003 04:51:49 -0000 1.19 --- pep-0008.txt 27 Sep 2003 02:53:59 -0000 1.20 *************** *** 547,552 **** - Avoid slicing strings when checking for prefixes or suffixes. ! Use startswith() and endswith() instead, since they are faster, ! cleaner and less error prone. E.g.: No: if foo[:3] == 'bar': --- 547,552 ---- - Avoid slicing strings when checking for prefixes or suffixes. ! Use startswith() and endswith() instead, since they are ! cleaner and less error prone. For example: No: if foo[:3] == 'bar': Index: pep-0290.txt =================================================================== RCS file: /cvsroot/python/python/nondist/peps/pep-0290.txt,v retrieving revision 1.9 retrieving revision 1.10 diff -C2 -d -r1.9 -r1.10 *** pep-0290.txt 7 Mar 2003 00:21:42 -0000 1.9 --- pep-0290.txt 27 Sep 2003 02:53:59 -0000 1.10 *************** *** 121,125 **** In Python 2.3, apply() was marked for Pending Deprecation because it ! was made obsolete by the Python 1.6's introduction of * and ** in function calls. Using a direct function call was always a little faster than apply() because it saved the lookup for the builtin. --- 121,125 ---- In Python 2.3, apply() was marked for Pending Deprecation because it ! was made obsolete by Python 1.6's introduction of * and ** in function calls. Using a direct function call was always a little faster than apply() because it saved the lookup for the builtin. *************** *** 128,132 **** Pattern:: ! apply(f,args, kwds) --> f(*args, **kwds) --- 128,132 ---- Pattern:: ! apply(f, args, kwds) --> f(*args, **kwds) *************** *** 278,283 **** '''''''''''''''''''''''''''''''''''''''''''''' ! Use these string methods instead of slicing. They're faster because ! no slice has to be created, and there's no risk of miscounting. Pattern:: --- 278,283 ---- '''''''''''''''''''''''''''''''''''''''''''''' ! Use these string methods instead of slicing. No slice has to be ! created and there's no risk of miscounting. Pattern::

1 0

python/dist/src/Doc/dist sysconfig.tex, 1.1, 1.1.34.1
by anthonybaxter＠users.sourceforge.net 26 Sep '03

26 Sep '03

Update of /cvsroot/python/python/dist/src/Doc/dist In directory sc8-pr-cvs1:/tmp/cvs-serv18468 Modified Files: Tag: release23-maint sysconfig.tex Log Message: backport Typo: sys.prefex -> sys.prefix Closes SF# 812152 Index: sysconfig.tex =================================================================== RCS file: /cvsroot/python/python/dist/src/Doc/dist/sysconfig.tex,v retrieving revision 1.1 retrieving revision 1.1.34.1 diff -C2 -d -r1.1 -r1.1.34.1 *** sysconfig.tex 2 Aug 2001 15:12:07 -0000 1.1 --- sysconfig.tex 26 Sep 2003 16:47:16 -0000 1.1.34.1 *************** *** 25,33 **** \begin{datadesc}{PREFIX} ! The result of \code{os.path.normpath(sys.prefex)}. \end{datadesc} \begin{datadesc}{EXEC_PREFIX} ! The result of \code{os.path.normpath(sys.exec_prefex)}. \end{datadesc} --- 25,33 ---- \begin{datadesc}{PREFIX} ! The result of \code{os.path.normpath(sys.prefix)}. \end{datadesc} \begin{datadesc}{EXEC_PREFIX} ! The result of \code{os.path.normpath(sys.exec_prefix)}. \end{datadesc}

1 0

python/dist/src/Doc/lib liblogging.tex, 1.12.8.1, 1.12.8.2
by anthonybaxter＠users.sourceforge.net 26 Sep '03

26 Sep '03

Update of /cvsroot/python/python/dist/src/Doc/lib In directory sc8-pr-cvs1:/tmp/cvs-serv18265 Modified Files: Tag: release23-maint liblogging.tex Log Message: backport [Bug #812936] Correct the documentation for RotatingFileHandler. Index: liblogging.tex =================================================================== RCS file: /cvsroot/python/python/dist/src/Doc/lib/liblogging.tex,v retrieving revision 1.12.8.1 retrieving revision 1.12.8.2 diff -C2 -d -r1.12.8.1 -r1.12.8.2 *** liblogging.tex 1 Sep 2003 22:52:14 -0000 1.12.8.1 --- liblogging.tex 26 Sep 2003 16:46:22 -0000 1.12.8.2 *************** *** 500,516 **** specified file is opened and used as the stream for logging. If \var{mode} is not specified, \code{'a'} is used. By default, the ! file grows indefinitely. You can use the \var{maxBytes} and \var{backupCount} values to allow the file to \dfn{rollover} at a predetermined size. When the size is about to be exceeded, the file is ! closed and a new file opened for output, transparently to the ! caller. Rollover occurs whenever the current log file is nearly ! \var{maxBytes} in length. If \var{backupCount} is >= 1, the system ! will successively create new files with the same pathname as the base ! file, but with extensions ".1", ".2" etc. appended to it. For example, ! with a backupCount of 5 and a base file name of "app.log", you would ! get "app.log", "app.log.1", "app.log.2", ... through to ! "app.log.5". When the last file reaches its size limit, the logging ! reverts to "app.log" which is truncated to zero length. If ! \var{maxBytes} is zero, rollover never occurs. \end{classdesc} --- 500,520 ---- specified file is opened and used as the stream for logging. If \var{mode} is not specified, \code{'a'} is used. By default, the ! file grows indefinitely. ! ! You can use the \var{maxBytes} and \var{backupCount} values to allow the file to \dfn{rollover} at a predetermined size. When the size is about to be exceeded, the file is ! closed and a new file is silently opened for output. Rollover occurs ! whenever the current log file is nearly \var{maxBytes} in length; if ! \var{maxBytes} is zero, rollover never occurs. If \var{backupCount} ! is non-zero, the system will save old log files by appending the ! extensions ".1", ".2" etc., to the filename. For example, with ! a \var{backupCount} of 5 and a base file name of ! \file{app.log}, you would get \file{app.log}, ! \file{app.log.1}, \file{app.log.2}, up to \file{app.log.5}. The file being ! written to is always \file{app.log}. When this file is filled, it is ! closed and renamed to \file{app.log.1}, and if files \file{app.log.1}, ! \file{app.log.2}, etc. exist, then they are renamed to \file{app.log.2}, ! \file{app.log.3} etc. respectively. \end{classdesc}

1 0

python/nondist/peps pep-0322.txt,1.3,1.4
by rhettinger＠users.sourceforge.net 26 Sep '03

26 Sep '03

Update of /cvsroot/python/python/nondist/peps In directory sc8-pr-cvs1:/tmp/cvs-serv11227 Modified Files: pep-0322.txt Log Message: Rename the proposal to ireverse(). Index: pep-0322.txt =================================================================== RCS file: /cvsroot/python/python/nondist/peps/pep-0322.txt,v retrieving revision 1.3 retrieving revision 1.4 diff -C2 -d -r1.3 -r1.4 *** pep-0322.txt 26 Sep 2003 03:07:56 -0000 1.3 --- pep-0322.txt 26 Sep 2003 16:09:54 -0000 1.4 *************** *** 47,59 **** ======== ! Add a method called *iter_backwards()* to sequence objects that can benefit from it. The above examples then simplify to:: ! for i in xrange(n).iter_backwards(): print seqn[i] :: ! for elem in seqn.iter_backwards(): print elem --- 47,59 ---- ======== ! Add a method called *ireverse()* to sequence objects that can benefit from it. The above examples then simplify to:: ! for i in xrange(n).ireverse(): print seqn[i] :: ! for elem in seqn.ireverse(): print elem *************** *** 105,109 **** and clearer with:: ! for func, target, kargs in _exithandlers.iter_backwards(): . . . del _exithandlers --- 105,109 ---- and clearer with:: ! for func, target, kargs in _exithandlers.ireverse(): . . . del _exithandlers *************** *** 132,136 **** result.sort() ! return [x for score, x in result[-n:].iter_backwards()] * heapq.heapify() uses ``for i in xrange(n//2 - 1, -1, -1)`` because --- 132,136 ---- result.sort() ! return [x for score, x in result[-n:].ireverse()] * heapq.heapify() uses ``for i in xrange(n//2 - 1, -1, -1)`` because *************** *** 159,163 **** be run in a forward direction but is less intuitive and rarely presented that way in literature. The replacement code ! ``for i in xrange(1, len(x)).iter_backwards()`` is much easier to mentally verify. --- 159,163 ---- be run in a forward direction but is less intuitive and rarely presented that way in literature. The replacement code ! ``for i in xrange(1, len(x)).ireverse()`` is much easier to mentally verify.

1 0

python/dist/src/Doc/lib liblogging.tex,1.13,1.14
by akuchling＠users.sourceforge.net 26 Sep '03

26 Sep '03

Update of /cvsroot/python/python/dist/src/Doc/lib In directory sc8-pr-cvs1:/tmp/cvs-serv15151 Modified Files: liblogging.tex Log Message: [Bug #812936] Correct the documentation for RotatingFileHandler. [2.3 bugfix candidate] Index: liblogging.tex =================================================================== RCS file: /cvsroot/python/python/dist/src/Doc/lib/liblogging.tex,v retrieving revision 1.13 retrieving revision 1.14 diff -C2 -d -r1.13 -r1.14 *** liblogging.tex 1 Sep 2003 22:50:52 -0000 1.13 --- liblogging.tex 26 Sep 2003 13:45:18 -0000 1.14 *************** *** 500,516 **** specified file is opened and used as the stream for logging. If \var{mode} is not specified, \code{'a'} is used. By default, the ! file grows indefinitely. You can use the \var{maxBytes} and \var{backupCount} values to allow the file to \dfn{rollover} at a predetermined size. When the size is about to be exceeded, the file is ! closed and a new file opened for output, transparently to the ! caller. Rollover occurs whenever the current log file is nearly ! \var{maxBytes} in length. If \var{backupCount} is >= 1, the system ! will successively create new files with the same pathname as the base ! file, but with extensions ".1", ".2" etc. appended to it. For example, ! with a backupCount of 5 and a base file name of "app.log", you would ! get "app.log", "app.log.1", "app.log.2", ... through to ! "app.log.5". When the last file reaches its size limit, the logging ! reverts to "app.log" which is truncated to zero length. If ! \var{maxBytes} is zero, rollover never occurs. \end{classdesc} --- 500,520 ---- specified file is opened and used as the stream for logging. If \var{mode} is not specified, \code{'a'} is used. By default, the ! file grows indefinitely. ! ! You can use the \var{maxBytes} and \var{backupCount} values to allow the file to \dfn{rollover} at a predetermined size. When the size is about to be exceeded, the file is ! closed and a new file is silently opened for output. Rollover occurs ! whenever the current log file is nearly \var{maxBytes} in length; if ! \var{maxBytes} is zero, rollover never occurs. If \var{backupCount} ! is non-zero, the system will save old log files by appending the ! extensions ".1", ".2" etc., to the filename. For example, with ! a \var{backupCount} of 5 and a base file name of ! \file{app.log}, you would get \file{app.log}, ! \file{app.log.1}, \file{app.log.2}, up to \file{app.log.5}. The file being ! written to is always \file{app.log}. When this file is filled, it is ! closed and renamed to \file{app.log.1}, and if files \file{app.log.1}, ! \file{app.log.2}, etc. exist, then they are renamed to \file{app.log.2}, ! \file{app.log.3} etc. respectively. \end{classdesc}

1 0

python/nondist/peps pep-0322.txt,1.2,1.3
by rhettinger＠users.sourceforge.net 25 Sep '03

25 Sep '03

Update of /cvsroot/python/python/nondist/peps In directory sc8-pr-cvs1:/tmp/cvs-serv478 Modified Files: pep-0322.txt Log Message: Fix typos. Index: pep-0322.txt =================================================================== RCS file: /cvsroot/python/python/nondist/peps/pep-0322.txt,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -d -r1.2 -r1.3 *** pep-0322.txt 25 Sep 2003 16:18:28 -0000 1.2 --- pep-0322.txt 26 Sep 2003 03:07:56 -0000 1.3 *************** *** 16,20 **** This proposal is to extend the API of several sequence types ! to include methods for iterating over the sequence in reverse. --- 16,20 ---- This proposal is to extend the API of several sequence types ! to include a method for iterating over the sequence in reverse. *************** *** 182,186 **** - fallback to: ``for i in xrange(len(obj)-1,-1,-1): yield obj[i]`` ! - fallback to: ``for i in itertools.count(): yield[obj[-i]]`` - fallback to: ``tmp=list(obj); tmp.reverse(); return iter(tmp)`` --- 182,186 ---- - fallback to: ``for i in xrange(len(obj)-1,-1,-1): yield obj[i]`` ! - fallback to: ``for i in itertools.count(): yield obj[-i]`` - fallback to: ``tmp=list(obj); tmp.reverse(); return iter(tmp)``

1 0

python/dist/src/Doc/lib libasynchat.tex, NONE, 1.3.18.1 lib.tex, 1.200, 1.200.4.1
by akuchling＠users.sourceforge.net 25 Sep '03

25 Sep '03

Update of /cvsroot/python/python/dist/src/Doc/lib In directory sc8-pr-cvs1:/tmp/cvs-serv22585 Modified Files: Tag: release22-maint lib.tex Added Files: Tag: release22-maint libasynchat.tex Log Message: [Bug #811681] The asynchat documentation would also apply to the 2.2 version of the module, but the docs aren't included. This adds a copy of libasynchat.tex. --- NEW FILE: libasynchat.tex --- \section{\module{asynchat} --- Asynchronous socket command/response handler} \declaremodule{standard}{asynchat} \modulesynopsis{Support for asynchronous command/response protocols.} \moduleauthor{Sam Rushing}{rushing(a)nightmare.com} \sectionauthor{Steve Holden}{sholden(a)holdenweb.com} This module builds on the \refmodule{asyncore} infrastructure, simplifying asynchronous clients and servers and making it easier to handle protocols whose elements are terminated by arbitrary strings, or are of variable length. \refmodule{asynchat} defines the abstract class \class{async_chat} that you subclass, providing implementations of the \method{collect_incoming_data()} and \method{found_terminator()} methods. It uses the same asynchronous loop as \refmodule{asyncore}, and the two types of channel, \class{asyncore.dispatcher} and \class{asynchat.async_chat}, can freely be mixed in the channel map. Typically an \class{asyncore.dispatcher} server channel generates new \class{asynchat.async_chat} channel objects as it receives incoming connection requests. \begin{classdesc}{async_chat}{} This class is an abstract subclass of \class{asyncore.dispatcher}. To make practical use of the code you must subclass \class{async_chat}, providing meaningful \method{collect_incoming_data()} and \method{found_terminator()} methods. The \class{asyncore.dispatcher} methods can be used, although not all make sense in a message/response context. Like \class{asyncore.dispatcher}, \class{async_chat} defines a set of events that are generated by an analysis of socket conditions after a \cfunction{select()} call. Once the polling loop has been started the \class{async_chat} object's methods are called by the event-processing framework with no action on the part of the programmer. Unlike \class{asyncore.dispatcher}, \class{async_chat} allows you to define a first-in-first-out queue (fifo) of \emph{producers}. A producer need have only one method, \method{more()}, which should return data to be transmitted on the channel. The producer indicates exhaustion (\emph{i.e.} that it contains no more data) by having its \method{more()} method return the empty string. At this point the \class{async_chat} object removes the producer from the fifo and starts using the next producer, if any. When the producer fifo is empty the \method{handle_write()} method does nothing. You use the channel object's \method{set_terminator()} method to describe how to recognize the end of, or an important breakpoint in, an incoming transmission from the remote endpoint. To build a functioning \class{async_chat} subclass your input methods \method{collect_incoming_data()} and \method{found_terminator()} must handle the data that the channel receives asynchronously. The methods are described below. \end{classdesc} \begin{methoddesc}{close_when_done}{} Pushes a \code{None} on to the producer fifo. When this producer is popped off the fifo it causes the channel to be closed. \end{methoddesc} \begin{methoddesc}{collect_incoming_data}{data} Called with \var{data} holding an arbitrary amount of received data. The default method, which must be overridden, raises a \exception{NotImplementedError} exception. \end{methoddesc} \begin{methoddesc}{discard_buffers}{} In emergencies this method will discard any data held in the input and/or output buffers and the producer fifo. \end{methoddesc} \begin{methoddesc}{found_terminator}{} Called when the incoming data stream matches the termination condition set by \method{set_terminator}. The default method, which must be overridden, raises a \exception{NotImplementedError} exception. The buffered input data should be available via an instance attribute. \end{methoddesc} \begin{methoddesc}{get_terminator}{} Returns the current terminator for the channel. \end{methoddesc} \begin{methoddesc}{handle_close}{} Called when the channel is closed. The default method silently closes the channel's socket. \end{methoddesc} \begin{methoddesc}{handle_read}{} Called when a read event fires on the channel's socket in the asynchronous loop. The default method checks for the termination condition established by \method{set_terminator()}, which can be either the appearance of a particular string in the input stream or the receipt of a particular number of characters. When the terminator is found, \method{handle_read} calls the \method{found_terminator()} method after calling \method{collect_incoming_data()} with any data preceding the terminating condition. \end{methoddesc} \begin{methoddesc}{handle_write}{} Called when the application may write data to the channel. The default method calls the \method{initiate_send()} method, which in turn will call \method{refill_buffer()} to collect data from the producer fifo associated with the channel. \end{methoddesc} \begin{methoddesc}{push}{data} Creates a \class{simple_producer} object (\emph{see below}) containing the data and pushes it on to the channel's \code{producer_fifo} to ensure its transmission. This is all you need to do to have the channel write the data out to the network, although it is possible to use your own producers in more complex schemes to implement encryption and chunking, for example. \end{methoddesc} \begin{methoddesc}{push_with_producer}{producer} Takes a producer object and adds it to the producer fifo associated with the channel. When all currently-pushed producers have been exhausted the channel will consume this producer's data by calling its \method{more()} method and send the data to the remote endpoint. \end{methoddesc} \begin{methoddesc}{readable}{} Should return \code{True} for the channel to be included in the set of channels tested by the \cfunction{select()} loop for readability. \end{methoddesc} \begin{methoddesc}{refill_buffer}{} Refills the output buffer by calling the \method{more()} method of the producer at the head of the fifo. If it is exhausted then the producer is popped off the fifo and the next producer is activated. If the current producer is, or becomes, \code{None} then the channel is closed. \end{methoddesc} \begin{methoddesc}{set_terminator}{term} Sets the terminating condition to be recognised on the channel. \code{term} may be any of three types of value, corresponding to three different ways to handle incoming protocol data. \begin{tableii}{l|l}{}{term}{Description} \lineii{\emph{string}}{Will call \method{found_terminator()} when the string is found in the input stream} \lineii{\emph{integer}}{Will call \method{found_terminator()} when the indicated number of characters have been received} \lineii{\code{None}}{The channel continues to collect data forever} \end{tableii} Note that any data following the terminator will be available for reading by the channel after \method{found_terminator()} is called. \end{methoddesc} \begin{methoddesc}{writable}{} Should return \code{True} as long as items remain on the producer fifo, or the channel is connected and the channel's output buffer is non-empty. \end{methoddesc} \subsection{asynchat - Auxiliary Classes and Functions} \begin{classdesc}{simple_producer}{data\optional{, buffer_size=512}} A \class{simple_producer} takes a chunk of data and an optional buffer size. Repeated calls to its \method{more()} method yield successive chunks of the data no larger than \var{buffer_size}. \end{classdesc} \begin{methoddesc}{more}{} Produces the next chunk of information from the producer, or returns the empty string. \end{methoddesc} \begin{classdesc}{fifo}{\optional{list=None}} Each channel maintains a \class{fifo} holding data which has been pushed by the application but not yet popped for writing to the channel. A \class{fifo} is a list used to hold data and/or producers until they are required. If the \var{list} argument is provided then it should contain producers or data items to be written to the channel. \end{classdesc} \begin{methoddesc}{is_empty}{} Returns \code{True} iff the fifo is empty. \end{methoddesc} \begin{methoddesc}{first}{} Returns the least-recently \method{push()}ed item from the fifo. \end{methoddesc} \begin{methoddesc}{push}{data} Adds the given data (which may be a string or a producer object) to the producer fifo. \end{methoddesc} \begin{methoddesc}{pop}{} If the fifo is not empty, returns \code{True, first()}, deleting the popped item. Returns \code{False, None} for an empty fifo. \end{methoddesc} The \module{asynchat} module also defines one utility function, which may be of use in network and textual analysis operations. \begin{funcdesc}{find_prefix_at_end}{haystack, needle} Returns \code{True} if string \var{haystack} ends with any non-empty prefix of string \var{needle}. \end{funcdesc} \subsection{asynchat Example \label{asynchat-example}} The following partial example shows how HTTP requests can be read with \class{async_chat}. A web server might create an \class{http_request_handler} object for each incoming client connection. Notice that initially the channel terminator is set to match the blank line at the end of the HTTP headers, and a flag indicates that the headers are being read. Once the headers have been read, if the request is of type POST (indicating that further data are present in the input stream) then the \code{Content-Length:} header is used to set a numeric terminator to read the right amount of data from the channel. The \method{handle_request()} method is called once all relevant input has been marshalled, after setting the channel terminator to \code{None} to ensure that any extraneous data sent by the web client are ignored. \begin{verbatim} class http_request_handler(asynchat.async_chat): def __init__(self, conn, addr, sessions, log): asynchat.async_chat.__init__(self, conn=conn) self.addr = addr self.sessions = sessions self.ibuffer = [] self.obuffer = "" self.set_terminator("\r\n\r\n") self.reading_headers = True self.handling = False self.cgi_data = None self.log = log def collect_incoming_data(self, data): """Buffer the data""" self.ibuffer.append(data) def found_terminator(self): if self.reading_headers: self.reading_headers = False self.parse_headers("".join(self.ibuffer)) self.ibuffer = [] if self.op.upper() == "POST": clen = self.headers.getheader("content-length") self.set_terminator(int(clen)) else: self.handling = True self.set_terminator(None) self.handle_request() elif not self.handling: self.set_terminator(None) # browsers sometimes over-send self.cgi_data = parse(self.headers, "".join(self.ibuffer)) self.handling = True self.ibuffer = [] self.handle_request() \end{verbatim} Index: lib.tex =================================================================== RCS file: /cvsroot/python/python/dist/src/Doc/lib/lib.tex,v retrieving revision 1.200 retrieving revision 1.200.4.1 diff -C2 -d -r1.200 -r1.200.4.1 *** lib.tex 18 Dec 2001 16:32:30 -0000 1.200 --- lib.tex 25 Sep 2003 18:25:51 -0000 1.200.4.1 *************** *** 217,220 **** --- 217,221 ---- \input{libsimplexmlrpc} \input{libasyncore} + \input{libasynchat} \input{netdata} % Internet Data Handling

1 0

python/nondist/peps pep-0322.txt,1.1,1.2
by rhettinger＠users.sourceforge.net 25 Sep '03

25 Sep '03

Update of /cvsroot/python/python/nondist/peps In directory sc8-pr-cvs1:/tmp/cvs-serv11222 Modified Files: pep-0322.txt Log Message: Updated to reflect comments on comp.lang.python. Index: pep-0322.txt =================================================================== RCS file: /cvsroot/python/python/nondist/peps/pep-0322.txt,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** pep-0322.txt 24 Sep 2003 10:30:08 -0000 1.1 --- pep-0322.txt 25 Sep 2003 16:18:28 -0000 1.2 *************** *** 30,35 **** One other current approach involves reversing a list before iterating over it. That technique wastes computer cycles, memory, and lines of ! code. Also, it only works with lists (strings, for example, do not ! define a reverse method):: rseqn = list(seqn) --- 30,34 ---- One other current approach involves reversing a list before iterating over it. That technique wastes computer cycles, memory, and lines of ! code:: rseqn = list(seqn) *************** *** 38,43 **** print value ! Extending slicing minimizes the code overhead but does nothing for ! memory efficiency, beauty, or clarity. Reverse iteration is much less common than forward iteration, but it --- 37,42 ---- print value ! Extending slicing is a third approach that minimizes the code overhead ! but does nothing for memory efficiency, beauty, or clarity. Reverse iteration is much less common than forward iteration, but it *************** *** 110,113 **** --- 109,115 ---- del _exithandlers + Note, if the order of deletion is important, then the first form + is still needed. + * difflib.get_close_matches() uses:: *************** *** 150,159 **** ``for n in range(len(verfiles)-1,-1,-1)`` because the loop deletes selected elements from *verfiles* but needs to leave the rest of ! the list intact for further iteration. This use case could be ! addressed with *itertools.ifilter()* but would require the ! selection predicate to be in a *lambda* expression. The net ! result is less clear and readable than the original. A better ! reformulation is to replace the first line with the proposed ! method. * random.shuffle() uses ``for i in xrange(len(x)-1, 0, -1)`` because --- 152,156 ---- ``for n in range(len(verfiles)-1,-1,-1)`` because the loop deletes selected elements from *verfiles* but needs to leave the rest of ! the list intact for further iteration. * random.shuffle() uses ``for i in xrange(len(x)-1, 0, -1)`` because *************** *** 161,165 **** elements from an ever diminishing pool. In fact, the algorithm can be run in a forward direction but is less intuitive and rarely ! presented that way in literature. * rfc822.Message.__delitem__() uses:: --- 158,164 ---- elements from an ever diminishing pool. In fact, the algorithm can be run in a forward direction but is less intuitive and rarely ! presented that way in literature. The replacement code ! ``for i in xrange(1, len(x)).iter_backwards()`` is much easier ! to mentally verify. * rfc822.Message.__delitem__() uses:: *************** *** 173,193 **** ! Rejected Alternative Ideas ! ========================== ! * Add a builtin function, *reverse()* which calls a magic method, ! __riter__. I see this as more overhead for no additional benefit. ! * Add a builtin function, *reverse()* which does the above, and ! if *__riter__* is not found, constructs its own using ! *__getitem__*, and if *__getitem__* is not found, builds a list ! from *__iter__* and returns a reverse iterator over the new list. ! The advantage is that one function takes care of almost everything ! that is potentially reversible. A disadvantage is that it can ! invisibility slip in to a low performance mode (in terms of time ! and memory) which would be more visible with an explicit ! ``list(obj).reverse()``. Another problem is that *__getitem__* ! is also used in mappings as well as sequences and that could lead ! to bizarre results. --- 172,201 ---- ! Alternative Ideas ! ================= ! * Add a builtin function, *riter()* which calls a magic method, ! *__riter__*. I see this as more overhead for no additional benefit. ! * Several variants were submitted that provided fallback behavior ! when *__riter__* is not defined: ! ! - fallback to: ``for i in xrange(len(obj)-1,-1,-1): yield obj[i]`` ! - fallback to: ``for i in itertools.count(): yield[obj[-i]]`` ! - fallback to: ``tmp=list(obj); tmp.reverse(); return iter(tmp)`` ! ! All of these attempt to save implementing some object methods at the ! expense of adding a new builtin function and of creating a new magic ! method name. ! ! The approaches using *__getitem__()* are slower than using a custom ! method for each object. Also, the *__getitem__()* variants produce ! bizarre results when applied to mappings. ! ! All of the variants crash when applied to an infinite iterator. ! ! The last variant can invisibly slip into a low performance mode ! (in terms of time and memory) which could be made more visible with ! an explicit ``list(obj).reverse()``.

1 0

python/dist/src/Doc Makefile,1.264,1.265
by fdrake＠users.sourceforge.net 25 Sep '03

25 Sep '03

Update of /cvsroot/python/python/dist/src/Doc In directory sc8-pr-cvs1:/tmp/cvs-serv30827 Modified Files: Makefile Log Message: define a variable to specify the mkhowto program itself, as for any other application Index: Makefile =================================================================== RCS file: /cvsroot/python/python/dist/src/Doc/Makefile,v retrieving revision 1.264 retrieving revision 1.265 diff -C2 -d -r1.264 -r1.265 *** Makefile 30 Jul 2003 19:14:54 -0000 1.264 --- Makefile 25 Sep 2003 15:25:37 -0000 1.265 *************** *** 72,88 **** DVIPS= dvips -N0 -t $(PAPER) ! MKDVI= $(PYTHON) ../tools/mkhowto --paper=$(PAPER) --dvi ! MKHTML= $(PYTHON) tools/mkhowto --html --about html/stdabout.dat \ --iconserver ../icons --favicon ../icons/pyfav.gif \ --address $(PYTHONDOCS) --up-link ../index.html \ --up-title "Python Documentation Index" \ --global-module-index "../modindex.html" --dvips-safe ! MKISILOHTML=$(PYTHON) tools/mkhowto --html --about html/stdabout.dat \ --iconserver ../icons \ --l2h-init perl/isilo.perl --numeric --split 1 \ --dvips-safe MKISILO= iSilo386 -U -y -rCR -d0 ! MKPDF= $(PYTHON) ../tools/mkhowto --paper=$(PAPER) --pdf ! MKPS= $(PYTHON) ../tools/mkhowto --paper=$(PAPER) --ps BUILDINDEX=$(TOOLSDIR)/buildindex.py --- 72,90 ---- DVIPS= dvips -N0 -t $(PAPER) ! MKHOWTO= $(PYTHON) ../tools/mkhowto ! ! MKDVI= $(MKHOWTO) --paper=$(PAPER) --dvi ! MKHTML= $(MKHOWTO) --html --about html/stdabout.dat \ --iconserver ../icons --favicon ../icons/pyfav.gif \ --address $(PYTHONDOCS) --up-link ../index.html \ --up-title "Python Documentation Index" \ --global-module-index "../modindex.html" --dvips-safe ! MKISILOHTML=$(MKHOWTO) --html --about html/stdabout.dat \ --iconserver ../icons \ --l2h-init perl/isilo.perl --numeric --split 1 \ --dvips-safe MKISILO= iSilo386 -U -y -rCR -d0 ! MKPDF= $(MKHOWTO) --paper=$(PAPER) --pdf ! MKPS= $(MKHOWTO) --paper=$(PAPER) --ps BUILDINDEX=$(TOOLSDIR)/buildindex.py

1 0

python/dist/src configure, 1.416.4.5, 1.416.4.6 configure.in, 1.427.4.5, 1.427.4.6 pyconfig.h.in, 1.83.4.2, 1.83.4.3
by montanaro＠users.sourceforge.net 25 Sep '03

25 Sep '03

Update of /cvsroot/python/python/dist/src In directory sc8-pr-cvs1:/tmp/cvs-serv29772 Modified Files: Tag: release23-maint configure configure.in pyconfig.h.in Log Message: backport of HAVE_FSYNC fix Index: configure =================================================================== RCS file: /cvsroot/python/python/dist/src/configure,v retrieving revision 1.416.4.5 retrieving revision 1.416.4.6 diff -C2 -d -r1.416.4.5 -r1.416.4.6 *** configure 20 Sep 2003 15:29:40 -0000 1.416.4.5 --- configure 25 Sep 2003 15:20:55 -0000 1.416.4.6 *************** *** 1,4 **** #! /bin/sh ! # From configure.in Revision: 1.427.4.4 . # Guess values for system-dependent variables and create Makefiles. # Generated by GNU Autoconf 2.57 for python 2.3. --- 1,4 ---- #! /bin/sh ! # From configure.in Revision: 1.427.4.5 . # Guess values for system-dependent variables and create Makefiles. # Generated by GNU Autoconf 2.57 for python 2.3. *************** *** 13385,13389 **** cat >>confdefs.h <<\_ACEOF ! #define HAVE_SYNC 1 _ACEOF --- 13385,13389 ---- cat >>confdefs.h <<\_ACEOF ! #define HAVE_FSYNC 1 _ACEOF Index: configure.in =================================================================== RCS file: /cvsroot/python/python/dist/src/configure.in,v retrieving revision 1.427.4.5 retrieving revision 1.427.4.6 diff -C2 -d -r1.427.4.5 -r1.427.4.6 *** configure.in 20 Sep 2003 15:29:42 -0000 1.427.4.5 --- configure.in 25 Sep 2003 15:21:00 -0000 1.427.4.6 *************** *** 2094,2098 **** AC_MSG_CHECKING(for fsync) AC_TRY_COMPILE([#include <unistd.h>], void *x=fsync, ! AC_DEFINE(HAVE_SYNC, 1, Define if you have the 'fsync' function.) AC_MSG_RESULT(yes), AC_MSG_RESULT(no) --- 2094,2098 ---- AC_MSG_CHECKING(for fsync) AC_TRY_COMPILE([#include <unistd.h>], void *x=fsync, ! AC_DEFINE(HAVE_FSYNC, 1, Define if you have the 'fsync' function.) AC_MSG_RESULT(yes), AC_MSG_RESULT(no) Index: pyconfig.h.in =================================================================== RCS file: /cvsroot/python/python/dist/src/pyconfig.h.in,v retrieving revision 1.83.4.2 retrieving revision 1.83.4.3 diff -C2 -d -r1.83.4.2 -r1.83.4.3 *** pyconfig.h.in 20 Sep 2003 15:29:42 -0000 1.83.4.2 --- pyconfig.h.in 25 Sep 2003 15:21:00 -0000 1.83.4.3 *************** *** 487,491 **** /* Define if you have the 'fsync' function. */ ! #undef HAVE_SYNC /* Define to 1 if you have the `sysconf' function. */ --- 487,491 ---- /* Define if you have the 'fsync' function. */ ! #undef HAVE_FSYNC /* Define to 1 if you have the `sysconf' function. */

1 0