On 20 March 2012 16:39, leif <not.rea...@online.de> wrote: > > I thought HTTPS (which requires SSL of course) wasn't strictly needed > in Sage, but since it is omnipresent (many Python packages use it), it > doesn't make sense to not have it. I.e., people frequently happen to > notice they don't have _ssl *after* they've built Sage's Python > package without SSL support.
Indeed: every time I build my working copy of Sage (not counting test version here) I have to do first sage -i openssl and then sage -f python to rebuild python. Otherwise some mercurial stuff does not work (complains of not having _ssl, I think). The sort of thing which does not work is pull/push requests froma remote repository. This is a real nuisance, and I have long wanted a way to get this built when I first build Sage, and not as an afterthought. If the current discussion will help that, I would be grateful! (Also if anyone can say what magic would make this work with Sage as currently organised.) John -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
