unsubscribe pygame-users
Hi,
On 22/11/10 03:15 PM, Kris Schnee wrote:
On 2010.11.22 5:52 PM, Lenard Lindstrom wrote:
Hi,
On 20/11/10 02:04 PM, Matthew Maniaci wrote:
I ran 2to3 on setup.py and it didn't quite get all of the raw_inputs.
A quick find-and-replace fixed that and I was able to install pygame
from source u
On 2010.11.22 5:52 PM, Lenard Lindstrom wrote:
Hi,
On 20/11/10 02:04 PM, Matthew Maniaci wrote:
I ran 2to3 on setup.py and it didn't quite get all of the raw_inputs.
A quick find-and-replace fixed that and I was able to install pygame
from source using Python 3.1. I haven't tested it yet, so us
Hi,
On 20/11/10 02:04 PM, Matthew Maniaci wrote:
I ran 2to3 on setup.py and it didn't quite get all of the raw_inputs.
A quick find-and-replace fixed that and I was able to install pygame
from source using Python 3.1. I haven't tested it yet, so use at your
own risk.
Why? Pygame already buil
Hi,
I think the documentation is the place to fix it. As code depends on
existing behaviour.
cheers,
On Sat, Nov 20, 2010 at 5:03 PM, Peter Shinners wrote:
> This looks like a quick fix. I don't know if it should go to the
> documentation or to the joystick code.
>
> Original Messa
