On Sat, Mar 10, 2012 at 06:59:56AM -0800, William Stein wrote:
> Making this change would (1) avoid an enormous amount of confusion
> when people type "foo??" and see the source location, which is not the
> path to the file they should edit
A big +1 to that change.
Another advantage is that it would not require to run `sage -b` after
each trivial change to a Python file. This will save me a few seconds
at each modify-test cycle, which will soon build up to a couple
minutes per days.
It's also much simpler to explain to newcomers (especially those using
a virtual machine where running sage -b is not immediate); we also
several times met the situation where running sage -b required a
compiler to be installed where it was not actually needed, which
forced us to download and install xcode. Which kind of ruined our
claim that "everybody could play around and edit the Sage sources".
Also that change might possibly even allow for "attaching" source
files from the Sage library, so that one could try new code without
even restarting Sage. That's not necessarily super robust, but would
save a lot of time in the easy cases; in case of doubt one can anyway
get back to a safe position by restarting Sage.
Cheers,
Nicolas
--
Nicolas M. Thiéry "Isil" <nthi...@users.sf.net>
http://Nicolas.Thiery.name/
--
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
