On 10/01/2022 17.01, Miro Hrončok wrote:
On 09. 01. 22 19:39, Christian Heimes wrote:
Hi,
I would like to remind everybody that Python's support for OpenSSL 3.0
is preliminary [1]. Python compiles with OpenSSL 3.0.0 and simple code
kinda works. However there are known performance regressions,
On 11/01/2022 12.02, Antoine Pitrou wrote:
Hi Christian,
On Sun, 9 Jan 2022 19:39:06 +0100
Christian Heimes wrote:
Hi,
I would like to remind everybody that Python's support for OpenSSL 3.0
is preliminary [1]. Python compiles with OpenSSL 3.0.0 and simple code
kinda works. However there are
Hi Christian,
On Sun, 9 Jan 2022 19:39:06 +0100
Christian Heimes wrote:
> Hi,
>
> I would like to remind everybody that Python's support for OpenSSL 3.0
> is preliminary [1]. Python compiles with OpenSSL 3.0.0 and simple code
> kinda works. However there are known performance regressions, mi
On 09. 01. 22 19:39, Christian Heimes wrote:
Hi,
I would like to remind everybody that Python's support for OpenSSL 3.0 is
preliminary [1]. Python compiles with OpenSSL 3.0.0 and simple code kinda
works. However there are known performance regressions, missing features (e.g.
usedforsecurity f
Is there an issue that keeps track of all the missing pieces? A "remaining
tasks" list would be useful for involving more devs (and of course useful when
resuming development, "now, where was I..."). A quick search on BPO revealed
some info:
- bpo-46313: SSLObject does not raise SSLEOFError on
