Hello Volker,
I'm happy to switch to closed when I merge it, and not only when it tests
ok.
Works for me. This way we will know the last commit that you consider
in your script, and we run no danger of adding a new one after that.
Eventually the
merge will be done by a script, so ideally
On Sunday, 19 April 2015 09:05:18 UTC+1, Snark wrote:
Le Sat, 18 Apr 2015 16:17:53 -0700 (PDT),
Volker Braun vbrau...@gmail.com javascript: a écrit :
Its a quad-core ARMv7 Cortex-A9 with 4gb ram iirc. (Calxeda)
That's much more powerful than what I have here, and it shouldn't take
I made distclean and started from scratch, now tests pass. Apparently,
something went wrong with the copying. I'll report as soon as the tests
are finished and patchbot is running...
Thanks,
Martin
--
You received this message because you are subscribed to the Google Groups
sage-devel
Hello,
It seems that the patchbot
Gentoo Base System/2.2/x86_64/3.2.1-gentoo-r2/sage4
is somewhat broken! (it fails at a very early step while other build bot
did well)
Please update it or shut it down!
Vincent
--
You received this message because you are subscribed to the Google Groups
Hello,
I really do not like
sage: M = MatrixSpace(QQ,3)
sage: G = SL(3, QQ)
sage: m1 = M(1)
sage: m2 = G(1)
sage: m1
[1 0 0]
[0 1 0]
[0 0 1]
sage: m2
[1 0 0]
[0 1 0]
[0 0 1]
sage: m1 == m2
False
Shouldn't it be True? One way would be to have a coerce embeddig from G
to M which looks natural
Le Sat, 18 Apr 2015 16:17:53 -0700 (PDT),
Volker Braun vbraun.n...@gmail.com a écrit :
Its a quad-core ARMv7 Cortex-A9 with 4gb ram iirc. (Calxeda)
That's much more powerful than what I have here, and it shouldn't take
that long to build sage 6.6 : the chromebook I (try to) use has an
exynos 5
On 14 Apr 2015 18:26, Niles Johnson nil...@gmail.com wrote:
another 2c: There is also the option of deprecating, but for less than
the somewhat arbitrary 1 year.
Although I would agree a year is somewhat arbitrary, a couple of things
are worth bearing in mind about the year.
1) If a lecturer
Can I just say I'm getting tired of people changing things in visual
representation (e.g. show)
Somewhat related: how should Sage plot
Poset([[1,2],[[1,2]]]).show()
? I made http://trac.sagemath.org/ticket/16865 from this 8 months ago, but
nobody has said which should be defined correct way.
On 19 April 2015 at 10:16, 'Martin R' via sage-devel
sage-devel@googlegroups.com wrote:
I made distclean and started from scratch, now tests pass. Apparently,
something went wrong with the copying. I'll report as soon as the tests are
finished and patchbot is running...
It is hard to make
On Sunday, April 19, 2015 at 8:28:49 PM UTC+2, leif wrote:
On 04/19/2015 06:42 PM, John Cremona wrote:
Do you have a reason for having SAGE_ROOT set at all? I don't.
That's exactly the purpose of a *user-set* SAGE_ROOT: To run a Sage
installation *somewhere else* in the filesystem
On 04/19/2015 11:42 PM, ggrafendorfer wrote:
On Sunday, April 19, 2015 at 8:28:49 PM UTC+2, leif wrote:
On 04/19/2015 06:42 PM, John Cremona wrote:
Do you have a reason for having SAGE_ROOT set at all? I don't.
That's exactly the purpose of a *user-set* SAGE_ROOT: To run a
Sagetex e.g., is one reason:
http://www.sagemath.org/doc/installation/sagetex.html
Georg
On Sunday, April 19, 2015 at 6:43:27 PM UTC+2, John Cremona wrote:
Do you have a reason for having SAGE_ROOT set at all? I don't.
John
On 19 April 2015 at 17:33, ggrafendorfer
On 04/19/2015 06:42 PM, John Cremona wrote:
Do you have a reason for having SAGE_ROOT set at all? I don't.
That's exactly the purpose of a *user-set* SAGE_ROOT: To run a Sage
installation *somewhere else* in the filesystem hierarchy.
It's probably a bit surprising that that even works with
On 19 April 2015 at 12:47, Vincent Delecroix 20100.delecr...@gmail.com wrote:
Hello,
I really do not like
sage: M = MatrixSpace(QQ,3)
sage: G = SL(3, QQ)
sage: m1 = M(1)
sage: m2 = G(1)
sage: m1
[1 0 0]
[0 1 0]
[0 0 1]
sage: m2
[1 0 0]
[0 1 0]
[0 0 1]
sage: m1 == m2
False
Am 2015-04-19 um 01:10 schrieb Volker Braun:
Freezing tickets once release manager starts merging them
- change status to closed
- some new status)
I'm happy to switch to closed when I merge it, and not only when it tests ok.
+1
The downside is that you'll
Hello,
I agree with the fact that it would be better to move ticket to 'closed'
as soon as the release manager is working on it. But I do not agree that
this should be automatic after one second!
I often have a look at positively reviewed tickets and sometimes ask
questions about the
Hellooo,
I often have a look at positively reviewed tickets and sometimes ask
questions about the review. Positive review just mean that one person agreed
that the changes were good to be integrated. But it might still interest
other to have a look (or even the reviewer might
As far as I can tell, it is never a good idea to set SAGE_ROOT, nor is it
ever suggested that you do so in the documentation. I think you could
expect things to break if you set environment variables which Sage uses
internally. One solution is to create a link '/usr/local/bin/sage' pointing
to
On Sun, Apr 19, 2015 at 10:18 AM, Volker Braun vbraun.n...@gmail.com
wrote:
I agree, coercion G - M is probably the right thing to do here.
+1
On Sunday, April 19, 2015 at 7:47:11 AM UTC-4, vdelecroix wrote:
Hello,
I really do not like
sage: M = MatrixSpace(QQ,3)
sage: G = SL(3, QQ)
On 04/20/15 09:23, ggrafendorfer wrote:
Sagetex e.g., is one reason:
http://www.sagemath.org/doc/installation/sagetex.html
I have to agree with other that setting SAGE_ROOT is
asking for trouble. For the case of of the makefile
we probably could do something about it.
However I want go back
On 04/19/2015 05:41 PM, Nathann Cohen wrote:
I often have a look at positively reviewed tickets and sometimes ask
questions about the review. Positive review just mean that one person agreed
that the changes were good to be integrated. But it might still interest
other to have a look (or even
Hi
When I build a new version of sage in a separate directory, and then, while
beeing in that directory, execute
./sage
then the current old version of sage, which can be found in SAGE_ROOT is
executed.
E.g., this looks as follows:
.../data/sage-6.6$ pwd
/mnt/data/sage-6.6
.../data/sage-6.6$
Do you have a reason for having SAGE_ROOT set at all? I don't.
John
On 19 April 2015 at 17:33, ggrafendorfer georg.grafendor...@gmail.com wrote:
Hi
When I build a new version of sage in a separate directory, and then, while
beeing in that directory, execute
./sage
then the current old
I agree, coercion G - M is probably the right thing to do here.
On Sunday, April 19, 2015 at 7:47:11 AM UTC-4, vdelecroix wrote:
Hello,
I really do not like
sage: M = MatrixSpace(QQ,3)
sage: G = SL(3, QQ)
sage: m1 = M(1)
sage: m2 = G(1)
sage: m1
[1 0 0]
[0 1 0]
[0 0 1]
24 matches
Mail list logo
