On 2025-11-06 08:10:44 -0800 (-0800), Clark Boylan wrote: [...]
It is a defacto standard today, but OpenStack predates that by some time. And note it is not *the* standard which lives in the python standard lib. I don't want to argue the merits of using pytest from a stability and ease of use standpoint, but I do think it is worth noting that a generally accepted practice is that when you work within an existing code base you should work within the frameworks that it has already established whether that be code formatting or library/tool choice. There is value is asking "why are things done this way?" before we unilaterally blaze ahead and make a different decision. It is possible that we may still decide to change things, but that should be done with an understanding of the existing choices (at least as much as possible). [...]
This is the point where I would typically refer to the principle of (G.K.) Chesterton's Fence:
The more modern type of reformer goes gaily up to it and says, "I don't see the use of this; let us clear it away." To which the more intelligent type of reformer will do well to answer: "If you don't see the use of it, I certainly won't let you clear it away. Go away and think. Then, when you can come back and tell me that you do see the use of it, I may allow you to destroy it."
I'll also note that "modernization" on its own is a hollow goal. What's modern today will be outdated tomorrow, so that's chasing a prize you can never win. Our collective time is far better spent investing in improvements the solutions we have than replacing them with those that bring their own new and yet-unknown problems. -- Jeremy Stanley