New on blog: "the story of #distutils build directory in #Gentoo".
"""
The #Python distutils build system, as well as #setuptools (that it was later merged into), used a two-stage build: first, a build command would prepare a built package version (usually just copy the .py files, sometimes compile Python extensions) into a build directory, then an install command would copy them to the live filesystem, or a staging directory. Curious enough, distutils were an early adopter of out-of-source builds — when used right (which often enough wasn’t the case), no writes would occur in the source directory and all modifications would be done directly in the build directory.
Today, in the #PEP517 era, two-stage builds aren't really relevant anymore. Build systems were turned into black boxes that spew wheels. However, setuptools still internally uses the two-stage build and the build directory, and therefore it still remains relevant to Gentoo eclasses. In this post, I'd like to shortly tell how we dealt with it over the years.
"""
https://blogs.gentoo.org/mgorny/2024/03/13/the-story-of-distutils-build-directory-in-gentoo/
Michał Górny (he/they) ∞🙀🚂🐧 /
npub1r9…t4ppx
2024-03-13 10:21:29
Author Public Key
npub1r9jmk6t0ape7t9ddfv5nrrsh87pluzxtepzjqu93sctkkurun0wqft4ppxPublished at
2024-03-13 10:21:29Event JSON
{
"id": "07ae1942117edfcdcf7bdaa42c4786be8f15d3a55d60c05e9da51f696f4a724d",
"pubkey": "1965bb696fe873e595ad4b29318e173f83fe08cbc8452070b186176b707c9bdc",
"created_at": 1710325289,
"kind": 1,
"tags": [
[
"t",
"distutils"
],
[
"t",
"gentoo"
],
[
"t",
"python"
],
[
"t",
"setuptools"
],
[
"t",
"pep517"
],
[
"proxy",
"https://social.treehouse.systems/users/mgorny/statuses/112087878189779956",
"activitypub"
]
],
"content": "New on blog: \"the story of #distutils build directory in #Gentoo\".\n\n\"\"\"\nThe #Python distutils build system, as well as #setuptools (that it was later merged into), used a two-stage build: first, a build command would prepare a built package version (usually just copy the .py files, sometimes compile Python extensions) into a build directory, then an install command would copy them to the live filesystem, or a staging directory. Curious enough, distutils were an early adopter of out-of-source builds — when used right (which often enough wasn’t the case), no writes would occur in the source directory and all modifications would be done directly in the build directory.\n\nToday, in the #PEP517 era, two-stage builds aren't really relevant anymore. Build systems were turned into black boxes that spew wheels. However, setuptools still internally uses the two-stage build and the build directory, and therefore it still remains relevant to Gentoo eclasses. In this post, I'd like to shortly tell how we dealt with it over the years.\n\"\"\"\n\nhttps://blogs.gentoo.org/mgorny/2024/03/13/the-story-of-distutils-build-directory-in-gentoo/",
"sig": "847029ef7319e917c69f4b70ff6219532a1744cbbd1c1d094af881c41874ecad2e235325a40ee5697f5c68f289a45fdf6e1ae2748264a94c9ee2b7c3b8144ab9"
}