On Wed, Mar 31, 2010 at 11:50 PM, David Kirkby wrote:
> On 1 April 2010 01:15, William Stein wrote:
>> On Wed, Mar 31, 2010 at 4:19 PM, Dr. David Kirkby
>>> http://wiki.sagemath.org/devel/BuildFarm/sage-4.3
>>>
>>> and report their success/failure. Wait until there is a successful build
>>> repor
On 1 April 2010 01:15, William Stein wrote:
> On Wed, Mar 31, 2010 at 4:19 PM, Dr. David Kirkby
>> http://wiki.sagemath.org/devel/BuildFarm/sage-4.3
>>
>> and report their success/failure. Wait until there is a successful build
>> report from each supported platform before releasing.
>
> That woul
On Wed, 31 Mar 2010 at 12:39PM -0700, Gokhan Sever wrote:
> I am interested in this integration idea. I haven't delved in neither
> of the packages as a developer but I have experience using both of the
> packages --Sage being the more preferable option.
>
> Sage is a powerful scientific Python di
PLEASE ADVERTISE WHERE APPROPRIATE
Sage Days 20.5
Second Announcement
Fields Institute, May 3--7, 2010
IMPORTANT UPDATES
The deadline to apply for financial support has been
On Wed, Mar 31, 2010 at 4:19 PM, Dr. David Kirkby
wrote:
> William Stein wrote:
>
>> My first worry -- how can you fix the problems that do get reported?
>> Often when people report build problems, those problems are on their
>> personal crufty Linux installs, which they won't or can't give access
Hi,
This user is reporting that the new iconv spkg fails if SAGE_CHECK is
set. This is now trac #8638:
http://trac.sagemath.org/sage_trac/ticket/8638
The fix is easy -- add two lines to spkg-check in that spkg.
William
On Wed, Mar 31, 2010 at 3:26 PM, William Laffin
wrote:
> Hi Dr. Stein
William Stein wrote:
My first worry -- how can you fix the problems that do get reported?
Often when people report build problems, those problems are on their
personal crufty Linux installs, which they won't or can't give access
to, and which can be (mis-)configured in all kinds of ways, or even
On Wed, Mar 31, 2010 at 1:14 PM, Andrey Novoseltsev wrote:
>> > We all want more testing. I see two options:
>>
>> > (1) Change lots of other people's behavior.
>> > (2) Set up a large-scale automated build farm.
>>
>> > Though we have neither right now, I see (2) happening before (1).
>>
> ...
>>
MPIR 1.4 is probably not far out. I'm hopeful Sage will include that.
The MPIR Team
On 5 Mar, 14:32, Bill Hart wrote:
> I doubt Sage will includempir1.3.1. Numerous versions of sage have
> past without including this, so presumably there is some reason for
> that.
>
> But I'm sure sage will even
On Mar 31, 1:14 pm, Andrey Novoseltsev wrote:
> However more than once I regretted "sage -upgrade" because it broke
> something that I was using and had to use it again right then.
Don't use "sage -upgrade" like this! I always copy the entire Sage
directory first: if I have a directory "sage-4-
> > We all want more testing. I see two options:
>
> > (1) Change lots of other people's behavior.
> > (2) Set up a large-scale automated build farm.
>
> > Though we have neither right now, I see (2) happening before (1).
>
...
> If I don't either
>
> (a) get much more money in grants,
> (b)
On Mar 29, 12:15 pm, William Stein wrote:
> Hi,
>
> The following is from Markus, director of the GeoGebra project:
>
> "GeoGebra is now a mentoring organization for Google Summer of Code
> 2010 (seehttp://www.geogebra.org/trac/wiki/Gsoc2010). This means that
> Google pays students $5500 for a 2
On 31 Mrz., 19:38, Harald Schilly wrote:
> On Mar 30, 3:47 pm, emil wrote:
>
> > I have uploaded
>
> > SageLivePup08.iso
>
> Cool, thanks! For the next time, could you send me or minh an email so
> that this doesn't go unnoticed? I'll update it on the mirror
> herehttp://boxen.math.washington.e
On 31 March 2010 17:59, William Stein wrote:
> If I don't either
>
> (a) get much more money in grants,
> (b) have more volunteers willing to do (2) and (1), or
> (c) start a company and sell Sage binaries that are more polished,
>
> then indeed Sage releases will likely never be as polishe
On Mar 30, 3:47 pm, emil wrote:
> I have uploaded
>
> SageLivePup08.iso
Cool, thanks! For the next time, could you send me or minh an email so
that this doesn't go unnoticed? I'll update it on the mirror here
http://boxen.math.washington.edu/sage/livecd/index.html now.
For the future, could you
On Wed, Mar 31, 2010 at 9:51 AM, Robert Bradshaw
wrote:
> On Mar 31, 2010, at 5:45 AM, David Kirkby wrote:
>
> [...]
>
>> IMHO, if Sage is ever to become a viable alternative to Mathematica,
>> Maple, MATLAB and Macsyma, you are going to have to shift the emphasis
>> towards more thorough testing
On Mar 31, 2010, at 5:45 AM, David Kirkby wrote:
[...]
IMHO, if Sage is ever to become a viable alternative to Mathematica,
Maple, MATLAB and Macsyma, you are going to have to shift the emphasis
towards more thorough testing before making releases. I can't imagine
Wolfram Research shipping bina
On Wed, Mar 31, 2010 at 3:49 AM, Peter Jeremy wrote:
> On 2010-Mar-29 16:08:48 -0700, William Stein wrote:
>>Let's make some system-wide Python a prerequisite. Full stop.
>
> It's not quite 1st April even here.
This is not an April fools joke.
>
> I could understand Python being a prerequisite
On Wed, Mar 31, 2010 at 5:45 AM, David Kirkby wrote:
> On 31 March 2010 01:57, William Stein wrote:
>> On Tue, Mar 30, 2010 at 4:33 PM, Dr. David Kirkby
>
>>> Could it be a forward compatibility issue?
>>>
>>> 1) Sage 4.3.4 contains the latest iconv (1.13.1)
>>>
>>> 2) Code is Sage tests iconv, f
On 31 March 2010 01:57, William Stein wrote:
> On Tue, Mar 30, 2010 at 4:33 PM, Dr. David Kirkby
>> Could it be a forward compatibility issue?
>>
>> 1) Sage 4.3.4 contains the latest iconv (1.13.1)
>>
>> 2) Code is Sage tests iconv, finds it's a late version, and makes use of the
>> features in t
I had no problem on linux or a mac running 10.5. But on my 10.6.2 I
get this:
I can't seem to build 4.3.5 on OS X 10.6.2. Here is the tail of my
install log:
Undefined symbols:
"_einflate", referenced from:
_ft_gzip_file_fill_output in ftgzip.o
"_einflateInit2_", referenced from:
On 2010-Mar-29 16:08:48 -0700, William Stein wrote:
>Let's make some system-wide Python a prerequisite. Full stop.
It's not quite 1st April even here.
I could understand Python being a prerequisite if Sage was going to
use it at runtime but requiring it to be present solely to build
another cop
On Mar 31, 11:40 am, "ma...@mendelu.cz" wrote:
> Dear Sage developers
>
> var('h1')._maxima_() returns a binomial coefficient instead of 'h1'.
> I was not find an explanation for this behavior in sage/interfaces and
> sage/symbolic. Do you have any explanation for this (I think
> unintended) beha
Dear Sage developers
var('h1')._maxima_() returns a binomial coefficient instead of 'h1'.
I was not find an explanation for this behavior in sage/interfaces and
sage/symbolic. Do you have any explanation for this (I think
unintended) behavior?
See trac http://trac.sagemath.org/sage_trac/ticket/8
24 matches
Mail list logo
