[sage-devel] Re: Getting rid of the pickle jar

See https://trac.sagemath.org/ticket/24337 for actually doing this. -- 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...@googlegroups.com. To

Re: [sage-devel] Re: Why doesn't #23931 get merged?

On 2017-12-08 10:26, Erik Bray wrote: a) Have a normal "bleeding edge" master branch into which all accepted changes are immediately merged Now everything boils down to defining "accepted changes". Just having a ticket set to positive review does not mean that much. It is a bad idea to merge

Re: [sage-devel] Why doesn't #23931 get merged?

On Thu, Dec 7, 2017 at 3:39 PM, Friedrich Wiemer wrote: > The ticket #23931 has a positive review for quite some time and I'm not > aware of any changes left for it, so my humble question is: Is there a > reason this ticket isn't merged yet? In the time between now and

Re: [sage-devel] Re: Why doesn't #23931 get merged?

On Thu, Dec 7, 2017 at 6:26 PM, William Stein wrote: > On Thu, Dec 7, 2017 at 7:02 AM, Frédéric Chapoton > wrote: >> We have currently 115 such positive-reviewed tickets waiting for inclusion, > > Maybe the release manager could use some assistance? Or we

Re: [sage-devel] Development suggestion

David, this is a great suggestion. I opened a ticket for that: https://github.com/sagemath/sagenb/issues/436 As others noted though, the legacy SageNB notebook is no longer actively developed but rather in maintenance mode, and focus has moved to the Jupyter notebook which one could say is

[sage-devel] SageNB and ldap packages

How to set up SageNB with LDAP to SageMath 8.1? After some trying I ended up with line from ldap.functions import strf_secs trying to give an error message but even ending with ImportError: cannot import name LDAPError i.e. error in error reporting. I was able to install SageNB such that it

Re: [sage-devel] dicts in doctests

On Thu, Dec 7, 2017 at 12:56 AM, Michael Orlitzky wrote: > On 12/06/2017 09:49 AM, Erik Bray wrote: >> >> Did anyone ever think up a better solution to this? >> > > Whatever you do, you wind up with a big pile of dict output in the > middle of your test case. So (where

Re: [sage-devel] Re: Why doesn't #23931 get merged?

On 2017-12-08 15:56, Erik Bray wrote: Right now the way it (seems to) work is new tickets get assigned to the next release milestone. That release is then made...whenever...regardless of what tickets are still open or not, and then all those tickets (typically) remain in old milestones for

Re: [sage-devel] Re: Build error

On 2017-12-07 23:57, Simon King wrote: from libc.string cimport memcpy This one is fine. include "cysignals/signals.pxi" from cysignals.signals cimport FOO include 'sage/ext/stdsage.pxi' from MODULE cimport BAR You'll have to fill in the exact values for FOO, BAR and MODULE though.

Re: [sage-devel] Re: Why doesn't #23931 get merged?

Your email was quite long so I'll just reply bit by bit... On 2017-12-08 15:56, Erik Bray wrote: What you really want is to have some set of "core maintainers", possibly with different responsibilities for different areas of the code depending on their expertise. And a sign-off from one of

Re: [sage-devel] Re: Why doesn't #23931 get merged?

On 2017-12-08 15:56, Erik Bray wrote: I don't understand the point about the "buildbot workflow" but it sounds like that might be a problem with that workflow. This was certainly the bottleneck when I was release manager. But I cannot speak for the current release manager. On most projects

Re: [sage-devel] Re: Why doesn't #23931 get merged?

On Fri, Dec 8, 2017 at 1:59 PM, Jeroen Demeyer wrote: > On 2017-12-08 10:26, Erik Bray wrote: >> >> a) Have a normal "bleeding edge" master branch into which all accepted >> changes are immediately merged > > > Now everything boils down to defining "accepted changes". Of

[sage-devel] Re: SageNB and ldap packages

Hi Jori, Maybe not a direct answer to your question. But if you plan on setting up an ldap authenticated sage server these days and you are planning on actually maintaining it for some time in the future, I would not go the SageNB way, since SageNB is not really being actively developed

Re: [sage-devel] Re: Why doesn't #23931 get merged?

On Friday, 8 December 2017 10:26:06 UTC+1, Erik Bray wrote: > > On Thu, Dec 7, 2017 at 6:26 PM, William Stein > wrote: > > On Thu, Dec 7, 2017 at 7:02 AM, Frédéric Chapoton > wrote: > >> We have currently 115 such positive-reviewed tickets waiting

Re: [sage-devel] Re: SageNB and ldap packages

On Fri, 8 Dec 2017, Maarten Derickx wrote: Maybe not a direct answer to your question. But if you plan on setting up an ldap authenticated sage server these days and you are planning on actually maintaining it for some time in the future, I would not go the SageNB way, since SageNB is not

[sage-devel] Re: Build error

Hi Jeroen, thanks, I'll do the changes accordingly. Best regards, Simon On 2017-12-08, Jeroen Demeyer wrote: > On 2017-12-07 23:57, Simon King wrote: >> from libc.string cimport memcpy > > This one is fine. > >> include "cysignals/signals.pxi" > > from cysignals.signals

[sage-devel] Re: Certificate of completion for Groebner Basis

On Friday, December 8, 2017 at 10:20:31 PM UTC, David Brandfonbrener wrote: > > When the Groebner basis is 1, is there a way to find the coefficients for > a linear combination of my original generators of the ideal that is equal > to 1? > > I want to be able to provably see which polynomials

[sage-devel] Merge fails of positive ticket HOWTO

Hi, A positive-review ticket was sent back because of merge conflict. Somewhere there has to be the info which other ticket caused it so I can provide a conflict fix. I also remember Volker giving me a web address once in such a case but it's buried in a ticket. So, I want to put a howto in a

Re: [sage-devel] Re: SageNB and ldap packages

On Fri, Dec 8, 2017 at 10:15 PM, Jori Mäntysalo wrote: > On Fri, 8 Dec 2017, William Stein wrote: > >>> I know. But there is still no notebook sharing in other choises, and that >>> is >>> what are used here for teaching. >> >> >> CoCalc has a completely new server for

[sage-devel] Re: Another build error

On Saturday, December 9, 2017 at 5:10:51 AM UTC+9, Simon King wrote: > > Hi Travis, > > On 2017-12-07, Travis Scrimshaw wrote: > > IMO, a better practice is to merge in old branches to a branch based off > > develop. If you want to rebase, then run rebase. That way you

Re: [sage-devel] Re: SageNB and ldap packages

On Fri, 8 Dec 2017, Dima Pasechnik wrote: How to set up SageNB with LDAP to SageMath 8.1? After some trying I ended up with line from ldap.functions import strf_secs I've no idea where this comes from, it's not in the current sagenb code, as far as I can tell. (I didn't

Re: [sage-devel] Re: SageNB and ldap packages

On Fri, 8 Dec 2017, William Stein wrote: I know. But there is still no notebook sharing in other choises, and that is what are used here for teaching. CoCalc has a completely new server for notebook sharing, which we just wrote in the last month. It is for publishing notebooks to the world,

[sage-devel] Re: SageNB and ldap packages

On Friday, December 8, 2017 at 8:56:07 AM UTC, Jori Mäntysalo wrote: > > How to set up SageNB with LDAP to SageMath 8.1? > > After some trying I ended up with line > > from ldap.functions import strf_secs > I've no idea where this comes from, it's not in the current sagenb code, as far as I

[sage-devel] Certificate of completion for Groebner Basis

When the Groebner basis is 1, is there a way to find the coefficients for a linear combination of my original generators of the ideal that is equal to 1? I want to be able to provably see which polynomials in my set of generators combine to 1. -- You received this message because you are

Re: [sage-devel] Re: SageNB and ldap packages

On Fri, Dec 8, 2017 at 11:35 AM, Jori Mäntysalo wrote: > On Fri, 8 Dec 2017, Maarten Derickx wrote: > >> Maybe not a direct answer to your question. But if you plan on setting up >> an ldap authenticated sage >> server these days and you are planning on actually maintaining

[sage-devel] Re: Another build error

Hi Travis, On 2017-12-07, Travis Scrimshaw wrote: > IMO, a better practice is to merge in old branches to a branch based off > develop. If you want to rebase, then run rebase. That way you never have > old cruft and have to watch Sage do a massive rebuild of things with