How to implement hooks "scope"?

[Batalex]

Hi,

Is there a way to implement some "scope" for build hooks similar to test fixtures?

I am running hatch 1.4.0.

Context

I use hatch to build a "dataset package" (meaning a python library with very few lines of codes but including heavy binary artifacts).
I would like to improve the following workflow:

• I have a build script (e.g. build.py) that downloads & merges files from multiple sources into a single binary resource.
• I configured my linters and docs envs to skip-install. So far so good running the CI.
• I import the build function in hatch_build.py in the initialize() method of the custom hook.
• To install the project in editable mode in the default env without running the build script (for running unit tests), I wrap the build function in a version != "editable" condition.

# hatch_build.py
from build import build_dataset

from hatchling.builders.hooks.plugin.interface import BuildHookInterface

class CustomBuildHook(BuildHookInterface):
    def initialize(self, version, build_data):
        super().initialize(version, build_data)
        if version != "editable":
                build_dataset()

This is where things get messy.
I would like the custom hook to run the actual build function only once per CLI use and only if needed.
I can easily implement the clean method to remove artifacts and a custom "skip-if-exists" configuration key with the setup above. However, the removal and artifact creation would still happen twice with the hatch build -c command (building tarball and wheel).

My question boils down to this: what would be the best way to run a hook only once or share information between runs?

[ofek]

Do you want it just for one target like wheel? https://hatch.pypa.io/latest/config/build/#build-hooks

or maybe Hatch could populate an env var with a unique value per build invocation?

[Batalex]

Do you want it just for one target like wheel?

Ideally, I want it for each hatch build command invocation (hence the parallel with test fixtures scope).

With the following pyproject.toml

# ...
[tool.hatch.build]
artifacts = ["binary_file.dat"]

[tool.hatch.build.targets.sdist]
[tool.hatch.build.targets.wheel]

[tool.hatch.build.hooks.custom]
# ...

• hatch build -c would run the hook once and build both sdist and wheel files with the same binary_file.dat.
• hatch build -c -t wheel would run the hook
• hatch build -c -t sdist would also run the hook

Thanks for the quick reply!