Maybe it can be fixed by using:
from __future__ import absolute_import
I at least know that python 3 fixed some issues caused by relative imports.
But I'm not 100% sure if this problem is also solved.
Le mercredi 10 octobre 2012 14:14:22 UTC+2, Jeroen Demeyer a écrit :
>
> On 2012-10-10 13:59,
On Wednesday, October 10, 2012 11:04:43 AM UTC-4, John H Palmieri wrote:
>
> On Wednesday, October 10, 2012 5:31:56 AM UTC-7, kcrisman wrote:
>>
>> Incidentally, I can't find the full test log in SAGE_TESTDIR - does it
>> exist, and where is it? Again, a cursory reading of the developer
>> gui
Hi Simon,
> On 2012-10-10, Florent Hivert wrote:
> > I'd like to gather proposal and find an agreement on the names for
> > SearchForest and post_process.
>
> I don't know if my answer to sage-devel will automatically appear here
> as well. If not: I suggested "RecursiveSet" and "branch_cut"
See trac.sagemath.org/12341, that patch needs to be rebased (SAGE_DATA ->
SAGE_SHARE), but otherwise it should fix this issue.
On Wed, Oct 10, 2012 at 7:53 AM, Dima Pasechnik wrote:
>
>
> On Wednesday, 10 October 2012 18:53:03 UTC+8, John Cremona wrote:
>>
>> This is very strange indeed.
>>
>> I
On Wednesday, October 10, 2012 5:31:56 AM UTC-7, kcrisman wrote:
>
> Incidentally, I can't find the full test log in SAGE_TESTDIR - does it
> exist, and where is it? Again, a cursory reading of the developer
> guide doesn't seem to have this info, but it's probably there.
>
When running doctes
On Wednesday, 10 October 2012 18:53:03 UTC+8, John Cremona wrote:
>
> This is very strange indeed.
>
> Installing the optional database will certainly affect some elliptic
> curve tests, and we have gradually eliminated the ones which are so
> affected, or marked hem as optional. But as far a
On 10/10/12 8:53 AM, Simon King wrote:
And what you tell about the role of "post_process" makes me think it could be
renamed into "branch_cut".
Or it could renamed "visit" or "trim" or even just "callback"
Jason
--
You received this message because you are subscribed to the Google Groups
"s
Le 10/10/2012 15:53, Simon King a écrit :
Why not "RecursiveSet"? The word "Generated" seems redundant to me.
And what you tell about the role of "post_process" makes me think it could be
renamed into "branch_cut".
Best regards,
Simon
Hello,
The post_process hardly depend on a fonction (plac
Hi Florent,
On 2012-10-10, Florent Hivert wrote:
> The enumerated set is mostly described by two data:
> - roots which are the starting nodes of the recursive generation
> - children with compute the immediate successors of a node in the generation
> tree.
> One can also provide a post_pr
Hi There,
Thanks to Nicolas the Little, Sage has a SearchForest class. It is a very nice
tools to iterate through sets defined by a recursive choice
tree. Unfortunately, currently due to the name someone who doesn't know that
it exists has no chance to find it. It seems that there is an agre
Incidentally, I can't find the full test log in SAGE_TESTDIR - does it
exist, and where is it? Again, a cursory reading of the developer
guide doesn't seem to have this info, but it's probably there.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group
On Fri, Sep 28, 2012 at 02:59:14PM -0500, Jason Grout wrote:
> Fernando posted this (below) on the IPython-dev list. This looks
> like a really impressive take on how to interact with Python code.
> It's using Jython, so not immediately usable for us. But if we
> could do these things from the no
Just to put this somewhere, here are the tests which failed on my XP
box. I have strong reason to believe these are not at all
independent, but putting them here anyway. Here are two very common
types, both of which I find unsurprising, given "fork" problems on
Cygwin. I also seem to have had is
On 2012-10-10 13:59, John Cremona wrote:
> Would it not be a good idea to disable testing this file (or the bad
> part in it) until this has been fixed? In all future testing &
> development releases?
The idea is *not* to do any further releases until this gets sorted out.
--
You received this m
Would it not be a good idea to disable testing this file (or the bad
part in it) until this has been fixed? In all future testing &
development releases?
John
On 10 October 2012 12:35, Nicolas M. Thiery wrote:
> On Wed, Oct 10, 2012 at 10:45:50AM +0200, Jeroen Demeyer wrote:
>> Volker Braun dis
On Wed, Oct 10, 2012 at 10:45:50AM +0200, Jeroen Demeyer wrote:
> Volker Braun discovered a serious security vulnerability in Sage when
> doctesting sage/tests/cmdline.py
Yikes! Good job Volker detecting this!
> * if you're a Sage developer: unless nobody else can log in to your
> system, do not
This is very strange indeed.
Installing the optional database will certainly affect some elliptic
curve tests, and we have gradually eliminated the ones which are so
affected, or marked hem as optional. But as far as I no, there is no
place in the elliptic curve code where GAP is used.
Could you
On Wednesday, 10 October 2012 18:06:36 UTC+8, Jeroen Demeyer wrote:
>
> On 2012-10-10 11:58, Dima Pasechnik wrote:
> > Many tests (with new gap-4.5 spkgs at #13211) in doctest
> > sage/groups/generic.py fail if database_cremona_ellcurve,
> > which is an optional package, is not installed.
> >
On 2012-10-10 11:58, Dima Pasechnik wrote:
> Many tests (with new gap-4.5 spkgs at #13211) in doctest
> sage/groups/generic.py fail if database_cremona_ellcurve,
> which is an optional package, is not installed.
> I wonder why these tests are not marked as optional.
If these are tests introduced
Many tests (with new gap-4.5 spkgs at #13211) in doctest
sage/groups/generic.py fail if database_cremona_ellcurve,
which is an optional package, is not installed.
I wonder why these tests are not marked as optional.
Should database_cremona_ellcurve be promoted to standard?
Dima
--
You receive
Volker Braun discovered a serious security vulnerability in Sage when
doctesting sage/tests/cmdline.py
Until this is fixed, *do not run Sage doctests on shared systems*.
Doctesting individual files, different from sage/tests/cmdline.py should
still be okay.
ISSUE:
The problem is really due to a
21 matches
Mail list logo
