Hi folks,
On Thu, Oct 16, 2008 at 11:25 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> Hello folks,
>
> due to the init.sage vs. IPython SNAFU I have just released a Sage
> 3.1.4 with two additional small fixes. Sources and a sage.math only
> binary (this time tested to extract :)) are in
>
> http:/
mabshoff wrote:
> Hello folks,
>
> due to the init.sage vs. IPython SNAFU I have just released a Sage
> 3.1.4 with two additional small fixes. Sources and a sage.math only
> binary (this time tested to extract :)) are in
>
> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.1.4/
>
Hi Michael,
Thanks a lot for the reply. Sorry, I forgot that you mentioned this
before. No hassle about the upgrades, as it's easy enough to compile
from source. Sleep well!
Stan
mabshoff wrote:
> The question is fair game here. The reason the upgrade does not work
> to 3.1.3 is that I held u
On Oct 17, 12:59 am, Stan Schymanski <[EMAIL PROTECTED]> wrote:
> mabshoff wrote:
> >
Hi Stan,
> > I started building binaries and am preparing to push out the release
> > for upgrades, so just don't attempt to upgrade just yet :)
>
> Perhaps this is a question for sage-support, but when I tr
mabshoff wrote:
>
>
> I started building binaries and am preparing to push out the release
> for upgrades, so just don't attempt to upgrade just yet :)
>
Perhaps this is a question for sage-support, but when I try to upgrade
from my sage 3.1.2, I get the message "make: Nothing to be done for
