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

update gap_reset_workspace() and gap_packages #22244

Closed
dimpase opened this issue Jan 24, 2017 · 7 comments
Closed

update gap_reset_workspace() and gap_packages #22244

dimpase opened this issue Jan 24, 2017 · 7 comments

Comments

@dimpase
Copy link
Member

dimpase commented Jan 24, 2017

We ship some obsolete GAP packages, and should ship many more (with very small extra effort).

In view of this, also gap_reset_workspace() will need an update.

Depends on #20914

Component: packages: optional

Reviewer: Jeroen Demeyer

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

@dimpase dimpase added this to the sage-7.6 milestone Jan 24, 2017
@dimpase
Copy link
Member Author

dimpase commented Jan 24, 2017

comment:1

Also, one needs to review the call to gap_reset_workspace() in spkg-install of database_gap.

@tscrim
Copy link
Collaborator

tscrim commented Jan 24, 2017

comment:2

QuaGroup and hecke are two I would like to see added.

@dimpase
Copy link
Member Author

dimpase commented Jan 25, 2017

comment:3

another request is to replace obsolete braid by mapclass - it provides the same functionality, and more.

@tscrim
Copy link
Collaborator

tscrim commented Mar 14, 2017

comment:4

#22190 is for replacing braid by mapclass.

@jdemeyer
Copy link

jdemeyer commented Jul 5, 2017

comment:5

I guess this can be closed as duplicate of #13426.

@jdemeyer jdemeyer removed this from the sage-7.6 milestone Jul 5, 2017
@jdemeyer
Copy link

jdemeyer commented Jul 5, 2017

Reviewer: Jeroen Demeyer

@embray
Copy link
Contributor

embray commented Jul 13, 2017

comment:7

Closing tickets in the sage-duplicate/invalid/wontfix module with positive_review (i.e. someone has confirmed they should be closed).

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

4 participants