-
-
Notifications
You must be signed in to change notification settings - Fork 596
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
polymake: Some properties are mapped as member functions #27841
Comments
Changed keywords from none to polymake, polytope |
comment:2
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). |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:5
Moving some tickets to 9.2. This is not a promise that I will be working on them. |
comment:7
Setting new milestone based on a cursory review of ticket status, priority, and last modification date. |
This looks similar to what had to be fixed for polymake 3.4 in #24905.
Other affected properties:
BOUNDED_VERTICES
,VISUAL
,LATTICE_POINTS
, ...CC: @jplab @dimpase
Component: packages: optional
Keywords: polymake, polytope
Issue created by migration from https://trac.sagemath.org/ticket/27841
The text was updated successfully, but these errors were encountered: