Since you are editing the file containing the dependency information, it is to be expected that you sometimes need to rebuild everything (depending on what you changed).
Having said that, I think there are some rough spots involving sage -b. I think the case that is not handled is if you delete a library (which is what you said); I've tripped over that one previously as well. On Tuesday, April 17, 2012 7:48:47 AM UTC-4, John Cremona wrote: > > Is it normal that after changing $SAGE_ROOT/devel/sage/module_list.py > it is not enough to do sage -b, but sage -ba is required? > > I just made some changes as I am testing a new eclib spkg which > required editing module_list.py since the new version has only one > library file instead of 4, and was surprised to see some doctest > failures in apparently unrelated places (sage/misc/sagedoc.py, > sage/misc/sageinspect.py and more) where the error was caused by teh > non-existence of the old libraries which are deleted. Is there > anywhere other than in sage_modules.py where libraries installed by > spkgs are mentioned? > > John > > -- 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
