Hello
Leonardo kindly reviewed #9422 several days ago, which was one of the
many ways to solve #10081 :-)
Nathann
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more option
We still have 4 blocker tickets for Sage 4.6 that need work or review:
Another doctest failure in sage/graphs/graphs.py
http://trac.sagemath.org/sage_trac/ticket/10081
Doctest error in sage/schemes/generic/toric_divisor.py on OS X
http://trac.sagemath.org/sage_trac/ticket/9926
Doctest failure in
On Oct 15, 3:48 am, Jan Groenewald wrote:
> Can some people on 32bit and 64bit and different CPUs (amd as well)
> send in the output of
64bit Debian here, no problem
goodr...@y560:/media/disk30/sage-4.6.alpha3$ grep name /proc/cpuinfo
model name : Intel(R) Core(TM) i7 CPU Q 720 @ 1.6
Hi
On Sun, Oct 17, 2010 at 08:26:08PM +0200, Jeroen Demeyer wrote:
> On 2010-10-17 20:09, John Cremona wrote:
> > After doing that the doctest still passes, and I still get
> >
> > j...@selmer%dmesg|grep pari
> > [8562085.592129] gp[1128] trap invalid opcode ip:7f7f003b5be7
> > sp:7fff08dcd840 er
Two data points:
Sage 4.5.2.alpha0, Sage 4.6.alpha0 32-bit, no segfault on either
everything else is the same for both:
model name : Intel(R) Pentium(R) M processor 2.00GHz
Linux atoll 2.6.32-21-generic #32-Ubuntu SMP Fri Apr 16 08:10:02 UTC
2010 i686 GNU/Linux
sage -t "devel/sage/sage
Right, but it may have finished within 5 seconds and proceeded on to
something that is interruptable.
David
On Sun, Oct 17, 2010 at 14:53, Jeroen Demeyer wrote:
> On 2010-10-17 20:49, David Roe wrote:
> > I suspect that this is aimed at C-computations that are not wrapped in a
> > _sig_on _sig_of
On 2010-10-17 20:49, David Roe wrote:
> I suspect that this is aimed at C-computations that are not wrapped in a
> _sig_on _sig_off pair. Such code should be wrapped if it's going to
> take substantial time, but since it isn't always, two interrupts are sent.
If the code isn't wrapped in sig_on()
I suspect that this is aimed at C-computations that are not wrapped in a
_sig_on _sig_off pair. Such code should be wrapped if it's going to take
substantial time, but since it isn't always, two interrupts are sent.
David
On Sun, Oct 17, 2010 at 11:51, Jeroen Demeyer wrote:
> I noticed that the
On 10/17/2010 07:39:44 AM, Dr. David Kirkby wrote:
In a similar way I feel "bug fix only releases" would be useful,
where one concentrates on removing bugs, and not adding features.
That idea has however been very much disliked by many people.
I believe that there are many people, who are n
On 2010-10-17 20:09, John Cremona wrote:
> After doing that the doctest still passes, and I still get
>
> j...@selmer%dmesg|grep pari
> [8562085.592129] gp[1128] trap invalid opcode ip:7f7f003b5be7
> sp:7fff08dcd840 error:0 in libpari-gmp-2.4.so.3[7f7f000d3000+421000]
> [8562093.886034] gp[26164]
After doing that the doctest still passes, and I still get
j...@selmer%dmesg|grep pari
[8562085.592129] gp[1128] trap invalid opcode ip:7f7f003b5be7
sp:7fff08dcd840 error:0 in libpari-gmp-2.4.so.3[7f7f000d3000+421000]
[8562093.886034] gp[26164] trap invalid opcode ip:7fafab0bdbe7
sp:7fffb3ad7540 e
Very strange that these errors do not result in a failing doctest...
John, Jan:
On the failing machines, could you install the PARI spkg with checking
enabled? i.e. please do
env SAGE_CHECK=yes ./sage -f
http://sage.math.washington.edu/home/release/sage-4.6.alpha3/sage-4.6.alpha3/spkg/standard
On two different 64-bit ubuntu machines:
1 works fine:
j...@fermat%uname -a
Linux fermat 2.6.32-21-server #32-Ubuntu SMP Fri Apr 16 09:17:34 UTC
2010 x86_64 GNU/Linux
j...@fermat% sage -v
| Sage Version 4.6.alpha3, Release Date: 2010-10-08 |
* Warning: this is a prerelease versi
I noticed that the notebook has a feature where interrupts are retried
after 5 seconds. Does anybody have concrete examples of code which
needs this?
If code simply cannot be interrupted, that is a bug with that code.
However, if a first interrupt doesn't work but a second one works, I
believe th
On 2010-10-16 14:21, Burcin Erocal wrote:
> - look at newly submitted tickets, notify the related developers
How are you going to figure out who the "related developers" are?
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
On Sun, 17 Oct 2010 16:03:29 +0100
Martin Albrecht wrote:
> > I prefer "squad" to "wrangler," so I suggest PestSquad or
> > TracNinja. :)
>
> > Does anybody else have suggestions for a name?
>
> "Since 2005 a crack commando unit of developers is blamed for bugs
> they didn't commit. ... If you
> I prefer "squad" to "wrangler," so I suggest PestSquad or TracNinja. :)
> Does anybody else have suggestions for a name?
"Since 2005 a crack commando unit of developers is blamed for bugs they didn't
commit. ... If you have a patch, if no-one else can help, and if you can e-
mail them, maybe y
> I was thinking of setting up trac to send a notice to a mailing list
> for each new issue. Then people interested in this effort can follow
> this list and help out. Is this possible? Can someone familiar with the
> trac set up comment?
> IMHO, distributing work day by day, or weekly is still pu
On 10/17/10 03:16 PM, Jan Groenewald wrote:
Hi
I believe any belief that having "bug hunt weeks" is a long term
solution is rather flawed. The issues should be tackled at an
earlier stage.
Despite not being a sufficient solution, are they not nonetheless
necessary? Or at least helpful?
regar
Hi Martin,
On Sun, 17 Oct 2010 12:42:26 +0100
Martin Albrecht wrote:
> > We might be able to overcome this with a "bug-wrangler" team, people
> > who volunteer to
> >
> > - look at newly submitted tickets, notify the related developers,
> > ask for examples and test cases if the report doesn't
Hi Minh,
On Sun, 17 Oct 2010 01:35:01 +1100
Minh Nguyen wrote:
> On Sat, Oct 16, 2010 at 11:21 PM, Burcin Erocal
> wrote:
> > We might be able to overcome this with a "bug-wrangler" team,
>
> I would have thought "weed-wrangler" or "pest-wrangler". You know,
> Sage and horticulture :-)
We sh
On 2010-10-17 16:16, Jan Groenewald wrote:
> Hi
>
>> I believe any belief that having "bug hunt weeks" is a long term
>> solution is rather flawed. The issues should be tackled at an
>> earlier stage.
>
> Despite not being a sufficient solution, are they not nonetheless
> necessary? Or at least h
Hi
> I believe any belief that having "bug hunt weeks" is a long term
> solution is rather flawed. The issues should be tackled at an
> earlier stage.
Despite not being a sufficient solution, are they not nonetheless
necessary? Or at least helpful?
regards,
Jan
--
.~.
/V\ Jan Groen
On 10/16/10 01:21 PM, Burcin Erocal wrote:
Hi,
Motivated by the call for the bug days, here is an idea to manage the
rapidly increasing number of "new" tickets on trac.
It is well known in industry that the cost to fix bugs increases rapidly as they
time to fix them is delayed. See for exampl
> We might be able to overcome this with a "bug-wrangler" team, people
> who volunteer to
>
> - look at newly submitted tickets, notify the related developers, ask
>for examples and test cases if the report doesn't provide them,
>etc.
>
> - every once in a while, go through the open tic
RDF just uses Python's str() method to format doubles, which
apparently has a default of about 12 decimal digits. RealField is the
mpfr arbitrary precision library. The default is 53bits as well, but
it tries to print all decimal digits.
Arguably the output should be the same, but then you'd eithe
Hi Florent,
On 17 Okt., 10:42, Florent Hivert
wrote:
> On Sat, Oct 16, 2010 at 05:08:37PM -0400, David Roe wrote:
> > You can either inherit from sage.rings.commutative_ring.CommutativeRing, or
> > modify FreeModule to work better with the category framework. The first is
> > probably the easier
Right. I'm just not sure if there's any point within FreeModule that relies
on having a method defined on sage.rings.commutative_ring.CommutativeRing,
but possibly not in ParentMethods on the category. The only reason that
changing the test in the __init__ method to checking "base_ring in
Commuta
On Sat, Oct 16, 2010 at 05:08:37PM -0400, David Roe wrote:
> You can either inherit from sage.rings.commutative_ring.CommutativeRing, or
> modify FreeModule to work better with the category framework. The first is
> probably the easier option.
Just a note: Testing if some parent belong to a categ
Hi
As I've had one external confirmation, more than one
sage version, and several laptops here, I'll continue to think
about this.
Looking for libpari-gmp.so, I found these:
r...@capepoint:/usr/local/src/sage-4.5.3/local/lib#ls -l libpari*
-rwxr-xr-x 1 root root 3160120 Oct 11 17:06 libpari-gmp
30 matches
Mail list logo
