On Thursday, April 21, 2022 at 2:28:06 PM UTC-7 hohoa...@gmail.com wrote:
> 1/- Why "Copy" was used instead of "Refactor"? There
> are of course good reasons for this, it is believed.
> 2/- What "deserves to be factored out at some point in the future"? The
> "resolvelinks" function or the
On Mon, May 2, 2022 at 11:24 AM 'Martin R' via sage-devel
wrote:
>
> I am actually not sure anymore, which methods or functionality this class
> should provide.
>
> Would it possibly be better to enhance PermutationGroup with an additional
> optional "from_action" and "from_cyclic_action"
I am actually not sure anymore, which methods or functionality this class
should provide.
Would it possibly be better to enhance PermutationGroup with an additional
optional "from_action" and "from_cyclic_action" argument? Eg.:
PermutationGroup(domain = X, cyclic_action = lambda x: f(x))
On Sunday, May 1, 2022 at 7:32:01 PM UTC-4 Travis Scrimshaw wrote:
> Sorry, I don't know an easy way. I've always just defined them by hand
>>> whenever needed.
>>> However, I agree with you that a better way is needed.
>>>
>>
>> I would love for there to be some standard way to define a
1) This is okay with me, but by "set" I assume you don't mean "Set":-)
For example,
sage: A = lambda g, x: g*x
sage: G = SL(2,5)
sage: X = GF(5)^2
sage: a = GroupAction(A, X, G)
sage: a.orbits()
should return something reasonable.
2) Your new class should be consistent with the built in action
of
Would you be happy with something like the following, as a unifying and
easily accessible framework? Of course, I am thinking of providing also
methods that convert it (back) into a representation, a combinatorial
species, a permutation group.
class FiniteGroupAction(SageObject):
def
