On Wed, Oct 18, 2017 at 8:36 PM, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > On 2017-10-18 19:02, Emmanuel Charpentier wrote: >> >> This option commits us to maintain (unnecessary and dangerous, IMHO) >> Sage-specifc SSL patches at least in R, Python and pip > > > Really? Which Sage-specific SSL patches does this require in Python and pip? > > It seems to me that R is the only package causing us so much trouble with > SSL.
There *was* an issue in pip (not Python itself though that I can recall--Python works fine without SSL support obviously). However, the pip issue has since been fixed upstream (pip can work without SSL for installing packages from sources other than PyPI, there was just a bug with imports failing if the ssl module was not importable). If R still requires such a patch I think we should get really pushy with upstream about getting them to accept it. R should at least be able to function without it, even if it means disabling package downloads from CRAN which is fine. -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
