Why _r_action_ and _l_action_ methods still in the reference manual?

[Kwankyu Lee]

Hi

I noticed that the coercion section of the sage reference manual mentions _r_action_ and _l_action methods instead of _act_on_ and _acted_upon_ methods, while it seems that the former methods were replaced with the latter methods 10 years ago in #5597!

Am I right? Then this is quite surprising.

[Dima Pasechnik]

quick grepping through src/sage/ shows that _r_action_ is never
defined/used (only mentioned in commented out code
or in messages), and _l_action is defined exactly once, in
src/sage/rings/multi_power_series_ring_element.py
and only used there, once.

So none of this is understood by any coersion/etc frameworks.

A documentation bug, I suppose (and probably a bug in
src/sage/rings/multi_power_series_ring_element.py, which uses
wrongly named stuff...)

I've opened https://trac.sagemath.org/ticket/27989 to deal with it.

Dima



>
> --
> 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+...@googlegroups.com.
> To post to this group, send email to sage-...@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/66a6a4c4-df4f-4cd4-9856-c582719c993d%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Kwankyu Lee]

On Friday, June 14, 2019 at 8:16:58 PM UTC+9, Dima Pasechnik wrote:

On Fri, Jun 14, 2019 at 12:04 PM Kwankyu Lee <ekwa...@gmail.com> wrote:
>
> Hi
>
> I noticed that the coercion section of the sage reference manual mentions _r_action_ and _l_action methods instead of _act_on_ and _acted_upon_ methods, while it seems that the former methods were replaced with the latter methods 10 years ago in #5597!
>
> Am I right? Then this is quite surprising.

quick grepping through src/sage/ shows that  _r_action_ is never
defined/used (only mentioned in commented out code
or in messages), and  _l_action is defined exactly once, in
src/sage/rings/multi_power_series_ring_element.py
and only used there, once.

So none of this is understood by any coersion/etc frameworks.

A documentation bug, I suppose (and probably a bug in
src/sage/rings/multi_power_series_ring_element.py, which uses
wrongly named stuff...)

I agree.

 

I've opened https://trac.sagemath.org/ticket/27989 to deal with it.

Thank you.