[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [pygame] Pygame's PyType_Init: Isn't it a little outdated?
- To: pygame-users@xxxxxxxx
- Subject: Re: [pygame] Pygame's PyType_Init: Isn't it a little outdated?
- From: René Dudfield <renesd@xxxxxxxxx>
- Date: Sat, 7 Feb 2009 12:29:47 +1100
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: pygame-users-outgoing@xxxxxxxx
- Delivered-to: pygame-users@xxxxxxxx
- Delivery-date: Fri, 06 Feb 2009 20:29:50 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=PJ0T7aXGOVciSnU0L3vhfhk1bGbIqoNyms00IBh4j8k=; b=I027tGWgW9eFThQx2cJikwW+wm6hy23xYUN6Wl/tyytr1MLi3pvrA/ZaYAzXU2EYLd 13ErTzX9DHulnizDrz7vljH5smtSHLBGsW4lGvvrce0+v7LwfhG8wLvMf0NnZO5hekN5 YwTtIht+znpUZXjG2JWNRaAP+c0xeSToOsXHM=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=sw4lEOKjuXhNlzb/tj5KL+z7AL9ZPOt/pNbFtPXli/B0oKgP9Sfrf/LodWXI2URUCr 1A2jIq3ldDhqxpEE4l7zJvjr8DkGRlAvnMYzKvsI6hp7jOVImUy9NxFVkU8m/+TlRwaC XP/2NMj4EL5DBcXmKt1XjRBoTymov5quNMsUA=
- In-reply-to: <498CD921.1030700@xxxxxxxxx>
- References: <498CD921.1030700@xxxxxxxxx>
- Reply-to: pygame-users@xxxxxxxx
- Sender: owner-pygame-users@xxxxxxxx
I guess the only reason would be that it's not broken.
On Sat, Feb 7, 2009 at 11:43 AM, Lenard Lindstrom <len-l@xxxxxxxxx> wrote:
> While updating the extension modules to prevent module loads on an error I
> noticed Pygame uses a macro, PyType_Init, to initialize Pygame types. The
> macro just sets the type's ob_type slot, nothing more. But the preferred,
> and newer (since 2.2) way is with Python's PyType_Ready. Any reason not to
> upgrade?
>
> Lenard
>
> --
> Lenard Lindstrom
> <len-l@xxxxxxxxx>
>
>