#5438: [with patch, positive review] Incorrect documentation and/or
functionality
in plot filling
----------------------+-----------------------------------------------------
Reporter: kcrisman | Owner: kcrisman
Type: defect | Status: assigned
Priority: minor | Milestone: sage-3.4.2
Component: graphics | Keywords: plot fill
----------------------+-----------------------------------------------------
Comment(by kcrisman):
Replying to [comment:4 mvngu]:
> produce the same looking plot. Notice that in the first command, the
value for the fill option is the string {{{"0.5"}}}. In the second
command, the value for the fill option is the number {{{0.5}}}. So for the
fill option, if its value is a number given as a string, then the string
is parsed for its numeric value. Is that intended?
Hmm, I would say that the answer is yes, because I didn't change that part
of the code:
{{{
sage: from sage.ext.fast_eval import fast_float, fast_float_constant,
is_fast_float
sage: fill=3
sage: hasattr(fill,'__call__')
False
sage: float(fill)
3.0
sage: fill='3'
sage: hasattr(fill,'__call__')
False
sage: float(fill)
3.0
}}}
So since that string can be coerced to a float, apparently the original
author intended this behavior (even if implicitly). Which certainly seems
reasonable to me; it's not clear that it should throw an exception, and I
can't think of another reasonable legitimate interpretation.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/5438#comment:5>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of
Reinventing the Wheel
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---
