Hi David,
> > Sage documentation still has a lot of dangling links. To check if there are
> > some please use the recently added option --warn-links as in:
> >
> > sage --docbuild --warn-links reference html
> >
> > Beware that it triggers a full recompilation of the doc the first time y
On Saturday, 24 March 2012 13:33:59 UTC, Nicolas M. Thiéry wrote:
>
> On Sat, Mar 24, 2012 at 04:35:42AM -0700, David Loeffler wrote:
> >I tried to use this, but ran into the following stupid glitch.
Yeah, those recompilations are a pain. In such a situation, one would
> want to hack sage-
On Sat, Mar 24, 2012 at 04:35:42AM -0700, David Loeffler wrote:
>I tried to use this, but ran into the following stupid glitch. If you do,
>in a clean copy of Sage, the following commands:
>
>sage -b main
>sage --docbuild --warn-links reference html
>sage -clone foo
>sage -
On Thursday, 22 March 2012 21:37:19 UTC, fhivert wrote:
>
> Hi there,
>
> Sage documentation still has a lot of dangling links. To check if there are
> some please use the recently added option --warn-links as in:
>
> sage --docbuild --warn-links reference html
>
> Beware that it trigger
Hi Niles,
On Sat, Jun 11, 2011 at 3:16 AM, Niles wrote:
> Thanks; I just tried it out. Here are some minor comments:
>
> * The phrase "bleeding edge" still appears in the download directory
> [1], and also in the readme file.
>
> * The large warning says the directory contains "builds", which lea
What about calling them "development snapshots"?
-Keshav
Join us in #sagemath on irc.freenode.net !
--
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
Thanks; I just tried it out. Here are some minor comments:
* The phrase "bleeding edge" still appears in the download directory
[1], and also in the readme file.
* The large warning says the directory contains "builds", which lead
me to think that I was downloading a binary for my system (even
th
Hi Jason,
On Fri, Jun 10, 2011 at 1:22 AM, Jason Grout
wrote:
> Perhaps: "unstable" or "nightly" or "latest alpha", or even "cutting edge".
> The warning could still be big and bold (like it should be!).
I have chosen "Development Release". Please test it out to see how usable it is.
--
Regar
I agree about bleeding edge. Cutting edge sounds bettwe, but this is
only for a menu choice, so why not "development version"? As long as
developers can find it easily (though I usually download from a link
in an email anyway) and non-developers are gently discouraged from
expecting this to be th
On 6/9/11 8:11 AM, Minh Nguyen wrote:
On Thu, Jun 9, 2011 at 11:05 PM, Minh Nguyen wrote:
Please see
http://www.sagemath.org/download-latest.html
which is linked from
http://www.sagemath.org/download.html#DevelRelease
On second thought, the page
http://www.sagemath.org/download-latest.htm
Could be worth mentioning in the devel release announcements as well,
with a suitable "beware" for delay. Boxen can be slow at times.
On Jun 8, 11:44 am, Jeroen Demeyer wrote:
> The last development version of Sage is always mirrored, see for
> examplehttp://boxen.math.washington.edu/sage/devel
11 matches
Mail list logo
