37 lines
1.2 KiB
Plaintext
37 lines
1.2 KiB
Plaintext
From: olipt at mayo.edu (Travis Oliphant)
|
|
Date: Thu, 29 Apr 1999 19:34:49 -0500
|
|
Subject: Extension Doc bug
|
|
In-Reply-To: <14120.52559.376120.364972@weyr.cnri.reston.va.us>
|
|
References: <WtnU2.298$7j4.117754@news.shore.net> <14120.52559.376120.364972@weyr.cnri.reston.va.us>
|
|
Message-ID: <Pine.LNX.4.04.9904291933330.5554-100000@us2.mayo.edu>
|
|
X-UID: 112
|
|
|
|
>
|
|
> Michael P. Reilly writes:
|
|
> > I just spent the morning trying to find a very obscure bug related to
|
|
> > the passing keyword arguments to a builtin method/function.
|
|
>
|
|
> Michael,
|
|
> You didn't post your original code that exhibited the bug, so I
|
|
> can't be sure of my conclusions. If you can send source for enough of
|
|
> your extension module that someone can compile it, that would be
|
|
> helpful.
|
|
> My first inclination, however, is that you passed in illegal
|
|
> arguments to PyArg_ParseTupleAndKeywords(). Passing NULL for the
|
|
> keywords dictionary is allowed; I've been looking at the
|
|
> implementation and don't see a way for that to be a problem (but I
|
|
> might have missed something).
|
|
>
|
|
|
|
FYI,
|
|
I've used PyArg_ParseTupleAndKeywords() in a C-extension and passed it a
|
|
NULL pointer with no problems.
|
|
|
|
Python 1.5.2b (Redhat 5.2 Linux 2.0.36)
|
|
|
|
|
|
|
|
|
|
|
|
|