On Tue, 18 Aug 2015, Dima Pasechnik wrote:
At http://trac.sagemath.org/ticket/17164 it seems that Sage 6.8 has not
support for vulnerable SSLv3 anymore. But it still seems to have - at
least on SageNB.
I have and old installation that I have upgraded version-by-version
for years.
Probably
On Fri, Aug 14, 2015 at 06:37:15AM -0700, kcrisman wrote:
>
>
> > At http://trac.sagemath.org/ticket/17164 it seems that Sage 6.8 has not
> > support for vulnerable SSLv3 anymore. But it still seems to have - at
> > least on SageNB.
> >
> >
> Dima was the one who green lighted that, I assume h
well, the subject ought to be something like "git trac plugin shows
nonsense".
On Tuesday, 18 August 2015 15:20:06 UTC-7, Stefan wrote:
>
> When I click on the green link with the branch name in this ticket, it
> makes it look like it deletes the contents of two files:
>
> http://trac.sagemath.o
>
> >
> > An obvious use-case is that you're switching branches/Sage versions
> and
> > you just want to try to compile a single package and you don't want
> to
> > be bothered by dependencies.
> >
> >
> > I'd call that "working around bugs in our broken build system".
> No, i
When I click on the green link with the branch name in this ticket, it
makes it look like it deletes the contents of two files:
http://trac.sagemath.org/ticket/18946
When I "git trac try 18946" and then do a diff against the previous commit,
everything is fine (i.e. the new code gets added, not
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 Tuesday, August 18, 2015 at 10:22:33 PM UTC+2, Jeroen Demeyer wrote:
>
> > I'd call that "working around bugs in our broken build system".
> No, it's called "not wanting to wait for hours until all dependencies
> are compiled".
There is no need to wait for the dependencies to compile, its th
On 2015-08-18 10:21, Simon King wrote:
Hi,
On 2015-08-17 19:00, Jeroen Demeyer wrote:
(A) change "sage -i PKG" to also install dependencies (adding some
option --no-dependencies to keep the old behaviour)
Since I maintain an optional package that depends on another optional
package that must
On 2015-08-18 21:16, Jeroen Demeyer wrote:
Good for me, since it is very close to my proposal (C)
I meant (B) here (add an option -m to install with dependencies)
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and
On 2015-08-18 20:42, Volker Braun wrote:
On Tuesday, August 18, 2015 at 9:26:44 PM UTC+2, Jeroen Demeyer wrote:
An obvious use-case is that you're switching branches/Sage versions and
you just want to try to compile a single package and you don't want to
be bothered by dependencies.
On 2015-08-18 12:00, Thierry wrote:
Actually, i do not see why (A) involves more complexity than (B).
1. We need to define how the various options to -i can be combined, in
particular the -f option is tricky.
2. The "sage -i" command would need to do two completely unrelated
things: act as high
On 2015-08-18 10:07, Jori Mäntysalo wrote:
Failed example:
singular.interrupt(timeout=3) # sometimes very slow (up to 60s on
This is fixed by #10476.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop
On Tuesday, August 18, 2015 at 9:26:44 PM UTC+2, Jeroen Demeyer wrote:
>
> An obvious use-case is that you're switching branches/Sage versions and
> you just want to try to compile a single package and you don't want to
> be bothered by dependencies.
I'd call that "working around bugs in our br
On 2015-08-18 14:49, Volker Braun wrote:
Whats the use case of attempting to install a package without
dependencies?
An obvious use-case is that you're switching branches/Sage versions and
you just want to try to compile a single package and you don't want to
be bothered by dependencies. I agre
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 Tue, Aug 18, 2015 at 10:26 AM, Nathann Cohen wrote:
> Hello everybody,
>
> Just a random thought. I typed "plot(sin(x))" today, and it felt "wrong"
> that the plot was on x=-1...1.
>
> I know that we are not wizards, and that we cannot magically guess the
> "right" interval to plot a function.
Hello everybody,
Just a random thought. I typed "plot(sin(x))" today, and it felt "wrong"
that the plot was on x=-1...1.
I know that we are not wizards, and that we cannot magically guess the
"right" interval to plot a function. But I wondered: what would you think
of changing that default to -3,
On Monday, 17 August 2015 14:29:01 UTC-7, Jeroen Demeyer wrote:
>
> On 2015-08-17 19:12, kcrisman wrote:
> > How many packages currently have such (additional) dependencies now as
> > opposed to several years ago?
> Currently, the only packages which depend on a package which is not
> standar
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,
I've seen that one before. Happens randomly. The doctest should be marked #
known bug
On Tuesday, August 18, 2015 at 11:07:33 AM UTC+2, Jori Mäntysalo wrote:
>
> I took the patch from http://trac.sagemath.org/ticket/18936 , compiled
> and
> ran long tests successfully. Then I installed dot2te
On Tuesday, August 18, 2015 at 6:49:47 AM UTC-7, Volker Braun wrote:
>
> Whats the use case of attempting to install a package without
> dependencies? I can't think of any.
>
I'm not sure I can come up with very compelling examples, but if I've
modified some package on which gcc depends, but
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
Whats the use case of attempting to install a package without dependencies?
I can't think of any. Whether you are developer or user, you always want to
have your dependencies in place before compiling something. The fact that
"sage -i" does not is 100% historical limitation. Now we can build pac
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
Hi,
thanks Jeroen for raising this question. Note that `sage -i` appears both
in `sage -h` and `sage -advanced`, which might explain why its status is
not well defined (user interface vs atomic dev tool). So, the question is
about splitting the two features.
>From the user point of view, (A) is d
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
> Since I maintain an optional package that depends on another optional
> package that must not be automatically installed because of licence:
> Will the automatic installation of dependencies be involve asking the
> user if the licence of the dependency is not GPL compatible?
Whatever happens, th
Hi,
> On 2015-08-17 19:00, Jeroen Demeyer wrote:
> (A) change "sage -i PKG" to also install dependencies (adding some
> option --no-dependencies to keep the old behaviour)
Since I maintain an optional package that depends on another optional
package that must not be automatically installed becaus
On 2015-08-17 19:00, Jeroen Demeyer wrote:
(A) change "sage -i PKG" to also install dependencies (adding some
option --no-dependencies to keep the old behaviour)
+1
Daniel
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from thi
I took the patch from http://trac.sagemath.org/ticket/18936 , compiled and
ran long tests successfully. Then I installed dot2tex and ran short tests,
and got
sage -t --warn-long 32.0 src/sage/interfaces/expect.py
**
File "src/s
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
First question first. Did you update/install anything new on that machine
before running into the problem? Think carefully.
François
> On 18/08/2015, at 19:18, Simon King wrote:
>
> Hi,
>
> I currently have a problem with the Sage installation on my laptop. I am
> developing some code, and sin
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
> My current vote (although I keep changing my mind):
>
> - document "make pkg" to install packages, not "sage -i pkg"
How do you propose we update the doc for that? Sage is filled with
exceptions which say "type sage -i " in ordert to install the
pacakge you need. We cannot just say "type make ",
Hi,
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. But when I do ./sage -br today, it very soon consumes
all available memory, freezes my laptop for a while, and finally fails.
The increas
42 matches
Mail list logo
