> I will be using experimental lambdify for writing the backend for
> extending matplotlib backend and implementing svgfig backend.
> Will it be a problem? Because I think experimental_lambdify might change a
> lot.
If you use https://github.com/sympy/sympy/pull/673 for your work, you
will not have a choice as the code there depends on
experimental_lambdify. Using simply lambdify will not permit you to
plot a substantial part of the possible expressions as lambdify does
not support them. Anyway, experimental_lambdify is not public and the
docstring clearly explains that it is not ready for use outside the
plotting module.

Moreover, I doubt that you will have to use it. The backends do not
use it directly - the matplotlib backend is mostly done and the svgfig
backend can just mimic it and nowhere in that part of the code one
uses experimental_lambdify directly. Of course there are many
potential bugs to be fixed there, but this is another problem.

It would be more interesting to add another types of plots as
mentioned on the ideas page. This is the only reason you would have to
work on the matplotlib backend (besides bug fixes (the module is not
well tested so you will have many such fixes to do)).

Finally, I am not a professional programmer and it may turn out that
the code I have written is an unsustainable mess :) (hopefully it is
not). Before starting work on it, you should really review it and
criticize strongly any drawbacks that you see, even if they are in the
basic architecture of the module.

-- 
You received this message because you are subscribed to the Google Groups 
"sympy" 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/sympy?hl=en.

Reply via email to