But you could choose which implementation to use at compile time based on the autoconf output, right?
On Sat, May 28, 2016 at 2:01 PM, Christian Heimes <christ...@python.org> wrote: > On 2016-05-27 09:41, Chris Barker wrote: >> I'm probably showing my ignorance here, but couldn't we swap in the >> OpenSSL implementation when that becomes available? > > No, not any time soon. As soon as we guarantee SHA3 support we have to > keep our own implementation for a couple of additional releases. We can > drop our own SHA3 code as soon as all supported OpenSSL versions have SHA3. > > For example when OpenSSL 1.2.0 is going to have SHA3 support, we must > wait until OpenSSL 1.1 and 1.0.2 are no longer supported by OpenSSL. > > Christian > > > _______________________________________________ > 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/guido%40python.org -- --Guido van Rossum (python.org/~guido) _______________________________________________ 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
