Gregory P. Smith

retitled back to 3.0 as per https://www.openssl.org/policies/releasestrat.html 3.0.x is Long Term Support and thus the release with the longest support guarantee: until 2026-09. I think that means we can skip...

We need to backport to 3.11. Mention it in the release notes. At most just point Windows people at where they can get a prebuilt past EOL `libssl-1_1.dll` to be...

> And I've confirmed that `debug` is then being called. Should I make a PR like this? A closure seems cleaner than passing `mp_util` around as you suggested. I typically...

I pretty much agree with what was already summarized above. One lesson from pylint: rules will need multiple names. Only one should be considered the _primary_ (presumably used in the...

Ninja uses mtime. (poke around in https://github.com/ninja-build/ninja) regardless, hacking timestamps to appease another build system not designed for a shared cache used on CI purpose doesn't sound like a sustainable...

Thanks for the nice PEP! We've posted our initial reply: https://discuss.python.org/t/pep-712-adding-a-converter-parameter-to-dataclasses-field/26126/57 This SC is not leaning towards accepting this PEP as is, but we are open to being convinced by...

My **personal** gut feel is that there is still a way forward to the ultimate feature people are wanting behind all of this (without the existing "just override dunder methods"...

I came here to suggest the same thing, great to find it already requested! We already do this within Google, many of our custom pylint or similar analysis tooling checks...

We run portservers everywhere. Our automation systems have a notably lower than 60 FIN timeout. It is not impossible for something to take longer than `tcp_fin_timeout` seconds before that component...

FYI digging a little further, `tcp_fin_timeout` is not the TIME_WAIT duration in Linux, it just happens to default to the same value, but changing `tcp_fin_timeout` does not change the TIME_WAIT...