Mailman 3 September 2004 - Python-checkins

python/dist/src/Objects enumobject.c, 1.17, 1.18 genobject.c, 1.3, 1.4 iterobject.c, 1.18, 1.19
by rhettinger＠users.sourceforge.net Sept. 1, 2004

Sept. 1, 2004

Update of /cvsroot/python/python/dist/src/Objects In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv13289/Objects Modified Files: enumobject.c genobject.c iterobject.c Log Message: SF patch #1020188: Use Py_CLEAR where necessary to avoid crashes (Contributed by Dima Dorfman) Index: enumobject.c =================================================================== RCS file: /cvsroot/python/python/dist/src/Objects/enumobject.c,v retrieving revision 1.17 retrieving revision 1.18 diff -u -d -r1.17 -r1.18 --- enumobject.c 25 Aug 2004 19:42:12 -0000 1.17 +++ enumobject.c 1 Sep 2004 07:02:44 -0000 1.18 @@ -230,10 +230,7 @@ PyErr_Clear(); } ro->index = -1; - if (ro->seq != NULL) { - Py_DECREF(ro->seq); - ro->seq = NULL; - } + Py_CLEAR(ro->seq); return NULL; } Index: genobject.c =================================================================== RCS file: /cvsroot/python/python/dist/src/Objects/genobject.c,v retrieving revision 1.3 retrieving revision 1.4 diff -u -d -r1.3 -r1.4 --- genobject.c 27 Jun 2004 15:43:12 -0000 1.3 +++ genobject.c 1 Sep 2004 07:02:44 -0000 1.4 @@ -51,8 +51,7 @@ * may keep a chain of frames alive or it could create a reference * cycle. */ assert(f->f_back != NULL); - Py_DECREF(f->f_back); - f->f_back = NULL; + Py_CLEAR(f->f_back); /* If the generator just returned (as opposed to yielding), signal * that the generator is exhausted. */ Index: iterobject.c =================================================================== RCS file: /cvsroot/python/python/dist/src/Objects/iterobject.c,v retrieving revision 1.18 retrieving revision 1.19 diff -u -d -r1.18 -r1.19 --- iterobject.c 12 Apr 2004 18:10:01 -0000 1.18 +++ iterobject.c 1 Sep 2004 07:02:44 -0000 1.19 @@ -192,18 +192,14 @@ return result; /* Common case, fast path */ Py_DECREF(result); if (ok > 0) { - Py_DECREF(it->it_callable); - it->it_callable = NULL; - Py_DECREF(it->it_sentinel); - it->it_sentinel = NULL; + Py_CLEAR(it->it_callable); + Py_CLEAR(it->it_sentinel); } } else if (PyErr_ExceptionMatches(PyExc_StopIteration)) { PyErr_Clear(); - Py_DECREF(it->it_callable); - it->it_callable = NULL; - Py_DECREF(it->it_sentinel); - it->it_sentinel = NULL; + Py_CLEAR(it->it_callable); + Py_CLEAR(it->it_sentinel); } } return NULL;

1 0

python/dist/src/Modules itertoolsmodule.c, 1.34, 1.35
by rhettinger＠users.sourceforge.net Sept. 1, 2004

Sept. 1, 2004

Update of /cvsroot/python/python/dist/src/Modules In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv13289/Modules Modified Files: itertoolsmodule.c Log Message: SF patch #1020188: Use Py_CLEAR where necessary to avoid crashes (Contributed by Dima Dorfman) Index: itertoolsmodule.c =================================================================== RCS file: /cvsroot/python/python/dist/src/Modules/itertoolsmodule.c,v retrieving revision 1.34 retrieving revision 1.35 diff -u -d -r1.34 -r1.35 --- itertoolsmodule.c 15 Jul 2004 05:32:47 -0000 1.34 +++ itertoolsmodule.c 1 Sep 2004 07:02:43 -0000 1.35 @@ -250,8 +250,7 @@ r = gbo->currvalue; gbo->currvalue = NULL; - Py_DECREF(gbo->currkey); - gbo->currkey = NULL; + Py_CLEAR(gbo->currkey); return r; }

1 0

python/dist/src/Include object.h,2.128,2.129
by rhettinger＠users.sourceforge.net Sept. 1, 2004

Sept. 1, 2004

Update of /cvsroot/python/python/dist/src/Include In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv13289/Include Modified Files: object.h Log Message: SF patch #1020188: Use Py_CLEAR where necessary to avoid crashes (Contributed by Dima Dorfman) Index: object.h =================================================================== RCS file: /cvsroot/python/python/dist/src/Include/object.h,v retrieving revision 2.128 retrieving revision 2.129 diff -u -d -r2.128 -r2.129 --- object.h 22 Jul 2004 01:46:43 -0000 2.128 +++ object.h 1 Sep 2004 07:02:42 -0000 2.129 @@ -623,7 +623,7 @@ #define Py_CLEAR(op) \ do { \ if (op) { \ - PyObject *tmp = (op); \ + PyObject *tmp = (PyObject *)(op); \ (op) = NULL; \ Py_DECREF(tmp); \ } \

1 0

Freezing for alpha3 - trunk FROZEN from 2004-09-01 13:00 UTC
by Anthony Baxter Sept. 1, 2004

Sept. 1, 2004

I plan to start alpha3 in about 24 hours time. From about 12 hours from now, the trunk should be considered frozen - that's starting at about 1700 UTC on 2004-09-01. If your name isn't Anthony, Fred or Martin, please do NOT check in while we're doing the release. Really. Really, really, really. I'm cc'ing python-checkins as well this time, as a few folks missed this last time. The trunk will stay frozen until about 6 hours or so after the release is done - this makes it easier for me to do an emergency brown-paper-bag release in the case of a cockup <wink> Thanks, Anthony

1 0

python/nondist/peps pep-0333.txt,1.4,1.5
by pje＠users.sourceforge.net Sept. 1, 2004

Sept. 1, 2004

Update of /cvsroot/python/python/nondist/peps In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv28642 Modified Files: pep-0333.txt Log Message: More formatting fixes Index: pep-0333.txt =================================================================== RCS file: /cvsroot/python/python/nondist/peps/pep-0333.txt,v retrieving revision 1.4 retrieving revision 1.5 diff -u -d -r1.4 -r1.5 --- pep-0333.txt 31 Aug 2004 22:00:28 -0000 1.4 +++ pep-0333.txt 1 Sep 2004 04:59:21 -0000 1.5 @@ -204,16 +204,14 @@ environ['wsgi.last_call'] = True def write(data): - sys.stdout.write(data) + sys.stdout.write(data) sys.stdout.flush() def start_response(status,headers): - sys.stdout.write("Status: %s\r\n" % status) for key,val in headers: sys.stdout.write("%s: %s\r\n" % (key,val)) sys.stdout.write("\r\n") - return write result = application(environ, start_response) @@ -333,30 +331,30 @@ **may** be an empty string, if there is no more appropriate value for them: - * ``REQUEST_METHOD`` +* ``REQUEST_METHOD`` - * ``SCRIPT_NAME`` (The initial portion of the request URL's "path" - that corresponds to the application object, so that the application - knows its virtual "location".) +* ``SCRIPT_NAME`` (The initial portion of the request URL's "path" + that corresponds to the application object, so that the application + knows its virtual "location".) - * ``PATH_INFO`` (The remainder of the request URL's "path", - designating the virtual "location" of the request's target within - the application) +* ``PATH_INFO`` (The remainder of the request URL's "path", + designating the virtual "location" of the request's target within + the application) - * ``QUERY_STRING`` +* ``QUERY_STRING`` - * ``CONTENT_TYPE`` +* ``CONTENT_TYPE`` - * ``CONTENT_LENGTH`` +* ``CONTENT_LENGTH`` - * ``SERVER_NAME`` and ``SERVER_PORT`` (which, when combined with - ``SCRIPT_NAME`` and ``PATH_INFO``, should complete the URL. Note, - however, that ``HTTP_HOST``, if present, should be used in - preference to ``SERVER_NAME`` for constructing the URL. See the - `URL Reconstruction`_ section below for more detail.) +* ``SERVER_NAME`` and ``SERVER_PORT`` (which, when combined with + ``SCRIPT_NAME`` and ``PATH_INFO``, should complete the URL. Note, + however, that ``HTTP_HOST``, if present, should be used in + preference to ``SERVER_NAME`` for constructing the URL. See the + `URL Reconstruction`_ section below for more detail.) - * Variables corresponding to the client-supplied HTTP headers (i.e., - variables whose names begin with ``"HTTP_"``). +* Variables corresponding to the client-supplied HTTP headers (i.e., + variables whose names begin with ``"HTTP_"``). In general, a server or gateway should attempt to provide as many other CGI variables as are applicable, including e.g. the nonstandard @@ -752,16 +750,16 @@ respect to some server(s). Such "middleware" components can perform such functions as: - * Routing a request to different application objects based on the - target URL, after rewriting the ``environ`` accordingly. +* Routing a request to different application objects based on the + target URL, after rewriting the ``environ`` accordingly. - * Allowing multiple applications or frameworks to run side-by-side - in the same process +* Allowing multiple applications or frameworks to run side-by-side + in the same process - * Load balancing and remote processing, by forwarding requests and - responses over a network +* Load balancing and remote processing, by forwarding requests and + responses over a network - * Perform content postprocessing, such as applying XSL stylesheets +* Perform content postprocessing, such as applying XSL stylesheets Given the existence of applications and servers conforming to this specification, the appearance of such reusable middleware becomes @@ -874,18 +872,18 @@ 1.1's "expect/continue" mechanism, if they implement HTTP 1.1. This may be done in any of several ways: - 1. Reject all client requests containing an ``Expect: 100-continue`` - header with a "417 Expectation failed" error. Such requests will - not be forwarded to an application object. +1. Reject all client requests containing an ``Expect: 100-continue`` + header with a "417 Expectation failed" error. Such requests will + not be forwarded to an application object. - 2. Respond to requests containing an ``Expect: 100-continue`` request - with an immediate "100 Continue" response, and proceed normally. +2. Respond to requests containing an ``Expect: 100-continue`` request + with an immediate "100 Continue" response, and proceed normally. - 3. Proceed with the request normally, but provide the application - with a ``wsgi.input`` stream that will send the "100 Continue" - response if/when the application first attempts to read from the - input stream. The read request must then remain blocked until the - client responds. +3. Proceed with the request normally, but provide the application + with a ``wsgi.input`` stream that will send the "100 Continue" + response if/when the application first attempts to read from the + input stream. The read request must then remain blocked until the + client responds. Note that this behavior restriction does not apply for HTTP 1.0 requests, or for requests that are not directed to an application @@ -1071,18 +1069,18 @@ Thanks go to the many folks on the Web-SIG mailing list whose thoughtful feedback made this revised draft possible. Especially: - * Gregory "Grisha" Trubetskoy, author of ``mod_python``, who beat up - on the first draft as not offering any advantages over "plain old - CGI", thus encouraging me to look for a better approach. +* Gregory "Grisha" Trubetskoy, author of ``mod_python``, who beat up + on the first draft as not offering any advantages over "plain old + CGI", thus encouraging me to look for a better approach. - * Ian Bicking, who helped nag me into properly specifying the - multithreading and multiprocess options, as well as badgering me to - provide a mechanism for servers to supply custom extension data to - an application. +* Ian Bicking, who helped nag me into properly specifying the + multithreading and multiprocess options, as well as badgering me to + provide a mechanism for servers to supply custom extension data to + an application. - * Tony Lownds, who came up with the concept of a ``start_response`` - function that took the status and headers, returning a ``write`` - function. +* Tony Lownds, who came up with the concept of a ``start_response`` + function that took the status and headers, returning a ``write`` + function. References

1 0

[Python-checkins] python/dist/src/Doc/whatsnew whatsnew24.tex, 1.95, 1.96
by fdrake＠users.sourceforge.net Sept. 1, 2004

Sept. 1, 2004

Update of /cvsroot/python/python/dist/src/Doc/whatsnew In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv20881 Modified Files: whatsnew24.tex Log Message: - add missing \end{seealso} - wrap long line Index: whatsnew24.tex =================================================================== RCS file: /cvsroot/python/python/dist/src/Doc/whatsnew/whatsnew24.tex,v retrieving revision 1.95 retrieving revision 1.96 diff -u -d -r1.95 -r1.96 --- whatsnew24.tex 31 Aug 2004 13:57:02 -0000 1.95 +++ whatsnew24.tex 1 Sep 2004 04:05:08 -0000 1.96 @@ -699,7 +699,10 @@ relative import. This part of the PEP is not yet implemented. \begin{seealso} -\seepep{328}{Imports: Multi-Line and Absolute/Relative}{Written by Aahz. Multi-line imports were implemented by Dima Dorfman.} +\seepep{328}{Imports: Multi-Line and Absolute/Relative} + {Written by Aahz. Multi-line imports were implemented by + Dima Dorfman.} +\end{seealso} %======================================================================

1 0