#18437: Fix PolyBoRi and Python 3
--------------------------------------+------------------------
Reporter: ohanar | Owner:
Type: task | Status: new
Priority: major | Milestone: sage-6.7
Component: packages: standard | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
--------------------------------------+------------------------
Comment (by ohanar):
Reposted from #15530:
fyi, I started working on an autotools based build system for polybori at
https://github.com/ohanar/PolyBoRi/tree/autotools. I'll probably work on
it a bit more next weekend during SD 64.25, but the important bits (the
c++ libraries) are currently working with only a couple of hacks. What
remains (for sage at least) is just a little cleanup and throwing in the
bit of the python bindings we use.
----
I also don't know how we should handle this with regards to upstream,
since upstream is dead. I certainly don't want to take over maintenance
for polybori, but we'll probably need to make some sort of fork.
--
Ticket URL: <http://trac.sagemath.org/ticket/18437#comment:1>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
