I realise that;s what you want to do personally but I understand other use pip to supplement sage’s collection of packages. William probably wouldn’t be happy with a package manager that cannot pull packages.
Now, if we can just make sure that pip doesn’t need SSL for local install but can still use it to pull packages that’s a win for everybody. François > On 7/04/2015, at 22:37, Volker Braun <vbraun.n...@gmail.com> wrote: > > Yes, we want to install local tarballs. > > > > On Tuesday, April 7, 2015 at 11:37:46 AM UTC+2, François wrote: > It depends. To just use pip as a local installer it probably will work > fine. If you want to connect to the pip repository to install extra > python packages you’ll need SSL (and a relatively recent one too). > The pip repo just won’t let you connect without SSL. > > François > > > On 7/04/2015, at 20:58, Volker Braun <vbrau...@gmail.com> wrote: > > > > I made http://trac.sagemath.org/ticket/18131 to deal with this > > > > > > On Tuesday, April 7, 2015 at 10:56:41 AM UTC+2, Volker Braun wrote: > > I took a quick look at the pip sources and I think the ssl dependency can > > be stubbed out relatively easily. Did anybody try this? Really we should > > push this upstream, pip ought to be usable without ssl. > > > > > > > > On Tuesday, April 7, 2015 at 10:27:43 AM UTC+2, Thierry wrote: > > Hi, > > > > this is a known issue : pip requires that Python is built with ssl, but > > openssl cannot be standard because of licensing, hence pip can only be > > used to install optional packages, see > > http://trac.sagemath.org/ticket/17368 for a discussion. > > > > The following should work if you do not have libssl-dev on your system: > > > > cd $SAGE_ROOT > > ./sage -i openssl > > ./sage -f python > > make > > ./sage -pip install optional_package > > > > Ciao, > > Thierry > > > > > > On Mon, Apr 06, 2015 at 06:37:52PM -0700, kcrisman wrote: > > > > > > > > > > Apparently pip requires SSL... I take it you don't have a system-wide > > > > openssl(-devel) installation? > > > > > > > >> > > > >> > > > I was indeed wondering whether that change would make any problems. Also > > > on > > > older installations? (Namely, which OS X versions should we assume will > > > have this? I honestly don't know.) > > > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "sage-release" group. > > > To unsubscribe from this group and stop receiving emails from it, send an > > > email to sage-release...@googlegroups.com. > > > To post to this group, send email to sage-r...@googlegroups.com. > > > Visit this group at http://groups.google.com/group/sage-release. > > > For more options, visit https://groups.google.com/d/optout. > > > > > > -- > > You received this message because you are subscribed to the Google Groups > > "sage-release" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to sage-release...@googlegroups.com. > > To post to this group, send email to sage-r...@googlegroups.com. > > Visit this group at http://groups.google.com/group/sage-release. > > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "sage-release" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-release+unsubscr...@googlegroups.com. > To post to this group, send email to sage-release@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-release. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at http://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
