Hi René,
Great news. Anything more I should do? I got distracted earlier this
year when, on the PyPy mailing list, I got the impression that new
buffer support was of low priority, making much of the work I did on
Pygame irrelevant to PyPy. But that is my personal interpretation, and
may be entirely wrong. This is something I need to address with the PyPy
developers, but can wait until after 1.9.2 is released. The added new
buffer support is still relevant to CPython.
I am for doing one final push to get version 1.9.2 release worthy, but
won't add any new features. These can wait until the basics of the SDL2
version 2.0 are decided. For now I can see more work on the
documentation, and looking at unit tests and bugs. Unfortunately I
cannot do much to help with the Windows build, as I only have XP i386
installed on my machine, and little interest in upgrading (I do have
access to a Windows 7 machine, so maybe I can do a final release build.)
I think an end-of-January release date is realistic. I will now go to
the bug tracker to see what is left to do.
Lenard Lindstrom
On 14-12-12 10:33 PM, René Dudfield wrote:
Hi,
I've been prodded by a bunch of people on finally getting this done.
But requests from people in the UK using it for teaching are the main
motivation. Yes, it's highly unbelievable it will actually happen this
time... but who knows?
1.9.2 release:
* https://bitbucket.org/pygame/pygame/issue/107/pygame-192-release
* https://bitbucket.org/pygame/pygame/issues?milestone=1.9.2
Debian python 3:
https://bitbucket.org/pygame/pygame/issue/221/debian-python-3-package-for-192
OS X: https://bitbucket.org/pygame/pygame/issues?component=OS%20X
Windows: https://bitbucket.org/pygame/pygame/issues?q=windows
I'm working on it this weekend. I'll concentrate on making
installation of what we have easier, but also getting the 1.9.2
release out which is blocking a new package in Debian.
I'll be moving stuff I deem not critical for the release into having a
1.9.3 tag, rather than 1.9.2. I'll eventually be removing modules that
are not stable and were not in previous releases. If they are blocking
the release, and no one can fix them they will be removed.
If anyone is around to help, there are a mountain of tasks to do. I'll
be in #pygame on irc, the mailing list, and in the issue tracker.
Also, if anyone is in Berlin and wants to meet up to hack on pygame,
that would be great.
best,