> I don't agree with Dima that putting their code into Sage is what > researchers should do, no matter what. > > I do care a lot about my research code, and I know some of it has no place > inside Sage. Maintaining it outside of Sage is not just carelessness or > laziness, it's a design choice.
For sure - and you were not in the group of people I meant, since you clearly stated you cared enough to rebase your code. Changes to Sage so that external packages like yours break is unfortunate. But I'm questioning how much we should shape our development methodology around research projects whose developers *don't* care enough to fix their code when it breaks. And it will break once in a while, as long as it is not part of Sage proper. How often do you feel that changes in Sage breaks your code? Best, Johan -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
