ports/lang/python311, branch 2025Q3FreeBSD ports treehttps://cgit-dev.freebsd.org/ports/atom?h=2025Q32025-06-30T15:00:23Z*: Update comment references to e2fsprogs-libuuid to libuuid.2025-06-30T15:00:23ZMatthias Andreemandree@FreeBSD.org2025-06-28T08:32:19Zurn:sha1:169ac0b9380f6ed8d0ff4e8cbfad131fd226812e
PR: 251489
python.mk: rename PYTHON_EXT_SUFFIX to PYTHON_TAG, document, etc2025-06-19T20:28:47ZCharlie Livishwin@FreeBSD.org2025-06-19T20:09:42Zurn:sha1:4f0eba1efd73e85ccb544708c967bca70ad3e7a6
EXT_SUFFIX, according to PEP 3149, refers to the full tag and
extension for compiled extension module objects, eg .cpython-311.so,
.cpython-313t.so, etc. We do not use the correct semantic meaning,
and this usage becomes ambiguous and confusing when tags do not
match between bytecode and compiled extension module objects.
Rename our PYTHON_EXT_SUFFIX to PYTHON_TAG to align with PEP 3147's
specification of a magic tag, which consists of implementation name
and shorthand version only. This is meant for bytecode and other
files containing this tag in their filename that do not depend on
a specific Python ABI for the same version. Chase all existing
consumers.
Introduce PYTHON_SOABI to align with PEP 3149's specification of a
tag, which consists of implementation name, shorthand version and
any ABI flags present (this and PYTHON_TAG are identical without
ABI flags). This is meant for compiled extension module objects and
other files that depend on a specific Python ABI for the same
version.
Add documentation for these variables that our PYTHON_EXT_SUFFIX
never had.
PR: 274671
Event: Kitchener-Waterloo Hackathon 202506
lang/python311: Update to 3.11.132025-06-12T00:32:31ZWen Hepingwen@FreeBSD.org2025-06-12T00:30:37Zurn:sha1:a7f52edcb041ce7792c98f48e33229e7051de09d
PR: 287313
Reported by: wen <wenheping2000@hotmail.com>
Exp-run by: antoine@
lang/python311: pull in upstream commit addressing CVE-2025-45162025-05-29T04:38:19ZCharlie Livishwin@FreeBSD.org2025-05-29T04:36:01Zurn:sha1:5e57ff8453ec6c1172fc575274cb5c466dd0bd30
Reference: https://github.com/python/cpython/pull/134341
PR: 287009
lang/python311: Update to 3.11.122025-04-18T01:03:19ZWen Hepingwen@FreeBSD.org2025-04-18T01:03:19Zurn:sha1:a1292020e61b6092626a9e799245eca4e4716003
PR: 285971
Reported by: wen@
Exp-run by: antoine@
lang/python311: Update to 3.11.112024-12-12T00:18:29ZWen Hepingwen@FreeBSD.org2024-12-12T00:18:29Zurn:sha1:63676c96dd013590952452dca21f647348b80a4b
PR: 283139
Reported by: wen@
Exp-run by: antoine@
lang/python311: Update to 3.11.102024-09-13T02:05:33ZWen Hepingwen@FreeBSD.org2024-09-13T01:58:33Zurn:sha1:b148c3ab99f599f5db350671a370e1e6b1d245b0
PR: 281379
Reported by: wen@
Exp-run by: antoine@
lang/python311: fix stage with DEBUG option ON2024-07-09T12:06:03ZVladimir Druzenkovvd@FreeBSD.org2024-07-09T12:03:15Zurn:sha1:a6e3b850c244b85bc0fe19b660833c5fe6f05a2flang/python311: disable LTO on powerpc64le2024-07-09T10:04:24ZPiotr Kubajpkubaj@FreeBSD.org2024-07-06T12:23:44Zurn:sha1:961bbfc94bd617321d304f8da70573c707f2c704
While LTOized python seems mostly fine, it crashes during build of x11/mate-terminal:
pid 71560 (python3.11), jid 151, uid 65534: exited on signal 11 (core dumped)
After disabling LTO, x11/mate-terminal builds fine.
lang/python311: refresh LibreSSL patches2024-06-24T17:56:55ZCharlie Livishwin@FreeBSD.org2024-06-24T17:50:17Zurn:sha1:3f76bb7c6fbff9496a1bfeea991635a6f71ef1ac
LibreSSL 3.9 introduced X509_STORE_get1_objects(3) so modify the
preprocessor guard to account. Prior to LibreSSL < 3.9 becoming
EOL, an additional conditional was needed to copy LibreSSL 3.9's
X509_STORE_get1_objects(3) as the included implementation for
OpenSSL < 3.3 clashed with LibreSSL.
Event: ARRL/RAC Field Day 2024
PR: 279390