Hi! I'm no expert on the way installation and compilation of sage work, so please bear with me as I go a little slowly (and perhaps get things somewhat wrong).
When you compile sage, .py/.pyx files from $SAGE_ROOT/devel/sage/ produce .py/.pyc files in $SAGE_ROOT/local/lib/python2.7/site-packages. If you then remove a .py or .pyx file from $SAGE_ROOT/devel/sage/ and rebuild sage, the corresponding file doesn't get deleted from the installation. This means that, for example, import statements that point to the file you removed will not raise errors. This seems like an excellent source of aggravation (as I just experienced last night, trying to figure out why a clean install of the combinat queue wouldn't work, when an old one would). #5977 (merged in 4.0) provides "sage -sync-build" which deletes old files in the installation. Would it be a good idea for sage -b to run this automatically? On my laptop, it takes just a few seconds to run sage -sync-build. So (at least for me) the added time doesn't seem like an issue. Of course, this is only really useful one time in a hundred (or less). But it seems to me that it would contribute to predictable behaviour of sage (in that one time in a hundred). cheers, Hugh -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
