-
Notifications
You must be signed in to change notification settings - Fork 219
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
Comments
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!
|
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? |
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. |
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. |
over at videlec/pypolymake#12, @videlec asked for the full logs after running:
|
Ubuntu 18.04 ships gcc 7.3.0, so the upgrade to Ubuntu 18.04 |
Please also install the Polymake Jupyter kernel: |
|
Reported by Ahmed: This breaks in current sagews:
|
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
I get a long backtrace. The important part shows that
If I try
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? |
https://github.com/videlec/pypolymake/
Requested by: Marc Masdeu
The text was updated successfully, but these errors were encountered: