Kyle Stanley <aeros...@gmail.com> added the comment:
> There are some platforms (Linux pre-3.9 kernels) that don't have > SO_REUSEPORT. I wish I could say I don't care about such platforms; alas, I > just had to compile Python 3.7 on a system running a 2.6 kernel last month at > a client site. Based on https://www.kernel.org/releases.html, pre-3.9 Linux kernels are no longer supported upstream, the oldest LTS version is 3.16. There are likely a number of systems running older unsupported kernel versions, but I don't think that we can be reasonably expected to maintain indefinite backwards compatibility to versions that aren't supported upstream, especially not at the expense of the ones that are supported. In those cases, I think the responsibility ultimately falls upon the owners of the system or third party group providing service. This particular fix would be fairly straightforward: > And, yes, someone who really wants SO_REUSEADDR can set it manually, for > example by calling `transport.get_extra_info('socket')`. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue37228> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
