Sorry, From MethodObject.h the 4th parameter is usually documented as
having a NULL, but is intended to be used for a documentation string
that will be available to the user under the various GUI IDE's such as
IDLE or PyWin32. I just wanted to point that out..
struct PyMethodDef {
const char
On 3/06/2006 1:38 PM, sam wrote:
> I recommend that you also replace the NULL after the METH_VARARGS with
> a valid documentations string such as:
>
> static PyMethodDef modglMethods[] =
>{
> { (char *)"glVertex4f", _wrap_glVertex4f, METH_VARARGS, "My
> Doc String"},
> {
I recommend that you also replace the NULL after the METH_VARARGS with
a valid documentations string such as:
static PyMethodDef modglMethods[] =
{
{ (char *)"glVertex4f", _wrap_glVertex4f, METH_VARARGS, "My
Doc String"},
{ NULL, NULL, 0, NULL }
};
Sam Schulenburg
On 3/06/2006 9:51 AM, Luke Miller wrote:
> Hello,
>
> I am working on my first python module based on a c program. The
> module builds and installs OK using dist-utils, and imports fine into
> python. However, when I try and use the one wrapper
> ("modgl.glVertex4f(1, 2, 3, 1)") in the module, it
Hello,
I am working on my first python module based on a c program. The
module builds and installs OK using dist-utils, and imports fine into
python. However, when I try and use the one wrapper
("modgl.glVertex4f(1, 2, 3, 1)") in the module, it seg faults.
Can anyone spot why this isn't working,
