sage.groups.matrix_gps: Modularization fixes for imports#35306
sage.groups.matrix_gps: Modularization fixes for imports#35306vbraun merged 24 commits intosagemath:developfrom
sage.groups.matrix_gps: Modularization fixes for imports#35306Conversation
…___all_for_namespace_packages' into matrix_groups_modularization
…te ..._gap module
…nitefield' into matrix_groups_modularization
…ce of is_MatrixGroup, is_ArithmeticSubgroup
… back to _generic
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## develop #35306 +/- ##
===========================================
- Coverage 88.62% 88.61% -0.02%
===========================================
Files 2148 2155 +7
Lines 398855 398915 +60
===========================================
+ Hits 353480 353484 +4
- Misses 45375 45431 +56
... and 28 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
SageMath version 10.0.beta7, Release Date: 2023-04-01
…ite_rings' when GF is involved, add '# optional - sage.symbolic'
SageMath version 10.0.beta8, Release Date: 2023-04-06
|
Looks good in the first pass. Would you put the boilerplate things like copyright notices in the new files? |
…lame -M -C -w --date=format:%Y FILE.py | sort -k2'
|
Done. |
…sed on 'git blame -M -C -w --date=format:%Y FILE.py | sort -k2'
|
Documentation preview for this PR is ready! 🎉 |
|
Thank you! |
|
I'm getting a test failure on Arch with system GAP 4.12.2 after this Strangely, the exact same test passed when it was in |
|
To examine the failure, I tried to run Next I tried to run What did I wrong? I have zero experience in testing sage on linux platforms, by the way. |
|
It's probably a bug in tox file. Anyway, you can just run archlinux in Docker, and build Sage there the usual way. |
|
Yes. This is a good opportunity for me to try sage on linux. |
|
After some more testing, it seems to be the line which triggers this. It is somehow interfering with the random generator status of GAP. was marked as |
|
tagging everything (this is both for pexpect and libgap interfaces - probably just one of these is needed) |
That's done in the |
|
Things get weirder, it depends on the order in which P and Psmaller are defined: vs |
|
How about replacing the iffy test with |
|
I finally figured out why this happens only when using system gap: the difference is the |

📚 Description
We move the
...MatrixGroup_gapclasses to separate modules named..._gap.This is part of:
📝 Checklist
⌛ Dependencies
is_FiniteFieldetc., makesage.rings.finite_ringsa namespace package #35119