ports/science/py-dwave-samplers, branch mainFreeBSD ports treehttps://cgit-dev.freebsd.org/ports/atom?h=main2026-06-23T17:11:28Zscience/py-dwave-samplers: update 1.7.0 → 1.8.02026-06-23T17:11:28ZYuri Victorovichyuri@FreeBSD.org2026-06-23T16:09:23Zurn:sha1:3aa2de6850797dae5bfa762ee5459dbd3b3e5a3b*/*: bump PORTREVISION after switching to NumPy 2.x2026-05-05T19:29:37ZMax Brazhnikovmakc@FreeBSD.org2026-05-05T19:27:16Zurn:sha1:2bf3834a197ccf8956332378eda8dd7577965246*/*: Switch to NumPy 2.x2026-05-05T19:29:37ZMax Brazhnikovmakc@FreeBSD.org2026-05-05T19:27:15Zurn:sha1:b0b4d9e1eae890d0de1591e20fb37358439a2ff6
PR: 294328
Exp-run: antoine
python.mk: retire ${PYNUMPY}2026-04-03T20:52:43ZCharlie Livishwin@FreeBSD.org2026-04-03T20:48:09Zurn:sha1:d04d23ae37d04c8ddf74c04ee868900b9189295a
With both math/py-numpy (2) and math/py-numpy1, the variable stopped
making sense. Also remove the upper version bound.
math/py-numpy1: bump more RUN_DEPENDS consumers2026-04-03T20:01:01ZCharlie Livishwin@FreeBSD.org2026-04-03T20:01:01Zurn:sha1:1912d150ac52993a0da6f5c68a485a6fd2a87f9d
These specify numpy indirectly using a different variable.
PR: 281470
science/py-dwave-samplers: update 1.6.0 → 1.7.02026-04-01T02:37:50ZYuri Victorovichyuri@FreeBSD.org2026-03-31T19:52:46Zurn:sha1:3570812f47dea76f6fade42582c2b06bba0ffc44Mk/Uses/python.mk: Remove USE_PYTHON=cython3{,_run,_test}2026-01-15T17:22:12ZPo-Chuan Hsiehsunpoet@FreeBSD.org2026-01-15T17:22:12Zurn:sha1:6d475ab2dcd08d35a6a3ef6bd9db134e3c7a71f0
- Convert all cython3 occurrence to USE_PYTHON=cython*
- Bump PORTREVISION dependent ports of USE_PYTHON=cython_run for dependency change
PR: 291778
science/py-dwave-samplers: update 1.3.0 → 1.6.02025-09-28T01:38:27ZYuri Victorovichyuri@FreeBSD.org2025-09-28T01:33:15Zurn:sha1:0be9fb7bd03d315fa42c63f2f70d03685def323aall: bump PORTREVISION after updating graphics/libyuv2025-08-31T10:30:51ZRene Ladanrene@FreeBSD.org2025-08-31T10:30:51Zurn:sha1:b304d8ab18ac96ddcd15f3cf7255ef89aababe5a
Using the Tools/scripts/bump_revision.pl script
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