A possible (hack) fix is to put something in the skpg script to explicitly ban it from installing python without specifying 2 or 3. It keeps the old python spkg for backwards compatibility for 5.x and prevents 6.x users from using the old outdated version. Either that or we provide a backport patch which changes the packaging system on older versions of Sage to the latest, but that doesn't sound very feasible.
To the discussion at hand, I think the current system of not allowing old spkgs to be installed is a waste. What are the current old style (non-experimental) spkgs, which of them have you tried, and which of them don't work on what system. I'm willing to put in some time and effort to convert some of them to new style (specifically chomp and Simon's cohomology) to try and get this resolved. However, if we are going to go with the current route, we should have a major version number bump for the next stable release. Best, Travis On Wednesday, September 9, 2015 at 8:37:43 AM UTC-5, Volker Braun wrote: > > On Wednesday, September 9, 2015 at 2:47:20 PM UTC+2, Jeroen Demeyer wrote: >> >> But by reverting #19004 (which is essentially what #19158 does), it is >> also possible to install them using "sage -i <package>". > > > It is possible to try, and almost always fail miserably, to install them. > -- 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.
