-
-
Notifications
You must be signed in to change notification settings - Fork 572
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
sage.modules.fg_pid.fgp_module: Rename a test_... function to _test_... (with deprecation) #33617
Comments
This comment has been minimized.
This comment has been minimized.
Commit: |
Author: Matthias Koeppe |
comment:4
For this one, I think we should move this to a method of the corresponding morphism class so we can test it on instances by -sage: set_random_seed(s); v = [fgp.test_morphism_0(1) for _ in range(30)]
+sage: set_random_seed(s)
+sage: for _ in range(30):
+....: phi = random_fgp_morphism_m(1)
+....: phi.test_morphism_0() This would also mean a bit other internal changes to the method, but then it can be applied more broadly. It would also be good to have a better name for this test too. Maybe |
Changed author from Matthias Koeppe to Tobias Diez, Matthias Koeppe |
comment:8
Looks okay to me, but what about tscrim's comment:4? |
comment:9
No idea what these tests do, which is why I cc'ed original authors... |
Reviewer: John Palmieri |
comment:10
I think we should merge this now and do the restructuring later. |
comment:11
Thanks! |
(split out from #33549, similar to #33612)
In this way we suppress generating the documentation of this undocumented function. https://doc.sagemath.org/html/en/reference/modules/sage/modules/fg_pid/fgp_module.html#sage.modules.fg_pid.fgp_module.test_morphism_0
While at it, we improve the markup of the documentation.
CC: @tscrim @tobiasdiez @simonbrandhorst @jhpalmieri
Component: documentation
Author: Tobias Diez, Matthias Koeppe
Branch/Commit:
66594c2
Reviewer: John Palmieri
Issue created by migration from https://trac.sagemath.org/ticket/33617
The text was updated successfully, but these errors were encountered: