Date: Thu, 16 Oct 2025 04:56:08 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 281470] math/py-numpy: update to 2.3.2 Message-ID: <bug-281470-21822-khF1zVjSRM@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-281470-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-281470-21822@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470 --- Comment #50 from Yuri Victorovich <yuri@freebsd.org> --- The problem of numpy-2.x vs. numpy-1.x can be resolved in this way: 1. Upgrade math/py-numpy to 2.x 2. Create a fork of the old math/py-numpy as math/py-numpy1 3. Make (hack) math/py-numpy1 to install into some other location, for example /usr/local/lib/python3.11/numpy1/site-packages/numpy 4. All programs that still need numpy-1.x would have to use PYTHONPATH=/usr/local/lib/python3.11/numpy1:/usr/local/lib/python3.11 This PYTHONPATH would make all imports of numpy to use numpy-1.x while numpy-2.x can be installed at the same time for other apps. There can't be a mix of numpy libraries with contradictory requirements like numpy>=2 and numpy<2 in the same process. They should either all work with numpy-1.x or with numpy-2.x This way it would be at least a path forward that would only put some pressure on apps requiring numpy-1.x, and apps running with numpy-2.x would be just normal. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-281470-21822-khF1zVjSRM>