[sage-devel] Re: Python as beginner language - Comm. ACM

Fulltext: http://cacm.acm.org/magazines/2015/3/183588-python-for-beginners/fulltext Evidently the author doesn't know Python. List comprehensions are described as "Python allows you summarize a list of data in one line of code, whereas in other languages it would take multiple lines." Its just

Re: [sage-devel] 'git trac' instructions for rebasing/merging

On Friday, March 13, 2015 at 6:10:09 PM UTC+1, Jonas Jermann wrote: > > At the moment the git history of sage looks quite messy > and I assume it will get worse, not better. It doesn't get messier over time, its more of a steady state. You either make the history more difficult to understand,

[sage-devel] Python as beginner language - Comm. ACM

See this article - I know some will be interested. If you are not a member of ACM (I am not), I think many institutions will have this in their database. *Communications of the ACM. *Mar2015, Vol. 58 Issue 3, p19-21. -- You received this message because you are subscribed to the Google Groups

Re: [sage-devel] 'git trac' instructions for rebasing/merging

Hi On 12.03.2015 08:28, Nathann Cohen wrote: Hello everybody, I just noticed that we do not seem to have in our developer's manual instructions about how to rebase/merge a branch when it becomes incompatible with the latest beta. I do not use 'git trac' myself, but it would be cool if anybody

Re: [sage-devel] Re: Polydict, ETuple, and large exponents

Le 12/03/2015 17:03, Marc Mezzarobba a écrit : Bruno Grenet wrote: My questions: Is my understanding correct? If not, what are supposed these arguments to be for? And if I understand correctly, is the behavior I mention a bug? I'd say you are right, and the reason for the bug is that ETuple cha

[sage-devel] SageManifolds 0.7 released

Hi, The version 0.7 of SageManifolds has just been released (see the changelog ). Numerous internal changes have been performed, resulting in a better integration into Sage's parent/element framework. Specifically, h

Re: [sage-devel] Re: 'git trac' instructions for rebasing/merging

On 2015-03-12 10:51, Nathann Cohen wrote: I was thinking of some entry like "Merging with the latest release (i.e. what should you do when the branch appears in red)". Note that the Trac algorithm to merge branches has flaws. In several cases, the Trac link was red, but manually doing "git mer

Re: [sage-devel] White-haired needs_review tickets

On 2015-03-11 17:44, Julien Puydt wrote: What should be really done with long-waiting needs_review tickets ? Where should the time limit be between "It's just taking long" and "It's outdated" ? I think the truly outdated tickets are a minority. Tickets which need review since a long time are n

Re: [sage-devel] Re: 'git trac' instructions for rebasing/merging

On 2015-03-12 10:46, Volker Braun wrote: There is nothing specific to our git setup as far as merging and rebasing is concerned. So there is no need to reinvent a git-trac wheel here, its just about making communicating with trac easier. I would find the following command useful: git trac merg

[sage-devel] Re: 17160: categories for finitely generated magmas, semigroups, groups, ...

Hi! On Wed, Mar 11, 2015 at 03:22:32PM -0700, Volker Braun wrote: > IMHO always assume constructive unless otherwise noted if you do > things on the computer. You can pick elements of sets, elements of > two sets (or other structure) can actually be distinguished, etc. > There is no need t

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

On Monday, January 12, 2015 at 11:59:53 AM UTC+1, Thierry (sage-googlesucks@xxx) wrote: > > Another mid-term compromise could be to strip some few upstream source, > but in a checkable and reproducible manner, that is, with a spkg-src > script that will produce deterministic tarballs, so that an