-
-
Notifications
You must be signed in to change notification settings - Fork 552
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
Bring Doctest coverage for element_ext_pari.py to 100% #12261
Comments
Author: David Roe |
comment:1
Attachment: 12261.patch.gz |
Reviewer: Karl-Dieter Crisman |
comment:2
I'm finding it hard to find any problems with this that aren't nearly trivial. Comments that may or may not warrant addressing:
and testing seems fine.
Let me know what you want to deal with on a refresh (probably at least the typos) and otherwise this should go in. |
Attachment: 12261.2.patch.gz Apply this patch only |
comment:3
Sorry: I should have made a reviewer patch rather than a whole new one. But I'd already qrefreshed... |
Work Issues: commit message, PARI (maybe?) |
comment:4
That's ok. Patch is fine. I don't feel comfortable giving final positive review because of the Also (less crucially) now I realize that I think the folks in Bordeaux really want PARI and not Pari... I just don't know, and hate all that stuff, but it's probably important to them. Jeroen probably also won't accept this due to the commit "message". I'm really sorry... I know from experience how much work doctest upgrades end up taking when you think they will be a 5-minute job. |
Most recent update |
comment:5
Attachment: 12261.3.patch.gz No problem. I'm not convinced that we need to worry about the I also updated the commit message and changed Pari to PARI. |
comment:6
As I suspected, changing
I don't mind you removing that function! I just don't know what it does or why it can now be removed - actually, upon reading it, it does make sense. If someone else (e.g., robertwb) can verify that the same functionality of checking that two such elements come from the same finite field is in Sage, I am very happy with reducing our doctest needs by removing that. |
Changed work issues from commit message, PARI (maybe?) to raise!=Raise |
Even more recent update. It would be nice to be able to delete patches.... |
comment:7
Attachment: 12261.4.patch.gz Oops. Command C on a Mac capitalizes things; that was not intentional. I've removed Apply 12261.4.patch only. |
Changed reviewer from Karl-Dieter Crisman to Karl-Dieter Crisman, Aly Deines |
Changed work issues from raise!=Raise to none |
Merged: sage-5.0.beta3 |
Part of metaticket #12024
CC: @robertwb
Component: doctest coverage
Author: David Roe
Reviewer: Karl-Dieter Crisman, Aly Deines
Merged: sage-5.0.beta3
Issue created by migration from https://trac.sagemath.org/ticket/12261
The text was updated successfully, but these errors were encountered: