Date: Wed, 29 Oct 2025 22:20:16 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 290653] Mk/Uses/python.mk: Enable building Python wheel files alongside packages Message-ID: <bug-290653-21822-OqoaWINWLH@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-290653-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-290653-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=290653 Charlie Li <vishwin@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|ports-bugs@FreeBSD.org |vishwin@freebsd.org Status|New |Open Assignee|portmgr@FreeBSD.org |python@FreeBSD.org --- Comment #2 from Charlie Li <vishwin@freebsd.org> --- Not a fan of this. Even as an opt-in since it's more liability to maintain. The point of ports is for system packaging purposes, nothing more. While currently unenforced because the relevant PEP has not been implemented in the lang/python distribution/interpreter ports, front-ends like pip and uv are expressly prohibited from touching the portions of hier(7) that are pkg(8)'s exclusive domain. Such tooling for other purposes can operate outside of the aforementioned portions of hier(7) like $HOME or virtual environments. -- You are receiving this mail because: You are on the CC list for the bug. 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-290653-21822-OqoaWINWLH>