So… what is a good example of a consensus driven culture on something popular with a lot of opinions, some legacy use cases, that can get these things done quickly?
This is a systems problem. Successful examples wanted.
This is a systems problem. Successful examples wanted.
https://www.postgresql.org/community/ is a good start to get a feel of all things related to Postgres community.
PEP 751 isn’t a python feature, it’s a feature that will be implemented by 3 projects - PDM, pip and uv. Consensus isn’t optional or nice to have, it’s necessary. If any of the 3 maintainers felt their needs weren’t met they wouldn’t have implemented it.
Some projects wait too long for consensus because they prioritise not rushing into a suboptimal solution or hurting people’s feelings. Sometimes it’s ok to just go ahead and implement something. Pep 751 is not one of those projects.
It's not so much a feature as a standard. And other tools will use it as well. I'm working on one of them. PEP 751 means I don't have to design the thing myself, and I can potentially share data with the tools you mentioned.
I’m pointing out that if they didn’t have your buy-in, the work would be dead on arrival.
Unlike a python feature like let’s say, typing - there’s no way it can be pushed through without 100% consensus.