Date: Wed, 21 Jul 2021 08:08:48 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 251626] math/py-numpy: Update to 1.20.3 (compatible with Python 3.9) Message-ID: <bug-251626-21822-rvKEDPdq0r@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-251626-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-251626-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D251626 --- Comment #40 from Kubilay Kocak <koobs@FreeBSD.org> --- (In reply to Thierry Thomas from comment #39) Can you clarify where this is at wrt QA? The exp-run has not been ack'd, the latest patch (and we have three), does = it pass QA? Does it need another exp-run?=20 With no open questions, python has no issue accepting an explicitly QA'd changeset. Other open questions: With the other port fixes: +- numpy>=3D1.16.6,<1.20 ++ numpy>=3D1.16.6,<1.21 Does the software pass tests with 1.21 ? Are there refs upstream that <1.20= is unnecessarily limiting, or has it been bumped upstream? -RUN_DEPENDS=3D=20=20 ${PYTHON_PKGNAMEPREFIX}numpy>=3D1.15,1<1.20,1:math/py-numpy@${PY_FLAVOR} \ +RUN_DEPENDS=3D ${PYNUMPY} \ Shared macros don't work with Python package dependency declarations, and w= e're removing instances of these. autoplist is preferred. I agree there are some cases where autoplists can c= ause lack of observability, but there are plenty of cases where autoplists assist immensely. We should have a discussion about improving the situation (possibly to have= our cake and eat it to) offline. In the meantime autoplist is preferred, especi= ally for complex ports, and particularly for C extension based python ports. It picks up enough upstream packaging issues that cause other issues downstream for us that its beneficial overall. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-251626-21822-rvKEDPdq0r>