Re: [sage-devel] Build error

I tried some of the suggestions: 1) deleting SAGE_LOCAL/lib/libpython* and then make -> failed 2) make distclean && make build -> success I still have to add the optional packages I need, but it's working. Thanks. David. -- You received this message because you are subscribed to the Google Grou

Re: [sage-devel] Development suggestion

On Wednesday, December 6, 2017 at 11:34:06 PM UTC-5, William wrote: > > On Wed, Dec 6, 2017 at 7:09 PM, David Cousens > wrote: > > Hi > > > > Has anyone considered making the menu section of the sage Web interface > non > > scrolling and only making the worksheet cell part of the interface

[sage-devel] Re: [OT] Re: Issue with quick start

> > In German, we have an abbreviation for "compulsive abbreviation > disorder": Aküfi ("Abkürzungsfimmel", which roughly means > "abbrevimania"). Nie gehört but I love it! -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe fro

[sage-devel] Re: Another build error

On Friday, December 8, 2017 at 8:30:48 AM UTC+9, Travis Scrimshaw wrote: > > > >> Anyway. The branch used to be an old one. I checked it out and then >> rebased on top of the latest develop. Do I understand correctly that >> while rebasing, git failed to remove the cypari2 folder? >> >> IMO, a

[sage-devel] Re: Another build error

> > Anyway. The branch used to be an old one. I checked it out and then > rebased on top of the latest develop. Do I understand correctly that > while rebasing, git failed to remove the cypari2 folder? > > IMO, a better practice is to merge in old branches to a branch based off develop. If yo

Re: [sage-devel] Build error

yeah, I agree that a stale library is the most probable reason for this error. -- 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.

[sage-devel] Re: Another build error

On 2017-12-07, François Bissey wrote: > Seems like it. Which is why I asked if there was anything in it. I think it was empty before I removed it. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving

Re: [sage-devel] Re: Build error

> On 8/12/2017, at 11:57, Simon King wrote: > > I just see the following in the diff: > > +from libc.string cimport memcpy > +include "cysignals/signals.pxi" > +include 'sage/ext/stdsage.pxi' > > I recall from some trac ticket I was involved in that all three of the > above statements should

[sage-devel] Re: Build error

On 2017-12-07, Simon King wrote: > On 2017-12-07, François Bissey wrote: >> No. I believe we stopped relying on that file when upgrading to cysignals >> 1.6.x. >> So the proper include to get that file may have been removed from somewhere. >> Your branch would be quite peculiar to be caught betw

Re: [sage-devel] Re: Another build error

> On 8/12/2017, at 11:48, Simon King wrote: > > Hi François, > > On 2017-12-07, François Bissey wrote: >>> Strangely, git status mentions >>> src/sage/libs/cypari2/ >>> which my local branch is *not* touching. So, what's happening? >>> >> >> Anything in that folder? That folder has been r

[sage-devel] Re: Another build error

Hi François, On 2017-12-07, François Bissey wrote: >> Strangely, git status mentions >>src/sage/libs/cypari2/ >> which my local branch is *not* touching. So, what's happening? >> > > Anything in that folder? That folder has been removed when cypari2 has been > made a separate package. git s

[sage-devel] Re: Build error

On 2017-12-07, François Bissey wrote: > No. I believe we stopped relying on that file when upgrading to cysignals > 1.6.x. > So the proper include to get that file may have been removed from somewhere. > Your branch would be quite peculiar to be caught between two changes. > Could you rebase it?

Re: [sage-devel] Re: Another build error

> On 8/12/2017, at 11:12, Simon King wrote: > > On 2017-12-07, Simon King wrote: >> Hi! >> >> Building Sage again, I get the error >> InternalError: Internal compiler error: 'cysignals/signals.pxi' not >> found >> >> Unfortunately, the error did not go away after "make distclean". >> >> W

[sage-devel] Re: Another build error

On 2017-12-07, Simon King wrote: > Hi! > > Building Sage again, I get the error > InternalError: Internal compiler error: 'cysignals/signals.pxi' not > found > > Unfortunately, the error did not go away after "make distclean". > > What can I do? The error occurs on some local branch (different

Re: [sage-devel] Re: Build error

No. I believe we stopped relying on that file when upgrading to cysignals 1.6.x. So the proper include to get that file may have been removed from somewhere. Your branch would be quite peculiar to be caught between two changes. Could you rebase it? François > On 8/12/2017, at 10:56, Simon King w

[sage-devel] Re: Build error

Hi! On 2017-12-07, François Bissey wrote: > OK this looks suspiciously like > https://bugs.python.org/issue30074 > which was fixed by > https://github.com/python/cpython/pull/1154 > which should be in 2.7.14. > What I suspect is happening is that those failures happen when > people upgrade pyth

[sage-devel] Another build error

Hi! Building Sage again, I get the error InternalError: Internal compiler error: 'cysignals/signals.pxi' not found Unfortunately, the error did not go away after "make distclean". What can I do? The error occurs on some local branch (different from develop), however I didn't touch cysignals.

Re: [sage-devel] Build error

OK this looks suspiciously like https://bugs.python.org/issue30074 which was fixed by https://github.com/python/cpython/pull/1154 which should be in 2.7.14. What I suspect is happening is that those failures happen when people upgrade python from 2.7.13 (or older) to 2.7.14. I have a feeling that

Re: [sage-devel] Build error

it would be interesting that try to debug this. You most probably can get a working version by doing make distclean (making sure it succeeds!) and then building, so please do cp -a of the whole tree before doing this... -- You received this message because you are subscribed to the Google

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

I'm currently preparing 8.1 which was held up for a while because of some last-minute fixes. When that is out we'll be back to the usual pace. On Thursday, December 7, 2017 at 3:39:07 PM UTC+1, Friedrich Wiemer wrote: > > The ticket #23931 has a positive >

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

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 could rotate to more release managers like we used to do for many years... > see > > https://trac.sage

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

OK, so its basically because lack of time? Is this something a newbie contributer like me can help with? Am Donnerstag, 7. Dezember 2017 16:02:56 UTC+1 schrieb Frédéric Chapoton: > > We have currently 115 such positive-reviewed tickets waiting for > inclusion, see > > > https://trac.sagemath.org

[sage-devel] Re: [OT] Re: Issue with quick start

On 2017-12-07, Jeroen Demeyer wrote: > On 2017-12-02 01:24, d...@shorewestern.com wrote: >> communicative human nature yearns for >> abbreviation > > My impression is that this is mostly an American phenomenon. When I did my PhD in Strasbourg, I thought it was a French phenomenon. Unless you see

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

We have currently 115 such positive-reviewed tickets waiting for inclusion, see https://trac.sagemath.org/query?status=positive_review&milestone=!sage-duplicate%2Finvalid%2Fwontfix&group=milestone&col=id&col=summary&col=type&col=component&col=changetime&col=author&col=reviewer&col=dependencies&re

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

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? -- You received this message becau

[sage-devel] [OT] Re: Issue with quick start

On 2017-12-02 01:24, d...@shorewestern.com wrote: communicative human nature yearns for abbreviation My impression is that this is mostly an American phenomenon. Off-topic true story: when I was a young PhD student, I spent a few weeks in Berkeley (California, USA). While walking to the unive

Re: [sage-devel] Re: Issue with quick start

On 2017-12-04 23:52, Dima Pasechnik wrote: I will open a trac ticket changing Math* to Wiskunde. Great idea! -- 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 sag

Re: [sage-devel] Build error

On 2017-12-07 15:13, Simon King wrote: How to fix that? This is a bug that several people have reported but I don't know how to reproduce it. make distclean and start again? That works. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To u

[sage-devel] Build error

Hi! On a laptop that I haven't used for a while, I tried to upgrade Sage. I.e., I did "git checkout develop", "git pull" and "make". While building python2-2.7.15.p2, I get [python2-2.7.14.p2] ImportError: No module named _ctypes [python2-2.7.14.p2] ctypes module failed to import and [pyt