I think that this discussion goes in same circle than about a year ago.
At least there is not majority wanting to move code from categories/* to
combinat/*. Hence I guess it will not be done. So, what to do with
http://trac.sagemath.org/ticket/18534 ? Somebody could give it a positive
review
Hello John,
For the future, just write to
sage-trac-acco...@googlegroups.com
For now, I will reset your password and send it to you.
Vincent
On 14/06/15 12:11, John Cremona wrote:
My browser forgot my trac password for some reason. Since this was
created in about 2007 and has been
Jori Mäntysalo writes:
I understood. But when do user have an object of class lattice and he or
she wants to check that it is a lattice?
This could easily happen in a function that accepts any poset but can do
clever stuff when the input happens to be a lattice.
Say I have a ProductPoset
Just to make sure that I don't do anything stupid:
There are algorithms for generating all posets of given size up to
isomorphism. So are for lattices and IIRC for vertically indecomposable
lattices. More migth exists or be invented.
Would this be good interface:
Posets_iterator(n,
My browser forgot my trac password for some reason. Since this was
created in about 2007 and has been entered for me automatically since
then on various machines, I seem to have forgotten it (or at least the
one I remembered was not accepted). So I asked for a password reset
and was duly emailed
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
On Sat, 13 Jun 2015, Johan S. R. Nielsen wrote:
trust_me_i_know_what_i_am_doing=True for posets or lattices.
Such a parameter would make lots of sense, I think.
I have thinked about it. It needs some more thinking - how much should be
trusted? But at least for lattices it could just
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
On Sat, 13 Jun 2015, Travis Scrimshaw wrote:
I would make the function which returns a list a private function and then
the public function calls the private one and converts it into a
poset/lattice as overall,
This kind of happens when private function is in hasse_diagram.py. It is
not
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 don't think more testing is the answer. Really, the problems boil down to
a) OSX users running outdated and usupported OSX versions (i.e. anything
10.10); Do you want to run a buildbot with an OS version that has major
unfixed security issues and that has been EOL'ed by the manufacturer?
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
The Sage docker image can be found here:
https://registry.hub.docker.com/u/sagemath/sage/
On Sunday, June 14, 2015 at 3:33:45 AM UTC+2, Christopher Swenson wrote:
I like the idea of having an official Docker image.
--
You received this message because you are subscribed to the Google
Hi Jori,
when I want to iterate through posets, I do this:
sage: P3 = Posets(3); P3
Posets containing 3 vertices
sage: list(P3)
[Finite poset containing 3 elements,
Finite poset containing 3 elements,
Finite poset containing 3 elements,
Finite poset containing 3 elements,
Finite poset
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
Would this be good interface:
Posets_iterator(n, properties=None, width=None, height=None)
Do you have a specific reason for creating a class Posets_iterator? Or
would a simple function do the job?
Whatever you chose, it should probably be made available as an element of
posets.tab.
Hello,
I just made a wrong move in ticket #16810 : I used a branch made by the
patchbot and commited myself on top of that
Now the branch is refused by trac (stays red).
and looking at the commit, it seems that my patchbot believes it is still
1969
how can I correct the branch to remove this
At first sight nothing seems to be wrong. Could yoy try with the absolute
path of the method (sage.mod1.mod2.Class.method_name) instead of only the
method's name?
You could also try to compile the doc with --warn-links, it may give you
more information on what's wrong.
Just in case it may
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
Wait, so Apple does not support an OS which came out in late 2013?
On 14 June 2015 at 11:05, Volker Braun vbraun.n...@gmail.com wrote:
I don't think more testing is the answer. Really, the problems boil down
to
a) OSX users running outdated and usupported OSX versions (i.e. anything
As said in trac#18691 http://trac.sagemath.org/ticket/18691, trac#17572
http://trac.sagemath.org/ticket/17572, accepted in 6.8.beta1 breaks the
installation of several R packages ; among them git2r, on which devtools
depends. This is serious breakage, and cannot be accepted.
It turns out that
On Sunday, 14 June 2015 19:59:59 UTC+1, Frédéric Chapoton wrote:
Hello,
I just made a wrong move in ticket #16810 : I used a branch made by the
patchbot and commited myself on top of that
Now the branch is refused by trac (stays red).
and looking at the commit, it seems that my patchbot
This should work.. Is there anything in the required directory ?
Are you sure you are calling the right sage ? not another one without the
patchbot installed ?
Le dimanche 14 juin 2015 21:03:33 UTC+2, John Cremona a écrit :
I thought I would start running a patchbot, so I followed the
On Sunday, June 14, 2015 at 9:15:17 PM UTC+2, bluescarni wrote:
Wait, so Apple does not support an OS which came out in late 2013
Well there are no official statements. But
a) The rootpipe vulnerability remains unpatched on 10.9.
b) Xcode = 6.3 requires OSX 10.10.
--
You received this
On 14 June 2015 at 20:33, Frédéric Chapoton fchapot...@gmail.com wrote:
This should work.. Is there anything in the required directory ?
Are you sure you are calling the right sage ? not another one without the
patchbot installed ?
Sorry, In did install into the wrong copy. It is starting to
On Sun, Jun 14, 2015 at 9:43 AM, 'Martin R' via sage-devel
sage-devel@googlegroups.com wrote:
I have now made a minimal non-working example, using one approach that
would look sensibel to me.
It fails doing the assignment self._codomain = C in Map.__init__, which is
something I do not
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
I have now made a minimal non-working example, using one approach that
would look sensibel to me.
It fails doing the assignment self._codomain = C in Map.__init__, which is
something I do not understand.
Best,
Martin
--
You received this message because you are subscribed to the Google
I just noticed in
http://trac.sagemath.org/ticket/18701
that the methods within the SEEALSO block for codim() aren't being
linked in the HTML docs. I don't see anything different between that
block and the one for e.g. is_proper() in the same class.
Did I overlook something in the docstring
I thought I would start running a patchbot, so I followed the
instructions at http://wiki.sagemath.org/buildbot/details
- Installed and built a new copy of Sage, latest develop branch
- ./sage -i http://chapoton.perso.math.cnrs.fr/patchbot-2.3.6.spkg
- make
- ./sage -patchbot
but I get the error
On Sunday, June 14, 2015 at 12:02:31 PM UTC-7, Nathann Cohen wrote:
At first sight nothing seems to be wrong. Could yoy try with the absolute
path of the method (sage.mod1.mod2.Class.method_name) instead of only the
method's name?
You could also try to compile the doc with --warn-links,
@Andrew Sorry, your Cudd sources are fine, I misunderstood some commit message.
About naming: I personally would prefer BRiAl, it was on my shortlist for
naming the new project 9 years ago. You are free to use it.
@Martin: Thank you for your emergency call at your Blog! Its nice to see that
On 2015-06-14 11:05, Volker Braun wrote:
But more machines won't
help unless you want to install random crap on them.
I don't know if you're serious, but I think that more machines *with*
random crap might actually be a good idea.
Normally, packages aren't supposed to look in /usr/local if
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 Sat, Jun 13, 2015 at 5:21 AM, 'Martin Albrecht' via sage-devel
sage-devel@googlegroups.com wrote:
Hi all,
On Saturday 13 Jun 2015 10:41:15 Francois Bissey wrote:
I think Andrew has already done quite a bit of the porting to autotools
and
some python 3 fixes. But neither he or I want
I would like to use the graphs cospectrals to a given graph to find the
cospectral's of only a particular adjacency matrix or graph given and not
all of the given order kind help.
--
You received this message because you are subscribed to the Google Groups
sage-combinat-devel group.
To
On 06/14/2015 03:42 PM, John H Palmieri wrote:
To link to a method in another class, you should do either
...
Well that explains it. I've been working in that file for a month and
never realized there was more than one class defined. Since my new
method uses only superclass methods, I guess
41 matches
Mail list logo
