[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [pygame] Python 3.0 to be backwards incompatible ?
- To: pygame-users@xxxxxxxx
- Subject: Re: [pygame] Python 3.0 to be backwards incompatible ?
- From: "René Dudfield" <renesd@xxxxxxxxx>
- Date: Tue, 5 Aug 2008 09:53:14 +1000
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: pygame-users-outgoing@xxxxxxxx
- Delivered-to: pygame-users@xxxxxxxx
- Delivery-date: Mon, 04 Aug 2008 19:53:18 -0400
- 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=QZr6+dRq+zawA0RbeXHZEfa4wJX+cQ8TQ1GuUTLblFM=; b=uD3VGkVuznQbwT0uo0licNL9yQG5inYxpQJvb6ZhAkZRRXXRIip0DfH0SwxucJN/9W r/vRwP2yIoa+6mCbMofFTCUd2D6IOw+TFnUUHObMvTxdcFT+dC8rxQWvQ7LqIhjijQ6j p58zMIIoo8Fkm3YjjB37HuMjGxcLozbCK9P8I=
- 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=yEqsEYoLnlJtIR24miOO39Fj7S65y6CqSGEAyML0VmdL9aBQTUn9qmbgEUlTUZY57X /byvqJ3IIDiX+WeDGUtX+i6Seg1j4vmRyLqmvKvhngbtLveCXhM+KAoELrqrch3+acmi Hg6XFgrGpfBwKUgsN2Qi7gkdN/cRZuGMwckHw=
- In-reply-to: <9b711ec60807311332s18e6469cl7cf73a04332b8f28@xxxxxxxxxxxxxx>
- References: <9b711ec60807311332s18e6469cl7cf73a04332b8f28@xxxxxxxxxxxxxx>
- Reply-to: pygame-users@xxxxxxxx
- Sender: owner-pygame-users@xxxxxxxx
Unfortunately python2.6 also breaks windows compatibility (win9x, win
me, win nt, and win2000 unless they have all the latest service
packs).
So if you want to write portable games, stick to python2.5.
Python 3.0 is the main reason Nicholas has been working these last
months on improving pygames tests... so that it will be easier to port
to py3k(and other python implementations like tinypy).
On Fri, Aug 1, 2008 at 6:32 AM, Paulo Silva <nitrofurano@xxxxxxxxx> wrote:
> http://it.slashdot.org/article.pl?sid=08/02/01/1624247
>
> well, this sounds to me as a huge headache... but i'd like to know
> oppinions about (what will be improved, what will be changed),
> specially all Pygame coders, and how far it may affect Pygame games
> supposed to be 'considered' done...
>