#18437: Fix PolyBoRi and Python 3
-------------------------------------+-------------------------------------
Reporter: ohanar | Owner:
Type: task | Status: needs_info
Priority: major | Milestone: sage-6.7
Component: packages: | Resolution:
standard | Merged in:
Keywords: | Reviewers:
Authors: R. Andrew Ohana | Work issues:
Report Upstream: N/A | Commit:
Branch: u/ohanar/polybori | b6aad4136aa9fc21844eaeacf11e9d32279f35c1
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by jdemeyer):
Replying to [comment:20 fbissey]:
> Fair point. The question then is "does anyone care to have to install
sage to get polybori instead of having it as stand alone package?".
I don't think that's "the question".
All the packaging effort in Sage is really converging towards separating
packages from the Sage library proper.
At the very least, moving `polybori` in the Sage library is a sufficiently
big change that it should be discussed on `sage-devel`.
--
Ticket URL: <http://trac.sagemath.org/ticket/18437#comment:21>
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.