Simon King <[email protected]> writes: > However, looking at the code, I wonder: There is devel/sage/sage/misc/ > sageinspect.py, and there also is devel/sagenb/sagenb/misc/ > sageinspect.py. The two files are *different*, in fact the file in > sagenb does not contain some patches that are important for source > inspection. It seems like the file in devel/sagenb is an old snapshot > of the file in devel/sage. > > Why is that? I mean, I can understand that the old stuff in devel/sage/ > sage/server/notebook is not actively maintained. But why is the > notebook not simply using the stuff from devel/sage whenever possible?
Possibly the stuff has moved from sagenb to Sage proper in preparation for the Flask notebook, which does not (I hypothesize) use the sageinspect.py found in the notebook, but uses the one in Sage. You might try to install the new notebook (at #11080) and see if you still see this weird code reuse... there are some old files still in the new sage notebook which are not used by anything, I believe. Maybe this sagenb/misc/sageinspect.py is one of them. (See ticket #11080 for an SPKG to install.) -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
