I would say such a function belongs in the documentation only, and we should have an easy way of testing (and perhaps importing) code defined there.
On Thu, Feb 26, 2015 at 12:19 PM, Travis Scrimshaw <tsc...@ucdavis.edu> wrote: > >> > Should there be code in Sage which is extremely slow and for educational >> > purposes only? >> >> I believe such code is valuable. > > > I believe so as well. As Michael said, at the very least it's useful as a > testing tool. (Also we have done something similar by having an "algorithm" > keyword for various methods.) I also agree with Karl-Dieter that we should > spend much more time documenting the functions than moving them to a > separate folder (much less deciding on which functions should go into such a > folder). > > Best, > Travis > > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
