Done and thanks!
workaround before the ticket is merged:
sage: from sage.libs.pynac.pynac import register_symbol
sage: register_symbol(abs, {'fricas': 'abs'})
(would it be better not to create symbolic functions for functions returned
by fricas unknown to sage?)
Martin
Am Samstag, 30. März
Hi,
Thanks MJ for reporting the bug and opening the ticket.
It is fixed in the ticket branch now.
Nils: yes I banged my head on the desk a couple of times :-)
Best wishes,
Eric.
Le samedi 30 mars 2019 20:49:37 UTC+1, MJ a écrit :
>
> Yes, of course. I'm just too impatient for tasks like
I have made https://trac.sagemath.org/ticket/27577, which needs review
(very simple ticket)
Frederic
Le samedi 30 mars 2019 10:56:59 UTC+1, Emmanuel Charpentier a écrit :
>
> *TL;DR :* Sage can produce a symbolic expression :
>
>- that it can't evaluate numerically when correcly substiuted,
Yes, of course. I'm just too impatient for tasks like this. Here's the
ticket:
https://trac.sagemath.org/ticket/27576#ticket
Am Samstag, 30. März 2019 20:35:19 UTC+1 schrieb Nils Bruin:
>
> Type: defect
> (you can leave it major, unless you really feel it's minor)
> Component: Manifolds, but
Type: defect
(you can leave it major, unless you really feel it's minor)
Component: Manifolds, but that doesn't exist, so Geometry I guess
cc likely authors to speed things up (Copyright in the file suggests
Gourgoulhon and/or Scrimshaw )
post a link to the ticket here when you've filed. That
Oh yes, the chart is wrongly defined. It should be:
|sage: c_xy.=U.chart()|
||obviously. I copied it once, changed the variables, and copied it back
changing the variables again. Sorry.|
|
What are appropriate settings for a ticket regarding this issue? I'm a
ticket virgin.|
|
Am
On Saturday, March 30, 2019 at 7:39:51 AM UTC-7, YoungMath wrote:
>
> Or, maybe, a better approach would be a direct manipulation via resu._name
> and resu._latex_name.
>
> However, I'm not familiar with the procedure. Furthermore, is this mailing
> list right the place to discuss my written
On Saturday, March 30, 2019 at 2:56:59 AM UTC-7, Emmanuel Charpentier wrote:
>
> *TL;DR :* Sage can produce a symbolic expression :
>
>- that it can't evaluate numerically when correcly substiuted, AND
>- that can be evaluated when typed manually.
>
> The problem seems ti be bound to
My dear developers,
right now, I'm working on my master thesis and my task is to implement
characteristic classes (of the tangent bdl. of a manifold), such as the
A-genus, into Sage. The implementation shall be based
upon this
Or, maybe, a better approach would be a direct manipulation via resu._name
and resu._latex_name.
However, I'm not familiar with the procedure. Furthermore, is this mailing
list right the place to discuss my written code?
--
You received this message because you are subscribed to the Google
Hey folks,
I'm pretty new to this, so please be patient.
During my developement of an implementation of characteristic classes of
the tangent bdl of manifolds, I've encountered a problem when wedging
unnamed differential forms on non-parallelizable manifolds. Let's have an
example:
sage: S2 =
*TL;DR :* Sage can produce a symbolic expression :
- that it can't evaluate numerically when correcly substiuted, AND
- that can be evaluated when typed manually.
The problem seems ti be bound to absolute values.
That, IMHO, is a first-class bug...
*Demonstation :* I think that some
See https://trac.sagemath.org/ticket/27477
--
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
I've recently seen a couple of random doctest failures, see below.
Anyone some ideas?
File "src/sage/rings/number_field/number_field.py", line 1288, in
sage.rings.number_field.number_field.NumberField_generic
Failed example:
for chi in G:
D = ModularSymbols(chi, 2,
14 matches
Mail list logo
