You must log in or register to comment.
There should be one-- and preferably only one --obvious way to do it.
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)
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.
-
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
It’s not me you disagree with. It’s PEP 20 - The Zen of Python
What a bunch of nonsense.
How many requirements related libraries are there?!
A standard or package which encourages plugins, but writing a plugin is bad?!
… weird. I don’t understand how you can argue that with a straight face
Maturin got top 5! Way to go Rust! 🎉
