-
-
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
Create a variant of the polymake interface using polymake's callable library (polymake::Main) via JuPyMake #22704
Comments
Dependencies: #22452 |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Branch: public/22704 |
comment:5
Here's a first version. Last 10 new commits:
|
This comment has been minimized.
This comment has been minimized.
Commit: |
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:10
Some polymake errors are not properly signalled by Polymake: Only the stderr slot [2] is filled but the error slot [3] is empty
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:47
OK, this is fixed by #27805 indeed. New commits:
|
Reviewer: Dima Pasechnik |
comment:48
I've put the remaining minor issue to a follow-up ticket, #27807 (Polymake-jupymake interface: Fix polymake's error handling in Shell::Mock) |
This comment has been minimized.
This comment has been minimized.
comment:49
Should I make that last failing doctest less specific regarding the error message for this ticket? (Before it's fixed fully in #27807) |
comment:50
If you like, you can tag it "known error". |
Branch pushed to git repo; I updated commit sha1 and set ticket back to needs_review. New commits:
|
comment:53
Merge conflict |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Changed branch from public/22704 to |
comment:57
The upstream package jupymake seems to be missing on the sage mirrors |
Changed commit from |
comment:58
Do I understand correctly that in the current version jupymake is necessary for polymake to function properly? Shouldn't jupymake become a dependancy of polymake? |
comment:59
Replying to @jplab:
No, there are two interface classes, which both work. |
Following up on #22452 (Create a Polymake pexpect interface):
As suggested by Gawrilow in https://forum.polymake.org/viewtopic.php?f=8&t=544, we could create a variant of the polymake pexpect interface that does not go through pty's but rather replaces the relevant send/receive methods of pexpect by calls to
simulate_shell_input
(linking to libpolymake).Recent polymake versions have developed this further and now provide a class
polymake::Main
with convenient access to the polymake interpreter. We use the (partial) Python bindings for this, https://github.com/polymake/JuPyMake which are used for Polymake's jupyter.Upstream package:
We do want to keep the current pty-based pexpect interface, though, because it may be handy for running polymake on a remote server; or for guarding against a crashing polymake (sigh).
Remaining issue: #27807
See also: #22710: Meta-ticket: polymake
Depends on #24905
Upstream: Reported upstream. No feedback yet.
CC: @simon-king-jena @jplab @sophiasage @LaisRast @kliem @sebasguts @videlec @tscrim
Component: interfaces
Keywords: days84
Author: Matthias Koeppe
Branch:
8d9e2c2
Reviewer: Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/22704
The text was updated successfully, but these errors were encountered: