Working Notes: a commonplace notebook for recording & exploring ideas.
Home. Site Map. Subscribe. More at expLog.

Pyproject

• Documented here

• The build backend takes a source tree and builds a source/built distribution from it; the build is delegated by a frontend like pip

• Build backend docs

  • uv
  • tooling handbook

• PEP 517

  • is the actual definition
  • terms
    • sdist, source distribution: static snapshot of a particular release
    • build frontend: take arbitrary source trees/dists and buids wheels, eg. pip
    • integration frontend: builds multiple sdists, eg. pip
  • build-backend is a string naming a python object to perform the build
    • module:object syntax
    • does not look in the source tree for the build backend
    • can specify a backend-path when the build backend is in the source tree
    • requirements:
      • dag of requirements, with no cycles
      • should use wheels when available, may skip
      • should check for cycles
    • interface: must provide hooks
      • build_wheel(dir, config, metadata): build a .whl and put it in the directory; should return the basename of the .whl file
      • build_sdist(dir, config): build a .tar.gz source distribution
    • interface: optional hooks
      • get_requires_for_build_wheel(config_settings)
      • prepare_metadata_for_build_wheel(metadata_dir, config_settings)
      • get_requires_for_build_sdist(config_settings)

• I suspect it should be very possible to use BUCK as a build backend

— Kunal