-
-
Notifications
You must be signed in to change notification settings - Fork 514
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
Can't construct fraction field #5982
Comments
This comment has been minimized.
This comment has been minimized.
Attachment: sage+multi-polynomial-fraction-fields2.diff.gz Fix/workaround using Macaulay 2 |
comment:2
[with patch, needs review]
|
comment:4
Hi, M2 isn't a default part of Sage, so the doctest must be made optional. I also don't see a reason why this cannot be implemented via libSingular for example, but maybe I am overlooking things. You also posted a diff, so please check in the code and post an hg patch to properly preserve credit. And since you are not listed at http://trac.sagemath.org/sage_trac/wiki please add yourself there. Cheers, Michael |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:6
Hi Michael, Attached is a Mercurial bundle with the same patch plus the docstring modifications you requested. I'd like to write a native Sage implementation of this in the future but for now this works well enough for me. Regards, |
comment:7
Hi Juan, a patch would have been better, but someone can extra the changeset from the bundle and post the patch. One more thing: When you post an updated patch you need to change the summary to read "needs review" again. Cheers, Michael |
Attachment: trac_5982.patch.gz Attachment: trac_5982-ncalexan.patch.gz |
comment:8
|
Author: Nick Alexander |
comment:9
Would it be reasonable to have both versions of |
comment:10
I thought about doing exactly that, but if you're clever enough to know one is better than the other, aren't you clever enough to call |
comment:11
Hi Nick, Could you point me to the location of Singular's ideal primality testing algorithm? Thanks |
comment:12
Replying to @jmbr:
AFAICT, Singular does not have a toplevel isprime() (or ismaximal()) function. Reading some mailing list posts regarding Singular and Macaulay2, I believe both implement the same two algorithms for calculating the complete primary decomposition of an ideal. I don't understand enough to say definitively and I may be misusing the complete primary decomposition for testing primality. I was hoping that Martin Albrecht would review and clarify the situation. |
comment:13
The patch looks good to me, I didn't run doctests though. I can't really clarify the situation any more than what Nick wrote above. |
comment:14
As far as I can recall, Macaulay2 implements the Gianni-Trager-Zacharias algorithm for primality testing instead of relying on primary decomposition. Best regards |
comment:15
Positive review modulo fixing this one trivial change to a doctest:
|
comment:22
In 4.1.2, I get a number of failures arising from NotImplementedErrors in is_integral_domain. |
comment:24
Curiously, all tests in sage/rings and sage/schemes pass for me under sage 4.6.2.alpha1. I'm going to reinstate the "needs review", since I can't replicate mhansen's problem. We'll see if patchbot agrees :-) Apply trac_5982-ncalexan-with-check.patch, trac_5982-reviewer.patch |
comment:25
Patchbot seems to be happy with it, but a full ptestlong run on my 4.6.2.alpha1 build revealed a couple of failures: |
comment:26
Attachment: trac_5982_review2.patch.gz Why is this
part of the documentation of All tests pass with these patches on sage-4.6.2.alpha4. Patches fix the problem in the ticket description, and all changes look good. |
This comment has been minimized.
This comment has been minimized.
Changed reviewer from William Stein, Mike Hansen to William Stein, Mike Hansen, Marco Streng |
comment:27
Marco, did you forget to mark this as "positive review"? |
comment:28
Replying to @JohnCremona:
Actually, I was waiting for an answer to my question first, and then forgot all about the ticket. If I recall correctly, the question was not that important. |
comment:30
attachment: trac_5982-ncalexan-with-check.patch is not a proper |
proper hg changeset version of trac_5982-ncalexan-with-check.patch |
This comment has been minimized.
This comment has been minimized.
comment:31
Attachment: trac_5982-ncalexan-with-check2.patch.gz I made that patch into a proper hg changeset. All tests still pass, and as the new patch does exactly the same as the old one, I put it back to positive_review. (apply attachment: trac_5982-ncalexan-with-check2.patch, attachment: trac_5982-reviewer.patch, attachment: trac_5982_review2.patch) |
Attachment: patches.diff.gz the difference between trac_5982-ncalexan-with-check.patch and trac_5982-ncalexan-with-check2.patch |
comment:32
(apply trac_5982-ncalexan-with-check2.patch, trac_5982-reviewer.patch, trac_5982_review2.patch) |
comment:33
(apply trac_5982-ncalexan-with-check2.patch, trac_5982-reviewer.patch, trac_5982_review2.patch ) |
Merged: sage-4.7.1.alpha0 |
Apply
attachment: trac_5982-ncalexan-with-check2.patch
attachment: trac_5982-reviewer.patch
attachment: trac_5982_review2.patch
CC: @malb
Component: algebra
Author: Nick Alexander, Juan M. Bello Rivas
Reviewer: William Stein, Mike Hansen, Marco Streng
Merged: sage-4.7.1.alpha0
Issue created by migration from https://trac.sagemath.org/ticket/5982
The text was updated successfully, but these errors were encountered: