assert_is is only supported in python2.7.
I've got other tests failing on my box, but I don't know how to fix them: http://bpaste.net/show/unemAaLZCxFixslh2FBi/
FIX nose.tools.assert_is is only supported with python2.7
seems to be a space missing.
Looks good to me. I'm quite surprised that this is a python version issue and not a nose version issue. Did you find this stated explicitly somewhere?
The other problems should ideally be raised in another issue. (with the image differences, did you check the two versions and see the differences?)
Nose only provides a warper around unittest that makes the assert* method pep8 compatible. assertIs was introduced in the standard library's unittest only for python2.7. Hence, nose doesn't expose assert_is for python2.5 and python2.6.
I've asked a bit if there were buildbots or jenkins running for matplotlib. If not, I can maybe try to set one up with python2.5 on the french python association server. Else, shiningpanda provides a jenkin installation for free for opensource softwares. That would allow to pick up on those non trivial and annoying problems :)
For the differences in the images, it looked to me like a font rendering problem. I can investigate the issues and open a bug report.
note: Deleted posts from @NelleV which were intended for another PR.
@NelleV: I python2.6 buildbot would be helpful, but matplotlib no longer officially supports python2.5 as of the 1.2 release (because it's so difficult to write 2/3 compatible code and support 2.5).
I have investigated shiningpanda and the past. Unfortunately, the runtimes of the matplotlib unit tests are so large that we use 3 times the daily CPU unit for a free project in a single test run, so it's kind of a no go. There is some Travis support in matplotlib now, but I haven't had a chance to really dig down into what it gives us yet.
As for the font difference, it may be that the test needs to be limited to a particular range of freetype versions, as some of our tests already do.
@mdboom Should I have a look at how to set this up ? I can have the build run every half an hour or every hour (that depends on the load of the server) if I have the permission of the AFPy.
It seems sane to me not support python2.5 anymore :)
I'm in the process of getting the Travis set up now -- that should test multiple versions of Python. Assuming this works, we may not need to take you up on your generous offer. It probably wouldn't hurt to have our own Travis instances running in various places, though.