From: Andrew M. Kuchling <amk@amk.ca>
Date: Thu, 11 Jul 2002 19:27:46 +0000 (+0000)
Subject: [Bug #567607] Suggest METH_NOARGS to replace PyArg_NoArgs
X-Git-Tag: v2.3c1~5039
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=7845e7c7266f246a8ff35cd5a433ecb1cb81064f;p=thirdparty%2FPython%2Fcpython.git

[Bug #567607] Suggest METH_NOARGS to replace PyArg_NoArgs
---

diff --git a/Doc/whatsnew/whatsnew23.tex b/Doc/whatsnew/whatsnew23.tex
index 87f5290098fd..9a147f1c5adb 100644
--- a/Doc/whatsnew/whatsnew23.tex
+++ b/Doc/whatsnew/whatsnew23.tex
@@ -653,9 +653,13 @@ when running Python's \file{configure} script.  (Contributed by Ondrej
 Palkovsky.)
 
 \item The \cfunction{PyArg_NoArgs()} macro is now deprecated, and code
-that
-uses it should be changed to use \code{PyArg_ParseTuple(args, "")}
-instead.
+that uses it should be changed.  For Python 2.2 and later, the method
+definition table can specify the
+\constant{METH_NOARGS} flag, signalling that there are no arguments, and 
+the argument checking can then be removed.  If compatibility with
+pre-2.2 versions of Python is important, the code could use
+\code{PyArg_ParseTuple(args, "")} instead, but this will be slower 
+than using \constant{METH_NOARGS}.
 
 \item A new function, \cfunction{PyObject_DelItemString(\var{mapping},
 char *\var{key})} was added
@@ -721,7 +725,7 @@ as well as \UNIX.
 The author would like to thank the following people for offering
 suggestions, corrections and assistance with various drafts of this
 article: Michael Chermside, Scott David Daniels, Fred~L. Drake, Jr.,
-Michael Hudson, Detlef Lannert, Andrew MacIntyre, Gustavo Niemeyer,
-Neal Norwitz.
+Michael Hudson, Detlef Lannert, Martin von L\"owis, Andrew MacIntyre,
+Gustavo Niemeyer, Neal Norwitz.
 
 \end{document}