Why separate it out into another function _list_plot? Why not just put a try block into the function? That seems like it would make the source harder to read and tracebacks longer without much benefit. It's also another matter whether or not complex numbers being in the list are an "exceptional" situation. We currently do have if/else blocks handling the different types of input for the list_plot function. What's so special about complex numbers that they should be separated out with a try block and/or a wrapper function?
What about if we just check is_ComplexNumber for things in the dataset? Is that not enough? Should be faster than coercing them, I imagine. Do we need list_plot to be smart enough to figure out if things in the data set are any object that could possibly be a complex number in disguise...? In any case, a 7 microsecond slowdown per datapoint is not a huge deal for a point plotter, I think. -Keshav ---- Join us in #sagemath on irc.freenode.net ! -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
