Hello,
I am trying to compile Sage-5.6.rc0 inside a virtual machine with
SAGE_ATLAS_ARCH=Corei7,SSE3,SSE2,SSE1 and it fails with
First attempt: automatic tuning.
Running configure with arch = Corei7 and isa extensions ['SSE3',
'SSE2', 'SSE1']
Running ../src/configure --prefix=/home/andrey/sage-5
>
>
> It's also worth noting that there's a ticket (#11273) that has been in
> review for roughly two years (most of the delay is my fault) that adds a
> lot of new functionality to this package. It doesn't change any code in
> this section, although it does add more documentation saying roughl
Hi, I'm the primary author of that file.
There are two things being discussed here, the divide-by-zero warnings and
the numerical errors. The same section of code is related to both:
olderr = np.geterr()['invalid'] # checks the current error handling
> np.seterr(invalid='ignore')
> K = np.array
Hi!
On 2013-01-18, Charles Bouillaguet wrote:
> The développer manual claims that if a doctoring contains the three word
> "optional", "package" and "installed", then all the doctests there are
> considered optional.
>
> I couldn't make this work, and looking a bit closer at
> $SAGE_ROOT/local
Hi,
The développer manual claims that if a doctoring contains the three word
"optional", "package" and "installed", then all the doctests there are
considered optional.
I couldn't make this work, and looking a bit closer at
$SAGE_ROOT/local/bin/sage-doctest, I couldn't find a trace of this.
D
Hi!
On 2013-01-14, Simon King wrote:
> On 2013-01-14, Volker Braun wrote:
>> Its probably just a matter of asking politely. Simon, do you know Bettina
>> Eick?
>
> Yes.
>
>> She seems to be the one who actually wrote the code. Do you want to
>> send her a message?
I did, and Bettina Eick wou
Hi Simon,
Thanks for your answer.
> > And the second errors occurs with the symbolic ring (example from
> > doctest)
> > {{{
> > sage: t = log(2)
> > sage: u = t.maxima_methods()
> > sage: SR(u)
> > Traceback (most recent call last):
> > ...
> > TypeError: Set_PythonType must be initialized with
On 2013-01-18 10:08, Jean-Pierre Flori wrote:
> * investigation of problem on OS X
Indeed, some OS X expert should look at this. I don't know why it works
on a pretty wide range of systems, except OS X.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" gr
Hi,
On 2013-01-18, vdelecroix <20100.delecr...@gmail.com> wrote:
> And the second errors occurs with the symbolic ring (example from
> doctest)
> {{{
> sage: t = log(2)
> sage: u = t.maxima_methods()
> sage: SR(u)
> Traceback (most recent call last):
> ...
> TypeError: Set_PythonType must be initi
1. Sage LiveCD, based on Ubuntu 12.04.1, with Sage 5.5 Source Code, and all
build and runtime dependencies
size: 1.5 GB iso file, 64bit, EN+FR on image, other languages available
from repos, automatic updates from aims/sagemath PPA.
2. Sage LiveCD, based on Ubuntu 12.04.1, with Sage 5.5 compiled, a
Am Freitag, 18. Januar 2013 10:54:39 UTC+1 schrieb Jan Groenewald:
>
> Hi
>
> This is now http://trac.sagemath.org/sage_trac/ticket/13966
>
> Could the author of each LiveCD/USB image send a one or two-line
> description of it? Of when it is appropriate?
> Size of image, Hardware Requirements (3
On 18/01/13 23:25, Volker Braun wrote:
> On Friday, January 18, 2013 9:47:53 AM UTC, François wrote:
>
> doctest:1: RuntimeWarning: divide by zero encountered in divide
> It doesn't correlate to any of the error you reported but it adds to
> the feeling that something needs fixing in t
FWIW its not in my patchbot logs.
On Friday, January 18, 2013 8:58:55 AM UTC, Jeroen Demeyer wrote:
>
> After merging a bunch of tickets, I found this failure:
>
> sage -t "devel/sage-main/sage/rings/polynomial/polynomial_ring.py"
>
On Friday, January 18, 2013 9:47:53 AM UTC, François wrote:
> doctest:1: RuntimeWarning: divide by zero encountered in divide
> It doesn't correlate to any of the error you reported but it adds to
> the feeling that something needs fixing in that file.
I would say it is precisely the kind of m
Hi
This is now http://trac.sagemath.org/sage_trac/ticket/13966
Could the author of each LiveCD/USB image send a one or two-line
description of it? Of when it is appropriate?
Size of image, Hardware Requirements (32/64 bit, resource requirements of
desktop environment), languages, whether or not a
On 18/01/13 22:40, Jeroen Demeyer wrote:
> On 2013-01-18 08:31, Jeroen Demeyer wrote:
>> After further investigating, I found the culprit to be ATLAS. Which
>> means that either:
>> * ATLAS returns quite bad results for some tuning parameters.
>> * or riemann.pyx misuses ATLAS in a way which caus
On 2013-01-18 08:31, Jeroen Demeyer wrote:
> After further investigating, I found the culprit to be ATLAS. Which
> means that either:
> * ATLAS returns quite bad results for some tuning parameters.
> * or riemann.pyx misuses ATLAS in a way which causes small errors to
> become very big.
Third po
Am Freitag, 18. Januar 2013 07:05:54 UTC+1 schrieb Jan Groenewald:
>
> Hi Jason,
>
> No, I don't have an account. Yes, that would be reasonable from my side.
>
> Regards,
> Jan
>
Maybe ask W. Stein directly about server access. I think it should be
possible to get an account.
Although I made
Hi,
I am working on #10962 about pickling of Set_PythonType (in sage/
structure/parent.pyx). I added a fast check in the constructor to
verifies that the argument is a and not something
else... it causes two errors. The first one occurs in sage/schemes as
in
{{{
sage: P2. = toric_varieties.P2()
Dear all,
The FLINT update has been stuck for some time at
http://trac.sagemath.org/sage_trac/ticket/12173.
On the Sage's library side, the changes are numerous but mostly easy, i.e.
we just switch to the new interface of FLINT.
It still needs:
* proper review of these changes (John Cremona alre
After merging a bunch of tickets, I found this failure:
sage -t "devel/sage-main/sage/rings/polynomial/polynomial_ring.py"
**
File
"/release/merger/sage-5.7.beta0/devel/sage-main/sage/rings/polynomial/polynomial_ring.py",
line 16
21 matches
Mail list logo
