Opened 5 years ago
Closed 4 years ago
#19367 closed defect (wontfix)
Deal with (new?) Maxima error message
Reported by: | kcrisman | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | sage-duplicate/invalid/wontfix |
Component: | interfaces | Keywords: | |
Cc: | Merged in: | ||
Authors: | Reviewers: | ||
Report Upstream: | N/A | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description
Apparently, we have
vertices = [(1,1,-1,-1,-1),(-1,-1,1,1,-1),(1,-1,-1,-1,1),(-1,1,1,1,1),(1,-1,1,-1,-1)] p = LatticePolytope(vertices) print p.vertices_pc() print lattice_polytope.positive_integer_relations(p.vertices_pc().column_matrix()) TypeError: unable to make sense of Maxima expression '"Problemnotfeasible!"' in Sage
as reported here. We should deal with this error message more appropriately.
Change History (5)
comment:1 Changed 5 years ago by
comment:2 Changed 5 years ago by
- Milestone changed from sage-6.9 to sage-duplicate/invalid/wontfix
- Status changed from new to needs_review
I move that this should be closed because it was for a specific Maxima call which is no longer used.
comment:3 Changed 5 years ago by
- Status changed from needs_review to needs_info
I dunno. I think it might still be useful to keep open; unless this really is the ONLY place in Maxima we could conceivably see this coming up. I would hate for it to bite us some other place in the future - e.g. by using maxima_commands()
or whatever it's called.
comment:4 Changed 5 years ago by
- Status changed from needs_info to positive_review
This method no longer uses Maxima after #20766. So it's time to close this one.
comment:5 Changed 4 years ago by
- Resolution set to wontfix
- Status changed from positive_review to closed
Determined to be invalid/duplicate/wontfix (closing as "wontfix" as a catch-all resolution).
See also #19365, which is about the actual bug itself (presumably in Maxima).