[sage-support] Re: SSL module not available

2016-11-11 Thread Eden Harder
Thank you all! It works! 在 2016年11月11日星期五 UTC+1下午7:01:55,Dima Pasechnik写道: > > right, installing openssl still needs python2 rebuild. Sorry, I forgot > about this. > thus, the order of packages to be rebuilt: > 1) openssl > 2) python2 > 3) pyopenssl > > -- You received this message because you

[sage-support] Re: Question regarding normalization of modular symbols.

2016-11-11 Thread francisco
Chris, Thank you for your comments, they are very helpful! On my computations, I am considering elliptic curves with rank 1. So, the value of the modular symbol [0] is zero, and we cannot normalise using the value of the L function at 1. I need the correct normalization because I am working on

[sage-support] Re: SSL module not available

2016-11-11 Thread Dima Pasechnik
right, installing openssl still needs python2 rebuild. Sorry, I forgot about this. thus, the order of packages to be rebuilt: 1) openssl 2) python2 3) pyopenssl -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and

[sage-support] Re: SSL module not available

2016-11-11 Thread John H Palmieri
On Friday, November 11, 2016 at 2:31:38 AM UTC-8, Dima Pasechnik wrote: > > Could you try first > > sage -i openssl > > and only then > > sage -i pyopenssl > > Do you need to run "sage -f python2" in between these, to make sure Python builds its ssl module? > > > On Monday, November 7, 2016 a

[sage-support] Re: SSL module not available

2016-11-11 Thread Eden Harder
`sage -i openssl` done, `sage -i pyopenssl` gives the following errors: Error building Sage. The following package(s) may have failed to build (not necessarily during this run of 'make pyopenssl'): The build directory may contain configuration files and other potentially helpful informa

Re: [sage-support] Cannot use pip because pip is configured with locations that require TLS/SSL

2016-11-11 Thread Dima Pasechnik
This mess partially stems from Apple pulling the support of OpenSSL, in favour of their own (incompatible) replacement. Currently this leads to the chicken vs egg problem on OSX (or any other system that has no system-wide OpenSSL or equivalent installation): we cannot include OpenSSL sources, an

[sage-support] Re: SSL module not available

2016-11-11 Thread Dima Pasechnik
Could you try first sage -i openssl and only then sage -i pyopenssl On Monday, November 7, 2016 at 1:10:56 PM UTC, Eden Harder wrote: > > There is some errors when I install pyopenssl > > eden:~ Eden$ sage -i pyopenssl > > /Library/Developer/CommandLineTools/usr/bin/make build/make/Makefile >

Re: [sage-support] Cannot use pip because pip is configured with locations that require TLS/SSL

2016-11-11 Thread John Cremona
To Sage developers: this is coming up a lot. Would it not be solved by making the appropriate openssh spkg a dependency of pip? On 11 Nov 2016 07:59, "Eden Harder" wrote: > I installed pip by sage -i pip, but when I use pip to install some python > packages, it always gives the following error