Hi, On 3 January 2018 at 06:53, Yury V. Zaytsev <y...@shurup.com> wrote: > Basically only bloat (not an argument) and necessity to track OpenSSL > security updates & release new versions when they come out...
...which I'm sure will not be done, because there is no-one in the PyPy core group that is both security-oriented and an OS X user. Given that situation my own vote would be to find the easiest solution that seems to work (maybe just link to the outdated openssl) and add a warning next to the download link on our web page, with a link to the homebrew version. A slightly different note: we now have to worry about two different ssl messes instead of one, because pypy3 uses cffi but not pypy2. Maybe the way forward is to throw away the pypy2 version and use cffi there too. A bientôt, Armin. _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
