As Jason said, the docstrings do indicate what model (simple, for now) we're using to transform colors. We mention in several places in colors.py docstrings that we reduce R, G, and B components modulo one. But we could be more explicit.
Anyway, we could make it possible to choose between this and "capped" behavior with a sage.plot.colors.MODULE_SCOPE_VARIABLE or another way. By the way, is it possible to do the equivalent of plot(sin(x), (x, -10, 10), color=Color(x, 1-x, x)) (succinctly)? Wrap-around might be useful here. On 03/05/2010 05:04 PM, Dr. David Kirkby wrote: > Expected: > RGB color (0.51829585732141792, 0.49333037605210095, 0.0) > Got: > RGB color (0.51829585732141814, 0.49333037605210117, 0.0) Does this stem from the slightly different value of e on Solaris? http://trac.sagemath.org/sage_trac/ticket/8374 http://trac.sagemath.org/sage_trac/ticket/8375 On 03/05/2010 07:27 PM, Dr. David Kirkby wrote: > IMHO, it would be good if the trac number appropriate to the test was Try 'hg log colors.py'. Sphinx 1.0 will have an extension http://sphinx.pocoo.org/latest/ext/extlinks.html that makes it a bit more convenient to insert Sage trac URLs. > My main points are Thanks! -- 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
