On Mon, Feb 1, 2010 at 3:03 AM, Minh Nguyen wrote:
> Hi folks,
>
> This is a rather quick release since Sage 4.3.2.alpha0. The original
> plan was for Sage 4.3.2 to be out a few days before Sage Days 20.
> However, the schedule for the final release has been shifted [1] to
> Saturday 06th February
Hi Alex,
On Mon, Feb 1, 2010 at 11:54 PM, Alex Ghitza wrote:
> The following tests failed:
> sage -t -long devel/sage/sage/parallel/decorate.py # Segfault
>
> This only seems to happen when I run the whole testsuite. If I try to
> run this test on its own, it always passes. (I ha
See below for 2 build/test reports.
(I had also tried upgrading on Mac OS 10.5.8, but that gave me a
bunch of doctest failures. I will double-check before reporting.)
Best,
Alex
- ONE --
OS version: Arch Linux
Machine name: artin
Architecture:
Hi Alex,
On Mon, Feb 1, 2010 at 8:23 PM, Alex Ghitza wrote:
> Could it be that one of the repositories had uncommited changes?
There is no uncommitted changes for the following files:
* sage-banner
* sage-gdb-commands
* sage-maxima.lisp
* sage-verify-pyc
Before packaging up the Sage 4.3.2.a
Just a quick note: on two different systems, upgrading from alpha0 has
mercurial put me in commit mode with something like:
HG: changed sage-banner
HG: changed sage-gdb-commands
HG: changed sage-maxima.lisp
HG: changed sage-verify-pyc
Could it be that one of the repositories had uncommited chang
Hi folks,
This is a rather quick release since Sage 4.3.2.alpha0. The original
plan was for Sage 4.3.2 to be out a few days before Sage Days 20.
However, the schedule for the final release has been shifted [1] to
Saturday 06th February 2010, Pacific time. The upcoming rc0 release is
strictly for b
