[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: Nick Moffitt <nick@xxxxxxxx>
Date: Thu, 31 Jul 2008 22:05:45 +0100
Delivered-to: archiver@xxxxxxxx
Delivered-to: pygame-users-outgoing@xxxxxxxx
Delivered-to: pygame-users@xxxxxxxx
Delivery-date: Thu, 31 Jul 2008 17:05:49 -0400
In-reply-to: <9b711ec60807311332s18e6469cl7cf73a04332b8f28@xxxxxxxxxxxxxx>
Mail-followup-to: Nick Moffitt <nick@xxxxxxxx>, pygame-users@xxxxxxxx
References: <9b711ec60807311332s18e6469cl7cf73a04332b8f28@xxxxxxxxxxxxxx>
Reply-to: pygame-users@xxxxxxxx
Sender: owner-pygame-users@xxxxxxxx
User-agent: Mutt/1.5.17+20080114 (2008-01-14)

I refuse to read Slashdot, but if they get rid of TKinter I'll put up
with every Python "Hello, world." program ever written breaking.

-- 
"There should be a homonym exam before people are         Nick Moffitt
issued keyboards."     -- George Moffitt                 nick@xxxxxxxx

Follow-Ups:
- Re: [pygame] Python 3.0 to be backwards incompatible ?
  - From: Nick Moffitt

References:
- [pygame] Python 3.0 to be backwards incompatible ?
  - From: Paulo Silva

Prev by Author: Re: [pygame] 100% CPU FAQ
Next by Author: Re: [pygame] Python 3.0 to be backwards incompatible ?
Previous by thread: [pygame] Python 3.0 to be backwards incompatible ?
Next by thread: Re: [pygame] Python 3.0 to be backwards incompatible ?
Index(es):
- Author
- Thread