[sage-devel] abs(matrix)

2014-12-03 Thread Vincent Delecroix
Hello, abs(matrix) is currently returning the determinant (and this goes back to the early implementation in 2006!). If anybody contests the fact that it should return the matrix whose entries are the absolute value of the initial matrix, please tell me. Otherwise, #17443 needs review. Vincent

[sage-devel] Sage listed as "free math analysis & design tool for engineers" in retimes

2014-12-03 Thread john_perry_usm
here's the link, for those interested http://www.eetimes.com/document.asp?page_number=1&doc_id=1322836&image_number=2 regards john perry -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emai

Re: [sage-devel] Re: possible issue with DiGraph in interval fields

2014-12-03 Thread Vincent Delecroix
2014-12-03 3:24 UTC+01:00, Nathann Cohen : >> sage: a = CIF(RIF(0, 1), RIF(0, 1)) >> sage: a is a >> True >> sage: a == a >> False >> >> So equality is not even reflexive. > > Okay. Please never define a graph with these things as vertices :-D +1 And for better behavior, we need troolean = {True,

Re: [sage-devel] Re: About Graph.to_partition and Poset.to_graph

2014-12-03 Thread Viviane Pons
> Vincent > > PS: Not speaking about Findstat, you know that I worked a bit to > propose something for the database of combinatorial maps (see #16408). > I receive exactly 0 answer since then... and it was 6 months ago. > I know, I still find it a very interesting project but months go quickly and

Re: [sage-devel] Re: About Graph.to_partition and Poset.to_graph

2014-12-03 Thread Vincent Delecroix
Hi Vivianne, 2014-12-03 15:07 UTC+01:00, Viviane Pons : > My comment on this: > > * Findstat does not need such methods to be in sage (anymore), as we > actually define our own maps outside of Sage (for the good of FindStat and > for the bad of Sage in my opinion) so at least, no one can be accuse

Re: [sage-devel] Re: Maple versus Mathematica

2014-12-03 Thread mmarco
I am not sure if it is also available in the M's, or if they have some other system to guide the user to the functions he wants to use, but for me, tab-completion is a great feature in Sage. El martes, 2 de diciembre de 2014 22:43:34 UTC+1, maldun escribió: > > The emphasis lies on 'trying' Con

Re: [sage-devel] Re: coeffs() & coefficients()

2014-12-03 Thread Ralf Stephan
I *did ask if I should deprecate, I just wasn't sure if we can deprecate the alias. On Wed Dec 03 2014 at 4:10:25 PM john_perry_usm wrote: > Will the ticket you've opened also deal with multivariate polynomial > ideals, or are you working on symbolic expressions only? > Yes. It's almost always

[sage-devel] Re: coeffs() & coefficients()

2014-12-03 Thread john_perry_usm
Sorry for the delay in replying; as noted earlier, I've been traveling. I agree with Samuel; it's important to deprecate first. Some of us run scripts that will break if you simply remove the command, but a deprecation warning both allows the script to keep running and (if it's a good warning)

Re: [sage-devel] PyClaw

2014-12-03 Thread Thierry
Hi, On Wed, Dec 03, 2014 at 09:30:12AM -0500, David Joyner wrote: > On Wed, Dec 3, 2014 at 3:35 AM, Thierry > wrote: > > Hi, > > > > perhaps this does not even require maintaining a spkg, does the following > > work ? > > > > sage -i pip > > sage -pip install clawpack > > > > This doesn

[sage-devel] Re: coeffs() & coefficients()

2014-12-03 Thread Samuel Lelievre
2014-12-03 10:27:53 UTC+1, Ralf Stephan wrote: > > Sorry, a bit late. I also agree with removing *coeffs* and referring to > *list *in the documentation of *coefficients*. > > What's more, the issue comes up with symbolic expressions too, where > *coeffs *is an alias of* coefficients*, and ther

Re: [sage-devel] PyClaw

2014-12-03 Thread Harald Schilly
On Wed, Dec 3, 2014 at 3:35 PM, David Joyner wrote: > On Wed, Dec 3, 2014 at 8:37 AM, Harald Schilly > wrote: >> Well, just tried their first example, seems like it crashes. No idea :( >> > > Same here. On SMC we all sit in the same boat. Either it works or it breaks for everyone. I think it is

Re: [sage-devel] PyClaw

2014-12-03 Thread David Joyner
On Wed, Dec 3, 2014 at 8:37 AM, Harald Schilly wrote: > > > On Wednesday, December 3, 2014 12:09:54 PM UTC+1, David Joyner wrote: >> >> maybe having it installed on the cloud would be better >> anyway? > > > It should be installed on SMC for some time now. Not sure how to to test it? > > Well, jus

Re: [sage-devel] PyClaw

2014-12-03 Thread David Joyner
On Wed, Dec 3, 2014 at 3:35 AM, Thierry wrote: > Hi, > > perhaps this does not even require maintaining a spkg, does the following > work ? > > sage -i pip > sage -pip install clawpack > This doesn't work for me using ubuntu linux and sage6.4.rc0 built from source. It says sage -pip is un

Re: [sage-devel] Re: About Graph.to_partition and Poset.to_graph

2014-12-03 Thread Viviane Pons
My comment on this: * Findstat does not need such methods to be in sage (anymore), as we actually define our own maps outside of Sage (for the good of FindStat and for the bad of Sage in my opinion) so at least, no one can be accused of being partial * If a method exists somewhere and has been th

[sage-devel] Re: Sage.app binary problems

2014-12-03 Thread Harald Schilly
On Wed, Dec 3, 2014 at 3:02 PM, Volker Braun wrote: > Harald? can you delete sage-6.4-x86_64-Darwin-OSX_10.9_x86_64* from the > mirrors? ok, they are gone. -- Harald -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this grou

[sage-devel] Re: Sage.app binary problems

2014-12-03 Thread Volker Braun
The 10.9 binaries were built on 10.10, too. They should just be removed. Harald? can you delete sage-6.4-x86_64-Darwin-OSX_10.9_x86_64* from the mirrors? On Wednesday, December 3, 2014 1:58:08 PM UTC, kcrisman wrote: > > Stephane, if you are reading this, is Samuel correct in assuming you mean

[sage-devel] Re: Sage.app binary problems

2014-12-03 Thread kcrisman
The 6.4 binary did not build the app version, but we fixed that for 6.4.1. > The latter are different. > Correct - but notice the OP asked about the *10.9* binaries, not 10.10 or 10.7. And those are the ones I reference below, which have the same hash, and are still at Sage version 6.4.

Re: [sage-devel] PyClaw

2014-12-03 Thread Harald Schilly
On Wednesday, December 3, 2014 12:09:54 PM UTC+1, David Joyner wrote: > > maybe having it installed on the cloud would be better > anyway? > It should be installed on SMC for some time now. Not sure how to to test it? Well, just tried their first example, seems like it crashes. No idea :( --

Re: [sage-devel] Re: PyClaw

2014-12-03 Thread Vincent Delecroix
Hi Thierrys, You can freeze version with pip pip install pyclaw=WHATEVER_VERSION and the advantage is that there is no package to maintain and the sage side. It is also possible to ask pip to download the tarball in SAGE_SRC/upstream and install it later. It is easily customized to all kind of p

Re: [sage-devel] Re: About Graph.to_partition and Poset.to_graph

2014-12-03 Thread Vincent Delecroix
Since you are working on it, I really like better Graph.connected_components_sizes() rather than Graph.connected_components_sizes_partition() Otherwise you should chage Graph.connected_components_number() to Graph.connected_components_number_integer() The output can be sorte

Re: [sage-devel] Re: PyClaw

2014-12-03 Thread Thierry Dumont
Le 03/12/2014 11:32, Simon King a écrit : > Hi Thierry, > > On 2014-12-03, Thierry Dumont wrote: >>> sage -i pip >>> sage -pip install clawpack >> >> But is it the good way to do? >> Is it not better to have an uniform method for installing things? > > I think I remember some people said

Re: [sage-devel] PyClaw

2014-12-03 Thread David Joyner
On Wed, Dec 3, 2014 at 3:35 AM, Thierry wrote: > Hi, > > perhaps this does not even require maintaining a spkg, does the following > work ? > > sage -i pip > sage -pip install clawpack > Didn't work for me (mac OS 10.10) but for the people I know that would be interested, maybe having it

Re: [sage-devel] Re: Maple versus Mathematica

2014-12-03 Thread Eric Gourgoulhon
Hi Le mardi 2 décembre 2014 22:43:34 UTC+1, maldun a écrit : > >1. Python: One could always argue about the language itself, but in >contrast to the others Sage uses a general purpose language. So it easy to >combine Sage with other programs (Ever build standalone Programs with the

[sage-devel] Re: PyClaw

2014-12-03 Thread Simon King
Hi Thierry, On 2014-12-03, Thierry Dumont wrote: >> sage -i pip >> sage -pip install clawpack > > But is it the good way to do? > Is it not better to have an uniform method for installing things? I think I remember some people said that thie *should* become the default way of installing

[sage-devel] Re: About Graph.to_partition and Poset.to_graph

2014-12-03 Thread Dima Pasechnik
On 2014-12-02, Travis Scrimshaw wrote: [...] > Also I cannot > emphasize sufficiently that not all Sage users who use the graph code are > graph theorists. Sure, the latter is an excellent defence for names like nchoosek... Do these people also describe car wheels as "these round things that can

Re: [sage-devel] PyClaw

2014-12-03 Thread Thierry Dumont
Le 03/12/2014 09:35, Thierry a écrit : > Hi, > > perhaps this does not even require maintaining a spkg, does the following > work ? > > sage -i pip > sage -pip install clawpack > > Ciao, > Thierry > may be. But is it the good way to do? Is it not better to have an uniform method for in

[sage-devel] Re: coeffs() & coefficients()

2014-12-03 Thread Ralf Stephan
Sorry, a bit late. I also agree with removing *coeffs* and referring to *list *in the documentation of *coefficients*. What's more, the issue comes up with symbolic expressions too, where *coeffs *is an alias of* coefficients*, and there is no list function. This would be the perfect opportuni

Re: [sage-devel] Oneliners

2014-12-03 Thread 'Martin R' via sage-devel
I'm trying to get a more precise notion of "one-liner" and understand better which one-liners should not be in the library. At first I thought it might be: "a function which is a composition of at most two 'user space' functions" but as Nathann just wrote, this is not correct for P.is_connecte

Re: [sage-devel] PyClaw

2014-12-03 Thread Thierry
Hi, perhaps this does not even require maintaining a spkg, does the following work ? sage -i pip sage -pip install clawpack Ciao, Thierry On Wed, Dec 03, 2014 at 08:41:35AM +0100, Thierry Dumont wrote: > I would like to know if anybody tried to install PyClaw in Sage. > > http://www.c

Re: [sage-devel] PyClaw

2014-12-03 Thread David Joyner
On Wednesday, December 3, 2014, Thierry Dumont wrote: > I would like to know if anybody tried to install PyClaw in Sage. > > http://www.clawpack.org/doc/pyclaw/ > > I am interested, and I propose to make an spkg. I didn't try but know people who are also interested, so please post to this list

Re: [sage-devel] Oneliners

2014-12-03 Thread Nathann Cohen
Hello ! > So should we get rid of at least first one? I think no, but how about > others? Well, I do not know about others but is_connected is "not exactly" a one-liner from user perspective. The function calls self._hasse_diagram.is_connected() while an user would call P.hasse_diagram().is_conn