Re: [sage-devel] Re: Proposal: install all pip-installable components of Sage via pip, directly

It should be fixed in distlib which is vendored into pip... On Monday, April 18, 2016 at 12:59:36 PM UTC+2, Erik Bray wrote: > > On Sat, Apr 16, 2016 at 2:13 PM, Jeroen Demeyer > wrote: > > Great... that still doesn't work. > > I agree that should be fixed. It's like

Re: [sage-devel] Re: Proposal: install all pip-installable components of Sage via pip, directly

On Monday, April 18, 2016 at 11:59:36 AM UTC+1, Erik Bray wrote: > > On Sat, Apr 16, 2016 at 2:13 PM, Jeroen Demeyer > wrote: > > Great... that still doesn't work. > > I agree that should be fixed. It's like a two line patch that I'll > submit to pip. > except

Re: [sage-devel] Re: Proposal: install all pip-installable components of Sage via pip, directly

On Sat, Apr 16, 2016 at 2:13 PM, Jeroen Demeyer wrote: > Great... that still doesn't work. I agree that should be fixed. It's like a two line patch that I'll submit to pip. -- You received this message because you are subscribed to the Google Groups "sage-devel"

Re: [sage-devel] Re: Proposal: install all pip-installable components of Sage via pip, directly

is this a clean experiment? I imagine one would try building pip over an ssl-less python... On Saturday, April 16, 2016 at 1:10:17 PM UTC+1, Volker Braun wrote: > > $ mv local/lib/python/lib-dynload/_ssl.so > local/lib/python/lib-dynload/_ssl.so-backup > $ sage -pip -h > Traceback (most recent

Re: [sage-devel] Re: Proposal: install all pip-installable components of Sage via pip, directly

Great... that still doesn't work. -- 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

Re: [sage-devel] Re: Proposal: install all pip-installable components of Sage via pip, directly

$ mv local/lib/python/lib-dynload/_ssl.so local/lib/python/lib-dynload/_ssl.so-backup $ sage -pip -h Traceback (most recent call last): File "/home/vbraun/Code/sage.git/local/bin/pip", line 9, in load_entry_point('pip==8.1.1', 'console_scripts', 'pip')() File

Re: [sage-devel] Re: Proposal: install all pip-installable components of Sage via pip, directly

On 2016-04-16 12:15, Volker Braun wrote: IMHO we should always use pip, but pip depends on openssl. Not for local packages, as far as I know. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving

[sage-devel] Re: Proposal: install all pip-installable components of Sage via pip, directly

Hi Thierry, On 2016-04-16, Thierry wrote: > - for standard packages, the source must be provided since the tarball is > supposed to be autonomous. If I understand correctly, that'S exactly what the proposal would change: Sage sources would contain the

[sage-devel] Re: Proposal: install all pip-installable components of Sage via pip, directly

I think there are two different tasks: 1) Use pip to install python packages, regardless of where the package is. Maybe we bundle the tarball, maybe its on PyPI, maybe its on github. Pip can install either just fine. IMHO we should always use pip, but pip depends on openssl. We'll save us much