-
-
Notifications
You must be signed in to change notification settings - Fork 481
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
convert all of Sage library code to libgap #26902
Comments
This comment has been minimized.
This comment has been minimized.
comment:2
Retarging tickets optimistically to the next milestone. If you are responsible for this ticket (either its reporter or owner) and don't believe you are likely to complete this ticket before the next release (8.7) please retarget this ticket's milestone to sage-pending or sage-wishlist. |
This comment has been minimized.
This comment has been minimized.
comment:4
Ticket retargeted after milestone closed (if you don't believe this ticket is appropriate for the Sage 8.8 release please retarget manually) |
comment:5
As the Sage-8.8 release milestone is pending, we should delete the sage-8.8 milestone for tickets that are not actively being worked on or that still require significant work to move forward. If you feel that this ticket should be included in the next Sage release at the soonest please set its milestone to the next release milestone (sage-8.9). |
Changed keywords from none to gap libgap |
This comment has been minimized.
This comment has been minimized.
comment:7
see #25477 for a long discussion on performance of GAP vs Cython.
In particular, even |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
this is just a 1-line change. A part of sagemath#26902 URL: https://trac.sagemath.org/34769 Reported by: dimpase Ticket author(s): Dima Pasechnik Reviewer(s): John Palmieri
…bgap in sage/rings/finite_rings implement coercion from libgap's finite fields, to fix e.g. {{{ sage: F=GF(25) sage: F(libgap.Z(25)^3) ------------------------------------------------------------------------ --- TypeError Traceback (most recent call last) ... TypeError: unable to coerce <class 'sage.libs.gap.element.GapElement_FiniteField'> }}} With the ticket branch, this works: {{{ sage: F=GF(25) sage: F(libgap.Z(25)^3) 4*z2 + 3 }}} ------------------------------------ As well, we switch to use libgap instead of pexpect GAP - internally in the affected files. This is a part of sagemath#26902 URL: https://trac.sagemath.org/34770 Reported by: dimpase Ticket author(s): Dima Pasechnik Reviewer(s): Matthias Koeppe
after sagemath#34737 there are still uses of pexpect GAP left there. We remove them on this ticket. Part of sagemath#26902 URL: https://trac.sagemath.org/34771 Reported by: dimpase Ticket author(s): Dima Pasechnik Reviewer(s): Vincent Delecroix, Matthias Koeppe
It's about time. The sooner this is done, the fewer code to cross pexpect gap/libgap boundary will have to be written.
Some completed tickets aiming at this: #26750, #26889, #27234, #28504, #28818, #28820, #34769, #34770, #34737, #34771
Also related:
#27923, #27911, #27878
Following completion of this work, we can look into formally deprecating the pexpect interface to GAP: #26963.
Component: interfaces
Keywords: gap libgap
Issue created by migration from https://trac.sagemath.org/ticket/26902
The text was updated successfully, but these errors were encountered: