On Fri, Mar 15, 2019 at 4:47 PM Dima Pasechnik <dimp...@gmail.com> wrote: > > On Fri, Mar 15, 2019 at 3:35 PM E. Madison Bray <erik.m.b...@gmail.com> wrote: > > > > On Fri, Mar 15, 2019 at 3:31 PM Dima Pasechnik <dimp...@gmail.com> wrote: > > > > > > It appears that Sage's openssl package is broken on MacOS nowadays. > > > Should this be a blocker? > > > > How is SSL support currently handled in MacOS? I have not kept up > > with that issue. Are OSX users still not able to do something as > > simple as pip install? > > > > current Sage 8.6 MacOS binary installer comes with urllib that cannot > work with https. > I presume this is precisely what we see reported here, as it's exactly > what oeis() function of Sage needs. > > However, 2.7.16 binary installer of Python from python.org comes with a script > Install\ Certificates.command , which says inside > > # install_certifi.py > # sample script to install or update a set of default Root Certificates > # for the ssl module. Uses the certificates provided by the certifi package: > # https://pypi.python.org/pypi/certifi > > and which, after you run it, allows urllib to function properly. > (but not before - perhaps it's launched automatically if you open some > Python GUI that comes in that installer) > > Perhaps we should do something like this...
That appears to be a separate issue. What do you mean by "binary installer comes with urllib that cannot work with https"? Because if there is no _ssl module included in Python then it can't use HTTPS anyways. But if `import _ssl` works then there is a working SSL library included, whatever it may be. The other issue is just a question of whether or not the SSL library has up-to-date root certificates to verify connections with. If it doesn't, then HTTPS connections will fail with some SSL_CERTIFICATE_VERIFY_FAILED which can be worked around in a number of different ways (including installing up-to-date root CA certs from a presumed "trusted" source into a location that Python's urllib knows where to look). > > > On Thu, Mar 14, 2019 at 4:49 PM Volker Braun <vbraun.n...@gmail.com> > > > wrote: > > > > > > > > Feel free to fix the Cygwin-related bugs, but some of these are > > > > longstanding issues that should be discussed with upstream first; > > > > Realistically thats not going to make it to the next Sage version. > > > > > > > > > > > > > > > > On Thursday, March 14, 2019 at 2:36:29 PM UTC+1, E. Madison Bray wrote: > > > >> > > > >> Hi Volker, > > > >> > > > >> I don't think there should be a release candidate at least until most > > > >> of the blocker issues [1] are resolved; in particular the four that > > > >> are already either positively reviewed or are in-progress. > > > >> > > > >> Thanks > > > >> > > > >> > > > >> [1] > > > >> https://trac.sagemath.org/query?priority=blocker&status=needs_info&status=needs_review&status=needs_work&status=new&status=positive_review&milestone=sage-8.7&group=status&col=id&col=summary&col=priority&col=owner&col=type&col=component&col=time&order=priority > > > >> > > > >> On Thu, Mar 14, 2019 at 2:25 PM Volker Braun <vbrau...@gmail.com> > > > >> wrote: > > > >> > > > > >> > Next develop release will be rc0 > > > >> > > > > >> > IMHO changes to gmpy2 should wait until the next version to give it > > > >> > some time to test out. > > > >> > > > > >> > -- > > > >> > 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+...@googlegroups.com. > > > >> > To post to this group, send email to sage-...@googlegroups.com. > > > >> > Visit this group at https://groups.google.com/group/sage-devel. > > > >> > For more options, visit https://groups.google.com/d/optout. > > > > > > > > -- > > > > 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. > > > > > > -- > > > 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. > > > > -- > > 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. > > -- > 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. -- 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.
