Simon King <[email protected]> writes: > If I am not mistaken, the sageinspect.py file in Sage was first > commited in the release of sage-2.3, March 2007, whereas the file in > sagenb was first commited in September 2009. So, it would have been > logical to use (and extend) sage/misc/sageinspect.py, instead of > copying it to sagenb/misc/. > > There is also a file sagenb/interfaces/expect.py, but that seems > totally different from sage/interfaces/expect.py. How are these > related?
Sorry, I have no more idea than you... > Are there plans to remove the code duplication in sagenb/misc (and > sagenb/interfaces?), in particular since the duplicated code is out of > synch? As far as I know there is no "action committee" for doing so, but I'm sure it's a good idea and one which the sagenb devs would support, just nobody has sat down and done it. (But then again maybe there's some mysterious reason why it is the way it is - maybe someone who knows more about the notebook can chime in.) > By comments on #11913, I got the impression that the sagenb > development takes place not on trac, but entirely on github. Is that > really the case? Yes, it is really the case. The notebook is no longer considered "part of Sage", but is instead just another upstream package. The official repository is at http://github.com/sagemath/sagenb/ if you want to hack on it :) We welcome pull requests! -Keshav ---- Join us in #sagemath on irc.freenode.net ! -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
