[ 18:09 kevans  ]

• 552351 lang/python36/Makefile
• 552351 lang/python36/files/patch-Modules___posixsubprocess.c
• 552351 lang/python36/files/patch-Modules_posixmodule.c
• 552351 lang/python36/files/patch-issue40422_issue40423
• 552351 lang/python37/Makefile
• 552351 lang/python37/files/patch-Modules___posixsubprocess.c
• 552351 lang/python37/files/patch-Modules_posixmodule.c
• 552351 lang/python37/files/patch-issue40422_issue40423
• 552351 lang/python38/Makefile
• 552351 lang/python38/files/patch-Modules___posixsubprocess.c

lang/python3{6,7,8,9}: Backport close_range patches

Worked out over BPO-40422 and BPO-40423, this is the culmination of months
of work to coordinate with Linux and get close_range(2) added to FreeBSD,
then the usage accepted into CPython. It has landed for Python 3.10 and here
I've backported it locally to all the supported Python 3 versions we have.

Note that this does include and supercede our previous closefrom(2) patches.
There was a lot of intersection between the work done, so this patch against
the ports tree does remove those patches from each of the ports in favor of
this patch. All the patches involved have been accepted and merged upstream.

This patch will bring a performance boost in some more situations on 12.2
and 13.0, as close_range exists there.

There is one additional patch sitting in an upstream PR that shuffles the
_Py_closerange implementation into a different file -- this is not important
for the backport, and the absence of that patch here will not realistically
cause any issues.

PR:		250322
Approved by:	lwhsu (python)