I followed the @ Søren method, but without the -u number.
The only complication was a few compilation errors on the last line, all due to differences in syntax and Unicode between Python 2 and Python 3, but with a little checking of the web documentation it was a few minutes with the text editor changing the following files (all paths belong to the directory pygame created at boot time):
gedit build/lib.linux-x86_64-3.2/pygame/colordict.py gedit build/lib.linux-x86_64-3.2/pygame/tests/test-utils/png.py gedit build/lib.linux-x86_64-3.2/pygame/examples/movieplayer.py
Line numbers from compiler error messages are great for giving you a place to start. Beware:
1 remove all references to u"xxxx" colours 2 use Python3 syntax for exceptions 3 change all print commands to Python3 equivalents
Then reinstall the final compilation command:
sudo python3 setup.py install
If you miss one or two or make a mistake, just keep working on editing the loop and recompiling it until it works.
By the way, I specifically did not give details about the compiler messages, because I expect that they will depend on the current assembly that you load. The files I needed to change were for the version "1.9.2pre" downloaded from the date of this post.
source share