Re: [pygame] What's next for Pygame project?

[Renà Dudfield <renesd@xxxxxxxxx>]

Hi,

It does a few different things the standard ones didn't do. For old pythons pre unit test in stdlib, and also for tagging, and running tests in separate processes. I guess the full details are in the mailing list and commit logs.

I'm not sure if changing it should be a priority for release of 1.9.2 but. 2.0 should use modern things for sure, and I guess this is what you mean?



best,

> On 15 Jul 2015, at 14:44, Sam Bull <sam.hacking@xxxxxxxx> wrote:
> 
>> On Sun, 2015-07-12 at 18:48 -0700, Lenard Lindstrom wrote:
>> A Pygame buildbot two tasks, building a Pygame installer for a 
>> particular operating system, then running the Pygame unit tests on the 
>> new build.
> 
> On the note of testing, I would also like to see pygame's unittest to be
> removed and for the tests to use Python's built-in unnittest module.
> 
> Does anybody know the reason this exists? Is there a valid reason we're
> not already using the standard library unittest module?
> 
> Pygame's unittest appears to emulate the standard library, but the
> implementation is different, and some things aren't tested properly.
> 
> For example, assertNotEqual does not test if they are not equal (with 
> !=), but rather if their equality is false (with ==). When running the
> rect tests under the standard library implementation which actually
> tests not equals, one of the tests failed.
> 
> I've fixed that test now, but it would make more sense to be using the
> standard library implementation that everyone else is using and is well
> maintained.