PEP 517 build system popularity (labs.quansight.org)

submitted 1 week ago by milliams@lemmy.world to c/python@programming.dev

10 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] wewbull@feddit.uk 4 points 1 week ago

There should be one-- and preferably only one --obvious way to do it.

[-] logging_strict@programming.dev 1 points 1 week ago

Disagree with you.

Isn't the entire point of Python adding support for roll your own build backend, so we can have many different build backends?

btw i wrote my own

[-] wewbull@feddit.uk 5 points 1 week ago

It's not me you disagree with. It's PEP 20 - The Zen of Python

[-] logging_strict@programming.dev 1 points 1 week ago

There already exists multiple build backends. So adding one more can't be violating some rule.

Are there gatekeepers who say it's ok for them but not for anyone else? Do i have to bribe them to be in the in crowd? Am i lower class or an outcast?

This reminds me of proof of stake (1998) with it's master nodes. Which are nodes run by elites where pleb nodes are lessor.

bitcoin (2009) solved that

[-] logging_strict@programming.dev 1 points 1 week ago* (last edited 1 week 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 1 points 5 days 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.