> > > >> Everyone working on the ticket thinks option 2 is the way to go. > >> Speaklater consists of a single python file and is already used in the > new > >> flask notebook (#11080) by including the python file. Rather than > introduce > >> a strange dependency of sage on the notebook or to separately include > the >
Well, the notebook *is* part of Sage, but not vice versa, so I don't know that it's that strange... > > Does this choice have to be "include speaklater.py in both sage and > sagenb", > > since sagenb uses it, and sagenb should function without the Sage > library? > > If that's right, then I'd prefer to avoid the code duplication, so I > prefer > > either > > > > [X] Make speaklater a standard spkg > > Please consider that every spkg has the potential of substantial > maintenance associated with it, given that the spkg system wasn't > designed to have thousands of standard spkg's at once. If you look > at the entire code of speaklater.py, you'll see it is *shorter* than > just the build/config code that we've written for some of the spkg's. > > Especially if the license allows it to be used in this way as opposed to an spkg (would there be any difference?) this does seem reasonable. For something that was optional I suppose it would be different, then an spkg would make a little more sense. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
