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

libgap can not use gap packages #23853

Closed
videlec opened this issue Sep 14, 2017 · 2 comments
Closed

libgap can not use gap packages #23853

videlec opened this issue Sep 14, 2017 · 2 comments

Comments

@videlec
Copy link
Contributor

videlec commented Sep 14, 2017

With gap pexpect interface

sage: gap.LoadPackage('"cryst"')
true
sage: gap.SpaceGroupIT(2,14)
SpaceGroupOnRightIT(2,14,'1')

With libgap

sage: libgap.LoadPackage("cryst")
true
sage: libgap.SpaceGroupIT(2,14)
Traceback (most recent call last):
...
AttributeError: No such attribute: SpaceGroupIT.

As noticed in #23854, there is the following work around

sage: libgap.eval('SpaceGroupIT')(2,14)
SpaceGroupOnRightIT(2,14,'1')

Component: interfaces

Keywords: thursdaysbdx

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

@videlec videlec added this to the sage-8.1 milestone Sep 14, 2017
@videlec

This comment has been minimized.

@embray embray removed this from the sage-8.1 milestone Feb 16, 2021
@embray embray added the pending label Feb 16, 2021
@embray
Copy link
Contributor

embray commented Feb 16, 2021

comment:3

This is fixed since some time ago. You could use any package to demonstrate, but I installed the cryst package to demonstrate the same example:

sage: libgap.load_package('cryst')                                                                                                                                                               
true
sage: libgap.SpaceGroupIT(2,14)                                                                                                                                                                  
SpaceGroupOnRightIT(2,14,'1')

This was likely fixed by #27911.

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