How to create two wheels with different artifacts?

[freddyaboulton]

Hello!

I am one of the maintainers of gradio (https://github.com/gradio-app/gradio). We build and publish a wheel that has some artifacts specified under [tool.hatch.build]. We also publish a version of our package called gradio-lite that's meant to run in the browser. Our issue is that gradio-lite has the same artifacts as gradio but some of these artifacts are not needed for gradio-lite. So the wheel size for lite is bigger than it needs to be and so the start-up time in the browser is slower.

So my question is, how can I specify a different set of artifacts for lite? Something like hatch build -t lite would be ideal but not sure how to specify a custom build target.

Thanks for the help.

[freddyaboulton]

I think I figured it out using the built in custom builder.

This is the builder implementation

from hatchling.builders.wheel import WheelBuilder

def get_builder():
    return LiteBuilder

class LiteBuilder(WheelBuilder):
    PLUGIN_NAME = 'lite'
    

These are the modifications to the toml:

[tool.hatch.build.targets.custom]
artifacts = ["gradio/templates", "*.pyi", "!/gradio/test_data", "!/gradio/_frontend_code", "!/gradio/node"]
path = ".config/lite_builder.py"

Then I build with hatch build -t custom

Final question - how do I rename the builder to be lite instead of custom

[ofek]

Unless you make your builder a dedicated third-party package I think there is no way currently to use the name that you supply.

I'm very happy to hear that the custom plugin is useful to you so far!

[freddyaboulton]

I made it a local third party package. I just converted the custom build script into a python package and then specified it as a dependency of my custom target

[tool.hatch.build.targets.lite]
artifacts = ["gradio/templates", "*.pyi", "!/gradio/test_data", "!/gradio/_frontend_code", "!/gradio/node"]
path = ".config/lite_builder.py"
directory = "dist-lite"
dependencies = ["lite-builder @ {root:uri}/../.config/lite-builder"]

Being able to use the built-in custom builder but with a different name would be a lot better! I hope that gets added as a feature to hatch.

[ofek]

Oh if you redefine the version methods you can probably do hatch build -t custom:lite:

• https://hatch.pypa.io/latest/plugins/builder/reference/#hatchling.builders.plugin.interface.BuilderInterface.get_version_api
• https://github.com/pypa/hatch/blob/hatchling-v1.22.4/backend/src/hatchling/builders/wheel.py#L391-L392

[freddyaboulton]

Neat! Thank you