#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 fbissey):
I think there are two separate issues:
1) polybori is using a internal copy of a third party package that may
not be dead upstream (I think it has updates once in a while): cudd.
2) the python bindings
We could package the libraries properly and then have a separate python
binding package, unless `polybori` is altering its upstream significantly
beyond the build system. The python binding could be moved in sage making
it "a collective" responsibility.
--
Ticket URL: <http://trac.sagemath.org/ticket/18437#comment:2>
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.
