On 2015-07-17 13:15, Julien Puydt wrote:
I'm not sure I understand how it can be an extra burden
The problem is not so much with additional packages, it's with additional packages which only exist for Sage. If there is an active upstream which would exist anyway without Sage, that's healthy.
However, "upstream" packages which are really part of Sage are a maintainance burden. I think that SageNB is a very good example of this: part of the reason that so little SageNB development happened recently is because it is a separate package. (I know there are other reasons too, but that's not the point here)
Jeroen. -- 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.
