Date: Sun, 07 Aug 2022 23:40:04 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 255722] Mk/Uses/python.mk: Needs to support pyproject.toml-based projects: USE_PYTHON=build feature Message-ID: <bug-255722-21822-ASk0Mey4bK@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-255722-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-255722-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=3D255722 --- Comment #11 from Charlie Li <vishwin@freebsd.org> --- autoplist is supported, just a different way of doing it (and much less fragile). "Minimalistic" will not work here, because a major part of PEP-517 is completely deprecating the setup.py or otherwise distutils path in package management and standardising on wheels. Even though setuptools includes an internal copy of distutils, there is no guarantee of it still existing in t= he future. Thus, in terms of future-proofing, this cannot go into the framework without also converting the toolchain to setuptools-less bootstrapping. USE_PYTHON=3Dbuild actually is misleading, because it's only one (minimalis= t) tool that only builds, not installs. In fact, py-build and py-installer did= n't exist until after PEP-517 was accepted and (ensure)pip gained support. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-255722-21822-ASk0Mey4bK>