Hi, The branch is svn://seul.org/svn/pygame/branches/python3 . I have config.py, config_win.py and setup.py working with Python 3.0.1. I also updated base.c and __init__.py. I was able to build pygame.base with Python 3 and call pygame.base.init() and pygame.base.quit() and pygame.base.get_sdl_version().
Also, I built it with Python 2.6 to confirm backwards compatibility. This confirms that Python 3.0 can use the Python 2.6 prebuilts for Windows: http://www3.telus.net/len_l/pygame/prebuilt-pygame1.9.0-msvcr90-win32.zip I will port the config.py stuff back into the main branch soon. Lenard Quoting René Dudfield <ren...@gmail.com>: > cool. I'll grab your branch and try to get it working on ubuntu. > > cu, > > On Sun, Apr 12, 2009 at 10:24 AM, Lenard Lindstrom <le...@telus.net> wrote: > > > Quoting Marcus von Appen <m...@sysfault.org>: > > > > > On, Sat Apr 11, 2009, Rene Dudfield wrote: > > > > > > > Yeah cool. > > > > > > > > I think it will give me a good push to finish off more tests as we > > change > > > > towards py3k. > > > > > > > > The sprite module is missing tests for a lot of the older sprite > > > > functionality. So that's the major one of the .py files I think. Our > > > build > > > > scripts, and tests are the other major .py files. > > > > > > > > If we start back porting some of the pgreloaded py3k stuff, then I > > think > > > we > > > > can have a pygame 1.9 prerelease for py3k within 4 weeks time(in time > > for > > > > the course). Remember, it only took Marcus a few days to port > > pgreloaded. > > > > > > It has a less messy internal API, though :-). > > > > > I think we could get a minimal Pygame ready: base, surface, mixer, image, > > gfxdraw. I have access to an XP box for the next few days so will fork off > > a > > python3 branch and see if I can get something to work for Windows. But > > don't let > > that stop anyone else from adapting Pygame to Python 3. We can merge > things > > back > > later. > > > > Lenard > > > > > > -- > > Lenard Lindstrom > > <le...@telus.net> > > > > > -- Lenard Lindstrom <le...@telus.net>