You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, plots for symbolic expressions do not go through the generic codepath, but through the expression.plot() function in symbolic/expression.pyx. This specialized codepath changes how the arguments are handled, etc. I think any functionality in the special codepath ought to go in the generic codepath, or we should reduce the generic codepath quite a bit and just pass things off to symbolic expressions. Too much code duplication here has led to lots of little inconsistencies.
As an example, this works plot(x^2,0,x,5), but this doesn't: parametric_plot((x,x^2), 0,x,5), since the first uses the expression.pyx codepath, but the parametric plot uses the generic codepath.
Right now, plots for symbolic expressions do not go through the generic codepath, but through the expression.plot() function in symbolic/expression.pyx. This specialized codepath changes how the arguments are handled, etc. I think any functionality in the special codepath ought to go in the generic codepath, or we should reduce the generic codepath quite a bit and just pass things off to symbolic expressions. Too much code duplication here has led to lots of little inconsistencies.
As an example, this works
plot(x^2,0,x,5)
, but this doesn't:parametric_plot((x,x^2), 0,x,5)
, since the first uses the expression.pyx codepath, but the parametric plot uses the generic codepath.CC: @burcin
Component: graphics
Issue created by migration from https://trac.sagemath.org/ticket/7641
The text was updated successfully, but these errors were encountered: