[Python-Dev] unicode/string asymmetries

[Guido van Rossum]

> Jack Jansen writes:
>  > Huh, what did I miss? Why is PyArg_Parse deprecated, and by what
>  > should it be replaced?
> 
>   I think it is only recommended to avoid this as the argument-parsing
> function for an extension function/method; PyArg_ParseTuple() should
> be used instead since it can give better error messages using the
> :funcname syntax for the format string (which is strongly
> recommended!).
> 
>   -Fred

The other problem with PyArg_Parse that PyArg_ParseTuple avoids is
that a function declared as taking N arguments can also be called with
a single tuple of N items.  This is not supposed to happen (you should
use apply or the *args call notation for that).

--Guido van Rossum (home page: http://www.python.org/~guido/)