Re: [sage-devel] Soliciting reviewers...

2012-08-21 Thread Robert Bradshaw
On Tue, Aug 21, 2012 at 10:45 PM, William Stein wrote: > On Tue, Aug 21, 2012 at 6:38 PM, Kwankyu Lee wrote: >> Hi, >> >> This is a question and suggestion. Are our tickets in "needs review" status >> being timely reviewed? Judging from my own (limited) experiences, it seems >> not. I again find

Re: [sage-devel] Soliciting reviewers...

2012-08-21 Thread William Stein
On Tue, Aug 21, 2012 at 6:38 PM, Kwankyu Lee wrote: > Hi, > > This is a question and suggestion. Are our tickets in "needs review" status > being timely reviewed? Judging from my own (limited) experiences, it seems > not. I again find myself soliciting a reviewer for my simple ticket #11593. > > I

Re: [sage-devel] Soliciting reviewers...

2012-08-21 Thread Robert Bradshaw
On Tue, Aug 21, 2012 at 6:38 PM, Kwankyu Lee wrote: > Hi, > > This is a question and suggestion. Are our tickets in "needs review" status > being timely reviewed? Judging from my own (limited) experiences, it seems > not. I again find myself soliciting a reviewer for my simple ticket #11593. > > I

[sage-devel] Soliciting reviewers...

2012-08-21 Thread Kwankyu Lee
Hi, This is a question and suggestion. Are our tickets in "needs review" status being timely reviewed? Judging from my own (limited) experiences, it seems not. I again find myself soliciting a reviewer for my simple ticket #11593. If this is the case, how about adopting a policy similar to the

[sage-devel] comparisons of Sage integer and numpy integer (trac 13386)

2012-08-21 Thread Vincent Delecroix
Hi, I propose a tiny patch ([1]) to solve several problems that appear on that list about comparisons of Sage integer with numpy.integer (namely [2] and [3]). The main problem is for me {{{ sage: import numpy sage: numpy.int32(1) == 1 True sage: 1 == numpy.int32(1) False }}} The issue was to modif

[sage-devel] How to debug a segfault that only occurs in parallel tests?

2012-08-21 Thread Simon King
Hi! At #13370, I have a debugging problem that seems difficult to me. There is a segfault when testing sage/rings/polynomial/infinite_polynomial_element.py, but the segfault seems only to occur when I do parallel tests. To be precise: sage -t devel/sage/sage/rings/polynomial/infinite_polynomial

[sage-devel] Re: one doctest fails on ubuntu 12.04

2012-08-21 Thread Keshav Kini
Rajeev Singh writes: > I have compiled sage-5.2 on ubuntu 12.04. The following test fails - > > sage -t --long -force_lib > "devel/sage/sage/modular/modform/find_generators.py" > > There was a segmentation fault. Can you rerun that particular file and attach or pastebin the output, so we c

[sage-devel] one doctest fails on ubuntu 12.04

2012-08-21 Thread Rajeev Singh
Hi, I have compiled sage-5.2 on ubuntu 12.04. The following test fails - sage -t --long -force_lib "devel/sage/sage/modular/modform/find_generators.py" There was a segmentation fault. Rajeev -- -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe fro

Re: [sage-devel] LLL-variants

2012-08-21 Thread Julien Puydt
Le 20/08/2012 19:46, spyros a écrit : I would like to develop variants of the LLL algorithm in SAGE. Can someone please inform me which variants already exist? I was hoping someone more knowledgeable would answer, but as it doesn't happen : sage contains libfplll, pari and flint -- I think tho

[sage-devel] Re: Proposal: Remove GNUTLS from Sage.

2012-08-21 Thread Keshav Kini
Keshav Kini writes: > If this is still your view, it seems to me that we can probably even get > rid of the OpenSSL headers dependency which has been causing users so > much trouble since 5.2 was released. We can just stop packaging > pyOpenSSL with the sagenb SPKG, and instead require users who w