[sage-devel] Re: Remove "A Tour of Sage"

2015-01-12 Thread Simon King
On 2015-01-13, Volker Braun wrote: > On Monday, January 12, 2015 at 7:16:23 PM UTC+1, Simon King wrote: >> >> If its purpose is to explain Sage for those who know other CAS, somehow >> explaining the differences and common points between various Ma* and >> Sage, then it should perhaps be kept un

Re: [sage-devel] Re: The Sage dev scripts

2015-01-12 Thread Robert Bradshaw
On Sun, Jan 11, 2015 at 3:00 AM, Simon King wrote: > Hi! > > On 2015-01-11, Nils Bruin wrote: >> On Sunday, January 11, 2015 at 12:54:56 AM UTC-8, Martin von Gagern wrote: >>> >>> On 11.01.2015 09:38, Robert Bradshaw wrote: >>> > Hopefully it's becoming stable enough that >>> > we should start sh

Re: [sage-devel] reducing upstream tarballs in a reproducible way

2015-01-12 Thread Nils Bruin
On Monday, January 12, 2015 at 4:13:33 PM UTC-8, François wrote: > > I agree with you that it is not deterministic. What is really important is > that the > checksums and the tarball come from a source you trust and are in > agreement. > The checksum of the file itself is simply a way of estab

[sage-devel] Re: Remove "A Tour of Sage"

2015-01-12 Thread Volker Braun
On Monday, January 12, 2015 at 7:16:23 PM UTC+1, Simon King wrote: > > If its purpose is to explain Sage for those who know other CAS, somehow > explaining the differences and common points between various Ma* and > Sage, then it should perhaps be kept under a different name? A First Taste of S

Re: [sage-devel] reducing upstream tarballs in a reproducible way

2015-01-12 Thread Francois Bissey
I agree with you that it is not deterministic. What is really important is that the checksums and the tarball come from a source you trust and are in agreement. It is a simple security measure and I am not sure there is value in making it deterministic. I have a feeling that if you want to do that

Re: [sage-devel] Build error for sage-6.4.1 in pynac-0.3.2

2015-01-12 Thread Francois Bissey
It looks like something has gone wrong with LD_LIBRARY_PATH & co. This means that libstdc++ found when running sage is from older version of gcc than the one used to compile sage. Here you find libstdc++ from the system (gcc-4.3.4 I presume) rather than whatever you used to compile. I assume yo

[sage-devel] Re: reducing upstream tarballs in a reproducible way

2015-01-12 Thread mmarco
If the problem is that packaging is not deterministic... what if we run the hash check on the unpacked files instead of the tarball? El lunes, 12 de enero de 2015, 11:59:53 (UTC+1), Thierry (sage-googlesucks@xxx) escribió: > > Hi, > > it is advised to distribute unmodified upstream tarball at

[sage-devel] Re: Build error for sage-6.4.1 in pynac-0.3.2

2015-01-12 Thread crookscj02
Setting the effective group to the same as the group on the build directory did allow pynac to compile. I am now stuck on an error in conway_polynomials-0.4.p0. ImportError: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /hpc/tstapps/src/sage/sage-6.4.1/local/lib/p

Re: [sage-devel] inherit group from monoid

2015-01-12 Thread David Roe
This is a circular import error. If you look at the chain of imports, you'll see that earlier you're in the file "sage/rings/all.py," and the error occurs when you later try to import sage.rings.all. A brief glance at your code doesn't reveal the cause of the problem for me, though it could be re

[sage-devel] Re: What is "Interface Issues" doing in the "Constructions" document ?

2015-01-12 Thread kcrisman
> > >> > > Lots of *users* of group theory use Sage, though. > > My impression is that group theorists use GAP but not necessarily Sage. > > I don't count group theorists as users of group theory (or at least, not only). My point was this is useful even if all group theorists use GAP only; l

Re: [sage-devel] reducing upstream tarballs in a reproducible way

2015-01-12 Thread David Roe
I'm on OS X 10.9.2, Macbook Pro, tar --version returns bsdtar 2.8.3 - libarchive 2.8.3 For me, your last line resulted in: tar: Option --mtime=1970-01-01 01:00 is not supported David On Mon, Jan 12, 2015 at 5:59 AM, Thierry wrote: > Hi, > > it is advised to distribute unmodified upstream tarba

Re: [sage-devel] reducing upstream tarballs in a reproducible way

2015-01-12 Thread Michael Orlitzky
On 01/12/2015 05:59 AM, Thierry wrote: > > In order to try such possibility on the next matplotlib update, could some > people (especially someone using OSX) give me (with minimal info on their > OS, arch, and tar --version) the result of: > > wget > https://downloads.sourceforge.net/project/mat

Re: [sage-devel] Re: What is "Interface Issues" doing in the "Constructions" document ?

2015-01-12 Thread Vincent Delecroix
2015-01-12 16:08 UTC+01:00, William Stein : > By the way, yesterday at the Sage booth at the Joint Math meetings somebody > walked up and said, "can you use Sage to enumerate the groups of order 16?" > For a group theorist, this is a very natural basic question. I tried > groups.[tab] and fou

Re: [sage-devel] Re: Remove "A Tour of Sage"

2015-01-12 Thread William Stein
On Mon, Jan 12, 2015 at 11:08 AM, Nathann Cohen wrote: > > > > What is the argument for removing the tour? I have seen absolutely no > > arguments at for removing it, except maybe "the first section of that > manual > > is also named "A guided tour".' That's not a compelling argument. A > > piece

Re: [sage-devel] Re: What is "Interface Issues" doing in the "Constructions" document ?

2015-01-12 Thread William Stein
On Mon, Jan 12, 2015 at 12:30 PM, Simon King wrote: > Hi! > > On 2015-01-12, David Joyner wrote: > > Depends on the group: > > > > ... > > > > The simplest explanation would be to use the small groups database > > which can be installed into Sage, but it is not open-source licensed. > > For exam

[sage-devel] Re: What is "Interface Issues" doing in the "Constructions" document ?

2015-01-12 Thread Simon King
On 2015-01-12, kcrisman wrote: >> I don't even know if there any group theorists at all that use Sage... >> >> > Lots of *users* of group theory use Sage, though. My impression is that group theorists use GAP but not necessarily Sage. -- You received this message because you are subscribed to

Re: [sage-devel] reducing upstream tarballs in a reproducible way

2015-01-12 Thread Volker Braun
Also compression programs sometimes improve (without changing the decompression routine), and/or their default parameters might be machine-dependent. On Monday, January 12, 2015 at 3:22:53 PM UTC+1, Thierry (sage-googlesucks@xxx) wrote: > > On Mon, Jan 12, 2015 at 04:47:55PM +0530, Nathann Coh

[sage-devel] Re: Bug Days?

2015-01-12 Thread Jean-Pierre Flori
On Thursday, January 8, 2015 at 4:34:22 PM UTC+1, William wrote: > > Hi, > > Would anybody be interested in helping me to organize a bug days > workshop sometime in the next few months? > I have plenty of funding for this for US people and can scrounge up > some funds for some non-US people.

Re: [sage-devel] Python 3 focused Sage Days

2015-01-12 Thread Francois Bissey
I have been thinking of converting polybori to distutils the same way that cvxopt does thing. It may turn out not to be possible without a bit of auto tools because of polybori builds proper libraries not just python extensions. But at best it is a band aid as no more development will be done. S

[sage-devel] Re: What is "Interface Issues" doing in the "Constructions" document ?

2015-01-12 Thread Simon King
Hi! On 2015-01-12, David Joyner wrote: > Depends on the group: > > ... > > The simplest explanation would be to use the small groups database > which can be installed into Sage, but it is not open-source licensed. For example: sage: [PermutationGroup(gap.SmallGroup(16,i).IsomorphismPermGroup()

[sage-devel] Re: Remove "A Tour of Sage"

2015-01-12 Thread Simon King
Hi! On 2015-01-12, kcrisman wrote: > The "Tutorial" is the original, *general* "intro to Sage" that was written > in the age of the dinosaurs. It is still quite useful for people who > already know a similar CAS, but a lot of the content dates to when we had > much less robust communication a

Re: [sage-devel] Re: What is "Interface Issues" doing in the "Constructions" document ?

2015-01-12 Thread kcrisman
> > You are assuming that the only target audience of the constructions guide > is a person actively using an interactive Sage session, but that is not the > only target audience. Google searches, especially from people who might > have never heard of Sage, are a big target audience for the c

Re: [sage-devel] Re: Remove "A Tour of Sage"

2015-01-12 Thread kcrisman
> > > What is the argument for removing the tour? I have seen absolutely no > > arguments at for removing it, except maybe "the first section of that > manual > > is also named "A guided tour".' That's not a compelling argument. A > > piece of our documentation has a target audience (or audience)

[sage-devel] inherit group from monoid

2015-01-12 Thread Daniel Krenn
In http://trac.sagemath.org/ticket/17626 the group class should have a newly created monoid class as a base. At the moment the group and the monoid parent do not have much in common (but their elements have). I've started implementing this, but have a rather strange problem. See below the outp

Re: [sage-devel] Re: What is "Interface Issues" doing in the "Constructions" document ?

2015-01-12 Thread Nathann Cohen
> Interesting. A lot of this should go in the Tutorial or FAQ, I think. Okay. I will write a patch for that, but I will wait before the other patches are reviewed as I worry about conflicts. Many things are being rewritten and moved around in all directions. Nathann -- You received this messag

Re: [sage-devel] Re: Remove "A Tour of Sage"

2015-01-12 Thread Nathann Cohen
> What is the argument for removing the tour? I have seen absolutely no > arguments at for removing it, except maybe "the first section of that manual > is also named "A guided tour".' That's not a compelling argument. A > piece of our documentation has a target audience (or audience) and a goal >

Re: [sage-devel] Re: What is "Interface Issues" doing in the "Constructions" document ?

2015-01-12 Thread David Joyner
On Mon, Jan 12, 2015 at 10:08 AM, William Stein wrote: > > > On Mon, Jan 12, 2015 at 8:58 AM, Nathann Cohen > wrote: >> >> > The best outcome would be to have a true "how do I do *** in Sage" >> > document >> > that keeps being updated; >> >> A small remark: in combinatorial designs and graphs th

Re: [sage-devel] Re: Remove "A Tour of Sage"

2015-01-12 Thread William Stein
On Mon, Jan 12, 2015 at 9:27 AM, Nathann Cohen wrote: > Let me add here that removing "A tour of Sage" also means removing all > of its translations. And bear in mind that some (few) sections of this > document do not exist elsewhere and need to be moved to some other > document ("how to cite Sag

Re: [sage-devel] Re: Remove "A Tour of Sage"

2015-01-12 Thread Nathann Cohen
Let me add here that removing "A tour of Sage" also means removing all of its translations. And bear in mind that some (few) sections of this document do not exist elsewhere and need to be moved to some other document ("how to cite Sage" -> FAQ, "Background jobs" -> tutorial). I began to do the wo

Re: [sage-devel] Re: What is "Interface Issues" doing in the "Constructions" document ?

2015-01-12 Thread kcrisman
> > A small remark: in combinatorial designs and graphs the anser to "How > do I build ***" is rather well answered by graphs., > digraphs., designs.. It gives a nice entry point for the > functions that "build something", and from there the classes/functions > doc is sufficient in our case.

Re: [sage-devel] Re: What is "Interface Issues" doing in the "Constructions" document ?

2015-01-12 Thread William Stein
On Mon, Jan 12, 2015 at 8:58 AM, Nathann Cohen wrote: > > The best outcome would be to have a true "how do I do *** in Sage" > document > > that keeps being updated; > > A small remark: in combinatorial designs and graphs the anser to "How > do I build ***" is rather well answered by graphs., > d

Re: [sage-devel] Re: Remove "A Tour of Sage"

2015-01-12 Thread kcrisman
> > > I never thought people would seriously consider deleting the main > overall > > tutorial for Sage. > > That is because nobody did. This thread is entitled "Remove 'A tour of > Sage'" and it is about whether we should remove "A tour of Sage". > > Which is this document: > http://www.sag

[sage-devel] Re: The Sage dev scripts

2015-01-12 Thread kcrisman
> > >> > Hopefully it's becoming stable enough that > >> > we should start shipping it as part of Sage? > >> > >> At first I thought so, too. But now I'm no longer sure: if you ship it > >> with Sage, then it will be difficult to use it if you want to work with > >> a patch from an older bran

Re: [sage-devel] Re: What is "Interface Issues" doing in the "Constructions" document ?

2015-01-12 Thread Nathann Cohen
> The best outcome would be to have a true "how do I do *** in Sage" document > that keeps being updated; A small remark: in combinatorial designs and graphs the anser to "How do I build ***" is rather well answered by graphs., digraphs., designs.. It gives a nice entry point for the functions tha

Re: [sage-devel] Re: What is "Interface Issues" doing in the "Constructions" document ?

2015-01-12 Thread William Stein
On Mon, Jan 12, 2015 at 8:46 AM, kcrisman wrote: > > > On Sunday, January 11, 2015 at 5:22:12 AM UTC-5, Nathann Cohen wrote: >> >> Hello everybody ! >> >> The "constructions" document is meant to "answer some questions along >> the line 'How do I construct ... in Sage?' " >> >> http://www.sagemat

Re: [sage-devel] Re: Remove "A Tour of Sage"

2015-01-12 Thread Nathann Cohen
> -1 to remove the tutorial > > +1 to updating and improving it > > I never thought people would seriously consider deleting the main overall > tutorial for Sage. That is because nobody did. This thread is entitled "Remove 'A tour of Sage'" and it is about whether we should remove "A tour of Sage"

[sage-devel] Re: Remove "A Tour of Sage"

2015-01-12 Thread William Stein
On Mon, Jan 12, 2015 at 8:42 AM, kcrisman wrote: > We already have many documents that can "contain all kind of stuff" like: >> - the Constructions manual >> - the Tutorials manual >> - the Thematic Tutorials manual >> >> The difference between the last two is not precisely obvious (if you >> loo

[sage-devel] Re: What is "Interface Issues" doing in the "Constructions" document ?

2015-01-12 Thread kcrisman
On Sunday, January 11, 2015 at 5:22:12 AM UTC-5, Nathann Cohen wrote: > > Hello everybody ! > > The "constructions" document is meant to "answer some questions along > the line 'How do I construct ... in Sage?' " > > http://www.sagemath.org/doc/constructions/index.html > > In principle, this

[sage-devel] Re: Remove "A Tour of Sage"

2015-01-12 Thread kcrisman
> > We already have many documents that can "contain all kind of stuff" like: > - the Constructions manual > - the Tutorials manual > - the Thematic Tutorials manual > > The difference between the last two is not precisely obvious (if you > look for something, where will it be ?) > > The "Tu

Re: [sage-devel] reducing upstream tarballs in a reproducible way

2015-01-12 Thread Thierry
On Mon, Jan 12, 2015 at 04:47:55PM +0530, Nathann Cohen wrote: > Hello Thierry ! > > What about checking that there is nothing wrong without a hashsum ? > > 1) Download the author's .tar.bz2 file > 2) Use the sage-src script to generate the .tar.bz2 file yourself > 3a) If the hashed match you are

[sage-devel] Error in Building Sage (particularly ecm-6.4)

2015-01-12 Thread Shadab Zafar
I am trying to build Sage from the current master branch but it errors in installing ecm. I've attached the log file. System Info: Linux version 3.5.0-57-generic (buildd@tipua) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #84~precise1-Ubuntu SMP Thu Nov 6 06:09:35 UTC 2014 -- You rec

Re: [sage-devel] How to link from one 'document' to another ?

2015-01-12 Thread Nathann Cohen
> The question has been asked before but I think it is not possible to make > links like that. Only links *to the reference manual* are currently > possible. Okay :-/ Then I will use http links. While trying to be a bit smart and use relative links, so that they still work when you are offline (a

Re: [sage-devel] How to link from one 'document' to another ?

2015-01-12 Thread Jeroen Demeyer
On 2015-01-11 11:56, Nathann Cohen wrote: Hello everybody ! Sorry if this question was already asked (I was not able to find it) but I wondered how to make link in our doc between documents ? The question has been asked before but I think it is not possible to make links like that. Only links *

Re: [sage-devel] reducing upstream tarballs in a reproducible way

2015-01-12 Thread Nathann Cohen
Hello Thierry ! What about checking that there is nothing wrong without a hashsum ? 1) Download the author's .tar.bz2 file 2) Use the sage-src script to generate the .tar.bz2 file yourself 3a) If the hashed match you are done 3b) If they do not match, extract them both and compare their content w

[sage-devel] reducing upstream tarballs in a reproducible way

2015-01-12 Thread Thierry
Hi, it is advised to distribute unmodified upstream tarball at much as possible, so that the end-user should be able to check that the tarball shipped by Sage has the same hash that upstreams. However, when size can be reduced by a huge factor, integrity arguments become pretty weak and we randoml

Re: [sage-devel] Re: Python 3 focused Sage Days

2015-01-12 Thread Martin Albrecht
Hi, here's a reply from a PolyBoRi developer: -- Forwarded Message -- Subject: Re: [Polybori-discuss] Fwd: Re: [sage-devel] Re: Python 3 focused SageDays Date: Saturday 10 Jan 2015, 22:19:16 From: Alexander Dreyer To: Martin Albrecht , Polybori Discuss Hi Martin, Unfort

[sage-devel] Re: number of lines of code in Sage

2015-01-12 Thread mmarco
Sorry, when i wrote sloc i meant sloccount. El lunes, 12 de enero de 2015, 10:55:11 (UTC+1), mmarco escribió: > > I did a similar calculation for a talk last october. I used wc -l for the > total lines and sloc for the single lines of code. On Sage 6.3 i got the > following: > > Language T

[sage-devel] Re: number of lines of code in Sage

2015-01-12 Thread mmarco
I did a similar calculation for a talk last october. I used wc -l for the total lines and sloc for the single lines of code. On Sage 6.3 i got the following: Language Total Lines Single lines of code Python 1117979 598043 Cython439495218669 an

[sage-devel] Re: Build error for sage 6.4 beta 5 under cygwin64

2015-01-12 Thread Sebastien Gouezel
Le 09/01/2015 12:30, Jean-Pierre Flori a écrit : That is easy to fix. Just add gmp to the linked libraries in module_list.py for these files. Indeed, this is very easy, and works like a charm. After this, everything compiles, and a lot of things are working! (well, a lot of things are also