Create a variant of the polymake interface using polymake's callable library (polymake::Main) via JuPyMake

[mkoeppe]

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:

  wget -P upstream https://files.pythonhosted.org/packages/32/dd/0a48546daa2461e57207d31eeb64a3ad77fd9fb339d90e1e067ea25991a5/JuPyMake-0.9.tar.gz

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

[mkoeppe]

Dependencies: #22452

[mkoeppe]

Description changed:

--- 
+++ 
@@ -1,3 +1,8 @@
+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).
 
 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). 
+
+See also: #22710: Meta-ticket: polymake
+

[mkoeppe]

Description changed:

--- 
+++ 
@@ -1,6 +1,8 @@
 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).
+
+https://github.com/sebasguts/JuPyMake - has Python bindings for something like this, it seems.
 
 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). 
 

[mkoeppe]

Changed dependencies from #22452 to #22452, #26333

[mkoeppe]

Branch: public/22704

[mkoeppe]

comment:5

Here's a first version.

---

Last 10 new commits:

7018013	polymake doctest: Mark a doctest random that depends on installed packages
78c10fb	Polymake._tab_completion: Fix for new apropos format in Polymake 3.4
1699019	Doctest fix for polymake 3.4: false/true instead of 0/1
f595909	Doctest fix for polymake 3.4: Use different function from the tropical application
76701f6	Doctest fix for polymake 3.4: Differences in available properties
83b51de	Polymake 3.4: Fix for typeof small objects
8510124	Polymake: Remove copy/paste error handling for code that cannot raise
3c6ae95	polymake: Make normaliz a dependency
b6eeaa1	polymake: Add a patch to polymake's libnormaliz configure
2f855b0	Refactor interface Polymake through PolymakeAbstract, add PolymakeJuPyMake

[mkoeppe]

Description changed:

--- 
+++ 
@@ -1,8 +1,12 @@
 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).
+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). We use the Python bindings for this, https://github.com/sebasguts/JuPyMake which are used for Polymake's jupyter.
 
-https://github.com/sebasguts/JuPyMake - has Python bindings for something like this, it seems.
+Prerequisite:
+
+```
+sage -pip install JuPyMake
+```
 
 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). 
 

[mkoeppe]

Commit: 2f855b0

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

78b5036

More doctests etc.

[sagetrac-git]

Changed commit from 2f855b0 to 78b5036

[mkoeppe]

Description changed:

--- 
+++ 
@@ -1,6 +1,6 @@
 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). We use the Python bindings for this, https://github.com/sebasguts/JuPyMake which are used for Polymake's jupyter.
+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). We use the Python bindings for this, https://github.com/polymake/JuPyMake which are used for Polymake's jupyter.
 
 Prerequisite:
 

[mkoeppe]

Description changed:

--- 
+++ 
@@ -2,10 +2,10 @@
 
 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). We use the Python bindings for this, https://github.com/polymake/JuPyMake which are used for Polymake's jupyter.
 
-Prerequisite:
+Upstream package:
 
 ```
-sage -pip install JuPyMake
+  wget -P upstream https://files.pythonhosted.org/packages/a2/20/df07a05d2b56f8a901e9eda147574a7c6f58137efbf65ba87ba749225eb0/JuPyMake-0.8.tar.gz
 ```
 
 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). 

[sagetrac-git]

Changed commit from 78b5036 to 92274e0

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

92274e0

Add package jupymake

[mkoeppe]

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

sage: from JuPyMake import ExecuteCommand
sage: ExecuteCommand('help("Triangulation");')
(True, '', "polymake:  ERROR: unknown help topic 'Triangulation'\n", '')