[sage-devel] Where is implemented the logic deciding whether to install git or not ?

Dear list, The git standard package is not installed when the system on whic Sage is built has a systemwide version of git. I have been unable to find where the logic of this decision is implemented. Can some kind soul point me to this place ? Sincerely, -- Emmanuel Charpentier -- You recei

Re: [sage-devel] Problems with sage -br

On 2017-01-15 15:44, Andrew wrote: then sage -br fails with the error message: Did you run make? -- 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+unsu

[sage-devel] Re: SageManifolds 1.0 in Sage 7.5 and development workflow

Eric, it seems to me that this is now an area in which SageMath is ahead of Mathematica, and you are to be congratulated for that. Given that Wolfram is a physicist, I've never understood why there is no native support in Mathematica for general relativity calculations. Have you considered addi

Re: [sage-devel] Re: SageManifolds 1.0 in Sage 7.5 and development workflow

Le dimanche 15 janvier 2017 23:10:33 UTC+1, William a écrit : > > Kind of like publishing and important and foundational research paper...? > More kind of like writing a book ;-) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe fro

Re: [sage-devel] Re: SageManifolds 1.0 in Sage 7.5 and development workflow

Kind of like publishing and important and foundational research paper...? On Sun, Jan 15, 2017 at 1:49 PM Eric Gourgoulhon wrote: > Le dimanche 15 janvier 2017 21:24:37 UTC+1, Kwankyu Lee a écrit : > > You managed to develop SageManifolds separately from Sage, and then to > integrate the code ful

[sage-devel] Re: SageManifolds 1.0 in Sage 7.5 and development workflow

Le dimanche 15 janvier 2017 21:24:37 UTC+1, Kwankyu Lee a écrit : > > You managed to develop SageManifolds separately from Sage, and then to > integrate the code fully with Sage. I am curious how this is done. It looks > daunting to me to chop out big code to small patches for gradual merge, > w

Re: [sage-devel] SageManifolds 1.0 in Sage 7.5 and development workflow

The support team has just fixed the issue; the server is up again: http://sagemanifolds.obspm.fr/contrib.html Eric. Le dimanche 15 janvier 2017 20:53:08 UTC+1, Eric Gourgoulhon a écrit : > > Le dimanche 15 janvier 2017 19:59:26 UTC+1, William a écrit : > > >> 404 Not Found >> >> > Indeed there

Re: [sage-devel] Re: Release note auto-generation RFC

On Sunday, January 15, 2017 at 6:58:38 PM UTC, William wrote: > > On Sun, Jan 15, 2017 at 5:18 AM, Dima Pasechnik > wrote: > > On Wednesday, January 11, 2017 at 11:09:53 PM UTC, Volker Braun wrote: > >> > >> There is a somewhat painless approach to generating human-readable > release > >> n

[sage-devel] Re: SageManifolds 1.0 in Sage 7.5 and development workflow

You managed to develop SageManifolds separately from Sage, and then to integrate the code fully with Sage. I am curious how this is done. It looks daunting to me to chop out big code to small patches for gradual merge, without breaking Sage. Current Sage development workflow forces an author o

Re: [sage-devel] SageManifolds 1.0 in Sage 7.5 and development workflow

Le dimanche 15 janvier 2017 19:59:26 UTC+1, William a écrit : > 404 Not Found > > Indeed there is a problem on the server. I am contacting the support team... -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and

Re: [sage-devel] SageManifolds 1.0 in Sage 7.5 and development workflow

On Sun, Jan 15, 2017 at 9:51 AM, Eric Gourgoulhon wrote: > Dear Sage devs, > > The just released Sage 7.5 contains the integrality of SageManifolds code, > the last SageManifolds tickets having been merged in 7.5.beta4 > (cf. https://trac.sagemath.org/ticket/18528 ) > Consequently, there is no nee

Re: [sage-devel] Re: Release note auto-generation RFC

On Sun, Jan 15, 2017 at 5:18 AM, Dima Pasechnik wrote: > On Wednesday, January 11, 2017 at 11:09:53 PM UTC, Volker Braun wrote: >> >> There is a somewhat painless approach to generating human-readable release >> notes using https://github.com/hawkowl/towncrier. As far as the ticket >> author is co

Re: [sage-devel] Detected access to protected memory, also kwown as 'bus or segmentation fault'.

This indeed seems to be a problem in maxima itself. With domain : complex; limit( (1/(c*n^6))^(log(n)/log(2/3)), n, inf); in maxima, the same problem arises. Without "domain : complex" there is no problem, so it's an unfortunate interaction somewhere. -- You received this message because you a

[sage-devel] Re: Detected access to protected memory, also kwown as 'bus or segmentation fault'.

IIRC I have seen this while working on https://trac.sagemath.org/ticket/18920 (and it's reported upstream - this is a Maxima or Maxima/ECL bug) see also https://trac.sagemath.org/wiki/symbolics On Sunday, January 15, 2017 at 2:27:32 PM UTC, Peleg Michaeli wrote: > > The following attempt: > > s

[sage-devel] Re: Problems with sage -br

On Sunday, January 15, 2017 at 2:44:12 PM UTC, Andrew wrote: > > I have compiled sage 7.5 and all tests pass. On the master and develop > branches using sage -br works fine. However, if I move to another branch, > for example with > > git trac checkout 20564 > the branch on https://trac.sagemat

[sage-devel] SendGrid (trac emails) issue

Some of my trac emails are still going missing. In the last case at least, this is because the message failed temporarily, and SendGrid never retried it (they're required to do by the RFCs). This is the original attempt, Jan 2 20:04:10 mx1 postfix/postscreen[5269]: NOQUEUE: reject: RCPT from

Re: [sage-devel] Detected access to protected memory, also kwown as 'bus or segmentation fault'.

The same happens for me on Sage 7.4 on Fedora, so definitely a bug. On Sun, Jan 15, 2017 at 3:27 PM, Peleg Michaeli wrote: > The following attempt: > > sage: var('c,n') > sage: (1/(c*n^6))^log(n,2/3).limit(n=infinity) > > Is ok (raises ValueError), but the following attempt: > > sage: var('c,n')

[sage-devel] SageManifolds 1.0 in Sage 7.5 and development workflow

Dear Sage devs, The just released Sage 7.5 contains the integrality of SageManifolds code, the last SageManifolds tickets having been merged in 7.5.beta4 (cf. https://trac.sagemath.org/ticket/18528 ) Consequently, there is no need for a separate installation of SageManifolds (*), which is released

[sage-devel] Detected access to protected memory, also kwown as 'bus or segmentation fault'.

The following attempt: sage: var('c,n') sage: (1/(c*n^6))^log(n,2/3).limit(n=infinity) Is ok (raises ValueError), but the following attempt: sage: var('c,n') sage: f = (1/(c*n^6))^log(n,2/3) sage: f.limit(n=infinity) hangs a little while, the prints a lot of times ;;; ;;; Detected access to pr

[sage-devel] Re: Our SSL serial drama-cum-cliffhanger

A first step towards a solution awaits your comments and review. Plan : 1. Document OpenSSL dependency, mention the possibility of compiling againts GnuTLS (with drawbacks) 2. Get OpenSSL development libs on the machines producing Unix binary

[sage-devel] Re: Release note auto-generation RFC

On Wednesday, January 11, 2017 at 11:09:53 PM UTC, Volker Braun wrote: > > There is a somewhat painless approach to generating human-readable release > notes using https://github.com/hawkowl/towncrier. As far as the ticket > author is concerned, if you think that your ticket #12435 is of wider >