On Sat, 1 Sep 2007, René Dudfield wrote:
[snip good ideas]
We could also do a search within the pygame cookbook, which is slowly
gaining more examples.
Or perhaps the code submitted to pyweek could be made browsable...
Richard
yeah, that could be cool too.
Here's an example of using googles code search for the
pygame.image.load function.
http://www.google.com/codesearch?q=pygame.image.load
That's pretty cool... and easy to put a link in the docs to it from
each function.
On 9/1/07, Richard Jones [EMAIL PROTECTED]
Hello,
What we need to do for pygame now is get *heaps* better test coverage.
This point was rammed home in a talk given by Guido about py3k. I've
been thinking about this over the last couple of months, and test
coverage is the main thing that we should be doing now in preparation
for python
Hi again,
the main problem with python 3 with regards to pygame is that most
games do not have tests written for them. Having tests is required in
the python 3 transition plan.
It's a bit hard to write unit tests for games, and also lots of people
write games for fun, so avoid writing boring
Thats pretty nice :).
On 9/1/07, René Dudfield [EMAIL PROTECTED] wrote:
yeah, that could be cool too.
Here's an example of using googles code search for the
pygame.image.load function.
http://www.google.com/codesearch?q=pygame.image.load
That's pretty cool... and easy to put a link in
René Dudfield wrote:
the main problem with python 3 with regards to pygame is that most
games do not have tests written for them. Having tests is required in
the python 3 transition plan.
I'm also wondering if SDL2 will be ready in the same timeframe as Python3.
That would be a great
The SDL 2 plan has become SDL 1.3. They are just incrementally
changing it rather than a complete change now.
I think it might be ready by then... but not sure. SDL has a release
when done road map for 1.3 I think. Very much a good time to break
backwards compatibility.
However note that SDL
