How to specify --python-tag with Hatch?

[facelessuser]

I assume this is something the build backend would support. I have a project that builds Unicode tables that match the Python version it is being installed on. So, when releasing, I build a python package for each supported Python version. They are all pure Python wheels, but each one contains a set of Unicode tables that matches the given Python distribution.

With setup tools, all I did was:

$ python3 setup.py bdist_wheel --python-tag py39

Using build, it is a little more awkward, but doable:

$ python3 -m build -w -C="--global-option=--python-tag" -C="--global-option=py310"

It seems that if you try this with a project that uses a Hatch backend, this doesn't work. I imagine this is because the backend would need to support such input. Does Hatch support this already, and I just haven't found where yet? If not, is it something that could be added?

[ofek]

https://ofek.dev/hatch/dev/plugins/builder/#build-data

[facelessuser]

Man, I was searching everywhere to try and find that 🙂.

So you just use a hook to populate it in metadata['tag']? This is a little unclear to me.

[ofek]

Examples:

• https://github.com/ofek/hatch/blob/7d1698c81f644e1c9aa257c262f8304da58c0f3f/tests/backend/builders/test_wheel.py#L622
• https://github.com/ofek/hatch-mypyc/blob/6009aee845e7daa76bcebdde60d9a59811e87c43/hatch_mypyc/plugin.py#L307-L310

[facelessuser]

Got it, I'll try this out later today.

[facelessuser]

Worked great!

[xalbertoisorna]

Do you have a pyproject.toml example of this? the link does not seem to work anymore

[taybenlor]

I got here when I was trying to figure out how to set infer_tag and pure_python from my pyproject.toml.

The way to do this is to create a custom hook called hatch_build.py that looks like this:

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

class CustomHook(BuildHookInterface):
    def initialize(self, version, build_data):
        build_data["infer_tag"] = True
        build_data["pure_pyton"] = False

And then in your pyproject.toml set the following option:

[tool.hatch.build.targets.wheel.hooks.custom]
path = "hatch_build.py"

This was extremely non-obvious but resulted in hatch building a platform specific wheel when run from cibuildwheel, which is what I wanted.

Hopefully this helps a future traveller!