But you would not use that password on a real install, right? Neither do i, and many others will chose a strong password.
Before, even empty password was allowed, but not anymore, as many things failed to work properly due to that. To enforce passwords to meet some parameters, it means that all that do VBox installs or whatever virtualization software, for quick testing purposes, will have to type sane passwords all the time, instead of just a very simple one, for convenience.
What requirements should password have?
Contain both upper- and lowercase characters (e.g., a–z, A–Z).
Have digits, punctuation characters, and letters (e.g., 0–9! @#$%^&*()_+|˜-=’{}[]:”;’<>?,./).
Are at least eight alphanumeric characters long, but twenty is safer …
Not a word in any language, slang, dialect, jargon, etc.
Are not based on personal information, names of family, etc.
So, there would have to be also some sort of a password-validator, with a messages for each failure of the password not meeting those requirements.
In case of libpwquality probably those going by generating random passwords with good pronounceability will fail, in few days, to remember that password. Then what? Password hint?
Then it begs the question, to be even safer than that, what is next:
Set a minimum password age?
Do not use the same password for root and make sure that option is not available?
Make sure the users will not write their passwords down on paper and store them anywhere in their office, phone, other devices?
Many users are barely persuaded to read the wiki when we point them to it, and many, for convenience, will use a simple password