I think it's time for this thread to stop as everyone seems to be talking in circles. Christian said he's going to write a PEP so let's wait for that before discussing this any further so we have a concrete proposal to focus around.
On Wed, 31 Aug 2016 at 05:04 Nick Coghlan <ncogh...@gmail.com> wrote: > On 31 August 2016 at 20:20, M.-A. Lemburg <m...@egenix.com> wrote: > > ... which would then mean: Python's compatibility roadmap will > > be dictated by OpenSSL. > > > > I won't buy into that, sorry. Crypto is a helper in certain > > situations, it's not what Python is all about. We should not > > let OpenSSL dictate how and when we deprecate platforms or > > OS versions. > > It won't dictate general support for those platforms, it will dictate > support for the *ssl module* on those platforms. If someone isn't > making secure network connections from Python, things will work fine. > If a redistributor is stepping in to provide the assertion that the > network connection is secure despite our upstream misgivings, things > will work fine. > > Connections will only fail in cases where neither we nor a > redistributor are prepared to make the assertion that a requested > secure network connection will actually be secure. > > Cheers, > Nick. > > -- > Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/brett%40python.org >
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
