Hi all, On Friday 12 Jun 2015 13:45:05 R. Andrew Ohana wrote: > What about this: > > Now: We work on making polybori an optional package in sage. > * At least going by this thread, the number of people who use polybori in > Sage is small enough for it to make sense to have polybori as an optional > package.
I know I might be outvoted and I haven't volunteered to just do the work, but I very much disagree with this. Dropping PolyBoRi as a default package makes Sage *a lot* less useful for me. Why does this need to happen now? > * (I looked into this before I did the autotoolization) It shouldn't take > too much work to optionalize polybori -- the main effort will be its uses > in the crypto code. > * Polybori is the sole dependency of Sage that doesn't at least build > against python 3 -- getting past this last major hurdle will make it much > easier to work on porting the actual sage library to python 3. > > Future: The Singular team or whoever dedicates the time to maintain a > sequel to polybori. > * This will be required once we stop supporting python 2 in the very > distant future (at least after 2020, which is the EOL for python 2). Martin -- .www: https://martinralbrecht.wordpress.com .pgp: 40BC 7F0D 724B 4AB1 CC98 4014 A040 043C 6532 AFB4 .xmpp: martinralbre...@jabber.ccc.de .twitter: https://twitter.com/martinralbrecht .keybase: https://keybase.io/martinralbrecht -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
