Opened 7 years ago
Last modified 18 months ago
#18343 needs_review defect
creation of libgap integers are slow (if not buggy)
Reported by: | vdelecroix | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | sage-duplicate/invalid/wontfix |
Component: | packages: standard | Keywords: | |
Cc: | Merged in: | ||
Authors: | Reviewers: | ||
Report Upstream: | N/A | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description
- Creating libGAP integers from python int is broken
sage: libgap(2r**61r) ... OverflowError: value too large to convert to int
This is due to a cast to a C<int>
insage.libs.gap.*
(Python integers do not necessarily fit into anint
(though they do in a long)).
- Creating libGAP integers from Sage integers is very slow since it goes through the string representation! As GAP internally uses mpz it could be very fast.
Change History (1)
comment:1 Changed 18 months ago by
- Milestone changed from sage-6.7 to sage-duplicate/invalid/wontfix
- Status changed from new to needs_review
Note: See
TracTickets for help on using
tickets.
This would be fixed by #31404. Of course, this ticket should still be kept open until/unless that one is merged.