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

2016-11-23 Thread Jeroen Demeyer
On 2016-11-23 22:46, Nicolas M. Thiery wrote: I have been using Jupyter locally for my teaching since two years, and am very happy with it. The only missing features have been migration tool from sagenb and interacts; both are on their way. For interacts, see https://trac.sagemath.org/ticket/21

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

2016-11-23 Thread Jack Dyson
Thanks I will! enough there to think about already ! J PS nteract looks cool On 24 November 2016 at 00:07, William Stein wrote: > On Wed, Nov 23, 2016 at 3:02 PM, Jack Dyson wrote: >> Right cheers for that William! will give it a go, hopefully we'll have it as >> standard at some point soon. > >

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

2016-11-23 Thread Eric Gourgoulhon
Hi Nicolas, Le mercredi 23 novembre 2016 22:46:34 UTC+1, Nicolas M. Thiéry a écrit : > > > I have been using Jupyter locally for my teaching since two years, and > am very happy with it. The only missing features have been migration > tool from sagenb and interacts; both are on their way. > >

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

2016-11-23 Thread William Stein
On Wed, Nov 23, 2016 at 3:02 PM, Jack Dyson wrote: > Right cheers for that William! will give it a go, hopefully we'll have it as > standard at some point soon. If you do want to work on that, some thoughts: - There is a "painful" dependency on RethinkDB, which is a C++ program that takes a wh

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

2016-11-23 Thread Jack Dyson
Right cheers for that William! will give it a go, hopefully we'll have it as standard at some point soon. Best from here, J On Wednesday, November 23, 2016 at 10:00:05 PM UTC+1, William Stein wrote: > On Wed, Nov 23, 2016 at 12:11 PM, Jan Groenewald > wrote: > > > > Hi > > > > On 23 Novembe

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

2016-11-23 Thread William Stein
On Wed, Nov 23, 2016 at 2:57 PM, Jack Dyson wrote: > Hi Dima, > > Thankyou for your quick reply - I appreciate what you said about development > of sagenb as a whole, and actually I do see the point. > > Logically therefore, as you indicate, iPython is a good alternative. > Unfortunately, it is no

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

2016-11-23 Thread Jack Dyson
Hi Dima, Thankyou for your quick reply - I appreciate what you said about development of sagenb as a whole, and actually I do see the point. Logically therefore, as you indicate, iPython is a good alternative. Unfortunately, it is not fully compatible with sagemath, for example R doesn't acces

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

2016-11-23 Thread Dima Pasechnik
On Wednesday, November 23, 2016 at 9:29:44 PM UTC, Jan Groenewald wrote: > > Hi > > On 23 November 2016 at 22:59, William Stein > wrote: > >> On Wed, Nov 23, 2016 at 12:11 PM, Jan Groenewald > > wrote: >> > >> > Hi >> > >> > On 23 November 2016 at 22:05, Dima Pasechnik > > wrote: >> >> >> >> >>

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

2016-11-23 Thread Nicolas M. Thiery
On Wed, Nov 23, 2016 at 10:11:02PM +0200, Jan Groenewald wrote: >Would jupyter be a possible replacement for sagenb if sagenb is >discontinued from active development? Is it already on a stand-alone >sagemath install? I have been using Jupyter locally for my teaching since two years,

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

2016-11-23 Thread William Stein
On Wed, Nov 23, 2016 at 1:29 PM, Jan Groenewald wrote: > Hi > > On 23 November 2016 at 22:59, William Stein wrote: >> >> On Wed, Nov 23, 2016 at 12:11 PM, Jan Groenewald wrote: >> > >> > Hi >> > >> > On 23 November 2016 at 22:05, Dima Pasechnik wrote: >> >> >> >> >> >> I understand that opinion

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

2016-11-23 Thread Jan Groenewald
Hi On 23 November 2016 at 22:59, William Stein wrote: > On Wed, Nov 23, 2016 at 12:11 PM, Jan Groenewald wrote: > > > > Hi > > > > On 23 November 2016 at 22:05, Dima Pasechnik wrote: > >> > >> > >> I understand that opinions on usability of https://github.com/sagemath/ > sagenb/tree/newui > >>

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

2016-11-23 Thread William Stein
On Wed, Nov 23, 2016 at 12:11 PM, Jan Groenewald wrote: > > Hi > > On 23 November 2016 at 22:05, Dima Pasechnik wrote: >> >> >> I understand that opinions on usability of >> https://github.com/sagemath/sagenb/tree/newui >> diverge. (and with the breakneck speed javascript >> frameworks are deve

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

2016-11-23 Thread Dima Pasechnik
On Wednesday, November 23, 2016 at 8:11:27 PM UTC, Jan Groenewald wrote: > > Hi > > On 23 November 2016 at 22:05, Dima Pasechnik > wrote: > >> >> I understand that opinions on usability of >> https://github.com/sagemath/sagenb/tree/newui >> diverge. (and with the breakneck speed javascript >>

Re: [sage-devel] requirements for publishing (reference request)

2016-11-23 Thread Justin C. Walker
Dear Hezi, > On Nov 23, 2016, at 03:39 , Hezi Halawi wrote: > > Dear all, > > I am writing a code in sage about automorphic representations and Eisenstein > series, and I would like to publish it as a package in sage. Does anybody > know the requirements for publishing? > > On the level of

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

2016-11-23 Thread Jan Groenewald
Hi On 23 November 2016 at 22:05, Dima Pasechnik wrote: > > I understand that opinions on usability of https://github.com/ > sagemath/sagenb/tree/newui > diverge. (and with the breakneck speed javascript > frameworks are developed, one may ask whether something written in 2012 is > still a great

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

2016-11-23 Thread Dima Pasechnik
On Wednesday, November 23, 2016 at 6:42:40 PM UTC, Jack Dyson wrote: > > On Friday, April 15, 2016 at 10:44:21 AM UTC+2, 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 installat

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

2016-11-23 Thread Jack Dyson
On Friday, April 15, 2016 at 10:44:21 AM UTC+2, 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 the sources

[sage-devel] Re: Implements change_ring() for BooleanPolynomialRing (#21817) -- Needs Review

2016-11-23 Thread Simon King
PS: On 2016-11-23, Simon King wrote: > Hence, if you want a polynomial ring over QQ that has the same algebraic > relations as a boolean polynomial ring, you could do > > sage: B. = BooleanPolynomialRing() > sage: B.defining_ideal().ring().change_ring(QQ).quo(B.defining_ideal()) >

[sage-devel] Re: Implements change_ring() for BooleanPolynomialRing (#21817) -- Needs Review

2016-11-23 Thread Simon King
Hi, On 2016-11-22, Rusydi H. Makarim wrote: >> Shouldn't it raise an error as soon as the "new" base ring is different >> from GF(2)? >> > > I don't see any reason why this should not be allowed in the case of > BooleanPolynomialRing. Because a BooleanPolynomialRing is defined to be a ring over

Re: [sage-devel] Update CDDLIB source package? (was: What is the correct way to patch packages that use autotools?)

2016-11-23 Thread Erik Bray
On Wed, Nov 23, 2016 at 12:58 PM, Dima Pasechnik wrote: > AFAIK (20+ years experience with (lib)CDD ;-)) autotools support was donated > to cdd many years ago, at 2001, > and it predates Sage. > I'm sure updates would be welcome. Alright, thanks for the history. I knew there were some pages that

Re: [sage-devel] Update CDDLIB source package? (was: What is the correct way to patch packages that use autotools?)

2016-11-23 Thread Dima Pasechnik
AFAIK (20+ years experience with (lib)CDD ;-)) autotools support was donated to cdd many years ago, at 2001, and it predates Sage. I'm sure updates would be welcome. On Wednesday, November 23, 2016 at 11:40:07 AM UTC, Jean-Pierre Flori wrote: > > > > On Wednesday, November 23, 2016 at 12:24:43 P

[sage-devel] requirements for publishing (reference request)

2016-11-23 Thread Hezi Halawi
Dear all, I am writing a code in sage about automorphic representations and Eisenstein series, and I would like to publish it as a package in sage. Does anybody know the requirements for publishing ? On the level of the documentation what is expected? Any tutorial will be helpful. Is there

Re: [sage-devel] Update CDDLIB source package? (was: What is the correct way to patch packages that use autotools?)

2016-11-23 Thread Jean-Pierre Flori
On Wednesday, November 23, 2016 at 12:24:43 PM UTC+1, Erik Bray wrote: > > On Wed, Nov 23, 2016 at 12:19 PM, Jean-Pierre Flori > wrote: > > > > > > On Wednesday, November 23, 2016 at 12:17:08 PM UTC+1, Jean-Pierre Flori > > wrote: > >> > >> We should definitely contact upstream if updating

[sage-devel] Re: libgap and dynamic loading of GAP packages

2016-11-23 Thread Nicolas M. Thiery
Hi Volker, Dima, On Tue, Nov 22, 2016 at 02:33:12PM -0800, Dima Pasechnik wrote: >Volker says that one most probably only >needs https://trac.sagemath.org/ticket/19915 >(which needs some love...) >and then it would work. Ah right! Thanks to both of you for the quick answer

Re: [sage-devel] Update CDDLIB source package? (was: What is the correct way to patch packages that use autotools?)

2016-11-23 Thread Erik Bray
On Wed, Nov 23, 2016 at 12:19 PM, Jean-Pierre Flori wrote: > > > On Wednesday, November 23, 2016 at 12:17:08 PM UTC+1, Jean-Pierre Flori > wrote: >> >> We should definitely contact upstream if updating the autotools stuff >> there is needed. > > But do they ship autotools stuff or does it come fro

Re: [sage-devel] Update CDDLIB source package? (was: What is the correct way to patch packages that use autotools?)

2016-11-23 Thread Erik Bray
On Wed, Nov 23, 2016 at 12:13 PM, Francois Bissey wrote: > configure.in are certainly a bad indicator. Anything with one > of these instead of configure.ac triggers a warning in gentoo > that support for it will be dropped sooner than later. Yes, I get that warning as well. It's mostly superfici

Re: [sage-devel] Update CDDLIB source package? (was: What is the correct way to patch packages that use autotools?)

2016-11-23 Thread Jean-Pierre Flori
On Wednesday, November 23, 2016 at 12:17:08 PM UTC+1, Jean-Pierre Flori wrote: > > We should definitely contact upstream if updating the autotools stuff > there is needed. > But do they ship autotools stuff or does it come from Sage? Old tickets: * https://trac.sagemath.org/ticket/13026 * htt

Re: [sage-devel] Update CDDLIB source package? (was: What is the correct way to patch packages that use autotools?)

2016-11-23 Thread Jean-Pierre Flori
We should definitely contact upstream if updating the autotools stuff there is needed. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@goog

Re: [sage-devel] Update CDDLIB source package? (was: What is the correct way to patch packages that use autotools?)

2016-11-23 Thread Francois Bissey
configure.in are certainly a bad indicator. Anything with one of these instead of configure.ac triggers a warning in gentoo that support for it will be dropped sooner than later. In any case what kind of changes do you want to apply, I may have better luck with my packaging machinery. François >

Re: [sage-devel] Re: libgap and dynamic loading of GAP packages

2016-11-23 Thread Erik Bray
On Tue, Nov 22, 2016 at 11:31 PM, Volker Braun wrote: > You need the "unprefixed libgap" where the symbols are not prefixed. > https://trac.sagemath.org/ticket/19915 Wouldn't it also be possible, in principle, to build a separate set of binaries for the GAP packages that are linked against libGAP

Re: [sage-devel] Re: Update CDDLIB source package? (was: What is the correct way to patch packages that use autotools?)

2016-11-23 Thread Dima Pasechnik
On Wednesday, November 23, 2016 at 10:59:26 AM UTC, Erik Bray wrote: > > On Wed, Nov 23, 2016 at 11:50 AM, Dima Pasechnik > wrote: > > > > > > On Wednesday, November 23, 2016 at 10:32:59 AM UTC, Erik Bray wrote: > >> > >> On Thu, Nov 17, 2016 at 5:28 PM, Jean-Pierre Flori > >> wrote: > >

Re: [sage-devel] Re: Update CDDLIB source package? (was: What is the correct way to patch packages that use autotools?)

2016-11-23 Thread Erik Bray
On Wed, Nov 23, 2016 at 11:50 AM, Dima Pasechnik wrote: > > > On Wednesday, November 23, 2016 at 10:32:59 AM UTC, Erik Bray wrote: >> >> On Thu, Nov 17, 2016 at 5:28 PM, Jean-Pierre Flori >> wrote: >> > >> > >> > On Thursday, November 17, 2016 at 5:27:15 PM UTC+1, Erik Bray wrote: >> >> >> >> Hmm

[sage-devel] Re: Update CDDLIB source package? (was: What is the correct way to patch packages that use autotools?)

2016-11-23 Thread Dima Pasechnik
On Wednesday, November 23, 2016 at 10:32:59 AM UTC, Erik Bray wrote: > > On Thu, Nov 17, 2016 at 5:28 PM, Jean-Pierre Flori > wrote: > > > > > > On Thursday, November 17, 2016 at 5:27:15 PM UTC+1, Erik Bray wrote: > >> > >> Hmm, okay. I am using my system's autoreconf. For the sage autoto

[sage-devel] Update CDDLIB source package? (was: What is the correct way to patch packages that use autotools?)

2016-11-23 Thread Erik Bray
On Thu, Nov 17, 2016 at 5:28 PM, Jean-Pierre Flori wrote: > > > On Thursday, November 17, 2016 at 5:27:15 PM UTC+1, Erik Bray wrote: >> >> Hmm, okay. I am using my system's autoreconf. For the sage autotools >> is that just an optional package I need to install? > > Yes. Well, this is still tur

[sage-devel] Re: OSX 10.12 openssl and other problems

2016-11-23 Thread Dima Pasechnik
On Tuesday, November 22, 2016 at 11:29:45 PM UTC, Volker Braun wrote: > > Thats a big shit sandwich We could just copy Apple's openssl headers > from the last version. Presumably they'll keep shipping the old library > since Python keeps depending on it. Or are they planning to pull a 3.5mm