Works for me. Although some suitable phrasing to distinguish between
plwarn and plabort would be be good. plabort is aborting the function
so will probably produce odd results, but it is not fatal and is not
aborting whole program.
Andrew
On Sat, Aug 18, 2007 at 02:19:38PM -0700, Alan Irwin
On 2007-08-20 10:37+0100 Andrew Ross wrote:
Works for me. Although some suitable phrasing to distinguish between
plwarn and plabort would be be good. plabort is aborting the function
so will probably produce odd results, but it is not fatal and is not
aborting whole program.
I have had some
On 2007-08-16 14:08-0700 Alan W. Irwin wrote:
I think this issue could be addressed in two ways:
(1) Change the plabort message to PLPLOT WARNING so it isn't confused with
the much more serious PLPLOT ERROR message delivered by plexit.
I haven't heard back from anyone about this suggestion,
On 2007-08-16 18:52+0100 Andrew Ross wrote:
This (PLPLOT ERROR not delivering a non-zero error code) is nothing to do
with python - a quick test with the C examples
shows the same thing if you make zg all zeros in example 21 (this is
what is returned by griddata in the faulty Numeric case).
