Calling ...simplify_trig() results in a traceback, somewhat elided here:
Traceback (most recent call last):
File
"/home/rllozes/Development/sage/local/lib/python2.7/site-packages/sage/manifolds/differentiable/metric.py",
line 692, in inverse
self._inverse._restrictions[dom] =
You do have some flexibility on how you want to implement actions. Some of
this might be more complicated due to the classes you are inheriting from,
including some older code. The easier (but can be more cumbersome and
restrictive) way is to implement either _rmul_ / _lmul_ or _acted_upon_
On Saturday, November 25, 2017 at 6:42:03 PM UTC+9, Simon Brandhorst wrote:
>
>
> However, that file was created in 2007, and it is almost not documented at
> all.
> Is it the way to go anyways?
>
This is a usual motivation that a sager contributes back to Sage
development. If you see some
Dear sagers,
I am implementing a matrix group action on a submodule of ZZ^n.
element*matrix does work but the result lies in the ambient space and
instead I want the
elements parent to be the invariant subspace we started with.
This can be done with sage.categories.action.Action
However, that
