• logging_strict
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    2 months ago

    There are very few one package to rule them all in Python. There are always various similar yet different packages.

    Gotta breakdown what you are trying to accomplish. And find packages that do only that. Packages which combine many things into one, might lead to not understanding how it’s doing what it’s doing.

    desired build backend features

    • supports build plugins

    • bypasses the pip limitation of not being able to pass build configs options thru to the build backend subprocess

    deal breaker (bad) in a build backend:

    • deals with requirements

    • written in a coding another language you are not familiar with (Rust or node or Go)

    • wewbull@feddit.uk
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 months ago

      Sure, but the Zen isn’t saying there must be only one. Just that to get stuff done the first trial shouldn’t be evaluate 20 different ways. There should be an obvious choice, with alternatives for the corner cases.

      Packaging is so fundamental to a project that you almost need to choose what you’re doing before a single line of code is written.

      • logging_strict
        link
        fedilink
        arrow-up
        1
        ·
        2 months ago

        Packaging seems to be a separate skill. Separate from coding. Lots of people are good at coding. Then hit the packaging roadblock.

        Can step in and white knight, but too many projects are like that.