On Thu, Oct 19, 2017 at 5:21 PM, Emmanuel Charpentier
<emanuel.charpent...@gmail.com> wrote:
>
>
> Le mercredi 18 octobre 2017 20:36:47 UTC+2, Jeroen Demeyer a écrit :
>>
>> 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? *
>
>
> From the Python license page :
>
> The modules hashlib, posix, ssl, crypt use the OpenSSL library for added
> performance if made available by the operating system. Additionally, the
> Windows and Mac OS X installers for Python may include a copy of the OpenSSL
> libraries, so we include a copy of the OpenSSL license here:

All of this is talking about optional functionality--either modules
that are completely optional, or functionality within some modules
that are optional.  Python works just fine without SSL support.

>> It seems to me that R is the only package causing us so much trouble
>> with SSL.
>
>
> No : *I* cause "so much trouble" with SSL issues because they become
> important to R real-world usage, and I do not think that a non-communicating
> R is useful in Sage.  Python/pip SSL usage do not cause "so much trouble"
> with SSL issues because the potential users of SSL functionalities are more
> patient than I am...

Ditto William on thanking you for causing this "trouble".  I know this
is a battle you've been fighting a long time and I really hope we can
come to a resolution soon.  In pointing out that SSL is not an issue
where Python is concerned I hope it alleviates some of your concerns.
Hopefully we can browbeat R into making the same acceptance (at least
insofar as allowing offline package installs).

-- 
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.

Reply via email to