> > This is not a bug, is not odd, and is not an inefficiency. GAP get > started to recreate it's startup cache whenever GAP is upgraded.
Okay, fair enough, but then why did it also do this later the same day when I used a copy of Sage I had kept around but not used in several months? It wasn't the first time I'd used that copy (something like 3.2.1) but it was the first time in a while; certainly I hadn't upgraded GAP. Does it just happen every time a different revision of GAP is used, up or down? Incidentally, I think that if it's not odd, it is at the very least mysterious to anyone not intimately familiar with startup code :) - kcrisman --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
