-
-
Notifications
You must be signed in to change notification settings - Fork 482
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
BooleanMonomial 1 is not equal to Integer(1) #27019
Comments
comment:1
Part of the problem is that So there cannot be a coercion from |
comment:2
Retarging tickets optimistically to the next milestone. If you are responsible for this ticket (either its reporter or owner) and don't believe you are likely to complete this ticket before the next release (8.7) please retarget this ticket's milestone to sage-pending or sage-wishlist. |
comment:3
Ticket retargeted after milestone closed (if you don't believe this ticket is appropriate for the Sage 8.8 release please retarget manually) |
comment:4
As the Sage-8.8 release milestone is pending, we should delete the sage-8.8 milestone for tickets that are not actively being worked on or that still require significant work to move forward. If you feel that this ticket should be included in the next Sage release at the soonest please set its milestone to the next release milestone (sage-8.9). |
Demonstration:
Note that this behavior is inconsistent with the behavior for polynomial rings over finite fields:
In the context of converting polynomials to lists, this has understandably caused confusion for at least one user on Ask SageMath.
Component: algebra
Keywords: BooleanMonomial, monomial, equality
Issue created by migration from https://trac.sagemath.org/ticket/27019
The text was updated successfully, but these errors were encountered: