Skip to content

Validate packaging configuration: uv build vs. hatch build #792

Closed

Description

@amotl

Sorry to nitpick further here, but I'm a bit confused about this change:

Using uv build creates a wheel package without any code. (8200dfe)

Isn't this an indication that there's something wrong with the pyproject.toml definition? uv build acts as a build frontend, using the build backend defined in [build-system]. So uv build should actually install & use hatch itself.

Originally posted by @mfussenegger in #786 (comment)

Activity

  1. amotl commented on Mar 4, 2026

    @amotl
    ContributorAuthor

    Thank you for bringing this up.

    Isn't this an indication that there's something wrong [...]

    Absolutely. I was equally confused, but it happened like described on my machine (uv 0.9.18, Hatch 1.16.2): The source package tarball was populated properly, but the wheel package included no code just package metadata. Let's try it again, possibly investigate why that happens, and report about it properly, or fix the Hatch configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions