-
-
Notifications
You must be signed in to change notification settings - Fork 491
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
Feature for sage.rings.padics #32881
Comments
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
|
Commit: |
Author: Matthias Koeppe |
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
|
comment:5
Merged updated #32174 |
comment:9
Copy pasting the command allowing to test the modified files here:
|
comment:10
Looks good, I get this:
Note that |
Reviewer: Sébastien Labbé |
comment:11
Patchbot is fine (only an irrelevant warning with respect to startup time). |
comment:12
Thank you and happy new year! |
comment:13
Happy new year to you to! I will continue to review few of your tickets for the year to come, slowly but surely. |
Changed branch from u/mkoeppe/feature_for_sage_rings_padics to |
We introduce a feature for the presence of
sage.rings.padics
(not included, for example in https://pypi.org/project/sagemath-polyhedra/ (#32432).We then mark some doctests in
sage.structure
andsage.misc
as# optional - sage.rings.padics
.Depends on #32174
CC: @saraedum @kwankyu @seblabbe
Component: refactoring
Author: Matthias Koeppe
Branch/Commit:
439db4b
Reviewer: Sébastien Labbé
Issue created by migration from https://trac.sagemath.org/ticket/32881
The text was updated successfully, but these errors were encountered: