[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [pygame] Py C/API - Using METH_O vs METH_VARARGS

To: pygame-users@xxxxxxxx
Subject: Re: [pygame] Py C/API - Using METH_O vs METH_VARARGS
From: Peter Shinners <pete@xxxxxxxxxxxx>
Date: Tue, 23 Dec 2008 08:16:19 -0800
Delivered-to: archiver@xxxxxxxx
Delivered-to: pygame-users-outgoing@xxxxxxxx
Delivered-to: pygame-users@xxxxxxxx
Delivery-date: Tue, 23 Dec 2008 11:16:33 -0500
In-reply-to: <7c1ab96d0812111447k3d4a5f21h6c12a7d3ff896441@xxxxxxxxxxxxxx>
References: <7c1ab96d0812111447k3d4a5f21h6c12a7d3ff896441@xxxxxxxxxxxxxx>
Reply-to: pygame-users@xxxxxxxx
Sender: owner-pygame-users@xxxxxxxx
User-agent: Thunderbird 2.0.0.18 (X11/20081125)

Campbell Barton wrote:

Noticed METH_O isnt used anywhere in pygame, this avoids creating a
tuple only to get a single PyObject back out with PyArg_ParseTuple()

I'm pretty sure METH_O has been added after Python 2.3. Someone shoulddefinitely find the minimum required Python version before switchinganything.

Follow-Ups:
- Re: [pygame] Py C/API - Using METH_O vs METH_VARARGS
  - From: Lenard Lindstrom

References:
- [pygame] Py C/API - Using METH_O vs METH_VARARGS
  - From: Campbell Barton

Prev by Author: Re: [pygame] keyboard layout problems
Next by Author: Re: [pygame] py2exe and pygame font causes segfaults
Previous by thread: Re: [pygame] Py C/API - Using METH_O vs METH_VARARGS
Next by thread: Re: [pygame] Py C/API - Using METH_O vs METH_VARARGS
Index(es):
- Author
- Thread