Mailman 3 December 2005 - Python-checkins

commit of r41831 - python/branches/release24-maint/Doc/tut/tut.tex
by reinhold.birkenfeld Dec. 27, 2005

Dec. 27, 2005

Author: reinhold.birkenfeld Date: Tue Dec 27 01:06:18 2005 New Revision: 41831 Modified: python/branches/release24-maint/Doc/tut/tut.tex Log: Bug #1375599: Correct grammar error in tutorial Modified: python/branches/release24-maint/Doc/tut/tut.tex ============================================================================== --- python/branches/release24-maint/Doc/tut/tut.tex (original) +++ python/branches/release24-maint/Doc/tut/tut.tex Tue Dec 27 01:06:18 2005 @@ -114,7 +114,7 @@ programs, or to test functions during bottom-up program development. It is also a handy desk calculator. -Python enables programs to written compactly and readably. Programs +Python enables programs to be written compactly and readably. Programs written in Python are typically much shorter than equivalent C or \Cpp{} programs, for several reasons: \begin{itemize}

1 0

commit of r41829 - python/trunk/Doc/lib/libwinreg.tex
by reinhold.birkenfeld Dec. 27, 2005

Dec. 27, 2005

Author: reinhold.birkenfeld Date: Tue Dec 27 01:03:18 2005 New Revision: 41829 Modified: python/trunk/Doc/lib/libwinreg.tex Log: Bug #1386675: winreg raises WindowsErrors Modified: python/trunk/Doc/lib/libwinreg.tex ============================================================================== --- python/trunk/Doc/lib/libwinreg.tex (original) +++ python/trunk/Doc/lib/libwinreg.tex Tue Dec 27 01:03:18 2005 @@ -42,7 +42,7 @@ \var{key} is the predefined handle to connect to. The return value is the handle of the opened key. - If the function fails, an \exception{EnvironmentError} exception is + If the function fails, an \exception{WindowsError} exception is raised. \end{funcdesc} @@ -63,7 +63,7 @@ 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, an \exception{EnvironmentError} exception is + If the function fails, an \exception{WindowsError} exception is raised. \end{funcdesc} @@ -80,7 +80,7 @@ \emph{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, an \exception{EnvironmentError} + is removed. If the method fails, an \exception{WindowsError} exception is raised. \end{funcdesc} @@ -106,7 +106,7 @@ The function retrieves the name of one subkey each time it is called. It is typically called repeatedly until an - \exception{EnvironmentError} exception + \exception{WindowsError} exception is raised, indicating, no more values are available. \end{funcdesc} @@ -122,7 +122,7 @@ The function retrieves the name of one subkey each time it is called. It is typically called repeatedly, until an - \exception{EnvironmentError} exception is raised, indicating + \exception{WindowsError} exception is raised, indicating no more values. The result is a tuple of 3 items: @@ -201,7 +201,7 @@ The result is a new handle to the specified key - If the function fails, \exception{EnvironmentError} is raised. + If the function fails, \exception{WindowsError} is raised. \end{funcdesc}

1 0

commit of r41830 - python/branches/release24-maint/Doc/lib/libwinreg.tex
by reinhold.birkenfeld Dec. 27, 2005

Dec. 27, 2005

Author: reinhold.birkenfeld Date: Tue Dec 27 01:03:19 2005 New Revision: 41830 Modified: python/branches/release24-maint/Doc/lib/libwinreg.tex Log: Bug #1386675: winreg raises WindowsErrors (backport) Modified: python/branches/release24-maint/Doc/lib/libwinreg.tex ============================================================================== --- python/branches/release24-maint/Doc/lib/libwinreg.tex (original) +++ python/branches/release24-maint/Doc/lib/libwinreg.tex Tue Dec 27 01:03:19 2005 @@ -42,7 +42,7 @@ \var{key} is the predefined handle to connect to. The return value is the handle of the opened key. - If the function fails, an \exception{EnvironmentError} exception is + If the function fails, an \exception{WindowsError} exception is raised. \end{funcdesc} @@ -63,7 +63,7 @@ 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, an \exception{EnvironmentError} exception is + If the function fails, an \exception{WindowsError} exception is raised. \end{funcdesc} @@ -80,7 +80,7 @@ \emph{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, an \exception{EnvironmentError} + is removed. If the method fails, an \exception{WindowsError} exception is raised. \end{funcdesc} @@ -106,7 +106,7 @@ The function retrieves the name of one subkey each time it is called. It is typically called repeatedly until an - \exception{EnvironmentError} exception + \exception{WindowsError} exception is raised, indicating, no more values are available. \end{funcdesc} @@ -122,7 +122,7 @@ The function retrieves the name of one subkey each time it is called. It is typically called repeatedly, until an - \exception{EnvironmentError} exception is raised, indicating + \exception{WindowsError} exception is raised, indicating no more values. The result is a tuple of 3 items: @@ -201,7 +201,7 @@ The result is a new handle to the specified key - If the function fails, \exception{EnvironmentError} is raised. + If the function fails, \exception{WindowsError} is raised. \end{funcdesc}

1 0

commit of r41828 - python/branches/release24-maint/Doc/lib/libstdtypes.tex
by reinhold.birkenfeld Dec. 26, 2005

Dec. 26, 2005

Author: reinhold.birkenfeld Date: Tue Dec 27 00:56:08 2005 New Revision: 41828 Modified: python/branches/release24-maint/Doc/lib/libstdtypes.tex Log: Bug #1389673: document correct return value of set methods (backport) Modified: python/branches/release24-maint/Doc/lib/libstdtypes.tex ============================================================================== --- python/branches/release24-maint/Doc/lib/libstdtypes.tex (original) +++ python/branches/release24-maint/Doc/lib/libstdtypes.tex Tue Dec 27 00:56:08 2005 @@ -1261,17 +1261,17 @@ \begin{tableiii}{c|c|l}{code}{Operation}{Equivalent}{Result} \lineiii{\var{s}.update(\var{t})} {\var{s} |= \var{t}} - {return set \var{s} with elements added from \var{t}} + {update set \var{s}, adding elements from \var{t}} \lineiii{\var{s}.intersection_update(\var{t})} {\var{s} \&= \var{t}} - {return set \var{s} keeping only elements also found in \var{t}} + {update set \var{s}, keeping only elements found in both \var{s} and \var{t}} \lineiii{\var{s}.difference_update(\var{t})} {\var{s} -= \var{t}} - {return set \var{s} after removing elements found in \var{t}} + {update set \var{s}, removing elements found in \var{t}} \lineiii{\var{s}.symmetric_difference_update(\var{t})} {\var{s} \textasciicircum= \var{t}} - {return set \var{s} with elements from \var{s} or \var{t} - but not both} + {update set \var{s}, keeping only elements found in either \var{s} or \var{t} + but not in both} \hline \lineiii{\var{s}.add(\var{x})}{}

1 0

commit of r41827 - python/trunk/Doc/lib/libstdtypes.tex
by reinhold.birkenfeld Dec. 26, 2005

Dec. 26, 2005

Author: reinhold.birkenfeld Date: Tue Dec 27 00:55:56 2005 New Revision: 41827 Modified: python/trunk/Doc/lib/libstdtypes.tex Log: Bug #1389673: document correct return value of set methods Modified: python/trunk/Doc/lib/libstdtypes.tex ============================================================================== --- python/trunk/Doc/lib/libstdtypes.tex (original) +++ python/trunk/Doc/lib/libstdtypes.tex Tue Dec 27 00:55:56 2005 @@ -1261,17 +1261,17 @@ \begin{tableiii}{c|c|l}{code}{Operation}{Equivalent}{Result} \lineiii{\var{s}.update(\var{t})} {\var{s} |= \var{t}} - {return set \var{s} with elements added from \var{t}} + {update set \var{s}, adding elements from \var{t}} \lineiii{\var{s}.intersection_update(\var{t})} {\var{s} \&= \var{t}} - {return set \var{s} keeping only elements also found in \var{t}} + {update set \var{s}, keeping only elements found in both \var{s} and \var{t}} \lineiii{\var{s}.difference_update(\var{t})} {\var{s} -= \var{t}} - {return set \var{s} after removing elements found in \var{t}} + {update set \var{s}, removing elements found in \var{t}} \lineiii{\var{s}.symmetric_difference_update(\var{t})} {\var{s} \textasciicircum= \var{t}} - {return set \var{s} with elements from \var{s} or \var{t} - but not both} + {update set \var{s}, keeping only elements found in either \var{s} or \var{t} + but not in both} \hline \lineiii{\var{s}.add(\var{x})}{}

1 0

commit of r41826 - python/trunk/Doc/lib/libprofile.tex
by reinhold.birkenfeld Dec. 26, 2005

Dec. 26, 2005

Author: reinhold.birkenfeld Date: Tue Dec 27 00:44:29 2005 New Revision: 41826 Modified: python/trunk/Doc/lib/libprofile.tex Log: Bug #489256: remove note about Python 1.1 profiler Modified: python/trunk/Doc/lib/libprofile.tex ============================================================================== --- python/trunk/Doc/lib/libprofile.tex (original) +++ python/trunk/Doc/lib/libprofile.tex Tue Dec 27 00:44:29 2005 @@ -55,47 +55,47 @@ \index{profiling, deterministic} -\section{How Is This Profiler Different From The Old Profiler?} -\nodename{Profiler Changes} - -(This section is of historical importance only; the old profiler -discussed here was last seen in Python 1.1.) - -The big changes from old profiling module are that you get more -information, and you pay less CPU time. It's not a trade-off, it's a -trade-up. - -To be specific: - -\begin{description} - -\item[Bugs removed:] -Local stack frame is no longer molested, execution time is now charged -to correct functions. - -\item[Accuracy increased:] -Profiler execution time is no longer charged to user's code, -calibration for platform is supported, file reads are not done \emph{by} -profiler \emph{during} profiling (and charged to user's code!). - -\item[Speed increased:] -Overhead CPU cost was reduced by more than a factor of two (perhaps a -factor of five), lightweight profiler module is all that must be -loaded, and the report generating module (\module{pstats}) is not needed -during profiling. - -\item[Recursive functions support:] -Cumulative times in recursive functions are correctly calculated; -recursive entries are counted. - -\item[Large growth in report generating UI:] -Distinct profiles runs can be added together forming a comprehensive -report; functions that import statistics take arbitrary lists of -files; sorting criteria is now based on keywords (instead of 4 integer -options); reports shows what functions were profiled as well as what -profile file was referenced; output format has been improved. - -\end{description} +%\section{How Is This Profiler Different From The Old Profiler?} +%\nodename{Profiler Changes} +% +%(This section is of historical importance only; the old profiler +%discussed here was last seen in Python 1.1.) +% +%The big changes from old profiling module are that you get more +%information, and you pay less CPU time. It's not a trade-off, it's a +%trade-up. +% +%To be specific: +% +%\begin{description} +% +%\item[Bugs removed:] +%Local stack frame is no longer molested, execution time is now charged +%to correct functions. +% +%\item[Accuracy increased:] +%Profiler execution time is no longer charged to user's code, +%calibration for platform is supported, file reads are not done \emph{by} +%profiler \emph{during} profiling (and charged to user's code!). +% +%\item[Speed increased:] +%Overhead CPU cost was reduced by more than a factor of two (perhaps a +%factor of five), lightweight profiler module is all that must be +%loaded, and the report generating module (\module{pstats}) is not needed +%during profiling. +% +%\item[Recursive functions support:] +%Cumulative times in recursive functions are correctly calculated; +%recursive entries are counted. +% +%\item[Large growth in report generating UI:] +%Distinct profiles runs can be added together forming a comprehensive +%report; functions that import statistics take arbitrary lists of +%files; sorting criteria is now based on keywords (instead of 4 integer +%options); reports shows what functions were profiled as well as what +%profile file was referenced; output format has been improved. +% +%\end{description} \section{Instant Users Manual \label{profile-instant}}

1 0

commit of r41825 - python/branches/release24-maint/Doc/lib/liburllib2.tex
by reinhold.birkenfeld Dec. 26, 2005

Dec. 26, 2005

Author: reinhold.birkenfeld Date: Tue Dec 27 00:36:49 2005 New Revision: 41825 Modified: python/branches/release24-maint/Doc/lib/liburllib2.tex Log: Bug #954981: urllib2 example wont work w/o ssl (backport) Modified: python/branches/release24-maint/Doc/lib/liburllib2.tex ============================================================================== --- python/branches/release24-maint/Doc/lib/liburllib2.tex (original) +++ python/branches/release24-maint/Doc/lib/liburllib2.tex Tue Dec 27 00:36:49 2005 @@ -771,7 +771,8 @@ \end{verbatim} Here we are sending a data-stream to the stdin of a CGI and reading -the data it returns to us: +the data it returns to us. Note that this example will only work when the +Python installation supports SSL. \begin{verbatim} >>> import urllib2

1 0

commit of r41824 - python/trunk/Doc/lib/liburllib2.tex
by reinhold.birkenfeld Dec. 26, 2005

Dec. 26, 2005

Author: reinhold.birkenfeld Date: Tue Dec 27 00:36:32 2005 New Revision: 41824 Modified: python/trunk/Doc/lib/liburllib2.tex Log: Bug #954981: urllib2 example wont work w/o ssl Modified: python/trunk/Doc/lib/liburllib2.tex ============================================================================== --- python/trunk/Doc/lib/liburllib2.tex (original) +++ python/trunk/Doc/lib/liburllib2.tex Tue Dec 27 00:36:32 2005 @@ -782,7 +782,8 @@ \end{verbatim} Here we are sending a data-stream to the stdin of a CGI and reading -the data it returns to us: +the data it returns to us. Note that this example will only work when the +Python installation supports SSL. \begin{verbatim} >>> import urllib2

1 0

commit of r41823 - python/branches/release24-maint/Doc/lib/libpickle.tex
by reinhold.birkenfeld Dec. 26, 2005

Dec. 26, 2005

Author: reinhold.birkenfeld Date: Tue Dec 27 00:27:50 2005 New Revision: 41823 Modified: python/branches/release24-maint/Doc/lib/libpickle.tex Log: Bug #839075 (backport): document that highly recursive data cannot be pickled Modified: python/branches/release24-maint/Doc/lib/libpickle.tex ============================================================================== --- python/branches/release24-maint/Doc/lib/libpickle.tex (original) +++ python/branches/release24-maint/Doc/lib/libpickle.tex Tue Dec 27 00:27:50 2005 @@ -395,6 +395,10 @@ Attempts to pickle unpicklable objects will raise the \exception{PicklingError} exception; when this happens, an unspecified number of bytes may have already been written to the underlying file. +Trying to pickle a highly recursive data structure may exceed the +maximum recursion depth, a \exception{RuntimeError} will be raised +in this case. You can carefully raise this limit with +\function{sys.setrecursionlimit()}. Note that functions (built-in and user-defined) are pickled by ``fully qualified'' name reference, not by value. This means that only the

1 0

commit of r41822 - python/trunk/Doc/lib/libpickle.tex
by reinhold.birkenfeld Dec. 26, 2005

Dec. 26, 2005

Author: reinhold.birkenfeld Date: Tue Dec 27 00:27:49 2005 New Revision: 41822 Modified: python/trunk/Doc/lib/libpickle.tex Log: Bug #839075: document that highly recursive data cannot be pickled Modified: python/trunk/Doc/lib/libpickle.tex ============================================================================== --- python/trunk/Doc/lib/libpickle.tex (original) +++ python/trunk/Doc/lib/libpickle.tex Tue Dec 27 00:27:49 2005 @@ -372,6 +372,10 @@ Attempts to pickle unpicklable objects will raise the \exception{PicklingError} exception; when this happens, an unspecified number of bytes may have already been written to the underlying file. +Trying to pickle a highly recursive data structure may exceed the +maximum recursion depth, a \exception{RuntimeError} will be raised +in this case. You can carefully raise this limit with +\function{sys.setrecursionlimit()}. Note that functions (built-in and user-defined) are pickled by ``fully qualified'' name reference, not by value. This means that only the

1 0