Florent Hivert wrote: > Dar all, > >>>> I'd rather fix the infrastructure if at all possible ... >>> It should be fairly simple to add a wipe option that kills all left >>> over pyc and so build remnants, but I personally tend to wipe out >>> "build" and just rebuild the Sage library if I can't manually fix it >>> in 2 minutes. >> We are too often working on our own laptop, where a sage build takes >> way too long compared to our usual debugging cycle. > > My university is 2h by train/metro away from my home. Which means that during > the week I've at least 2h30 each day of work without net connection. > > +1 > >> PLEEEAAAAAAAAAAAAAAASE! A free Sage-Combinat T-Shirt and an invitation >> to a good restaurant to anyone kind enough to take care of this! > > +((100)!^(100!))!
Wow, if the price tag on this feature is bumped up to that.... So, is this what is being asked for: * Whenever you build, compare the list of .pyc files and .so files in the build directory with the list in the source directory. If a file has been removed in the source directory, delete the corresponding .pyc and .so files (or maybe even: if a file has been removed from version control, then wipe the .pyc/.so files, even if the actual file still exists in the source directory). OR * Make an option that wipes all .pyc files and .so files in any directory that has changed OR something else? I don't have time to do this...but that offer of a T-Shirt is pretty tempting :). P.S. This has bitten me too plenty enough to be annoying. Jason --~--~---------~--~----~------------~-------~--~----~ 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 For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
