Dear all,
I thought that the interfaces to gap, singular, maxima etc. are
considered to be unique parents. Apparently gap and singular are, but
maxima is only half ways unique:
--
| Sage Version 4.0, Release Date: 2009-05-29
Hello,
On Sat, Jun 6, 2009 at 12:31 AM, Simon King wrote:
>
> Dear all,
>
> I thought that the interfaces to gap, singular, maxima etc. are
> considered to be unique parents. Apparently gap and singular are, but
> maxima is only half ways unique:
Each expect interface parent corresponds to a ses
On Fri, 5 Jun 2009 20:31:51 -0700 (PDT)
Marshall Hampton wrote:
>
> I had two failures on an intel mac running 10.4 (for rc2):
>
> sage -t "devel/sage/sage/numerical/optimize.py"
> sage -t "devel/sage/sage/symbolic/relation.py"
These are all caused by making the hashes of sy
On Jun 6, 3:47 am, William Stein wrote:
> * Galois theory and ramification groups for p-adic extensions (needs
> the previous features)
I wrote a (very simplistic) implementation of Artin symbols and
decomposition and ramification groups a few months back for extensions
of *number fields*
On Sat, Jun 6, 2009 at 8:05 AM, Dr. David Kirkby wrote:
>
> I've downloaded gcc 4.4.0 with a view to building this to try to get rid
> of the internal compiler bug on the T2.
>
As a general question to the list:
I understand that sage is designed to be built by just typing make on
any platform.
Two or three things:
1. Rational conics. Magma first implemented my algorithms, which are
in eclib but not wrapped, so we could do a lot quite easily there.
But now Magma uses Denis Simon's algorithm which is better in certain
cases, and he would certainly donate his code (in gp I think).
2. El
Anthony David wrote:
> On Sat, Jun 6, 2009 at 8:05 AM, Dr. David Kirkby
> wrote:
>> I've downloaded gcc 4.4.0 with a view to building this to try to get rid
>> of the internal compiler bug on the T2.
>>
>
> As a general question to the list:
>
> I understand that sage is designed to be built by
I need to do some other things now, so will return to this later. But I
believe I've found some of the reasons Sage is not building on
t2.math.washington.edu whereas it does on my Blade 2000.
1) It is possible the gcc 4.3.1 binaries in
/usr/local/sparc-solaris-toolchain were created in a newer
On Sat, Jun 6, 2009 at 6:31 AM, Dr. David Kirkby wrote:
>
> I need to do some other things now, so will return to this later. But I
> believe I've found some of the reasons Sage is not building on
> t2.math.washington.edu whereas it does on my Blade 2000.
>
> 1) It is possible the gcc 4.3.1 binari
William Stein wrote:
> On Sat, Jun 6, 2009 at 6:31 AM, Dr. David Kirkby
> wrote:
>> I need to do some other things now, so will return to this later. But I
>> believe I've found some of the reasons Sage is not building on
>> t2.math.washington.edu whereas it does on my Blade 2000.
>>
>> 1) It is
On Sat, Jun 6, 2009 at 2:25 AM, Anthony David wrote:
>
> On Sat, Jun 6, 2009 at 8:05 AM, Dr. David Kirkby
> wrote:
>>
>> I've downloaded gcc 4.4.0 with a view to building this to try to get rid
>> of the internal compiler bug on the T2.
>>
>
> As a general question to the list:
>
> I understand t
On Sat, Jun 6, 2009 at 1:18 AM, davidloeffler wrote:
>
> On Jun 6, 3:47 am, William Stein wrote:
>
>> * Galois theory and ramification groups for p-adic extensions (needs
>> the previous features)
>
> I wrote a (very simplistic) implementation of Artin symbols and
> decomposition and ramifi
Hi,
Has anybody here ever compiled or built a recent version of Mathemagix?
http://www.mathemagix.org
I'm planning to try to make an optional source spkg of it for Sage, if
possible, but if anybody has already partly done so it would be
helpful. My main motivation is that when I gave my
> VIII. Finite Groups; Finitely-Presented Groups
>
> * I'm not enough of a group theorist to appreciate differences
> between what Sage provides via GAP and Magma. They seem pretty
> similar to me for group theory. Sage exposes much of GAP's
> functionality for groups.
William,
I
On Sat, Jun 6, 2009 at 8:45 AM, Dr. David Kirkby wrote:
> William Stein wrote:
>
>>
>> -bash-3.00$ cat /etc/release
>> Solaris 10 1/06 s10s_u1wos_19a SPARC
>> Copyright 2005 Sun Microsystems, Inc. All Rights Reserved.
>> Use is subject to lic
On Sat, Jun 6, 2009 at 9:09 AM, William Stein wrote:
> On Sat, Jun 6, 2009 at 8:45 AM, Dr. David Kirkby
> wrote:
>> William Stein wrote:
>>
>>>
>>> -bash-3.00$ cat /etc/release
>>> Solaris 10 1/06 s10s_u1wos_19a SPARC
>>> Copyright 2005 Sun Microsystems, Inc. All
On Tue, May 19, 2009 at 12:18 PM, Brian Granger wrote:
>
>> I agree that there still is a problem. Before, I didn't think that
>> Sage's matplotlib would need to have different options to even be able
>> to function.
>
> The problem that I am running into is that my
> ~./matplotlib/matplotlibrc s
William Stein wrote:
> 2009/6/4 Mike Hansen :
>> Hello,
>>
>> Now that sage.math is back up, I've cut rc0 and put it in
>> /home/mhansen/sage-4.0.1.rc0.tar. All tests passed on sage.math.
>>
>
sage-4.0.1.rc3 built fine and all tests passed on Fedora 9 and 10, 32 bit.
Jaap
--~--~-~--~
On Sat, Jun 6, 2009 at 10:25 AM, Jaap Spies wrote:
>
> William Stein wrote:
>> 2009/6/4 Mike Hansen :
>>> Hello,
>>>
>>> Now that sage.math is back up, I've cut rc0 and put it in
>>> /home/mhansen/sage-4.0.1.rc0.tar. All tests passed on sage.math.
>>>
>>
>
> sage-4.0.1.rc3 built fine and all test
There's a fully built MPIR in my home directory. The include (gmp.h)
is in /home/wbhart/mpir-trunk/ and the libraries (libgmp.*) are in /
home/wbhart/mpir-trunk/.libs
Bill.
On 6 June, 17:13, William Stein wrote:
> On Sat, Jun 6, 2009 at 9:09 AM, William Stein wrote:
> > On Sat, Jun 6, 2009 at 8
On Jun 6, 2009, at 1:06 AM, Mike Hansen wrote:
> Hello,
>
> On Sat, Jun 6, 2009 at 12:31 AM, Simon King
> wrote:
>>
>> Dear all,
>>
>> I thought that the interfaces to gap, singular, maxima etc. are
>> considered to be unique parents. Apparently gap and singular are, but
>> maxima is only half
-bash-3.00$ cat /etc/release
Solaris 10 1/06 s10s_u1wos_19a SPARC
Copyright 2005 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 07 December 2005
-bash-3.00$ cat /etc/relea
> I want to reopen this thread.
Great! matplotlib under Sage is still broken for me because of this
issue - I would love to see this resolved.
> I have a build farm with many (nearly 20) different OS's that all build and
> test
> Sage in parallel. My home directory on each of those machines i
Bill Hart wrote:
> -bash-3.00$ cat /etc/release
>Solaris 10 1/06 s10s_u1wos_19a SPARC
>Copyright 2005 Sun Microsystems, Inc. All Rights Reserved.
> Use is subject to license terms.
>Assembled 07 December 2005
Hi,
Sage-4.0.1 has been released (by William Stein and Mike Hansen). You
can download it from
http://sagemath.org/src/
as usual. I'm building binaries right now too (which should work on a
wider range of processors, by the way!).
We closed 76 tickets in this release, as listed here:
htt
2009/6/6 Brian Granger :
>
>> I want to reopen this thread.
>
> Great! matplotlib under Sage is still broken for me because of this
> issue - I would love to see this resolved.
>
>> I have a build farm with many (nearly 20) different OS's that all build and
>> test
>> Sage in parallel. My home
>> But, wait, does SAGE_HOME point to $HOME/.sage by default? That is
>> the right place for this, I just don't remember exactly where
>> SAGE_HOME points.
>
> Yep, it does. We can make sure easily enough by running Sage and asking:
>
> sage: DOT_SAGE
> '/Users/wstein/.sage/'
>
> By the way, I j
Hi Sage Devel,
Now that sage-4.0.1 has been released (13 hours ahead of schedule, and
on budget!), it's time for the *community* to work on planning the
next Sage release.
To get things going, here are some questions.
Should it be a quick 4.0.2 or a bigger 4.1? What should the planned
release
Hi!
On 6 Jun., 21:40, William Stein wrote:
> We closed 76 tickets in this release, as listed here:
> http://trac.sagemath.org/sage_trac/query?status=closed&group=resoluti...
One question about trac.
I had a ticket #6208. Originally I thought it'd be too late for
sage-4.0.1, so, I started wit
William Stein wrote:
> I have just confirmed that mark and mark2 have identical Solaris installs.
> So I guess that wasn't the problem.
OK, that confirms my initial thought that the gfortran binary was too
new is wrong.
>> Either way, that fortran compiler is definitely a problem on t2, as eve
William Stein wrote:
> Hi Sage Devel,
>
> Now that sage-4.0.1 has been released (13 hours ahead of schedule, and
> on budget!), it's time for the *community* to work on planning the
> next Sage release.
>
> To get things going, here are some questions.
>
> Should it be a quick 4.0.2 or a bigger
Brian Granger wrote:
>> I want to reopen this thread.
>
> Great! matplotlib under Sage is still broken for me because of this
> issue - I would love to see this resolved.
>
>> I have a build farm with many (nearly 20) different OS's that all build and
>> test
>> Sage in parallel. My home dire
2009/6/6 Jason Grout :
>
> Brian Granger wrote:
>>> I want to reopen this thread.
>>
>> Great! matplotlib under Sage is still broken for me because of this
>> issue - I would love to see this resolved.
>>
>>> I have a build farm with many (nearly 20) different OS's that all build and
>>> test
>>
William Stein wrote:
>
> 4. Do export MPLCONFIGDIR=$DOT_SAGE/matplotlibconfig
>
> That avoids every single problem above. :-)
Brilliant. It does leave an unused and possibly confusing matplotlibrc
file in their .sage directory, but I suppose that's happening right now,
so it's not any worse
Is there a fixed top-level home, independent of the current release
manager, for announced development archives?
William Stein wrote:
> Cool. I just cut sage-4.0.1, which is here:
>
> http://sage.math.washington.edu/home/wstein/release/4.0.1/final/sage-4.0.1/
> http://sage.math.washington.edu
> >> due to a *major* bug in the tinyMCE integration, which anybody who has
> >> seriously used the SAge notebook has run into. Nobody has come up
> >> with a clean test case though. My worksheet is unfortunately
> >> completely scrambled, and I'll have to spend an hour sorting it
> >> through
Hi,
(1) pynac .conjugate() method returns wrong answer:
f(x) = function('f',x)
f(x).conjugate()
--
f(conjugate(x))
Above is certainly not true. For example: f(x) = I + x implies
f(x).conjugate() = -I + conjugate(x) which is not equal to
f(conjugate(x))
(2) view() causes SI
> This sounds great. However, what do we do about every sage install that
> exists out there right now? Every .sage directory already has a
> matplotlibrc file that throws warnings with the current matplotlibrc.
> Back when the decision was made, some ideas were kicked around:
>
> 1. Make a FAQ
Brian Granger wrote:
>> This sounds great. However, what do we do about every sage install that
>> exists out there right now? Every .sage directory already has a
>> matplotlibrc file that throws warnings with the current matplotlibrc.
>> Back when the decision was made, some ideas were kicked a
> ah, right, I wasn't understanding your solution (for some reason, I
> thought you were using what we used before, not a new variable pointing
> to a new directory).
>
> +1 to your solution (I'd rather use your more standard directory name
> over William's non-standard name).
It is important to
40 matches
Mail list logo
