Strange Recursion error with plot()

Hi,
I'm using matplotlib on Ubuntu Jaunty and a script that I wrote recently stopped working. I think this may have something to do with changes in matplotlib as it fails with the error pasted at http://pastebin.ca/1325576 and the main problem is that I can't actually work out what the error is because it just recurses until python stops it.
I don't think this is a fault of my script so it might be a bug with matplotlib but I'm really not sure...

The matplotlib version is 0.98.5.2-1 but I'm not sure that that will help. Numpy version is 1:1.1.1-2 and Python is 2.5.4. If I need to add more details, please ask.

Thanks.

It would help to know what exactly
you are passing to plot(). I suspect that you are passing strings at
some point where you should be passing numbers.

Darren

···

On Mon, Feb 2, 2009 at 2:17 PM, Durand <durand1@…287…> wrote:

Hi,

I’m using matplotlib on Ubuntu Jaunty and a script that I wrote recently stopped working. I think this may have something to do with changes in matplotlib as it fails with the error pasted at http://pastebin.ca/1325576 and the main problem is that I can’t actually work out what the error is because it just recurses until python stops it.

I don’t think this is a fault of my script so it might be a bug with matplotlib but I’m really not sure…

The matplotlib version is 0.98.5.2-1 but I’m not sure that that will help. Numpy version is 1:1.1.1-2 and Python is 2.5.4. If I need to add more details, please ask.

Hmm... I was passing strings! That is really weird because it used to work when I just passed strings and I have no idea why. I guess I should have converted to numbers right from the beginning. Anyway, I've fixed it by using int and float convertors! Did something change with matplotlib recently? I normally use the right types and it had been working for about 6 months with string types.

Thanks a lot!

···

On Mon, 02 Feb 2009 19:30:58 -0000, Darren Dale <dsdale24@...287...> wrote:

On Mon, Feb 2, 2009 at 2:17 PM, Durand <durand1@...287...> wrote:

Hi,
I'm using matplotlib on Ubuntu Jaunty and a script that I wrote recently
stopped working. I think this may have something to do with changes in
matplotlib as it fails with the error pasted at http://pastebin.ca/1325576and the main problem is that I can't actually work out what the error is
because it just recurses until python stops it.
I don't think this is a fault of my script so it might be a bug with
matplotlib but I'm really not sure...

The matplotlib version is 0.98.5.2-1 but I'm not sure that that will help.
Numpy version is 1:1.1.1-2 and Python is 2.5.4. If I need to add more
details, please ask.

It would help to know what exactly you are passing to plot(). I suspect that
you are passing strings at some point where you should be passing numbers.

Darren

Oh and thinking about it, I think matplotlib needs a better error message. Maybe something will less recursions =]

Thanks again.

···

On Mon, 02 Feb 2009 19:30:58 -0000, Darren Dale <dsdale24@...287...> wrote:

On Mon, Feb 2, 2009 at 2:17 PM, Durand <durand1@...287...> wrote:

Hi,
I'm using matplotlib on Ubuntu Jaunty and a script that I wrote recently
stopped working. I think this may have something to do with changes in
matplotlib as it fails with the error pasted at http://pastebin.ca/1325576and the main problem is that I can't actually work out what the error is
because it just recurses until python stops it.
I don't think this is a fault of my script so it might be a bug with
matplotlib but I'm really not sure...

The matplotlib version is 0.98.5.2-1 but I'm not sure that that will help.
Numpy version is 1:1.1.1-2 and Python is 2.5.4. If I need to add more
details, please ask.

It would help to know what exactly you are passing to plot(). I suspect that
you are passing strings at some point where you should be passing numbers.

Darren

This is fixed in SVN head now so that strings will work again (though I wouldn't
exactly say that this is supported.)

Durand wrote:

···

On Mon, 02 Feb 2009 19:30:58 -0000, Darren Dale <dsdale24@...287...> wrote:

Oh and thinking about it, I think matplotlib needs a better error message. Maybe something will less recursions =]

Thanks again.

On Mon, Feb 2, 2009 at 2:17 PM, Durand <durand1@...287...> wrote:

Hi,
I'm using matplotlib on Ubuntu Jaunty and a script that I wrote recently
stopped working. I think this may have something to do with changes in
matplotlib as it fails with the error pasted at http://pastebin.ca/1325576and the main problem is that I can't actually work out what the error is
because it just recurses until python stops it.
I don't think this is a fault of my script so it might be a bug with
matplotlib but I'm really not sure...

The matplotlib version is 0.98.5.2-1 but I'm not sure that that will help.
Numpy version is 1:1.1.1-2 and Python is 2.5.4. If I need to add more
details, please ask.

It would help to know what exactly you are passing to plot(). I suspect that
you are passing strings at some point where you should be passing numbers.

Darren

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

--
Ryan May
Graduate Research Assistant
School of Meteorology
University of Oklahoma

I think it makes sense to accept only numbers but I suppose it's needed for backwards compatibility. Maybe you could have a deprecation warning?

This is fixed in SVN head now so that strings will work again (though I wouldn't
exactly say that this is supported.)

Durand wrote:

Oh and thinking about it, I think matplotlib needs a better error message. Maybe something will less recursions =]

Thanks again.

...

···

On Mon, 02 Feb 2009 19:57:15 -0000, Ryan May <rmay31@...287...> wrote:

On Mon, 02 Feb 2009 19:30:58 -0000, Darren Dale <dsdale24@...287...> wrote:

Durand wrote:

···

On Mon, 02 Feb 2009 19:57:15 -0000, Ryan May <rmay31@...287...> wrote:

I think it makes sense to accept only numbers but I suppose it's needed for backwards compatibility. Maybe you could have a deprecation warning?

This is fixed in SVN head now so that strings will work again (though I wouldn't
exactly say that this is supported.)

Durand wrote:

On Mon, 02 Feb 2009 19:30:58 -0000, Darren Dale <dsdale24@...287...> wrote:

Oh and thinking about it, I think matplotlib needs a better error message. Maybe something will less recursions =]

I'd call it an implementation specific detail. Since it's not advertised as a
feature, I don't feel bad if it goes away in the future by changing the
implementation. The purpose of 'fixing' it was only to eliminate the infinite
recursion. :slight_smile:

Ryan

--
Ryan May
Graduate Research Assistant
School of Meteorology
University of Oklahoma

Fair enough I suppose. I'm not really sure where I got the string input idea from anyway..

···

On Mon, 02 Feb 2009 20:17:06 -0000, Ryan May <rmay31@...287...> wrote:

Durand wrote:

On Mon, 02 Feb 2009 19:57:15 -0000, Ryan May <rmay31@...287...> wrote:

I think it makes sense to accept only numbers but I suppose it's needed for backwards compatibility. Maybe you could have a deprecation warning?

This is fixed in SVN head now so that strings will work again (though I wouldn't
exactly say that this is supported.)

Durand wrote:

On Mon, 02 Feb 2009 19:30:58 -0000, Darren Dale <dsdale24@...287...> wrote:

Oh and thinking about it, I think matplotlib needs a better error message. Maybe something will less recursions =]

I'd call it an implementation specific detail. Since it's not advertised as a
feature, I don't feel bad if it goes away in the future by changing the
implementation. The purpose of 'fixing' it was only to eliminate the infinite
recursion. :slight_smile:

Ryan