Opened 2 years ago

Last modified 4 months ago

#27841 new defect

polymake: Some properties are mapped as member functions

Reported by: mkoeppe Owned by:
Priority: major Milestone: sage-9.4
Component: packages: optional Keywords: polymake, polytope
Cc: jipilab, dimpase Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description (last modified by mkoeppe)

This looks similar to what had to be fixed for polymake 3.4 in #24905.

sage: p = polymake.rand_sphere(3,20)
sage: g = p.GRAPH
sage: g
sage: g.N_NODES
Member function 'N_NODES' of Polymake::polytope::Polytope__Rational::_prop_GRAPH object  ### should have given: 20
sage: g.N_NODES()

Other affected properties: BOUNDED_VERTICES, VISUAL, LATTICE_POINTS, ...

Change History (7)

comment:1 Changed 2 years ago by jipilab

  • Keywords polymake polytope added

comment:2 Changed 2 years ago by embray

  • Milestone sage-8.8 deleted

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).

comment:3 Changed 23 months ago by mkoeppe

  • Description modified (diff)

comment:4 Changed 23 months ago by mkoeppe

  • Description modified (diff)

comment:5 Changed 14 months ago by mkoeppe

  • Milestone set to sage-9.2

Moving some tickets to 9.2. This is not a promise that I will be working on them.

comment:6 Changed 10 months ago by mkoeppe

  • Milestone changed from sage-9.2 to sage-9.3

comment:7 Changed 4 months ago by mkoeppe

  • Milestone changed from sage-9.3 to sage-9.4

Setting new milestone based on a cursory review of ticket status, priority, and last modification date.

Note: See TracTickets for help on using tickets.