Guest96 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Guest96 has joined #pypy
Guest96 has quit [Ping timeout: 240 seconds]
otisolsen70 has joined #pypy
_whitelogger has joined #pypy
[Arfrever] has joined #pypy
nanonyme has quit [Ping timeout: 256 seconds]
otisolsen70 has joined #pypy
nanonyme has joined #pypy
lritter has joined #pypy
greedom has joined #pypy
greedom has quit [Remote host closed the connection]
greedom has joined #pypy
* tumbleweed
contemplates what to do about OpenSSL 3
<tumbleweed>
mattip: I see you didn't even try to support it in pypy 2.7
<tumbleweed>
was there technical reasons for that?
<tumbleweed>
at the moment in Debian we're keeping cpython 2.7 alive to build pypy 2.7, which we're keeping alive to build pypy 3
greedom has quit [Remote host closed the connection]
<tumbleweed>
porting cpython 2.7 to openssl 3 is easy enough, pypy looks trickier
<tumbleweed>
don't really want to ship a pypy 2.7 in a stable release, that's using an old openssl. And I'm sure our security team would be strongly against that
<tumbleweed>
wondering if we should persue a minimal ssl module that has the hash functions and no more
<mattip>
tumbleweed: CPython is not very happy with its OpenSSL3 support, what is wrong with 1.1.1m?
<mattip>
debian would drop cpython2.7 if pypy did not need it?
<tumbleweed>
Debian & Ubuntu try very hard to have only one version of each thing
<[Arfrever]>
Or just disable ssl module in CPython 2.7 and PyPy 2.7?