On Tue, Nov 18, 2014 at 2:15 PM, Andrew <andrew.mat...@gmail.com> wrote: > >> > I've gone back to sage -b. >> Please don't, or at the very least don't ever report a bug or failing >> doctest without doing "make" first. > > > I am confused by Jeroen's comment. According to the sage 6.4 developers > guide: > > Rebuilding Sage > > Once you have made any changes you of course want to build Sage and try out > your edits. As long as you only modified the Sage library (that is, Python > and Cython files under src/sage/...) you just have to run: > [user@localhost sage]$ ./sage -br > > to rebuild the Sage library and then start Sage. This should be quite fast. > If you made changes to third-party packages then you have to run: > [user@localhost sage]$ make > > as if you were installing Sage from scratch. However, simply running make > will only recompile packages that were changed, so it shoud be much faster > than compiling Sage the first time. Rarely there are conflicts with other > packages, or with the already-installed older version of the package that > you changed, in that case you do have to recompile everything using: > [user@localhost sage]$ make distclean && make > > Also, don't forget to run the tests (see Doctesting the Sage Library) and > build the documentation (see The Sage Manuals). > > > That is, the manual states that the recommended route is to use sage -br > unless you are modifying packages. Does the manual need to be updated or do > Jeroen's comments only apply when playing with external packages/code? > > Btw, as William mentioned in another post, sage's requirement to use sage > -br, or make, when python files are changed shouldn't be necessary (cf. for > example, this is done automatically when using setup tools). Are their plans > to fix this?
Yes, definitely. We're I think just literally waiting for somebody persistent to decide to do it. There's no real downside. It was also dramatically reduce a massive source of confusion, where a person does foo?? in some context (maybe sage or ipython), or maybe just uses "find" on the command line, then tries to directly edit the file based on the listed source code location. There's also potentially a small savings of disk space. > > Andrew > > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- William Stein Professor of Mathematics University of Washington http://wstein.org -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
