this is http://trac.sagemath.org/ticket/18724
Needs review!
On Thursday, 18 June 2015 08:56:53 UTC+1, Dima Pasechnik wrote:
On Monday, 15 June 2015 00:57:44 UTC+1, vdelecroix wrote:
All right. I recompiled Sage without chomp. Now, beyond the binary tree
issues with bliss (#18698), I have
On Monday, 15 June 2015 00:57:44 UTC+1, vdelecroix wrote:
All right. I recompiled Sage without chomp. Now, beyond the binary tree
issues with bliss (#18698), I have failing doctests related to
gap_database (all of them are marked with #option - database_gap) in
-
I would suspect that topcom should be responsible for the homology errors.
No idea for what happens to binary trees. They seem to be reversed
(left-right symmetry ?)
That could be 'bliss'. It becomes the default algorithm to compute
automorphism groups of graphs and canonical
Indeed, chomp is installed but not in the list of sage -t optional
packages.
$ sage -optional|grep -v not_installed|cut -d. -f1
[package]
arb
bliss
cbc
chomp
cryptominisat
d3js
database_cremona_ellcurve
database_gap
database_odlyzko_zeta
database_pari
database_stein_watkins
Indeed, chomp is installed but not in the list of sage -t optional
packages.
Turn 'chomp' into a new-style package and your problem is solved.
Nathann
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this group and stop
according to #16364, chomp could lead to this kind of things. But it is not
in your list !!
Le dimanche 14 juin 2015 10:29:33 UTC+2, Frédéric Chapoton a écrit :
For binary trees, I have made http://trac.sagemath.org/ticket/18698 that
needs review.
Le dimanche 14 juin 2015 10:19:22 UTC+2,
I would suspect that topcom should be responsible for the homology errors.
No idea for what happens to binary trees. They seem to be reversed
(left-right symmetry ?)
Frederic
Le dimanche 14 juin 2015 00:14:24 UTC+2, Jeroen Demeyer a écrit :
On 2015-06-13 22:21, Vincent Delecroix wrote:
Indeed, the failure for binary trees should come from canonical labeling.
It would be enough to
change the doctest so that they are no longer sensitive to that.
I am no longer that sure that TOPCOM is the other problem. What other
package is delaing with homology ? chomp ?
Frederic
Le
For binary trees, I have made http://trac.sagemath.org/ticket/18698 that
needs review.
Le dimanche 14 juin 2015 10:19:22 UTC+2, Frédéric Chapoton a écrit :
Indeed, the failure for binary trees should come from canonical labeling.
It would be enough to
change the doctest so that they are no
On Sunday, June 14, 2015 at 7:41:32 AM UTC-7, Nathann Cohen wrote:
CHomP gets used by Sage if the system detects its presence. And then it
leads to doctest errors.
It should not: do you have an example of that? Only new-style optional
packages should be automatically added to
CHomP gets used by Sage if the system detects its presence. And then it
leads to doctest errors.
It should not: do you have an example of that? Only new-style optional
packages should be automatically added to --optional=..., and chomp
is not a new-style package.
Nathann
--
You received this
It's not a matter of an optional doctest flag. The Sage code says (in
cell_complex.py)
O I see, sorry sorry. We are having the same problem with 'bliss' (#18698).
Nathann
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from
CHomP gets used by Sage if the system detects its presence. And then it
leads to doctest errors.
On Sunday, June 14, 2015 at 4:15:14 AM UTC-7, Nathann Cohen wrote:
Indeed, chomp is installed but not in the list of sage -t optional
packages.
Turn 'chomp' into a new-style package and
All right. I recompiled Sage without chomp. Now, beyond the binary tree
issues with bliss (#18698), I have failing doctests related to
gap_database (all of them are marked with #option - database_gap) in
- sage/groups/perm_gps/permgroup_named.py
- sage/tests/gap_packages.py
-
On 13/06/15 12:41, Nathann Cohen wrote:
This mail advertises a couple of changes that appeared in the latest beta:
- sage -t now involves all (installed) optional packages by default [1]
Cool!
This means that if you installed an optional package X, you don't have to add
What is our politic about that? Should we force a patchbot green light with
respect to all optional packages?
A green patchbot is not exactly a requirement for a ticket to pass.
It's more a help than anything else. You see what it says, act on that
knowledge.
1) the set of installed optional
Hellooo everybody,
This mail advertises a couple of changes that appeared in the latest beta:
- sage -t now involves all (installed) optional packages by default [1]
This means that if you installed an optional package X, you don't have to add
--optional=sage,X to sage -t in order to
On 13/06/15 13:25, Nathann Cohen wrote:
What is our politic about that? Should we force a patchbot green light with
respect to all optional packages?
A green patchbot is not exactly a requirement for a ticket to pass.
It's more a help than anything else. You see what it says, act on that
All right, I now have a lot of optional packages on librae
arb
bliss
cbc
cryptominisat
d3js
database_cremona_ellcurve
database_gap
database_odlyzko_zeta
database_pari
database_stein_watkins
database_symbolic_data
gambit
lidia
modular_decomposition
mpir
nauty
normaliz
nose
plantri
python2
sage
On 2015-06-13 22:21, Vincent Delecroix wrote:
By the way I add trouble by installing some of them which tries to write
in '/jones' or '/something' (that were two databases).
Yes, there are some old packages which don't install anymore.
In any case, like Nathann said, the automatic optional
On 2015-06-13 22:21, Vincent Delecroix wrote:
The problem is that now some tests fail (with make ptestlong)
sage -t --long src/sage/combinat/binary_tree.py # 2 doctests failed
sage -t --long src/sage/homology/examples.py # 6 doctests failed
sage -t --long src/sage/geometry/fan.py # 4
21 matches
Mail list logo
