MAJOR BUG: test compare doesn't work as expected

[kawa-kokosowa]

Test compare doesn't work as expected, which is my error, I should've read closer that PixelArray.compare uses 1bit masks, thus if you test a GIF which is two frames of two different solid colors, it may say they're exactly alike.

I'll restore the version which @txanatan made.

[ghost]

Oh wow, I didn't realize it uses 1bit masks. My old method was slow as anything but it's guaranteed to work I guess.

We should really test the compare method...

[kawa-kokosowa]

I implemented a new method, however, I uncovered a super depressing recent bug in Pygame for OS X, which felt like a steel blade to my heart.

https://bitbucket.org/pygame/pygame/issues/298/bmp-and-png-images-not-loaded-correctly

In summary, I'll open an image, I can test that the color data is wrong, and when I save it it's exactly as I expected when finding the color samplings wrong. Again, if pygame opens an image, the color data is super messed, and you can test such with get_at() and by saving said image.

I'll have to develop on another... operating system... until these issues are resolved. :(

[kawa-kokosowa]

Okay so this occurs because of the difference in pygame being tested with py.test and our tests in tests/. Namely, that pygame never actually initializes or anything like that in the tests, and as such, that is the only major difference between files saved in test and files saved in demo.

In summation, pygame bug only in tests, not when pygame actually initialized.

[ghost]

Is there a way to have an init function that py.test will run before running the tests?