[sage-devel] Re: Merging sage-7.0 into existing branch

2016-01-23 Thread David Roe
Good idea, but it doesn't fix the problem. I'm still getting the same result. David On Sat, Jan 23, 2016 at 4:49 PM, Travis Scrimshaw wrote: > DId you try ``make distclean && make``? > > Best, > Travis > > > > On Saturday, January 23, 2016 at 3:34:56 PM UTC-6, David Roe wrote: >> >> I'm trying

[sage-devel] Re: Merging sage-7.0 into existing branch

2016-01-23 Thread Travis Scrimshaw
DId you try ``make distclean && make``? Best, Travis On Saturday, January 23, 2016 at 3:34:56 PM UTC-6, David Roe wrote: > > I'm trying to merge sage-7.0 into http://trac.sagemath.org/ticket/812. > I've built a fresh sage-7.0 on SMC then did the following (after a bit of > fiddling around wit

[sage-devel] Merging sage-7.0 into existing branch

2016-01-23 Thread David Roe
I'm trying to merge sage-7.0 into http://trac.sagemath.org/ticket/812. I've built a fresh sage-7.0 on SMC then did the following (after a bit of fiddling around with other tickets) git trac checkout 812 git merge master make It ends up with an error that looks like Building interpreters for fast_

[sage-devel] Re: [sage-edu] building Software Carpentry "lesson" for Sagemath

2016-01-23 Thread Raniere Silva
[Sorry for the cross-post] Hi Dima, thanks for the email. > Software Carpentry, see http://software-carpentry.org, is a charity that > does "Teaching basic lab skills for research computing". But goes beyond > that; their workshops can include more nontrivial components, e.g. recently > GAP p

Re: [sage-devel] Re: Rationale behind HasseDiagram class

2016-01-23 Thread Travis Scrimshaw
They are fair questions, and it is worth (re)evaluating these things every once in awhile. Let me know if you have any more. Best, Travis On Saturday, January 23, 2016 at 12:47:40 PM UTC-6, Nathann Cohen wrote: > > Thank you Travis. By talking with you I do not have any more doubt on > how/why

Re: [sage-devel] Re: Rationale behind HasseDiagram class

2016-01-23 Thread Nathann Cohen
Thank you Travis. By talking with you I do not have any more doubt on how/why this class was built as it is. Nathann On 23 January 2016 at 19:39, Travis Scrimshaw wrote: > >> >> class Poset: >> >> def A(): >> for i in ZZ: >> self._B() >> >> def _B(): >> # wor

Re: [sage-devel] Re: Rationale behind HasseDiagram class

2016-01-23 Thread Travis Scrimshaw
> > class Poset: > > def A(): > for i in ZZ: > self._B() > > def _B(): > # works on the digraph self._hasse_diagram, taking advantage > of its labelling > > I do not see where the problem is. It requires a helper function _B a > in the current design (

Re: [sage-devel] Re: The sage.rings.finite_rings.constructor module

2016-01-23 Thread Dima Pasechnik
On Saturday, 23 January 2016 17:22:23 UTC, David Loeffler wrote: > > (The joke doesn't actually work in British English, because we'd always > say "X is really lazy" rather than "X is real lazy".) > no, no, the joke is about real vs complex... > David > > On 23 January 2016 at 17:03, Dima Pas

Re: [sage-devel] Re: The sage.rings.finite_rings.constructor module

2016-01-23 Thread David Loeffler
(The joke doesn't actually work in British English, because we'd always say "X is really lazy" rather than "X is real lazy".) David On 23 January 2016 at 17:03, Dima Pasechnik wrote: > > > On Saturday, 23 January 2016 14:47:26 UTC, David Loeffler wrote: >> >> I have also raised some objections

Re: [sage-devel] Re: The sage.rings.finite_rings.constructor module

2016-01-23 Thread Dima Pasechnik
On Saturday, 23 January 2016 14:47:26 UTC, David Loeffler wrote: > > I have also raised some objections on the ticket, which relate less to the > content of the ticket than to the tone of the discussion (both on the > ticket and on this thread). It is one thing to propose a change to a file >

Re: [sage-devel] Re: The sage.rings.finite_rings.constructor module

2016-01-23 Thread David Loeffler
I have also raised some objections on the ticket, which relate less to the content of the ticket than to the tone of the discussion (both on the ticket and on this thread). It is one thing to propose a change to a file name; it is another thing to mock a fellow Sage contributor or to accuse the