one way or another, there is also sage-windows
surely it should be there.
On Friday, May 18, 2018 at 5:23:03 PM UTC+1, Erik Bray wrote:
>
> I've already had the Windows build for Sage 8.2 out since shortly
> after 8.2 was released.
>
> However, I'm putting together a new version of the installer
2018-05-19 13:48 GMT+02:00 Samuel Lelievre :
>
> Fri 2018-05 16:42:03 UTC, vdelecroix:
>
> > This is great!
>
> +1
>
> > I think that sage-release (for developers) + sage-support (for users)
> > would make sense. Perhaps not exactly the same message.
>
> Yes.
>
> > On the other hand, having the cha
Fri 2018-05 16:42:03 UTC, vdelecroix:
> This is great!
+1
> I think that sage-release (for developers) + sage-support (for users)
> would make sense. Perhaps not exactly the same message.
Yes.
> On the other hand, having the changelog easily accessible on the main
> website sagemath.org would
On 11 May 2018 at 17:17, John Cremona wrote:
>
>
> The patchbot David Loeffler and I run in Warwick is on a machine which has
> Magma on it.
>
> John
>
I'd be grateful if someone could explain how to configure the patchbot to
run the Magma optional doctests -- I couldn't find this in the patchbot
>
> OK, so how do we see whether the $SAGE_ROOT/sage script needs to be used?
> Can we just see if $SAGE_ROOT/sage is present and executable and if not,
> use $SAGE_LOCAL/bin/sage? The remark by François seems quite to the point:
> if sage is installed system-wide as a package of python2, the
