Hi Vincent,
On 2015-08-18, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
> But what happend with more recent version of Cython? The syntax error
> should remain with or without upgrading to a more recent Sage version...
In the morning, I had my branch on top of an older Sage version. In t
On 18/08/15 20:54, Simon King wrote:
On 2015-08-18, Simon King wrote:
Meanwhile I found that with HEAD~, sage builds, but with HEAD it
doesn't. So, my last commit apparently created a problem.
I only wonder how.
Found it. The strange reason was the line
print "return pos
Note the missin
On 2015-08-18, Simon King wrote:
> Meanwhile I found that with HEAD~, sage builds, but with HEAD it
> doesn't. So, my last commit apparently created a problem.
>
> I only wonder how.
Found it. The strange reason was the line
print "return pos
Note the missing ".
Of course I would expect cyth
On 2015-08-18, Simon King wrote:
> What now?
Meanwhile I found that with HEAD~, sage builds, but with HEAD it
doesn't. So, my last commit apparently created a problem.
I only wonder how. The last commit only touches files in
src/sage/quivers/, thus, shouldn't affect the build system. Is there a
Sigh.
On 2015-08-18, Simon King wrote:
> After changing to develop (and pulling in the latest beta), it seems to
> work, in the sense that many cython files have successfully been built.
It did succeed
> If the build succeeds, I will merge the develop branch with my work branch.
To be precise,
Hi Vincent,
On 2015-08-18, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
> It might. There was this cython memleak #18294 but it has been merged in
> 6.8.beta2... so I am not sure what is the problem.
>
> If I was you I would try to upgrade to the last beta.
After changing to develop (and
PS:
>On 2015-08-18, Simon King wrote:
> On 2015-08-18, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
>> Are you up to date with the last develop?
>
> No. The branch that I was working on is based on 6.8.beta2. But would it
> explain why the branch first works and then by changing a file in
On 18/08/15 15:40, Simon King wrote:
On 2015-08-18, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
Are you up to date with the last develop?
No. The branch that I was working on is based on 6.8.beta2. But would it
explain why the branch first works and then by changing a file in
src/sage
On 2015-08-18, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
> Are you up to date with the last develop?
No. The branch that I was working on is based on 6.8.beta2. But would it
explain why the branch first works and then by changing a file in
src/sage/quivers/ suddenly the memory consumpti
Are you up to date with the last develop?
--
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 post to this group, send emai
On 2015-08-18, Simon King wrote:
> On 2015-08-18, Simon King wrote:
>> I tried, but it did *not* help. So, now I have a serious problem. What
>> else might do the trick? "make python" before doing make again (since it
>> is python that uses all the memory)?
>
> I tried ./sage -f python, but when
On 2015-08-18, Simon King wrote:
> I tried, but it did *not* help. So, now I have a serious problem. What
> else might do the trick? "make python" before doing make again (since it
> is python that uses all the memory)?
I tried ./sage -f python, but when I then did "make", I found that the
proble
Hi Francois,
On 2015-08-18, Francois Bissey wrote:
> First question first. Did you update/install anything new on that machine
> before running into the problem? Think carefully.
openSuse creates a snapshot before installing/updating anything. So, I
can say that I did not change the system since
PPS:
On 2015-08-18, Simon King wrote:
> I tried, but it did *not* help. So, now I have a serious problem. What
> else might do the trick? "make python" before doing make again (since it
> is python that uses all the memory)?
An additional observation: After killing the process, htop shows me tha
PS:
On 2015-08-18, Simon King wrote:
> I currently have a problem with the Sage installation on my laptop. I am
> developing some code, and since yesterday ./sage -br was correctly
> building stuff.
Typo, I mean "till yesterday" it was working. Actually till a few hours
ago.
> Any clue what wen
15 matches
Mail list logo
