Re: [sage-devel] Proposal: move SageNB back to Sage

On 2016-04-15 14:12, Erik Bray wrote: I say focus on fixing the real problems, not the symptoms. I don't care. I want *any* fix (a real fix or a symptom-fix) and the status-quo is not a fix. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To

Re: [sage-devel] Proposal: move SageNB back to Sage

On Friday, April 15, 2016 at 2:02:34 PM UTC+1, Erik Bray wrote: > > On Fri, Apr 15, 2016 at 2:22 PM, Dima Pasechnik > wrote: > > > > > > On Friday, April 15, 2016 at 1:12:20 PM UTC+1, Erik Bray wrote: > >> > >> On Fri, Apr 15, 2016 at 10:44 AM, Jeroen Demeyer

Re: [sage-devel] Proposal: move SageNB back to Sage

On Fri, Apr 15, 2016 at 2:22 PM, Dima Pasechnik wrote: > > > On Friday, April 15, 2016 at 1:12:20 PM UTC+1, Erik Bray wrote: >> >> On Fri, Apr 15, 2016 at 10:44 AM, Jeroen Demeyer >> wrote: >> > Hello all, >> > >> > I propose to make SageNB no longer a

Re: [sage-devel] Proposal: move SageNB back to Sage

On Friday, April 15, 2016 at 1:12:20 PM UTC+1, Erik Bray wrote: > > On Fri, Apr 15, 2016 at 10:44 AM, Jeroen Demeyer > wrote: > > Hello all, > > > > I propose to make SageNB no longer a separate package but to move it > back > > into the Sage git tree. For purposes

Re: [sage-devel] Proposal: move SageNB back to Sage

On Fri, Apr 15, 2016 at 10:44 AM, Jeroen Demeyer wrote: > Hello all, > > I propose to make SageNB no longer a separate package but to move it back > into the Sage git tree. For purposes of installation and use of SageNB, it > will still be a separate Python package, but

[sage-devel] Proposal: move SageNB back to Sage

Hello all, I propose to make SageNB no longer a separate package but to move it back into the Sage git tree. For purposes of installation and use of SageNB, it will still be a separate Python package, but the sources will be in $SAGE_ROOT/src/sagenb instead of a separate git repo. The changes