#13849: deprecate degrevlex when using PolyBoRi
---------------------------------------+------------------------------------
Reporter: malb | Owner: malb
Type: enhancement | Status: new
Priority: major | Milestone: sage-5.6
Component: commutative algebra | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
---------------------------------------+------------------------------------
Comment (by AlexanderDreyer):
Replying to [comment:3 malb]:
> Hi Alexander, so your vote is to attempt to fix it instead of dropping
it?
Well, that had been my idea. #13202 should have fixed these issues, but I
did not think about multi_polynomial_sequence.py. Of course, one could
fix it here (by intraoducing a function to pboriy.pyx that wraps and
dewraps `DegRevLex`). But that would only fix this special issue. But
since a user could call polybori's functions manually, I must admit that
is not really a solution.
The correct solution would be to split pbori.pyx into polybori-interface
(just reimplemention our upstream boost.python-based interface) and the
implementation of `BooleanPolynomial`, `BooleanPolynomialRing`, etc.
But I guess we won't find the time for this on short notice. (It might me
a good idea, if we switch to cython upstream. This might be happen, but
also not on short notice.)
So, -langerredekurzersinn- finally removing `DegRevLex` seem to be the
best feasible way.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13849#comment:4>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
