So the natural thing for Sage would be to implement e.g.:
table(range(100), highlight=is_prime)
On Tuesday, April 7, 2015 at 3:28:10 AM UTC+2, kcrisman wrote:
He showed us that one can consider the square root of a picture of a
siamese cat, but also a nice feature: one can very easily
Hello,
Are you referring to the table functionality, which works great in
notebook and maybe also now in the cloud? This sounds like what you're
saying, which is an often-requested thing that finally is top level
(previously was html.table, which also still works).
I did not know about this
Am 2015-04-02 um 20:01 schrieb Daniel Krenn:
Am 2015-04-02 um 13:25 schrieb Daniel Krenn:
Am 2015-04-02 um 13:18 schrieb Thierry:
Should we offer a kind of test-sage ? Should we propose a kind of
proprecation warning that says This code is very new and its design is not
foolproof. Its design
2015-04-03 4:05 GMT-04:00 Volker Braun vbraun.n...@gmail.com:
On Friday, April 3, 2015 at 9:56:40 AM UTC+2, Daniel Krenn wrote:
Actually, it is a short for
view(latex(transducers.GrayCode()))
I know. And who cares? The important point is to present a uniform user
interface for
Dear Harald,
Thank you very much the detailed answer! This is pretty much what I was
looking for!
Indeed, it seems like a big decision to change the logo just like that.
It is good to know
about the whole story behind the logo.
Of course, the point that logos develop a certain signature for
I did not know about this function (thanks!) though I had something
different in mind, i.e.:emphasize *some* elements of a list. What
Volker would define as:
table(range(100), highlight=is_prime)
Right, I see what you mean now. In principle the LaTeX and other outputs
of table
On Tue, Apr 7, 2015 at 9:12 AM, kcrisman kcris...@gmail.com wrote:
Sorry for dredging this up from the depths...
So I see that http://trac.sagemath.org/ticket/14418 has a more explicit
interface. What gets me wondering about the current state in Sage is an
article in the most recent Notices
Sorry for dredging this up from the depths...
So I see that http://trac.sagemath.org/ticket/14418 has a more explicit
interface. What gets me wondering about the current state in Sage is an
article in the most recent Notices which contains a reference
to
Interestingly, I just noticed that on the sagetrac webpage, the logo is
different than the usual one:
http://trac.sagemath.org/
It seems that this is actually the real picture behind Sagemath logo.
Could that be?
This would be that the logo is actually some sort of Schlegel diagram of a
No, I'm saying its nice functionality but attached at the wrong place. If
you can't use .plot() to generate the graphics the how on earth is a new
user supposed to discover that functionality? Its just a terrible UI.
On Tuesday, April 7, 2015 at 4:30:58 PM UTC+2, Viviane Pons wrote:
Hello,
We currently ship two implementations of floating point complex numbers:
- ComplexField: home made implementation based on two mpfr for the
real and imaginary parts
- MPComplexField: implementation based on the library mpc
Those two implementations serve the same purpose. Note that in
I think a logo refresh would be great. Companies refresh their logos all
the time without loss of continuity or brand recognition. I agree with the
concern that this kind of thing requires the skills of a professional
designer, but I don't see why such a professional couldn't be involved at
Hello,
On 07/04/2015, Benjamin Hackl benjamin.ha...@aau.at wrote:
Hello everybody,
today I had a look at http://trac.sagemath.org/ticket/15846 and I think I
may have tracked down the issue to SymPy (details in the comments of the
ticket).
Assuming what I found actually is the problem, I'm
On Saturday, April 4, 2015 at 3:18:53 PM UTC+2, Nicolas M. Thiéry wrote:
Actually you can ref from the thematic tutorial back to the reference
manual, and there already are many (not enough!!!) such links:
Really. Is that ticket obsolete then:
http://trac.sagemath.org/ticket/14091
--
You
Am 2015-04-04 um 15:18 schrieb Nicolas M. Thiery:
On Fri, Apr 03, 2015 at 06:24:42AM -0700, Ralf Stephan wrote:
I think it would already be better if there wasn't this bug
preventing authors from linking between document trees.That's
presumably why the three random tutorials I picked
Hello everybody,
today I had a look at http://trac.sagemath.org/ticket/15846 and I think I
may have tracked down the issue to SymPy (details in the comments of the
ticket).
Assuming what I found actually is the problem, I'm not quite sure how to
proceed from there (i.e. reporting the issue
Hello,
Could please the one of you that run the sage4 patchbot upgrade it to 2.3.2
?
It seems to be stuck on ticket #9386. Maybe updating the patchbot could
help ?
sage -i http://chapoton.perso.math.cnrs.fr/patchbot-2.3.2.spkg
cheers,
Frederic
--
You received this message because you are
... turns out that not only SymPy, but also GiNaC has a problem when
expanding zeta around 1. However, it is more likely for the error to come
from GiNaC -- so I'll do some more investigations, and then report the
issue there as well.
In any case, thanks for help!
Best wishes,
Benjamin
Am
On Tuesday, April 7, 2015 at 6:56:56 PM UTC+2, vdelecroix wrote:
Hello,
We currently ship two implementations of floating point complex numbers:
- ComplexField: home made implementation based on two mpfr for the
real and imaginary parts
- MPComplexField: implementation based on the
2015-04-07 12:13 GMT-04:00 Volker Braun vbraun.n...@gmail.com:
No, I'm saying its nice functionality but attached at the wrong place. If
you can't use .plot() to generate the graphics the how on earth is a new
user supposed to discover that functionality? Its just a terrible UI.
You're right
Exterior algebras were included as part of
http://trac.sagemath.org/ticket/15300 (which was merged into Sage 6.4).
sage: E.x,y = ExteriorAlgebra(QQ)
sage: a = x * y + x - 3*y / 2; a
x^y + x - 3/2*y
sage: a.interior_product(x)
y + 1
sage: a.interior_product(y)
-x - 3/2
Best,
Travis
--
You
21 matches
Mail list logo
