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

Upgrade Polymake; install pypolymake; install Polymake kernel for Jupyter #905

Open
williamstein opened this issue Sep 15, 2016 · 10 comments

Comments

@williamstein
Copy link
Contributor

https://github.com/videlec/pypolymake/

Requested by: Marc Masdeu

@haraldschilly
Copy link
Contributor

I've added build instructions to install it into the sagemath 7.3 environment. This of course doesn't solve the import issue. I.e. this needs some upstream reporting!

sage: from polymake import *
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
<ipython-input-1-722853e5518e> in <module>()
----> 1 from polymake import *

/projects/sage/sage-7.3/local/lib/python2.7/site-packages/polymake/__init__.py in <module>()
      5 from .matrix import MatrixRational
      6
----> 7 from .polytope import Polytope
      8 from .functions import *

src/polymake/perl_object.pxd in init polymake.polytope (src/polymake/polytope.cpp:1300)()

ImportError: /projects/sage/sage-7.3/local/lib/python2.7/site-packages/polymake/perl_object.so: undefined symbol: _ZNK2pm4perl6Object4saveERKNSt7__cxx1112basic_stringIcSt
11char_traitsIcESaIcEEE

@mmasdeu
Copy link

mmasdeu commented Sep 16, 2016

When is gcc 6 planned to be installed? In my machine (on which it compiles) I have 6.2.1 installed. It seems that it's complaining about cxx11, and maybe it's related to the switch to C++11?

@haraldschilly
Copy link
Contributor

There are no plans for gcc6, just a plan to switch to a new compute environment, which is based on ubunteu 16.04. I don't know if that has gcc 6.

@haraldschilly
Copy link
Contributor

there seems to be a gcc-6 package for ubuntu 16.04, which conflicts with the version 4, but the default is gcc 5. so, maybe that can be installed, but I'm not sure what it really contains -- there doesn't seem to be that much support so far.

@saliola
Copy link

saliola commented Mar 7, 2017

over at videlec/pypolymake#12, @videlec asked for the full logs after running:

$ sage -f polymake
$ sage -pip install git+https://github.com/videlec/pypolymake

@slel
Copy link
Contributor

slel commented May 2, 2018

Ubuntu 18.04 ships gcc 7.3.0, so the upgrade to Ubuntu 18.04
should allow this issue to go forward. While we are at it, it would
be nice to replace Polymake 3.0 (currently in CoCalc) with the
latest Polymake, which at this time is Polymake 3.2r2.

@slel
Copy link
Contributor

slel commented May 2, 2018

Please also install the Polymake Jupyter kernel:
https://github.com/polymake/jupyter-polymake

@slel slel changed the title add python package to SMC -- pypolymake Upgrade Polymake; install pypolymake; install Polymake kernel for Jupyter May 2, 2018
@slel
Copy link
Contributor

slel commented May 2, 2018

@DrXyzzy
Copy link
Contributor

DrXyzzy commented Jul 24, 2018

Reported by Ahmed:

This breaks in current sagews:

%default_mode polymake
--- new cell
application 'tropical';

@jdchristensen
Copy link

It appears that polymake is an optional sage package and that the binary is installed in CoCalc. It works from the command line, but not within a sage worksheet. If I type

polymake.cell24()

I get a long backtrace. The important part shows that /usr/bin/env TERM=dumb polymake is being run, and that does indeed lead to an error if run in the terminal:

Can't locate object method "new" via package "Term::ReadLine::Gnu" at (eval 141) line 4.

If I try

p = sage.interfaces.polymake.PolymakeExpect(command='/usr/bin/env TERM=vt100 polymake')

there is no error, but it doesn't return. I suspect that what is happening is that Sage doesn't recognize the prompt because it is surrounded by bold escape sequences.

Any suggestions? Should I open a separate issue?

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

7 participants