Skip to content
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: Better syntax to call functions with <template arguments> #27861

Open
mkoeppe opened this issue May 23, 2019 · 5 comments
Open

Polymake: Better syntax to call functions with <template arguments> #27861

mkoeppe opened this issue May 23, 2019 · 5 comments

Comments

@mkoeppe
Copy link
Contributor

mkoeppe commented May 23, 2019

Currently we have to write:

sage: polymake("tropical::uniform_linear_space<Max>(3,2)")

or

sage: getattr(polymake, "tropical::uniform_linear_space<Max>")(3, 2)

or

sage: polymake.function_call("tropical::uniform_linear_space<Max>", [3, 2])

because the template brackets cannot become part of the Python function name, so the normal . syntax cannot work.

(Also, but not the point of this ticket - #27736: Polymake: Turn polymake applications into objects with directories.)

Also,

    polymake("tropical::uniform_linear_space<Max>")(3,2)

does not work. It looks for an overloaded function without arguments, which fails:

    TypeError: no matching overloaded instance of Polymake::tropical::uniform_linear_space<Max>()

Also,

sage: polymake.call("tropical::uniform_linear_space<Max>", 3, 2)

does not work -- the undocumented and untested call method passes the args tuple to function_call, which expects lists instead of tuples.

CC: @simon-king-jena @jplab @dimpase

Component: packages: experimental

Issue created by migration from https://trac.sagemath.org/ticket/27861

@embray
Copy link
Contributor

embray commented Jun 14, 2019

comment:1

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

@embray embray removed this from the sage-8.8 milestone Jun 14, 2019
@mkoeppe

This comment has been minimized.

@mkoeppe

This comment has been minimized.

@mkoeppe
Copy link
Contributor Author

mkoeppe commented May 1, 2020

comment:4

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

@mkoeppe mkoeppe added this to the sage-9.2 milestone May 1, 2020
@mkoeppe mkoeppe modified the milestones: sage-9.2, sage-9.3 Aug 29, 2020
@mkoeppe
Copy link
Contributor Author

mkoeppe commented Feb 13, 2021

comment:6

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

@mkoeppe mkoeppe modified the milestones: sage-9.3, sage-9.4 Feb 13, 2021
@mkoeppe mkoeppe modified the milestones: sage-9.4, sage-9.5 Jul 19, 2021
@mkoeppe mkoeppe modified the milestones: sage-9.5, sage-9.6 Dec 14, 2021
@mkoeppe mkoeppe modified the milestones: sage-9.6, sage-9.7 Mar 5, 2022
@mkoeppe mkoeppe modified the milestones: sage-9.7, sage-9.8 Aug 6, 2022
@mkoeppe mkoeppe modified the milestones: sage-9.8, sage-9.9 Jan 7, 2023
@mkoeppe mkoeppe removed this from the sage-10.0 milestone Mar 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants