[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [pygame] So can anyone confirm, does pygame work with python 3?
- To: pygame-users@xxxxxxxx
- Subject: Re: [pygame] So can anyone confirm, does pygame work with python 3?
- From: "René Dudfield" <renesd@xxxxxxxxx>
- Date: Mon, 8 Dec 2008 12:02:13 +1100
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: pygame-users-outgoing@xxxxxxxx
- Delivered-to: pygame-users@xxxxxxxx
- Delivery-date: Sun, 07 Dec 2008 20:02:20 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=2PSHbF58W//BCTztZSZNwRfH3VXMP9RFK5y/nH1AuPQ=; b=Zgn/vo+odGKCxD8XxmSKHrX1T1dDPgcZUoW309cyG4YE/LqHo5m1Vk50Dh4q4bWrjm ZLlkWh7N6htHmq5JDr0HWH4NByJ+FfKYc3EeK1GI8n6oPjOAAFdNzdKCmzmUyw80M/sy GaKuJQjGnAKYqRLnOVL9Hk0dcWgvzvYfQ0teQ=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=WC7RFZwIpMVIt/lScD850X5x4TsEgxl1AgbI1dNzWqtFnRKTB1XvF52DbW9AhF5e40 I0/5IwHyPU4ORVSCxwKj3op7zq4ZfQINzhVnItY2DSSZaE1BGUko5+V3T0e2oFl5fixv oaTNjCpaZT8HzmG9kA7YbflZJPz0eNgziwJv4=
- In-reply-to: <5b0fce7a0812071631q265ef9d1i5535f7045e12809b@xxxxxxxxxxxxxx>
- References: <5b0fce7a0812071631q265ef9d1i5535f7045e12809b@xxxxxxxxxxxxxx>
- Reply-to: pygame-users@xxxxxxxx
- Sender: owner-pygame-users@xxxxxxxx
hi,
kind of(no). There are branches for python3 stuff in svn started
about 7 months ago... both Marcus and Lenard have done work on it -
but I don't think anything is complete. We have also been preparing
for py3k by improving our unittests significantly.
There is currently *no* complete C API migration document provided by
the python 3 developers. I have set up a wiki here with notes for
migrating:
http://wiki.python.org/moin/cporting
Also the python 3 developers were changing the C API as they went...
but unfortunately not documenting all the changes. So it was best to
wait until they finished and released py3k, rather than changing code
constantly as their API changed.
I wouldn't switch to python3 yet...
- no support for older operating systems that make up more than 3% or
so of computer users.
- eg it doesn't work on versions of win98, win2k, current linux
distros, older versions of mac os(there's no installer for mac osx at
all yet).
- most modules haven't been ported to py3k yet.
- a lot of modules haven't even been ported to python 2.6 yet(eg numpy).
- the 2to3 tool is still buggy, but should improve over time as more
people port their code and fix bugs in the tool.
- print is now a function! (well probably not important at all... but
it just annoys me... hehe)
- no pygame for it yet! hehe. Well I think you could build a lot of
it from source with a bit of effort.
- python 3 is slower. I think around 10% slower with the standard benchmarks.
- no macosx installer yet for python 3.
- most example code, and projects are written for python 2.x
cu,
On Mon, Dec 8, 2008 at 11:31 AM, Lamonte <scheols@xxxxxxxxx> wrote:
> Curious.
>
> --
> Join cleanscript.com Come here for professional PHP coding.
>