Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SymmetricGroup should accept libgap permutations #25622

Closed
videlec opened this issue Jun 20, 2018 · 2 comments
Closed

SymmetricGroup should accept libgap permutations #25622

videlec opened this issue Jun 20, 2018 · 2 comments

Comments

@videlec
Copy link
Contributor

videlec commented Jun 20, 2018

works with gap

sage: SymmetricGroup(3)(gap("(1,3)"))
(1,3)

fails with libgap

sage: SymmetricGroup(3)(libgap.eval("(1,3)"))
Traceback (most recent call last):
...
TypeError: 'sage.libs.gap.element.GapElement_Permutation' object is not iterable

Though we have

sage: libgap.eval("(1,3)").sage()
(1,3)
sage: parent(_)
Symmetric group of order 3! as a permutation group

Component: interfaces

Issue created by migration from https://trac.sagemath.org/ticket/25622

@videlec videlec added this to the sage-8.3 milestone Jun 20, 2018
@embray
Copy link
Contributor

embray commented Feb 16, 2021

comment:1

This is fixed by #31404, though this ticket should remain open until/unless that one is merged:

sage: SymmetricGroup(3)(libgap.eval("(1,3)"))                                                                                                                                                    
(1,3)
sage: parent(_)                                                                                                                                                                                  
Symmetric group of order 3! as a permutation group

@embray embray removed this from the sage-8.3 milestone Feb 16, 2021
@embray
Copy link
Contributor

embray commented Feb 16, 2021

comment:2

Actually this example is currently fixed in Sage, at least as far back as 9.1--I didn't check further. It was probably fixed by #18267.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants