• esc@piefed.social
    link
    fedilink
    English
    arrow-up
    0
    arrow-down
    1
    ·
    2 months ago

    Please, you’ve wasted a lot of time writing the article without bothering to read documentation (it’s mentioned in both python guide and on the hatchling page), which takes one click and like three paragraphs down, and uv_build requires to use uv and not everyone likes it or wants to use it. Anyway reading documentation is far more important for beginners than automagical tools that supposedly solve all the problems in the world.

    • dan_p_the_dev@lemmy.worldOP
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      Please, you’ve wasted a lot of time writing the article without bothering to read documentation

      ? I linked directly to the documentation I read, and that’s how I wound up using hatch in the first place. Did you read my article…? Reading the official Python documentation is what led to me uploading my .jj folder and a gitignored .env file to PyPI and writing this post. And writing the post was not a waste of time.

      uv_build requires to use uv and not everyone likes it or wants to use it

      That’s fine. I’m sure there are other build backends that work similarly to uv_build and only grab what’s needed to distribute your library. The point isn’t that everyone needs to use uv_build, the point is that hatch has surprising and imo dangerous default behavior.

      • esc@piefed.social
        link
        fedilink
        English
        arrow-up
        0
        arrow-down
        1
        ·
        2 months ago

        You see, I’ve actually read your article, you even linked to the hatchling site yourself. It takes little effort. Demonstration