That’s fair. But how do we determine consensus except by proposing something and then looking at the responses? That’s not intended as a rhetorical question - if there’s a better way of getting a feel for how many people support an idea, it would be worth knowing about it.
To be honest, though, the number of people supporting or objecting to a proposal isn’t the most important matter. What’s more important is the arguments presented on each side. I should probably not have framed my comment in terms of numbers, that’s my error. What I was really trying to say is that it’s not correct to characterise the discussion here as “we have to have this and it is wrong to say otherwise” - the reality is simply that the arguments against haven’t persuaded people to change their mind.
IMO, anyone’s view can be challenged, but conversely no-one can assume their views must be accepted. And personally, I prefer concrete arguments referring to actual benefits and use cases over more abstract arguments of principle. Which is not what I’ve seen presented here. And frankly, the “this isn’t the business of the stdlib” argument is particularly weak given that so many other modules have command line interfaces. I’m not claiming that “we’ve done it before” is a sufficient argument on its own, but it is enough to undermine claims that “we shouldn’t do this because it’s not a direction we want to go in”…