On 29 May 2014 21:02, Nathann Cohen <nathann.co...@gmail.com> wrote: >> > BUT: this would result in code in Sage that is not useful purely >> > within Sage. And there are people, loud people, that say there should >> > not be such code in Sage.
I do not know what is "code in Sage that is not useful purely within Sage". John >> >> I can hear your frustration ... In similar situations, it helped me to >> keep in mind that loud people are not always representative. Of course >> the difficulty is to fetch the opinion from the others. > > > Ahahahahahahah. Well, only including in Sage code that is useful to "a Sage > user" or "other developpers" does not seem that far-fetched. I still do not > see what the problem is with that. > > Err.... Well, assuming the obvious : that I am the "loud people" you > mention. > > Nathann > > -- > 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.
