[sage-devel] Re: parents and elements and categories

Sorry for being slow. I just tried to make FindStatMap inherit from Morphism, and create its parent "on the fly" (because the parent doesn't do all that much anyway) with Morphism.__init__(self, homset(self.domain(), self.codomain()) However, sage complains that homset wants a parent (and sel

[sage-devel] Re: sage-6.7 build failed on Cygwin64 for python-2.7.8 No module named crypt

initially I tried to install via git as described here http://trac.sagemath.org/wiki/Cygwin64Port but, because I have a very poor internet connection behind some company firewalls I dit not suceed with git clone git://trac.sagemath.org/sage.git. So I downloaded sage-6.7.tar.gz

[sage-devel] Re: parents and elements and categories

Hi Martin, Le lundi 8 juin 2015 10:04:08 UTC+2, Martin R a écrit : > > Sorry for being slow. I just tried to make FindStatMap inherit from > Morphism, and create its parent "on the fly" (because the parent doesn't do > all that much anyway) with > > Morphism.__init__(self, homset(self.domain()

[sage-devel] show() vs. plot() on digraphs or posets

Documentation on posets.py seems to say that show() accepts some parameters "in itself" and others to be forwarded to plot(). But is there really anything on the first class? Or to put it other way: can documentation of show() be simplified to something like "Display the Hasse diagram of the p

[sage-devel] Re: sage-6.7 build failed on Cygwin64 for python-2.7.8 No module named crypt

IMHO running Cygwin without admin rights is next to impossible :( On Monday, 8 June 2015 11:15:33 UTC+1, Stefan Auracher wrote: > > initially I tried to install via git as described here > http://trac.sagemath.org/wiki/Cygwin64Port but, because I have a very > poor internet connection behind som

[sage-devel] Re: sage-6.7 build failed on Cygwin64 for python-2.7.8 No module named crypt

In the past I had the same experience. I did it but in the last years, but it was really difficult. But recently I tried an install of cygwin with the setup-x86_64.exe --no-admin switch and it worked very well wihout any problems. The recent problems with installation of sage are really my first

[sage-devel] Re: show() vs. plot() on digraphs or posets

When reading graph_plot.py doc [1], I thought figsize was accepted by show but not by plot: sage: from sage.graphs.graph_plot import DEFAULT_PLOT_OPTIONS, DEFAULT_SHOW_OPTIONS sage: [o for o in DEFAULT_SHOW_OPTIONS if o not in DEFAULT_PLOT_OPTIONS] ['figsize'] but when I do the following, I rea

[sage-devel] Re: sage-6.7 build failed on Cygwin64 for python-2.7.8 No module named crypt

Le lundi 8 juin 2015 13:54:01 UTC+2, Stefan Auracher a écrit : > > In the past I had the same experience. I did it but in the last years, but > it was really difficult. But recently I tried an install of cygwin with the > setup-x86_64.exe --no-admin switch and it worked very well wihout any >

Re: [sage-devel] Re: show() vs. plot() on digraphs or posets

On Mon, 8 Jun 2015, Sébastien Labbé wrote: When reading graph_plot.py doc [1], I thought figsize was accepted by show but not by plot: - - So, the question is still open. Just the same issue that I found... There might be something like axes_*() or so, but they will do nothing (or do somethi

[sage-devel] Re: sage-6.7 build failed on Cygwin64 for python-2.7.8 No module named crypt

Le lundi 8 juin 2015 14:22:20 UTC+2, Jean-Pierre Flori a écrit : > > > > Le lundi 8 juin 2015 13:54:01 UTC+2, Stefan Auracher a écrit : >> >> In the past I had the same experience. I did it but in the last years, >> but it was really difficult. But recently I tried an install of cygwin with >>

[sage-devel] About "Math Processing Error"

Documentation on sagemath.org works. In my own machine, where Sage is compiled from source taken from git, it works when loading local www-page: Return True if x is greater than but not equal to y in the poset, and False otherwise. And then after loading is completed, changes to Return True

[sage-devel] Documentation: Adding function from A to list of functions in B

There is some discussion at http://trac.sagemath.org/ticket/18534 . Maybe this could be a topic in this sage-devel list also. For now there is no list of "what can I do with these posets" -functions. That's because we have, for example, is_connected() on .../combinat/posets/posets.py and is_se

Re: [sage-devel] Re: show() vs. plot() on digraphs or posets

Hello guys, I don't know anything about Poset's show/plot functions. For Graph.plot(), however, it is true that it is never said explicitly that additional parameters will be forwarded to matplotlib. It is done in Graph.show? but not in Graph.plot?. I'll patch that soon. Nathann -- You rece

[sage-devel] Re: Documentation: Adding function from A to list of functions in B

To me it is not a problem of doc but a problem of code. The issue is that we have 99% of the poset functions in the poset/ folder, and a couple of them in the category/ folder. If we move everything to posets, there's no problem. I don't see any advantage in having poset code in a file that is

Re: [sage-devel] Re: Documentation: Adding function from A to list of functions in B

Yo, > I disagree with that. There's some advantage: if your code only depends on > general mathematical properties of posets and not on the specific > implementation of the poset object, then it should be in the category. Absolutely no code in poset.py depends on the actual implementation. This i

Re: [sage-devel] Re: Documentation: Adding function from A to list of functions in B

2015-06-08 9:51 GMT-05:00 Nathann Cohen : > To me it is not a problem of doc but a problem of code. The issue is that > we have 99% of the poset functions in the poset/ folder, and a couple of > them in the category/ folder. If we move everything to posets, there's no > problem. I don't see any ad

Re: [sage-devel] Re: Documentation: Adding function from A to list of functions in B

2015-06-08 10:14 GMT-05:00 Nathann Cohen : > Yo, > > > I disagree with that. There's some advantage: if your code only depends > on > > general mathematical properties of posets and not on the specific > > implementation of the poset object, then it should be in the category. > > Absolutely no cod

[sage-devel] Re: sage-6.7 build failed on Cygwin64 for python-2.7.8 No module named crypt

How to do this ? I found in ~/sage-6.7/src/module_list.py Extension('sage.rings.polynomial.pbori', sources = ['sage/rings/polynomial/pbori.pyx'], libraries=['polybori-' + polybori_major_version, 'polybori_groebner-' + polybori_major_version, '

[sage-devel] Re: sage-6.7 build failed on Cygwin64 for python-2.7.8 No module named crypt

Le lundi 8 juin 2015 18:02:46 UTC+2, Stefan Auracher a écrit : > > How to do this ? > > I found in ~/sage-6.7/src/module_list.py > > Extension('sage.rings.polynomial.pbori', > sources = ['sage/rings/polynomial/pbori.pyx'], > libraries=['polybori-' + polybori_major_vers

Re: [sage-devel] Re: Documentation: Adding function from A to list of functions in B

On Mon, 8 Jun 2015, Viviane Pons wrote: if your code only depends on general mathematical properties of posets and not on the specific implementation of the poset object, then it should be in the category. Then I guess is_bounded should be in the category. But this has been discussed earlier

[sage-devel] Question about Free algebra

Hi everyone, I'm doing this: sage: FreeA. = FreeAlgebra(QQ,implementation="letterplace") sage: P = a*b*a*c*c*b + a*b*a*d*d*b + a*c*a*d*d*c + b*c*b*d*d*c sage: X = P.lm() sage: X a*b*a*c*c*b And now I would like a way to "cut" my element X into two factors of a given size. Something like sage: u