Opened 2 years ago
Last modified 5 weeks ago
#28421 new enhancement
Fix weighted term order construction
Reported by: | bruno | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | sage-9.6 |
Component: | algebra | Keywords: | |
Cc: | Merged in: | ||
Authors: | Bruno Grenet | Reviewers: | |
Report Upstream: | N/A | Work issues: | |
Branch: | weighted_term_orders | Commit: | |
Dependencies: | Stopgaps: |
Description
Currently, weighted term orders that are not given a tuple or a list as parameter behave strangely (and this causes confusion, cf on Ask¹):
sage: t = TermOrder('wdegrevlex', 2) sage: t Weighted degree reverse lexicographic term order sage: t.is_weighted_degree_order() False sage: P.<x> = PolynomialRing(QQ, 1, order=t) sage: x.degree() 1
In this ticket, we change the behavior as follows:
sage: t = TermOrder('wdegrevlex', 2) sage: t Weighted degree reverse lexicographic term order with weights (2,) sage: t.is_weighted_degree_order() True sage: P.<x> = PolynomialRing(QQ, 1, order=t) sage: x.degree() 2
Note: Another possibility is to raise an Exception when an integer is given rather than a tuple/list. I think the proposed solution is more useful to the users.
¹ The Ask question uncovers two distinct problems, the second one is fixed in #28420.
Change History (6)
comment:1 Changed 2 years ago by
- Milestone changed from sage-8.9 to sage-9.1
comment:2 Changed 21 months ago by
- Milestone changed from sage-9.1 to sage-9.2
Moving tickets to milestone sage-9.2 based on a review of last modification date, branch status, and severity.
comment:3 Changed 15 months ago by
- Milestone changed from sage-9.2 to sage-9.3
comment:4 Changed 9 months ago by
- Milestone changed from sage-9.3 to sage-9.4
comment:5 Changed 5 months ago by
- Milestone changed from sage-9.4 to sage-9.5
comment:6 Changed 5 weeks ago by
- Milestone changed from sage-9.5 to sage-9.6
Note: See
TracTickets for help on using
tickets.
Ticket retargeted after milestone closed