> 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. >
It would be helpful for this discussion to know what packages we are actually talking about. For instance, for some of them (e.g. beautifulsoup or brian) we could just make new-style packages that say "this is no longer supported this way, please do sage -sh and pip install packagename." I agree that if python is the only one that is an actual disaster (TOPCOM vs. topcom seems very unlikely to cause a Sage installation to self-destruct to me) then that should be solved separately from this issue. There is also the question of how long/much to support earlier versions of Sage that might want some of these packages. I'm not sure what the answer to that is - and Volker, don't just say they should upgrade their system if it won't build from scratch, because (as you very well know) some people don't have admin authority or access to a newer system (e.g. if it's hardware provided by their employer). XP is still out there in the wild so many places... and maybe the virtual machine image even works there :-) - kcrisman -- 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.
