Re: [matplotlib-devel] Weird KnownFailure problem in IPython test suite with mpl master

2013-06-19 Thread Fernando Perez
Thanks a ton, Mike! Great not to have to worry about this on our side. cheers, f On Wed, Jun 19, 2013 at 10:02 AM, Michael Droettboom wrote: > Just to close the loop on this, I have created: > > https://github.com/matplotlib/matplotlib/pull/2139 > > > On 06/18/2013 07:18 PM, Fernando Perez wrot

Re: [matplotlib-devel] Weird KnownFailure problem in IPython test suite with mpl master

2013-06-19 Thread Michael Droettboom
Just to close the loop on this, I have created: https://github.com/matplotlib/matplotlib/pull/2139 On 06/18/2013 07:18 PM, Fernando Perez wrote: Good point, I didn't know about that new mechanism. I think we should keep 2.6 support for IPython 1.0, but drop it afterwards. We can discuss that d

Re: [matplotlib-devel] Weird KnownFailure problem in IPython test suite with mpl master

2013-06-19 Thread Michael Droettboom
On 06/18/2013 07:09 PM, Fernando Perez wrote: > Hi Mike, > > On Tue, Jun 18, 2013 at 3:37 PM, Michael Droettboom wrote: >> This was an attempt to fix a bug that mpl's KnownFailure plugin wouldn't >> load when running tests directly using the nosetests commandline >> script. I see IPython has a te

Re: [matplotlib-devel] Weird KnownFailure problem in IPython test suite with mpl master

2013-06-18 Thread Thomas Kluyver
On 19 June 2013 00:09, Fernando Perez wrote: > I wish we could just fix this plugin issue. When we drop support for Python 2.6, I think we can use the expectedFailure mechanism included in unittest from 2.7 onwards. So long as nose recognises that, we should be able to drop our copy of the Know

Re: [matplotlib-devel] Weird KnownFailure problem in IPython test suite with mpl master

2013-06-18 Thread Fernando Perez
Good point, I didn't know about that new mechanism. I think we should keep 2.6 support for IPython 1.0, but drop it afterwards. We can discuss that during the dev meeting... Cheers, f On Tue, Jun 18, 2013 at 4:16 PM, Thomas Kluyver wrote: > On 19 June 2013 00:09, Fernando Perez wrote: >> >> I

Re: [matplotlib-devel] Weird KnownFailure problem in IPython test suite with mpl master

2013-06-18 Thread Fernando Perez
Hi Mike, On Tue, Jun 18, 2013 at 3:37 PM, Michael Droettboom wrote: > This was an attempt to fix a bug that mpl's KnownFailure plugin wouldn't > load when running tests directly using the nosetests commandline > script. I see IPython has a testing wrapper script (iptest) -- is that > in part to

Re: [matplotlib-devel] Weird KnownFailure problem in IPython test suite with mpl master

2013-06-18 Thread Michael Droettboom
This was an attempt to fix a bug that mpl's KnownFailure plugin wouldn't load when running tests directly using the nosetests commandline script. I see IPython has a testing wrapper script (iptest) -- is that in part to solve that problem? In any case, the revert should be simple -- can you tr

Re: [matplotlib-devel] Weird KnownFailure problem in IPython test suite with mpl master

2013-06-18 Thread Fernando Perez
Hi Ben, On Tue, Jun 18, 2013 at 1:29 PM, Benjamin Root wrote: > Does the same thing happen with the v1.3.x branch? You said you tested > master, but that isn't exactly the same as v1.3.x. I just tested with the v1.3.0rc3, and the problem is present there: ((v1.3.0rc3))longs[matplotlib]> iptes

Re: [matplotlib-devel] Weird KnownFailure problem in IPython test suite with mpl master

2013-06-18 Thread Benjamin Root
On Tue, Jun 18, 2013 at 4:19 PM, Fernando Perez wrote: > Hi folks, > > > > Since SciPy'13 is coming and I know Mike will be there, I'm happy to > try to debug this face to face in Austin. I just wanted to put it on > your radar, in case it's an easy fix (esp. if it's one you can apply > before 1

[matplotlib-devel] Weird KnownFailure problem in IPython test suite with mpl master

2013-06-18 Thread Fernando Perez
Hi folks, I'm wondering if the following rings any bells for you... Right now, on an ubuntu 13.04 machine, if I install mpl master (say to my home directory), the IPython test suite fails here: iptest -vx IPython.core.tests.test_run ... ==