FreeBSD ports tree https://cgit-dev.freebsd.org/ports/atom?h=main 2021-12-31T13:02:03Z 2021-12-31T13:02:03Z Rene Ladan rene@FreeBSD.org 2021-12-31T13:02:03Z urn:sha1:6c401020d1946446ed7f46742d7dca78c201408f 2021-12-31 lang/python36: Upgrade to a newer Python version. 3.6 is in maintenance status and gets security fixes only. End-of-Life: 2021-12-23. See https://devguide.python.org/ 2021-11-26T18:48:57Z Dimitry Andric dim@FreeBSD.org 2021-11-26T16:02:16Z urn:sha1:4af982e6bea019a33ae85c6c92a3042fadccb739 In ports 6bef09666460 we patched out python's erroneous multiarch detection using sed, but upstream changed the surrounding parts in the configure script to defeat the regex we were using. Update the regex to cope with the change. PR: 259896, 258377 MFH: 2021Q4 Approved by: maintainer timeout (9 days) 2021-10-13T17:05:40Z Thierry Thomas thierry@FreeBSD.org 2021-10-13T16:48:56Z urn:sha1:693abe1cb40ba9f505b2c72497443ca3ce85887d The Python ports install the library libpython3.x.so under $PREFIX/lib, and they set USE_LDCONFIG, but these libraries are not registered, due to a missing symlink, and they are not found by `ldconfig -r'. This commit make them to be registered, and for some reason it helps the dynamic linker to find them, and this allows to fix an error in french/aster. It also helps to fix errors in newer releases of math/sage (not yet ready to be committed due to other problems). No exp-run, but it has been tested with many ports on several platforms. PR: 257864 Approved by: koobs (Python team) MFH: 2021Q4 2021-09-27T17:56:59Z Dimitry Andric dim@FreeBSD.org 2021-09-27T17:39:05Z urn:sha1:6bef09666460fb9f9052550854fa69f5d5e4a0e8 It breaks with clang >= 13, which adds a major.minor version number in -print-multiarch output, and the dot confuses Python: ModuleNotFoundError: No module named '_sysconfigdata__freebsd14_x86_64-unknown-freebsd14' Since we do not support multiarch, and the configure script has no way to disable the multiarch check, stub it out during post-patch. PR: 258377 Approved by: maintainer timeout (2 weeks) MFH: 2021Q3 2021-09-09T09:02:38Z Kai Knoblich kai@FreeBSD.org 2021-09-09T08:59:19Z urn:sha1:c92e5f7b9ad0fb306bbc01171ba4bc95d01ba55b Python 3.6 will reach its End-of-Life at 23rd December 2021. Set the deprecation note and expiration date accordingly. Approved by: koobs (python, maintainer) MFH: No (not neccessary, 3+ months from now should be OK) Differential Revision: https://reviews.freebsd.org/D31783 2021-05-25T13:55:44Z Dmitry Marakasov amdmi3@FreeBSD.org 2021-04-09T13:28:59Z urn:sha1:5f69415313f894338dca54e21b5c3981e5e5f58f This brings python framework in consistense with handbook recommendations to prefer DISTVERSION and simplifies adding prerelease versions of python PR: 255013 Differential Revision: https://reviews.freebsd.org/D29418 Exp-run by: antoine Approved by: wen@, no objection from python@ or portmgr@ 2021-05-15T07:14:04Z Yasuhiro Kimura yasu@utahime.org 2021-05-15T06:50:22Z urn:sha1:9671981826f7ef8b1e7fb0a430ee24d4a1f0acf2 PR: 248459 Exp-run by: antoine 2021-04-06T14:31:07Z Mathieu Arnold mat@FreeBSD.org 2021-04-06T11:55:50Z urn:sha1:305f148f482daf30dcf728039d03d019f88344eb 2021-02-23T11:43:07Z Wen Heping wen@FreeBSD.org 2021-02-23T11:43:07Z urn:sha1:47227f3b6b6e773a56f3917531f77b75a84d6174 2020-10-14T18:09:41Z Kyle Evans kevans@FreeBSD.org 2020-10-14T18:09:41Z urn:sha1:02966fbc519489256c36645be4993091cb26dee9 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)